 | | | Subject: Bad Sectors on a SATA Drive | Subject: Bad Sectors on a SATA Drive 2007-01-19 - By Lawrence Houston
Back
Tom:
On Fri, 19 Jan 2007, Tom G. Christensen wrote:
> Lawrence Houston wrote:
>>
>> On Thu, 18 Jan 2007, John Haxby wrote:
>>
>>> Lawrence Houston wrote:
>>>> Question 2: Is there any way to have RHEL3 complete a Surface Scan while
>>>> it is still running in the Networked Multi-User Mode (I am
>>>> located 100 Miles away)? I ask since dropping into Single
>>>> User Mode and Remounting in Read-ONLY Mode to run Utilities
>>>> from the Command-Line on the Console is NOT something the
>>>> less
>>>> experienced computer users are willing to do on their own!
>>> You can run badblocks read-only without bringing the system down -- I did
>>> it this morning on a disk I was suspicious of that doesn't support SMART.
>>> Well, the disk does, but the USB enclosure doesn't so I'm planning to put
>>> it in a machine and see what smartctl has to say. It'll probably say
>>> it's not well :-(
>>
>> Running a SMARTCTL Query reports the Device does NOT support SMART??
>>
>> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---
>> [root]# /usr/sbin/smartctl -i /dev/sda
>> smartctl version 5.1-11 Copyright (C) 2002-3 Bruce Allen
>> Home page is http://smartmontools.sourceforge.net/
>>
>> Device: ATA ST3160023AS Version: 8.12
>> Serial number: 5MT0MLQB
>> Device type: disk
>> Local Time is: Thu Jan 18 14:20:49 2007 EST
>> Device does not support SMART [bad value in scsi command]
>> -- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
>>
>> The 160 GIG Seagate is accessed via SCSI Emulation (not sure if that is a
>> SATA, RHEL3 or DELL "Thing"?), should that affect whether a SATA Disk can
>> return SMART Inforation???
>>
> It's not accessed via SCSI Emulation according to dmesg.
> It's a SATA drive and claimed by libata which exports devices as SCSI
> devices. However smartctl needs to know that it's accessing a libata device
> to work correctly.
>
> Try this instead:
> # smartctl -d ata -i /dev/sda
Yes adding the libata paramater was the answer, thanks...
Is a SATA Drive being claimed by libata and being exported as a SCSI
Device a good thing or a bad thing??
Can someone with more experience reading SMART Data tell me the state of
this 160 GIG Seagate Drive??? It does NOT look very good, how immediate
does this "Pre-Fail" mean???
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
[root]# /usr/sbin/smartctl -d ata -a /dev/sda | more
smartctl version 5.1-11 Copyright (C) 2002-3 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST3160023AS
Serial Number: 5MT0MLQB
Firmware Version: 8.12
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 (See http://API-6.ora-code.com) T13 1410D revision 2
Local Time is: Fri Jan 19 09:50:48 2007 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Off-line data collection status: (0x82) Offline data collection activity
completed without error.
Auto Off-line Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete off-line
data collection: ( 430) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Automatic timer ON/OFF support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 94) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE WHEN_FAILED
RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 065 052 006 Pre-fail -
119980341
3 Spin_Up_Time 0x0003 097 097 000 Pre-fail - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age - 23
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail - 0
7 Seek_Error_Rate 0x000f 080 060 030 Pre-fail -
112315953
9 Power_On_Hours 0x0032 086 086 000 Old_age -
12597
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age - 23
194 Temperature_Celsius 0x0022 038 045 000 Old_age - 38
(Lifetime Min/Max 0/16)
195 Hardware_ECC_Recovered 0x001a 065 052 000 Old_age -
119980341
197 Current_Pending_Sector 0x0012 100 100 000 Old_age - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age - 0
202 Unknown_Attribute 0x0032 100 253 000 Old_age - 0
SMART Error Log Version: 1
ATA Error Count: 85 (device log contains only the most recent five errors)
DCR = Device Control Register
FR = Features Register
SC = Sector Count Register
SN = Sector Number Register
CL = Cylinder Low Register
CH = Cylinder High Register
D/H = Device/Head Register
CR = Content written to Command Register
ER = Error register
STA = Status register
Timestamp is seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.
Error 85 occurred at disk power-on lifetime: 12533 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:00 SN:90 CL:af CH:18 D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 08 90 af 18 e0 25 17007.104
00 00 08 90 af 18 e0 25 17003.319
00 00 08 90 af 18 e0 25 17101.186
00 00 08 90 af 18 e0 25 17097.357
00 00 08 90 af 18 e0 25 17093.580
Error 84 occurred at disk power-on lifetime: 12533 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:00 SN:90 CL:af CH:18 D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 08 90 af 18 e0 25 17007.104
00 00 08 90 af 18 e0 25 17003.319
00 00 08 90 af 18 e0 25 16999.524
00 00 08 90 af 18 e0 25 17097.357
00 00 08 80 af 18 e0 35 17093.580
Error 83 occurred at disk power-on lifetime: 12533 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:00 SN:90 CL:af CH:18 D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 08 90 af 18 e0 25 17007.104
00 00 08 90 af 18 e0 25 17003.319
00 00 08 90 af 18 e0 25 16999.524
00 00 08 80 af 18 e0 35 16995.741
00 00 08 88 af 18 e0 25 17093.580
Error 82 occurred at disk power-on lifetime: 12533 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:00 SN:90 CL:af CH:18 D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 08 90 af 18 e0 25 17007.104
00 00 08 90 af 18 e0 25 17003.319
00 00 08 80 af 18 e0 35 16999.524
00 00 08 88 af 18 e0 25 16995.741
00 00 08 88 af 18 e0 25 80.772
Error 81 occurred at disk power-on lifetime: 12533 hours
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER:40 SC:00 SN:90 CL:af CH:18 D/H:e0 ST:51
Sequence of commands leading to the command that caused the error were:
DCR FR SC SN CL CH D/H CR Timestamp
00 00 08 90 af 18 e0 25 17007.104
00 00 08 80 af 18 e0 35 17003.319
00 00 08 88 af 18 e0 25 16999.524
00 00 08 88 af 18 e0 25 16995.741
00 00 08 88 af 18 e0 25 80.772
SMART Self-test log, version number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Short captive Completed 00% 5167 -
# 2 Short off-line Completed 00% 2 -
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Lawrence Houston -- (houston@(protected))
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|