Custom Query (1451 matches)

smartctl -i does not give WWN for SATA disks; still, this value seem to exists, since udev can create it:

START OF INFORMATION SECTION

Model Family: Western Digital Caviar Green family Device Model: WDC WD10EADS-00L5B1 Serial Number: WD-WCAU45613240 Firmware Version: 01.01A01 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed May 28 15:10:00 2014 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled

# ls -l /dev/disk/by-id/ | grep sda | grep -v part lrwxrwxrwx 1 root root 9 2014-05-28 15:04 ata-WDC_WD10EADS-00L5B1_WD-WCAU45613240 -> ../../sda lrwxrwxrwx 1 root root 9 2014-05-28 15:04 scsi-SATA_WDC_WD10EADS-00_WD-WCAU45613240 -> ../../sda lrwxrwxrwx 1 root root 9 2014-05-28 15:04 wwn-0x50014ee257ac47cd -> ../../sda

Some details can be found here: ​http://stackoverflow.com/questions/21977311/obtaining-wwn-of-sata-disks

scsiprint.cpp pout("SMART Health Status: OK\n");

should be changed to: pout("SMART overall-health self-assessment test result: PASSED\n");

It allows to parse output for different devices in the same way.

Hi,

I'm forwarding a bug reported by a Debian user.

smartctl can be used to execute a test on a drive already running another test. In my case, I ran a short test on a drive already running a long test. I was not aware that SMART could only handle 1 test at a time. Apparently, SMART can't resume aborted tests.

smartctl's behavior in this case seems to be to execute the newly requested test without caring about the already one. The worst problem with this is loss of time, as in my scenario. I see two options: running the newly requested test after the currently running one is finished, or prompt for what to do.