Talk:Issues and Workarounds
From NAS-4220
Hitachi Deskstar 750gb & Western Digital WD250AAKS Caviar SE16(250gb)
I had trouble with this combination, but after a lot of headscratching I believe it was in fact due to a broken sata connection on one of the drives. Since the WD Caviar SE16 has been swapped for another drive I've had no more crashes. Sweet. Left this here in case it wasn't Just the Sata connector Gazzat5 20:49, 12 May 2010 (CEST)
UPDATE: Raidsonic uk arm nanopoint have sent me some new SATA cables and knock on wood it hasn't crashed yet. Gazzat5 18:42, 15 July 2010 (CEST)
Hitachi Deskstar 750gb errors
error with the drive that hasn't been changed; occured after shutdown and reboot... output from dmesg
Enable hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: DMA disabled hdb speed:U5 (50MHz)(0x45) ide0: reset: success hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hdb speed:U4 (66MHz)(0x44) ide0: reset: master: ECC circuitry error; slave: failed hdb: dma_timer_expiry: dma status == 0x61 hdb: DMA timeout error hdb: dma timeout error: status=0x50 { DriveReady SeekComplete } ide: failed opcode was: unknown end_request: I/O error, dev hdb, sector 6121 hdb: status error: status=0x51 { DriveReady SeekComplete Error } hdb: status error: error=0x05 { DriveStatusError AddrMarkNotFound }, LBAsect=6129, high=0, low=6129, sector=6129 ide: failed opcode was: unknown hdb: no DRQ after issuing MULTWRITE_EXT hdb: status error: status=0x51 { DriveReady SeekComplete Error } hdb: status error: error=0x05 { DriveStatusError AddrMarkNotFound }, LBAsect=6129, high=0, low=6129, sector=6129 ide: failed opcode was: unknown hdb: no DRQ after issuing MULTWRITE_EXT hdb: lost interrupt hdb: recal_intr: status=0x51 { DriveReady SeekComplete Error } hdb: recal_intr: error=0x05 { DriveStatusError AddrMarkNotFound }, LBAsect=0, high=0, low=0, sector=6129 ide: failed opcode was: unknown hdb: status error: status=0x51 { DriveReady SeekComplete Error } hdb: status error: error=0x05 { DriveStatusError AddrMarkNotFound }, LBAsect=6129, high=0, low=6129, sector=6129 ide: failed opcode was: unknown hdb: no DRQ after issuing MULTWRITE_EXT ide0: reset: master: controlling MPU error end_request: I/O error, dev hdb, sector 6129 end_request: I/O error, dev hdb, sector 1094713473 Buffer I/O error on device hdb1, logical block 136839184 lost page write due to I/O error on hdb1 end_request: I/O error, dev hdb, sector 1100404993 end_request: I/O error, dev hdb, sector 1100405001 end_request: I/O error, dev hdb, sector 1100405009 end_request: I/O error, dev hdb, sector 1100405017 end_request: I/O error, dev hdb, sector 1100405025 end_request: I/O error, dev hdb, sector 1100405033 end_request: I/O error, dev hdb, sector 1100405041 end_request: I/O error, dev hdb, sector 1100405049 end_request: I/O error, dev hdb, sector 1100405057 end_request: I/O error, dev hdb, sector 1100405065 end_request: I/O error, dev hdb, sector 1100405073 end_request: I/O error, dev hdb, sector 1100405081 end_request: I/O error, dev hdb, sector 6137 Buffer I/O error on device hdb1, logical block 767 lost page write due to I/O error on hdb1 end_request: I/O error, dev hdb, sector 1100404993 Aborting journal on device hdb1. do_generic_mapping_read page not uptodate twice, error=--EIO!!! ext3_abort called. EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only end_request: I/O error, dev hdb, sector 1100369249 end_request: I/O error, dev hdb, sector 1100369257 end_request: I/O error, dev hdb, sector 1100369265 end_request: I/O error, dev hdb, sector 1100369273 end_request: I/O error, dev hdb, sector 1100369281 end_request: I/O error, dev hdb, sector 1100369289 end_request: I/O error, dev hdb, sector 1100369297 end_request: I/O error, dev hdb, sector 1100369305 end_request: I/O error, dev hdb, sector 1100369313 end_request: I/O error, dev hdb, sector 1100369321 end_request: I/O error, dev hdb, sector 1100369329 end_request: I/O error, dev hdb, sector 1100369337 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369345 end_request: I/O error, dev hdb, sector 1100369249 do_generic_mapping_read page not uptodate twice, error=--EIO!!! end_request: I/O error, dev hdb, sector 1094713553 Buffer I/O error on device hdb1, logical block 136839194 lost page write due to I/O error on hdb1 hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown end_request: I/O error, dev hdb, sector 621805585 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=38862849, block=77725698 end_request: I/O error, dev hdb, sector 303038481 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=18939905, block=37879810 end_request: I/O error, dev hdb, sector 343408657 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=21463050, block=42926082 end_request: I/O error, dev hdb, sector 234618897 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=14663681, block=29327362 end_request: I/O error, dev hdb, sector 919076881 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=57442305, block=114884610 end_request: I/O error, dev hdb, sector 1123024913 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=70189057, block=140378114 end_request: I/O error, dev hdb, sector 1432092689 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=89505793, block=179011586 end_request: I/O error, dev hdb, sector 388235297 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=24264772, block=48529412 end_request: I/O error, dev hdb, sector 388235281 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=24264705, block=48529410 end_request: I/O error, dev hdb, sector 502267921 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=31391745, block=62783490 end_request: I/O error, dev hdb, sector 342622225 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=21413889, block=42827778 end_request: I/O error, dev hdb, sector 1311097 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=81921, block=163887 end_request: I/O error, dev hdb, sector 33816593 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=2113537, block=4227074 end_request: I/O error, dev hdb, sector 343409489 EXT3-fs error (device hdb1): ext3_get_inode_loc: unable to read inode block - inode=21466387, block=42926186 hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown hdb: DMA disabled ide0: reset: success hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: irq timeout: status=0xd0 { Busy } ide: failed opcode was: unknown ide0: reset: success hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hda: task_in_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_in_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown
Maybe it's overheating, maybe it's a controller error. Whatever, it's very annoying! Gazzat5 17:52, 23 May 2010 (CEST)
Still Buggin
Yep, after being stable for a nice long time (left on 24/7). One hot spell in my room, shut it down for a bit and now it won't come back reliably. :'(
Experiencing drive IO errors on the second drive (the one with my data on it).
Reboot (and presumably an automatic e2fsck fix) and the data's back but it crashes out soon after!
I hate this box!! Gazzat5 13:46, 1 June 2010 (CEST)
