Dear Sir,
On a caviar 2tb WD I get a relevant issue with DMA UDM and got also a sector defect. I would like to check both in details.
I fear that the disk is dying :( :( :(
In the man page, I notice that nothing about bad blocks/sectors is displayed. I would be great to mention it. I know that for a 2tb bad sector check, howerver large, will take eternity, -but seems that no other choice appears.
In furthre info. typical reported logs errors:
I hope that I can post those info regarding the JFS disk, if it helps for understanding:
Sep 15 06:09:32 debian05 chipcardd[6354]: chipcardd.c: 861: Daemon terminated, exiting.
Sep 15 06:09:32 debian05 lircd-0.8.3[6577]: caught signal
Sep 15 06:09:32 debian05 mc: *** info
Sep 15 06:09:32 debian05 mc: Warning: closing connection
Sep 15 06:09:32 debian05 nmbd[6599]: [2010/09/15 06:09:32, 0] nmbd/nmbd.c:71(terminate)
Sep 15 06:09:32 debian05 nmbd[6599]: Got SIGTERM: going down...
Sep 15 06:09:33 debian05 kernel: [19113.478439] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 15 06:09:33 debian05 kernel: [19113.478551] ata3.00: BMDMA stat 0x24
Sep 15 06:09:33 debian05 kernel: [19113.478614] ata3.00: failed command: READ DMA EXT
Sep 15 06:09:33 debian05 kernel: [19113.478698] ata3.00: cmd 25/00:08:f8:17:00/00:00:80:00:00/e0 tag 0 dma 4096 in
Sep 15 06:09:33 debian05 kernel: [19113.478700] res 51/40:00:f8:17:00/40:00:80:00:00/e0 Emask 0x9 (media error)
Sep 15 06:09:33 debian05 kernel: [19113.479010] ata3.00: status: { DRDY ERR }
Sep 15 06:09:33 debian05 kernel: [19113.479078] ata3.00: error: { UNC }
Sep 15 06:09:33 debian05 kernel: [19113.494308] ata3.00: configured for UDMA/133
Sep 15 06:09:33 debian05 kernel: [19113.494319] ata3: EH complete
Sep 15 06:09:33 debian05 avahi-daemon[6249]: Got SIGTERM, quitting.
Sep 15 06:09:33 debian05 avahi-daemon[6249]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::e2cb:4eff:fec1:ae15.
Sep 15 06:09:33 debian05 avahi-daemon[6249]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Sep 15 06:09:33 debian05 lircd-0.8.3[24624]: lircd(userspace) ready
Sep 15 06:09:36 debian05 kernel: [19116.317610] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 15 06:09:36 debian05 kernel: [19116.317720] ata3.00: BMDMA stat 0x24
Sep 15 06:09:36 debian05 kernel: [19116.317784] ata3.00: failed command: READ DMA EXT
Sep 15 06:09:36 debian05 kernel: [19116.317868] ata3.00: cmd 25/00:08:f8:17:00/00:00:80:00:00/e0 tag 0 dma 4096 in
Sep 15 06:09:36 debian05 kernel: [19116.317870] res 51/40:00:f8:17:00/40:00:80:00:00/e0 Emask 0x9 (media error)
Sep 15 06:09:36 debian05 kernel: [19116.318127] ata3.00: status: { DRDY ERR }
Sep 15 06:09:36 debian05 kernel: [19116.318194] ata3.00: error: { UNC }
Sep 15 06:09:36 debian05 kernel: [19116.334476] ata3.00: configured for UDMA/133
Sep 15 06:09:36 debian05 kernel: [19116.334488] ata3: EH complete
Sep 15 06:09:36 debian05 kernel: [19116.888955] fuse exit
Sep 15 06:09:38 debian05 kernel: [19119.156828] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 15 06:09:38 debian05 kernel: [19119.156952] ata3.00: BMDMA stat 0x24
Sep 15 06:09:38 debian05 kernel: [19119.157016] ata3.00: failed command: READ DMA EXT
Sep 15 06:09:38 debian05 kernel: [19119.157100] ata3.00: cmd 25/00:08:f8:17:00/00:00:80:00:00/e0 tag 0 dma 4096 in
Sep 15 06:09:38 debian05 kernel: [19119.157102] res 51/40:00:f8:17:00/40:00:80:00:00/e0 Emask 0x9 (media error)
Sep 15 06:09:38 debian05 kernel: [19119.157338] ata3.00: status: { DRDY ERR }
Sep 15 06:09:38 debian05 kernel: [19119.157404] ata3.00: error: { UNC }
Sep 15 06:09:38 debian05 kernel: [19119.173686] ata3.00: configured for UDMA/133
Sep 15 06:09:38 debian05 kernel: [19119.173698] ata3: EH complete
Sep 15 06:09:41 debian05 kernel: [19121.995998] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Sep 15 06:09:41 debian05 kernel: [19121.996110] ata3.00: BMDMA stat 0x24
Sep 15 06:09:41 debian05 kernel: [19121.996173] ata3.00: failed command: READ DMA EXT
Sep 15 06:09:41 debian05 kernel: [19121.996257] ata3.00: cmd 25/00:08:f8:17:00/00:00:80:00:00/e0 tag 0 dma 4096 in
Sep 15 06:09:41 debian05 kernel: [19121.996259] res 51/40:00:f8:17:00/40:00:80:00:00/e0 Emask 0x9 (media error)
Sep 15 06:09:41 debian05 kernel: [19121.996505] ata3.00: status: { DRDY ERR }
Sep 15 06:09:41 debian05 kernel: [19121.996572] ata3.00: error: { UNC }
Sep 15 06:09:41 debian05 kernel: [19122.012870] ata3.00: configured for UDMA/133
Sep 15 06:09:41 debian05 kernel: [19122.012884] sd 2:0:0:0: [sdd] Unhandled sense code
Sep 15 06:09:41 debian05 kernel: [19122.012888] sd 2:0:0:0: [sdd] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Sep 15 06:09:41 debian05 kernel: [19122.012893] sd 2:0:0:0: [sdd] Sense Key : Medium Error [current] [descriptor]
Sep 15 06:09:41 debian05 kernel: [19122.012899] Descriptor sense data with sense descriptors (in hex):
Sep 15 06:09:41 debian05 kernel: [19122.012902] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
Sep 15 06:09:41 debian05 kernel: [19122.012914] 80 00 17 f8
Sep 15 06:09:41 debian05 kernel: [19122.012919] sd 2:0:0:0: [sdd] Add. Sense: Unrecovered read error - auto reallocate failed
Sep 15 06:09:41 debian05 kernel: [19122.012927] sd 2:0:0:0: [sdd] CDB: Read(10): 28 00 80 00 17 f8 00 00 08 00
Sep 15 06:09:41 debian05 kernel: [19122.012938] end_request: I/O error, dev sdd, sector 2147489784
Sep 15 06:09:41 debian05 kernel: [19122.013036] metapage_read_end_io: I/O error
I am bit stuck with this issue of disk, and maybe jfs utils have the swiss knife tool to fix this or in the future.
Jfs is so stable over ext3; I'm lovin' it !
also touch /forcefsck !
best regards