Greg Lopp on 10 Jul 2006 18:25:28 -0000 |
Jeff Abrahamson wrote: On Mon, Jul 10, 2006 at 09:31:11AM -0400, Flint Heart wrote:But your system(where you'd be running smartd) doesn't know that and doesn't care. The only thing that it knows is that it talks to it via SCSI. This would be the case both for firewire and USB drives. So, what is the equivalent of smartd for SCSI drives?......no, wait, the smartd manpage indicates that it does work with SCSI. It also says that it uses a drive's internal "Self-Monitoring, Analysis and Reporting Technology (SMART)". Could be that your enclosure, which translates the firewire encapsulated SCSI commands to IDE, does not support the set of SCSI commands required to invoke the SMART. Not sure about firewire, but I know that on the USB world, a drive is not required to support more than about five commands. Those five are enough to report its capacity, indicate that it's ready (spun up), read and write. I would not be surprised if firewire requires the same SCSI subset as USB. I'd recommend making contact with the firewire maintainers. They may have more experience with your enclosure and/or issues with Maxtor. The problem could be on the protocol level with your enclosure - your input could result in a more robust firewire drive driver. ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|