19 Jul 05 …As The Future Repeats Today
- Good morning, how may I ruin your life today?
- How about messing with my ATA-drives like you did a month ago?
- Hang on to your suspenders, here we go!
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
...
hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdb: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide: failed opcode was: unknown
ide0: reset: success
EXT3-fs error (device hdb1): ext3_free_blocks_sb: bit already cleared for block 2045422
Aborting journal on device hdb1.
ext3_abort called.
EXT3-fs error (device hdb1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device hdb1) in ext3_free_blocks_sb: Journal has aborted
...
EXT3-fs error (device hdb1) in ext3_free_blocks_sb: Journal has aborted
EXT3-fs error (device hdb1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdb1) in ext3_truncate: Journal has aborted
EXT3-fs error (device hdb1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device hdb1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device hdb1) in ext3_reserve_inode_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
As it seems I simply just cannot catch a break with ATA-drives recently. This scenario happened to my brand new Maxtor drive today, although I highly suspect the IDE-controller on the motherboard is the culprit in this case.
The partitions on the drive were suddenly remounted read-only by the kernel. After I rebooted my system parted wouldn’t even read the partition table and gpart appeared to hang while scanning the drive. I decided to upgrade my 2.6.11 kernel to 2.6.12 just in case it was a driver problem, although I very much doubted it as the motherboard has an Intel 801 controller which is a quite mature chipset. After the reboot I was presented with the kernel output shown above, strangely it would now read the partition table. Thanks to this I was able to run fsck on both the partitions on that drive (/home and /public), it did find a lot of problems but most of them were probably just created by files which had only been in part created when the read-only remount took place.
So far I haven’t found any corrupted files on the drive and I consider myself lucky. I’m going to spend the rest of the day burning DVDs. Luckily it’s raining outside so it’s not like my spirits were high to begin with.
Similar Posts:
- Benchmark Galore
- Hard drives suck and then you die
- A look at the latest in free real-time scheduling in the Linux kernel
Reader's Comments
Leave a Comment
Ohh my god, not again
Seems like you and harddrives don’t like eachother. Anyway, good you didn’t lose any data this time.
i had similary thing. i thing there is a bug in 2.6.12 and 2.6.11 according ur post ( but i don’t use it )
my hard drive works well in 2.6.10
but since i upgrade on kernel 2.6.12, my hard drive gonna crazy.
and i can’t copy files on it
i make many mke2fs on it, but nothing..
i downgrade in 2.6.10 and the hard drive still gonna crazy
but i make a mke2fs under 2.6.10 and now i don’t have error
in 2.6.12
Jul 28 19:48:58 tuxgateway kernel: kjournald starting. Commit interval 5 seconds
Jul 28 19:48:58 tuxgateway kernel: EXT3 FS on hde1, internal journal
Jul 28 19:48:58 tuxgateway kernel: EXT3-fs: recovery complete.
Jul 28 19:48:58 tuxgateway kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 19:49:37 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 19:49:37 tuxgateway kernel: hde: dma_intr: error=0×01 { AddrMarkNotFound }, LBAsect=262187, sector=262185
Jul 28 19:49:37 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 19:49:41 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 19:49:41 tuxgateway kernel: hde: dma_intr: error=0×40 { UncorrectableError }, LBAsect=262188, sector=262185
Jul 28 19:49:41 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 19:49:41 tuxgateway kernel: end_request: I/O error, dev hde, sector 262185
Jul 28 19:49:41 tuxgateway kernel: __journal_remove_journal_head: freeing b_committed_data
Jul 28 19:53:46 tuxgateway kernel: kjournald starting. Commit interval 5 seconds
Jul 28 19:53:46 tuxgateway kernel: EXT3-fs warning (device hde1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Jul 28 19:53:46 tuxgateway kernel: EXT3-fs warning (device hde1): ext3_clear_journal_err: Marking fs in need of filesystem check.
Jul 28 19:53:46 tuxgateway kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jul 28 19:53:46 tuxgateway kernel: EXT3 FS on hde1, internal journal
Jul 28 19:53:46 tuxgateway kernel: EXT3-fs: recovery complete.
Jul 28 19:53:46 tuxgateway kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 19:54:00 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 19:54:00 tuxgateway kernel: hde: dma_intr: error=0×40 { UncorrectableError }, LBAsect=262191, sector=262185
Jul 28 19:54:00 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 19:54:00 tuxgateway kernel: end_request: I/O error, dev hde, sector 262185
Jul 28 19:54:01 tuxgateway kernel: __journal_remove_journal_head: freeing b_committed_data
Jul 28 19:56:31 tuxgateway kernel: kjournald starting. Commit interval 5 seconds
Jul 28 19:56:31 tuxgateway kernel: EXT3 FS on hde1, internal journal
Jul 28 19:56:31 tuxgateway kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 20:00:30 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 20:00:30 tuxgateway kernel: hde: dma_intr: error=0×40 { UncorrectableError }, LBAsect=262192, sector=262185
Jul 28 20:00:30 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 20:00:30 tuxgateway kernel: end_request: I/O error, dev hde, sector 262185
Jul 28 20:05:28 tuxgateway kernel: __journal_remove_journal_head: freeing b_committed_data
Jul 28 20:08:59 tuxgateway shutdown[1263]: shutting down for system reboot
reboot in 2.6.10
Jul 28 20:11:47 tuxgateway kernel: kjournald starting. Commit interval 5 seconds
Jul 28 20:11:47 tuxgateway kernel: EXT3-fs warning (device hde1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Jul 28 20:11:47 tuxgateway kernel: EXT3-fs warning (device hde1): ext3_clear_journal_err: Marking fs in need of filesystem check.
Jul 28 20:11:47 tuxgateway kernel: EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
Jul 28 20:11:47 tuxgateway kernel: EXT3 FS on hde1, internal journal
Jul 28 20:11:47 tuxgateway kernel: EXT3-fs: recovery complete.
Jul 28 20:11:47 tuxgateway kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 20:13:35 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 20:13:35 tuxgateway kernel: hde: dma_intr: error=0×01 { AddrMarkNotFound }, LBAsect=243382, sector=243377
Jul 28 20:13:35 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 20:13:37 tuxgateway kernel: hde: dma_intr: status=0×51 { DriveReady SeekComplete Error }
Jul 28 20:13:37 tuxgateway kernel: hde: dma_intr: error=0×40 { UncorrectableError }, LBAsect=243378, sector=243377
Jul 28 20:13:37 tuxgateway kernel: ide: failed opcode was: unknown
Jul 28 20:13:37 tuxgateway kernel: end_request: I/O error, dev hde, sector 243377
Jul 28 20:13:51 tuxgateway kernel: __journal_remove_journal_head: freeing b_committed_data
Jul 28 20:13:51 tuxgateway kernel: __journal_remove_journal_head: freeing b_committed_data
Jul 28 20:15:09 tuxgateway kernel: kjournald starting. Commit interval 5 seconds
– mke2fs in 2.6.10
Jul 28 20:15:09 tuxgateway kernel: EXT3 FS on hde1, internal journal
Jul 28 20:15:09 tuxgateway kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 20:30:18 tuxgateway — MARK –
15min without any errors
hi, i had a similar problem with a scsi hdd. when i boot-up the box i get a message like ‘journal commit i/o error’. i am trying to copy the data from sda5 partition on another disk and format that partition