SMART Status Query
A message that is not in the archive (sent off-list or not yet received): [email protected]
(Cc'd LSML in case I write nonsense)
Quoted 18 lines · Sean Bruno
Out of curiosity, I tried to query the smart status from disks in a FW400 enclosure. I was prompted that the drives do not support SMART.
The Seagates in the enclosure do indeed support SMART and I suppose that there is a missing bit in the firewire stack or in my enclosure that would allow these commands to be passed down to the disks.
Does this situation have a resolution? Is there a way around it?
I do find it interesting, that the the actual disk information is returned and not the "spoofed" enclosure disk names.
I tried "smartctl -a
/dev/sdd" and was presented with:
[sean@home-desk ~]$ sudo smartctl -a/dev/sdc
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Quoted 8 lines
Device: ST380811 AS Version: 3.AA
Serial number: 5PS13NWB
Device type: disk
Local Time is: Mon Feb 2 22:36:07 2009 PST
Device does not support SMARTError Counter logging not supported
Device does not support Self Test logging
AFAIK SMART requires "ATA pass-through", i.e. the tunneling of ATA commands through SCSI.
The FireWire drivers happily send any command to the target which the Linux kernel or an application emits. The missing piece here is ATA pass-through support in the firmware of the FireWire-to-SATA bridge chip of the drive enclosure.
I have not yet heard of FireWire-to-SATA bridges which do support ATA pass-through.
Signature · 3 lines
Stefan Richter -=====-==--= --=- ---== http://arcgraph.de/sr/
Quoted 33 lines · Stefan Richter
(Cc'd LSML in case I write nonsense)
Quoted 18 lines · Sean Bruno
Out of curiosity, I tried to query the smart status from disks in a FW400 enclosure. I was prompted that the drives do not support SMART.
The Seagates in the enclosure do indeed support SMART and I suppose that there is a missing bit in the firewire stack or in my enclosure that would allow these commands to be passed down to the disks.
Does this situation have a resolution? Is there a way around it?
I do find it interesting, that the the actual disk information is returned and not the "spoofed" enclosure disk names.
I tried "smartctl -a
/dev/sdd" and was presented with:
[sean@home-desk ~]$ sudo smartctl -a/dev/sdc
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/Quoted 8 lines
Device: ST380811 AS Version: 3.AA
Serial number: 5PS13NWB
Device type: disk
Local Time is: Mon Feb 2 22:36:07 2009 PST
Device does not support SMARTError Counter logging not supported
Device does not support Self Test loggingAFAIK SMART requires "ATA pass-through", i.e. the tunneling of ATA commands through SCSI.
Quoted 7 lines
The FireWire drivers happily send any command to the target which the Linux kernel or an application emits. The missing piece here is ATA pass-through support in the firmware of the FireWire-to-SATA bridge chip of the drive enclosure.
I have not yet heard of FireWire-to-SATA bridges which do support ATA pass-through.
That makes sense, unfortunate, but not unexpected.
Can you tell me how my system is getting the Seagate drive information then? I've looked over the data available to me on the Firewire bus, and don't see where it's being pulled from.
Sean
Quoted 25 lines · Sean Bruno
Quoted 24 lines · Stefan Richter
Quoted 6 lines · Sean Bruno
I tried "smartctl -a
/dev/sdd" and was presented with:
[sean@home-desk ~]$ sudo smartctl -a/dev/sdc
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/Quoted 8 lines
Device: ST380811 AS Version: 3.AA
Serial number: 5PS13NWB
Device type: disk
Local Time is: Mon Feb 2 22:36:07 2009 PST Device does not support SMARTError Counter logging not supported Device does not support Self Test logging
AFAIK SMART requires "ATA pass-through", i.e. the tunneling of ATA commands through SCSI.
The FireWire drivers happily send any command to the target which the Linux kernel or an application emits. The missing piece here is ATA pass-through support in the firmware of the FireWire-to-SATA bridge chip of the drive enclosure.
Quoted 8 lines
Quoted 2 lines
I have not yet heard of FireWire-to-SATA bridges which do support ATA pass-through.
That makes sense, unfortunate, but not unexpected.
Can you tell me how my system is getting the Seagate drive information then? I've looked over the data available to me on the Firewire bus, and don't see where it's being pulled from.
According to a quick look at the smartmontools source, these data come from the SCSI INQUIRY command.
FireWire firmwares insert all sorts of data into their INQUIRY responses. Sometimes the response is hardcoded by the firmware author, sometimes it is built from data which were transparently obtained from the attached SATA disk --- like with your Seagate disk.
Signature · 3 lines
Stefan Richter -=====-==--= --=- ---== http://arcgraph.de/sr/