ide problem - is this a known problem, or is the disk dead?

Hi

I'm running 2.4.21-rc6, and one of my drives has failed with the following messages. Does this indicate a hardware failure?

All but one of the partitions are raid1, so they still work. The one raid0 partition, which holds less important stuff like squid cache files, obviously doesn't. I tried to remount it read-only, but mount hangs for ever. It would be nice if linux could deal with hardware failures like this gracefully, and allow the fs to be unmounted.

here is the log:

Jun  1 06:28:00 r2d2 kernel: hdc: dma_timer_expiry: dma status == 0x21
Jun  1 06:28:10 r2d2 kernel: hdc: timeout waiting for DMA
Jun  1 06:28:10 r2d2 kernel: hdc: timeout waiting for DMA
Jun  1 06:28:10 r2d2 kernel: hdc: (__ide_dma_test_irq) called while not waiting
Jun  1 06:28:10 r2d2 kernel: hdc: status timeout: status=0xd0 { Busy }
Jun  1 06:28:10 r2d2 kernel:
Jun  1 06:28:10 r2d2 kernel: hdc: drive not ready for command
Jun  1 06:28:40 r2d2 kernel: ide1: reset timed-out, status=0xd0
Jun  1 06:28:40 r2d2 kernel: hdc: status timeout: status=0xd0 { Busy }
Jun  1 06:29:11 r2d2 kernel:
Jun  1 06:29:11 r2d2 kernel: hdc: drive not ready for command
Jun  1 06:29:11 r2d2 kernel: ide1: reset timed-out, status=0xd0
Jun  1 06:29:11 r2d2 kernel: blk: queue c03886b4, I/O limit 4095Mb (mask 0xfffff
fff)
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 905
464
Jun  1 06:29:11 r2d2 kernel: raid1: Disk failure on ide/host0/bus1/target0/lun0/
part6, disabling device.
Jun  1 06:29:11 r2d2 kernel: ^IOperation continuing on 1 devices
Jun  1 06:29:11 r2d2 kernel: md: updating md3 RAID superblock on device
Jun  1 06:29:11 r2d2 kernel: md: (skipping new-faulty ide/host0/bus1/target0/lun
0/part6 )
Jun  1 06:29:11 r2d2 kernel: md: ide/host0/bus0/target0/lun0/part6 [events: 0000
0077]<6>(write) ide/host0/bus0/target0/lun0/part6's sb offset: 94095168
Jun  1 06:29:11 r2d2 kernel: raid1: ide/host0/bus1/target0/lun0/part6: reschedul
ing block 905464
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 192
0
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 192
8
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 193
6
Jun  1 06:29:11 r2d2 kernel: raid1: ide/host0/bus0/target0/lun0/part6: redirecti
ng sector 905464 to another mirror
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 194
4
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 195
2
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 196
0
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 196
8
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 197
6
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 198
4
Jun  1 06:29:11 r2d2 kernel: end_request: I/O error, dev 16:06 (hdc), sector 199

2
[...]
more of the same.

Get back to me if you need more info. I'll try the drive in another machine soon to check it.

Cheers

Rob

Its hard to tell if thats a dead disk or just terminally confused. The drive stopped taking to us, set itself Busy and never came back even after we tried to reset it.

* Alan Cox <[email protected]>:

|> Jun  1 06:28:00 r2d2 kernel: hdc: dma_timer_expiry: dma status == 0x21
|> Jun  1 06:28:10 r2d2 kernel: hdc: timeout waiting for DMA
|> Jun  1 06:28:10 r2d2 kernel: hdc: timeout waiting for DMA
|> Jun  1 06:28:10 r2d2 kernel: hdc: (__ide_dma_test_irq) called while not waiting
|> Jun  1 06:28:10 r2d2 kernel: hdc: status timeout: status=0xd0 { Busy }
|> Jun  1 06:28:10 r2d2 kernel:
|> Jun  1 06:28:10 r2d2 kernel: hdc: drive not ready for command
|> Jun  1 06:28:40 r2d2 kernel: ide1: reset timed-out, status=0xd0
|> Jun  1 06:28:40 r2d2 kernel: hdc: status timeout: status=0xd0 { Busy }
|> Jun  1 06:29:11 r2d2 kernel:
| 
| Its hard to tell if thats a dead disk or just terminally confused. The
| drive stopped taking to us, set itself Busy and never came back even
| after we tried to reset it.

I'm running 2.4.21-rc3 on the host where i got this today:

hdc: dma_timer_expiry: dma status == 0x20
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: status timeout: status=0xd0 { Busy }

hdc: drive not ready for command
ide1: reset timed-out, status=0xd0
hdc: status timeout: status=0xd0 { Busy }

hdc: drive not ready for command
ide1: reset timed-out, status=0xd0
end_request: I/O error, dev 16:01 (hdc), sector 78496
end_request: I/O error, dev 16:01 (hdc), sector 78496
end_request: I/O error, dev 16:01 (hdc), sector 20328
end_request: I/O error, dev 16:01 (hdc), sector 20336
end_request: I/O error, dev 16:01 (hdc), sector 20344
end_request: I/O error, dev 16:01 (hdc), sector 20352
end_request: I/O error, dev 16:01 (hdc), sector 20360
end_request: I/O error, dev 16:01 (hdc), sector 20368
end_request: I/O error, dev 16:01 (hdc), sector 25427984
end_request: I/O error, dev 16:01 (hdc), sector 20376
end_request: I/O error, dev 16:01 (hdc), sector 20384
end_request: I/O error, dev 16:01 (hdc), sector 20392
end_request: I/O error, dev 16:01 (hdc), sector 20400
end_request: I/O error, dev 16:01 (hdc), sector 20408
end_request: I/O error, dev 16:01 (hdc), sector 20416
end_request: I/O error, dev 16:01 (hdc), sector 20424
end_request: I/O error, dev 16:01 (hdc), sector 16
end_request: I/O error, dev 16:01 (hdc), sector 37486592
end_request: I/O error, dev 16:01 (hdc), sector 37486608
end_request: I/O error, dev 16:01 (hdc), sector 54788120
end_request: I/O error, dev 16:01 (hdc), sector 0
end_request: I/O error, dev 16:01 (hdc), sector 37486608
EXT3-fs error (device ide1(22,1)): ext3_get_inode_loc: unable to read inode block - inode=2338338, block=4685826 Aborting journal on device ide1(22,1).
end_request: I/O error, dev 16:01 (hdc), sector 4176
Remounting filesystem read-only
end_request: I/O error, dev 16:01 (hdc), sector 0
EXT3-fs error (device ide1(22,1)) in ext3_reserve_inode_write: IO failure
EXT3-fs error (device ide1(22,1)) in ext3_orphan_add: IO failure
EXT3-fs error (device ide1(22,1)) in ext3_truncate: IO failure
EXT3-fs error (device ide1(22,1)) in start_transaction: Journal has aborted

My setup looks like:

Memory: 516616k/524204k available (1051k kernel code, 7200k reserved, 228k data, 76k init, 0k highmem)
CPU: Intel(R) Celeron(TM) CPU 1400MHz stepping 01
Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH2: IDE controller at PCI slot 00:1f.1
ICH2: chipset revision 17
ICH2: not 100% native mode: will probe irqs later

    ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio

hda: IC25N040ATCS04-0, ATA DISK drive
blk: queue c0278660, I/O limit 4095Mb (mask 0xffffffff)
hdc: IC25N040ATCS04-0, ATA DISK drive
blk: queue c0278ab4, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 78140160 sectors (40008 MB) w/1768KiB Cache, CHS=4864/255/63, UDMA(100)
hdc: attached ide-disk driver.
hdc: host protected area => 1
hdc: 78140160 sectors (40008 MB) w/1768KiB Cache, CHS=77520/16/63, UDMA(100) Partition check:
/dev/ide/host0/bus0/target0/lun0: p1 p2 /dev/ide/host0/bus1/target0/lun0: p1

Now I'm trying heavy reads/writes on the drive which failed, but I'm unable to generate any error (yet). I had more than 2 weeks of uptime with this kernel.

/dev/hda: IC25N040ATCS04-0: 40 C
/dev/hdc: IC25N040ATCS04-0: 42 C