Ext3 Fs Error Device Ide0 3 3
Contents |
November 20, 2007 By Major Hayden 18 Comments If your system abruptly loses power, or if a RAID card is beginning to fail, you might
Ext3_reserve_inode_write: Io Failure
see an ominous message like this within your logs: XHTML EXT3-fs error (device hda3) in start_transaction: Journal has aborted 1 EXT3-fs error (device hda3) in start_transaction: Journal has aborted Basically, the system is telling you that it's detected a filesystem/journal mismatch, and it can't utilize the journal any longer. When this situation pops up, the filesystem gets mounted read-only almost http://kb.fortinet.com/kb/documentLink.do?externalID=FD31857 immediately. To fix the situation, you can remount the partition as ext2 (if it isn't your active root partition), or you can commence the repair operations. If you're working with an active root partition, you will need to boot into some rescue media and perform these operations there. If this error occurs with an additional partition besides the root partition, https://major.io/2007/11/20/ext3-fs-error-device-hda3-in-start_transaction-journal-has-aborted/ simply unmount the broken filesystem and proceed with these operations. Remove the journal from the filesystem (effectively turning it into ext2): XHTML # tune2fs -O ^has_journal /dev/hda3 1 # tune2fs -O ^has_journal /dev/hda3 Now, you will need to fsck it to correct any possible problems (throw in a -y flag to say yes to all repairs, -C for a progress bar): XHTML # e2fsck /dev/hda3 1 # e2fsck /dev/hda3 Once that's finished, make a new journal which effectively makes the partition an ext3 filesystem again: XHTML # tune2fs -j /dev/hda3 1 # tune2fs -j /dev/hda3 You should be able to mount the partition as an ext3 partition at this time: XHTML # mount -t ext3 /dev/hda3 /mnt/fixed 1 # mount -t ext3 /dev/hda3 /mnt/fixed Be sure to check your dmesg output for any additional errors after you're finished! Share this post:TwitterGoogleLinkedInRedditEmailPrintTagged With: command line, emergency, filesystem Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Email check failed, please try again Sorry, your blog cannot share posts by email.
Up Home Storage Reviews Enterprise Reviews Consumer Reviews Enterprise VMmark Benchmark MarkMail Benchmark MarkLogic Benchmark MySQL OLTP http://forums.storagereview.com/index.php?/topic/14657-ext3-fs-error/ Benchmark FIO Synthetic Benchmark Enterprise Test Lab Storage Webinars Leaderboard Reference Guides http://mandrivausers.org/index.php?/topic/19807-hard-drive-io-errors-help/ Forums View New Content Forums Members Calendar Reliability Survey About SR Review Process Sponsors Consumer Test Platforms View New Content Storage Review Forums Members Calendar More All Activity Home Storage Hardware Hard Disk Drives (HDD) Ext3 Fs Error Sign in to follow this Followers 0 Ext3 Fs fs error Error Started by blakerwry, March 25, 2004 5 posts in this topic blakerwry 0 StorageReview Patron Patron 0 4840 posts Location:Kansas City USA Posted March 25, 2004 · Report post I was burning in my newly upgraded server last night and when I awoke my screen was filled with ext3 errors. EXT3-fs error (device ide0(3,1)): ext3_readdir: directory unable to read #97538 contains a hole at offset 1297817600 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297821696 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297825792 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297829888 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297833984 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297838080 EXT3-fs error (device ide0(3,1)): ext3_readdir: directory #97538 contains a hole at offset 1297842176 *(each offset is increased by 4096 over the last) The anatomy of my server looks like the following: Onboard VIA 8233 IDE .hda = Fujitsu desktop10 (hda1=/, hda2=swap, hda3=/var) .hdb = empty .hdc = empty .hdd = empty Promise Ultra100 (PDC20267) .hde = empty .hdf = empty .hdg = empty .hdh = empty Promise Ultra133 (PDC20269) .hde = 160GB DM+9 .hdf = 160GB DM+9 .hdg = 160GB DM+9 .hdh = 160GB DM+9 each dm+9 has a single primary partition defined as type FD (linux RAID auto detect) and are RAIDed as de
Blogs Portal Calendar Easy URPMI Chat MandrivaUsers.org > General Help > Hardware Posting Guidelines View New Content Page 1 of 1 You cannot start a new topic You cannot reply to this topic Hard Drive I/O Errors - Help #1 fuzzylizard MUB Addict Group: Members Posts: 803 Joined: 23-September 02 Posted 19 October 2004 - 01:25 PM I am getting the following errors showing up in /var/log/messages about every 5 - 20 seconds and I don't really understand what they mean. Oct 18 21:55:16 Rivendell kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } Oct 18 21:55:16 Rivendell kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=89894191, sector=17039416 Oct 18 21:55:16 Rivendell kernel: end_request: I/O error, dev 03:03 (hda), sector 17039416 Oct 18 21:55:16 Rivendell kernel: EXT3-fs error (device ide0(3,3)): ext3_get_inode_loc: unable to read inode block - inode=1054725, block=2129927 Oct 18 21:55:16 Rivendell kernel: EXT3-fs error (device ide0(3,3)) in ext3_reserve_inode_write: IO failure In addition, I tried to reboot the server and was welcomed with a ton of disk errors. I did a manual fsck and simply selected the defaults when it asked to fix/ignore/save something. This took about an hour to run through. I restarted the computer and everything seemed to be going fine, although I had lost some functionality. This lasted for about 10 minutes. I tried the following command to see if there were any bad blocks on the drive: $ /sbin/badblocks -v /dev/hda This basically killed the drive. The entire computer became inactive. When I tried to switch to another console (ctrl-alt-1, 2,3,4,etc) all I got, on every screen, were the error listed above. I finally had to turn the machine off. My next move is to pull the drive out, put it in another computer and run the Maxtor disk diagnostic tools on. (no floppy drive in the server). Anyone have any idea as to what might be going on here. The universe began with a word. But which came first: the word or the thought behind the word? Y