DriveReady SeekComplete Error

Hi,

Is this drive fubar? It's installed brand-new, and after only three days of operating it's giving me these errors from time to time.

May 30 07:08:18 web3 kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
May 30 07:08:18 web3 kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=227270012, sector=227270007
May 30 07:08:18 web3 kernel: end_request: I/O error, dev hda, sector

227270007

I could find some other people on the net with these problems, but none of them happened with brandnew drives.

What can I do?

Rick Jansen

Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Seems so, try getting the SMART utils and have a look at the output of smartctl -a <device>.

However I fail to see why this l-k related and as such offtopic here.

Servus,
Daniel

Quote from Daniel Egger <[email protected]>:

1. I see no particular evidence to suggest that the drive is necessarily faulty.
2. It is on topic because it may well be a coding error in the kernel.

John.

Quote from Rick Jansen <[email protected]>:

Please post more information. First, what size is the disk?

The LBAsect number suggests an access around 108 Gb. If the disk is smaller than this, then it would appear that a request was made for a non-existant sector.

Is the LBAsect number the same in each error? What is the machine doing when the errors occur?

John.

Here's some more information about the disk from the boot log. I also found some StatusErrors in there.

May 10 11:14:07 web3 kernel: hda: Maxtor 6Y120P0, ATA DISK drive
May 10 11:14:07 web3 kernel: hda: max request size: 128KiB
May 10 11:14:07 web3 kernel: hda: 240121728 sectors (122942 MB)
w/7936KiB Cache, CHS=65535/16/63, UDMA(133)
May 10 11:14:07 web3 kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
May 10 11:14:07 web3 kernel: hda: task_no_data_intr: status=0x51 {
DriveReady SeekComplete Error }
May 10 11:14:07 web3 kernel: hda: task_no_data_intr: error=0x04 {
DriveStatusError }
May 10 11:14:07 web3 kernel: hda: Write Cache FAILED Flushing!

Thats a different error then what it gives me occasionaly. Googling this error lead me to believe this is a bug in the ide driver, that my disk doesnt support some flush command.

After parsing the log with simple script, these sectors seem to give the errors:

227270012
227270483
236708724
237757036
237757472
238018530
238020393
238279554
238804853
239066426
239328347
239590823
240116567
240121662
58619113
58619120
58619127
58619447
58619448
58619519
58620045
58620048
58620331

I've tried to reproduce these errors by rsyncing the whole filesystem, executing various find / commands, but nothing triggered them. The machine is primarily a web server, so my guess is they happen when apache tries to do something to the disk.

The output from smartctl -a seems a bit large to include in this email.

Rick Jansen

Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

It is, what kernel are you using?

Jens Axboe

This is 2.6.6.

Rick Jansen

Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

(don't trim people from the cc list, thanks)

The that's a known error, you should not worry about it. It's fixed in later kernels.

Jens Axboe

Hi,

In article <[email protected]>,

I'm seeing this error too, and also frequent crashes (total lock ups) of the machine (every day or two at the moment). Could the two be related?

I haven't got round to doing any diagnostics yet, but there's nothing obvious in the logs. I was going to dismantle the machine and check connections etc. first.

Andy

This is usually also a bad sign, escpecially if the size is caused by the Error Log Structure areas.

Please send the info of smartctl -v <device>. This should give a good indication of whether this is a kernel or a drive problem because it will show some of the internal status of the drive.

Servus,
Daniel

I don't think -v is the option you mean:

smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/

=======> INVALID ARGUMENT TO -v: /dev/hda <======= =======> VALID ARGUMENTS ARE:

	help
	9,halfminutes
	9,minutes
	9,seconds
	9,temp
	192,emergencyretractcyclect
	193,loadunload
	194,10xCelsius
	194,unknown
	198,offlinescanuncsectorct
	200,writeerrorcount
	201,detectedtacount
	220,temp
	N,raw8
	N,raw16
	N,raw48

<=======

Use smartctl -h to get a usage summary

Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Send all the data.

John.

smartctl version 5.30 Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===

Device Model:     Maxtor 6Y120P0
Serial Number:    Y43XXY5E
Firmware Version: YAR41BW0
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Fri Jun  4 16:16:57 2004 CEST
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:
Offline data collection status: (0x80) Offline data collection activity was
never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 118) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 182) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection 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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 60) minutes.

SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  3 Spin_Up_Time            0x0027   252   252   063    Pre-fail  Always       -       1249
  4 Start_Stop_Count        0x0032   253   253   000    Old_age   Always       -       6
  5 Reallocated_Sector_Ct   0x0033   252   252   063    Pre-fail  Always       -       15
  6 Read_Channel_Margin     0x0001   253   253   100    Pre-fail  Offline      -       0
  7 Seek_Error_Rate         0x000a   253   252   000    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0027   249   244   187    Pre-fail  Always       -       41816
  9 Power_On_Minutes        0x0032   251   251   000    Old_age   Always       -       908h+44m
 10 Spin_Retry_Count        0x002b   252   252   157    Pre-fail  Always       -       0
 11 Calibration_Retry_Count 0x002b   252   252   223    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   253   253   000    Old_age   Always       -       8
192 Power-Off_Retract_Count 0x0032   253   253   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0032   253   253   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0032   253   253   000    Old_age   Always       -       38
195 Hardware_ECC_Recovered  0x000a   253   252   000    Old_age   Always       -       1632
196 Reallocated_Event_Count 0x0008   253   253   000    Old_age   Offline      -       0
197 Current_Pending_Sector  0x0008   252   252   000    Old_age   Offline      -       13
198 Offline_Uncorrectable   0x0008   252   252   000    Old_age   Offline      -       1
199 UDMA_CRC_Error_Count    0x0008   199   199   000    Old_age   Offline      -       0
200 Multi_Zone_Error_Rate   0x000a   253   252   000    Old_age   Always       -       0
201 Soft_Read_Error_Rate    0x000a   253   252   000    Old_age   Always       -       5
202 TA_Increase_Count       0x000a   253   252   000    Old_age   Always       -       0
203 Run_Out_Cancel          0x000b   253   252   180    Pre-fail  Always       -       0
204 Shock_Count_Write_Opern 0x000a   253   252   000    Old_age   Always       -       0
205 Shock_Rate_Write_Opern  0x000a   253   252   000    Old_age   Always       -       0
207 Spin_High_Current       0x002a   252   252   000    Old_age   Always       -       0
208 Spin_Buzz               0x002a   252   252   000    Old_age   Always       -       0
209 Offline_Seek_Performnce 0x0024   195   195   000    Old_age   Offline      -       0
 99 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
100 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0
101 Unknown_Attribute       0x0004   253   253   000    Old_age   Offline      -       0

SMART Error Log Version: 1
ATA Error Count: 440 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Timestamp = decimal seconds since the previous disk power-on.
Note: timestamp "wraps" after 2^32 msec = 49.710 days.

Error 440 occurred at disk power-on lifetime: 843 hours
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 77 dd 8b ed Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2045545.712  READ DMA
  ca 00 08 e8 a1 3c e0 08 2045545.680  WRITE DMA
  ca 00 08 37 41 54 e2 08 2045545.680  WRITE DMA
  ca 00 08 d0 ca 95 e0 08 2045545.680  WRITE DMA
  ca 00 70 78 a1 3c e0 08 2045545.680  WRITE DMA

Error 439 occurred at disk power-on lifetime: 843 hours
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 77 dd 8b ed Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2045544.688  READ DMA
  c8 00 40 ff 0b c7 e2 08 2045544.656  READ DMA
  c8 00 08 4f df 8b ed 08 2045543.632  READ DMA
  ca 00 08 17 0f a8 e2 08 2045543.584  WRITE DMA
  ca 00 08 ef ba 97 e2 08 2045543.584  WRITE DMA

Error 438 occurred at disk power-on lifetime: 843 hours
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 04 4f df 8b ed Error: UNC 4 sectors at LBA = 0x0d8bdf4f = 227270479

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 4f df 8b ed 08 2045543.632  READ DMA
  ca 00 08 17 0f a8 e2 08 2045543.584  WRITE DMA
  ca 00 08 ef ba 97 e2 08 2045543.584  WRITE DMA
  ca 00 10 d7 ba 97 e2 08 2045543.584  WRITE DMA
  ca 00 10 8f ba 97 e2 08 2045543.584  WRITE DMA

Error 437 occurred at disk power-on lifetime: 843 hours
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 04 4f df 8b ed Error: UNC 4 sectors at LBA = 0x0d8bdf4f = 227270479

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 4f df 8b ed 08 2045542.560  READ DMA
  c8 00 08 8f 0b c7 e2 08 2045542.560  READ DMA
  c8 00 50 af 0b c7 e2 08 2045542.560  READ DMA
  c8 00 10 9f 0b c7 e2 08 2045542.560  READ DMA
  c8 00 08 97 0b c7 e2 08 2045542.560  READ DMA

Error 436 occurred at disk power-on lifetime: 843 hours
When the command that caused the error occurred, the device was in an unknown state.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 03 77 dd 8b ed Error: UNC 3 sectors at LBA = 0x0d8bdd77 = 227270007

Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Timestamp  Command/Feature_Name
  -- -- -- -- -- -- -- --   ---------  --------------------
  c8 00 08 77 dd 8b ed 08 2043137.264  READ DMA
  c8 00 18 f7 36 7c e3 08 2043137.248  READ DMA
  c8 00 10 3f 0f 7c e3 08 2043137.248  READ DMA
  c8 00 10 57 d5 7b e3 08 2043137.248  READ DMA
  c8 00 08 37 c7 7b e3 08 2043137.232  READ DMA

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed: read failure       60%       839         0x0d8bdd7c
# 2  Short offline       Completed: read failure       60%       816         0x0d8bdd7c
# 3  Short offline       Completed: read failure       60%       805         0x0d8bdd7c

Looking for books? Try http://www.megabooksearch.com
The Linux on 64-Bit platforms Wiki: http://www.linux64.net
PGP Public Key: http://www.rockingstone.nl/rick/pubkey.asc

Hi Rick,

Some comments below.

You can use selective self-tests on this drive. You'll need smartmontools version 5.31 or greater. This will help you pin down the bad LBAs quickly.

You have some unreadable disk sectors.

This is a very useful disk feature!

Your disk has already reallocated 15 bad sectors.

There are 13 unreadable disk sectors that the OS has tried to access, and one additional unreadable disk sector found in an off-line scan.

This is a typical read that failed at LBA 227270007.

See http://smartmontools.sourceforge.net/BadBlockHowTo.txt for info on how to locate and force reallocation of the bad sectors. When you are done you should be able to run a long self-test (-t long) with no errors found. You can use selective self-tests (-t select,M-N) to help locate the bad sectors.

Bruce

DOH! Works for version 2.1 and will list all attributes as well as their values.

Servus,
Daniel

Please don't trim the CC list.

Quote from Rick Jansen <[email protected]>:

The lower ones are definitely within the capacity of the drive. I suspect it _may_ genuinuely be faulty after all.

Back up your data.

If practical, try overwriting the whole disk, with something like:

dd if=/dev/zero of=/dev/hda

and see if it makes the errors go away.

John.