Arno Lehmann wrote: > This happens, as far as I can see, only with external drives (USB in > your and other cases, FireWire here), so I attribute it to imperfect > external disk controller chips or USB / FireWire stacks. Whenever I > saw those sort of errors on internal disks, I either get log messages > or can identify faulty disk drives using smartctl. For external disks, > this usually doesn't work. :-(
Do you know if this will also happen with eSATA? There are several external cases with eSATA+USB-2.0 ports. I could grab those if this will help but I'm not sure if the eSATA connection is also wrapped through the controller chip of if it is attached directly to the SATA port of the harddisk. -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
