Ext3-fs Sdb1 Error No Journal Found
Contents |
error after running fsck Issues related to hardware problems Post Reply Print view Search Advanced search 10 posts • Page 1 of 1 maksaraswat Posts: 44 Joined: ext3 fs error journal has aborted 2011/10/14 19:00:52 Location: New York Contact: Contact maksaraswat Website [SOLVED] EXT3-fs error ext3-fs error unable to read inode block after running fsck Quote Postby maksaraswat » 2012/01/31 20:43:31 Hi,For some reason my RAID 6 mount was unmountable ext3-fs error fortigate and I was getting the error message when I tried to mount it manually [root@server ~]# mount /dev/sdb1 /local1/mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or
Ext3-fs Error (device Sda6) In Start_transaction Journal Has Aborted
other error In some cases useful info is found in syslog - try dmesg | tail or so [root@server ~]# dmesg | tail Add. Sense: Internal target failureend_request: I/O error, dev sdb, sector 806617154sd 1:0:0:0: SCSI error: return code = 0x08000002sdb: Current: sense key: Hardware Error Add. Sense: Internal target failureend_request: I/O error, dev sdb, sector 3025928274JBD: recovery failedEXT3-fs: error loading journal.After ext3-fs error (device dm-0) analyzing the situation and some Googling I found out that I should do a file system check with fsck and that what I did nextroot@server ~]# fsck -f -y /dev/sdb1...after almost 5hrs it completed with following message: /dev/sdb1: ***** FILE SYSTEM WAS MODIFIED *****/dev/sdb1: 1064317/548929536 files (5.7% non-contiguous), 836681827/1097856503 blocksAfter this completion I was able to mount and I can see part (about 80-85%) of my data however the mount is READ-ONLY!!!! And I am getting following message [root@server ~]# dmesg | tailAdd. Sense: Internal target failureend_request: I/O error, dev sdb, sector 781189162EXT3-fs error (device sdb1): read_inode_bitmap: Cannot read inode bitmap - block_group = 2980, inode_bitmap = 97648641Aborting journal on device sdb1.ext3_abort called.EXT3-fs error (device sdb1): ext3_journal_start_sb: Detected aborted journalRemounting filesystem read-onlyEXT3-fs error (device sdb1) in ext3_new_inode: IO failureEXT3-fs error (device sdb1) in ext3_mkdir: IO failureOne of the HDD looks bad and I am getting SMART messages which I will replace tomorrow. But is it possible to make the mount READ-WRITE? It keeps some of our automated backups and I don't want backups to miss anymore.Please help!Thanks in advance!Mayank Top pschaff Retired Mod
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings ext3-fs error (device dm-0) ext3_journal_start_sb detected aborted journal and policies of this site About Us Learn more about Stack Overflow
Detected Aborted Journal Ext4
the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users
Ext3 Fs Error Ext3_journal_start_sb Detected Aborted Journal
Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it http://www.centos.org/forums/viewtopic.php?t=24611 works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to recover data from a corrupted ext3 partition? up vote 5 down vote favorite 1 A server of mine had a drive failure of some sort which caused the OS (CentOS 5) to crash and stop working (it refuses to http://serverfault.com/questions/493091/how-to-recover-data-from-a-corrupted-ext3-partition boot). So we put another drive with a working OS and from there we try to mount the partitions in the old drive. Most partitions mount fine except for one: the /var partition, where my MySQL tables reside. When I try to mount that one, I see these errors with dmesg: sd 0:0:1:0: Unhandled sense code sd 0:0:1:0: SCSI error: return code = 0x08100002 Result: hostbyte=invalid driverbyte=DRIVER_SENSE,SUGGEST_OK sdb: Current: sense key: Medium Error Add. Sense: Unrecovered read error Info fld=0x4a47e JBD: Failed to read block at offset 9863 JBD: recovery failed EXT3-fs: error loading journal. Is there a way I can recover the data in that partition? EDIT: As requested, the output of tune2fs -l /dev/sdb2 is: tune2fs 1.39 (29-May-2006) Filesystem volume name: /var1 Last mounted on:
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 https://major.io/2007/11/20/ext3-fs-error-device-hda3-in-start_transaction-journal-has-aborted/ 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 fs error 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, ext3-fs error (device 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.