Hello, and sorry for replying so late... I've been busy with lots of other things.
20.12.2009 11:44, Oliver Lehmann wrote: > 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. I don't know - if my backup server could use eSATA I would use that anyway. I'm pretty sure, though, that the eSATA interface would connect to the disk directly, bypassing any USB interface, as that should be simpler and thus cheaper than the other way. Arno -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
