Custom Query (1386 matches)
Results (250 - 252 of 1386)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #263 | invalid | Drive does not support SMART, but health check shows 'Ok' | ||
| Description |
Why would smartctl show the SMART Health status as 'ok' when the device does not support SMART ? Below is output of the commands. smartctl -H /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-w64-mingw32-2003r2-sp2] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org SMART Health Status: OK smartctl -a /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-w64-mingw32-2003r2-sp2] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org Vendor: PERC Product: LD 0 PERCRAID Revision: User Capacity: 36,364,615,680 bytes [36.3 GB] Logical block size: 512 bytes Serial number: 021400000000 Device type: disk Local Time is: Tue Mar 12 00:33:22 2013 CDT Device does not support SMART Error Counter logging not supported Device does not support Self Test logging smartctl -i /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-w64-mingw32-2003r2-sp2] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org Vendor: PERC Product: LD 0 PERCRAID Revision: User Capacity: 36,364,615,680 bytes [36.3 GB] Logical block size: 512 bytes Serial number: 021400000000 Device type: disk Local Time is: Tue Mar 12 00:33:22 2013 CDT Device does not support SMART smartctl -s on -d scsi /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-w64-mingw32-2003r2-sp2] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org unable to fetch IEC (SMART) mode page [Input/output error] A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. smartctl -d test /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-w64-mingw32-2003r2-sp2] (sf-6.0-1) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sda: Device of type 'scsi' [SCSI] detected /dev/sda: Device of type 'scsi' [SCSI] opened |
|||
| #264 | duplicate | Support for Serial Attached SCSI Drives | ||
| Description |
Is log page dump supported to Serial Attached SCSI Drives? How do we issue CDB commands for log pages? PAGE CODE=01: Buffer Over-Run/Under-Run Log Page PAGE CODE=02: Write Error Counter log page PAGE CODE=03: Read Error Counter log page PAGE CODE=05: Verify Error Counter log page PAGE CODE=06: Non Medium Error Counter log page PAGE CODE=0D: Temperature log page PAGE CODE=0E: Start-Stop Cycle Counter log page PAGE CODE=0F: Application client log page PAGE CODE=10: Self-Test Results log page PAGE CODE=15: Background Scan Results log page PAGE CODE=18: : Protocol Specific Port log page PAGE CODE=1A: Power Condition Transition log page PAGE CODE=2F: SMART Status log page PAGE CODE=38: SMART Data log page E6: DUMP SMART |
|||
| #265 | invalid | Support for Serial Attached SCSI Drives | ||
| Description |
Is log page dump supported to Serial Attached SCSI Drives? How do we issue CDB commands for log pages? PAGE CODE=01: Buffer Over-Run/Under-Run Log Page PAGE CODE=02: Write Error Counter log page PAGE CODE=03: Read Error Counter log page PAGE CODE=05: Verify Error Counter log page PAGE CODE=06: Non Medium Error Counter log page PAGE CODE=0D: Temperature log page PAGE CODE=0E: Start-Stop Cycle Counter log page PAGE CODE=0F: Application client log page PAGE CODE=10: Self-Test Results log page PAGE CODE=15: Background Scan Results log page PAGE CODE=18: : Protocol Specific Port log page PAGE CODE=1A: Power Condition Transition log page PAGE CODE=2F: SMART Status log page PAGE CODE=38: SMART Data log page E6: DUMP SMART |
|||
