Jbd No Valid Journal Superblock Found Ext3-fs Error Loading Journal
Contents |
message: Adrian Bunk: "[2.6 patch] fs/hugetlbfs/inode.c: make a function static" Next in thread: Jan Niehusmann: "Re: ext3 corruption: "JBD: no valid journal superblock found"" Messages sorted by: [ ext3 fs error journal has aborted date ] [ thread ] [ subject ] [ author ] Currently,
Ext3-fs Error Unable To Read Inode Block
I'm experiencing a strange problem with one of my ext3 filesystems: There seems to be some journal corruption, but
Detected Aborted Journal Ext4
up to now I didn't see any sign of hardware problems, so I wonder if there could be some filesystem bug involved. The symptoms are the kernel not mounting the filesystem but
Ext3-fs Error (device Sda6) In Start_transaction Journal Has Aborted
giving the following error message: Oct 31 19:48:18 knautsch kernel: [17179601.724000] JBD: no valid journal superblock found Oct 31 19:48:18 knautsch kernel: [17179601.724000] EXT3-fs: error loading journal. e2fsck -n tells me e2fsck 1.38 (30-Jun-2005) Superblock has an invalid ext3 journal (inode 8). Clear? no e2fsck: Illegal inode number while checking ext3 journal for /dev/vgnb/compile There are two things I did with the filesystem ext3 fs error ext3_journal_start_sb detected aborted journal which may be related to this: First, on Oct. 27 I did resize the filesystem (umount, lvextend, e2fsck -f, resize2fs, mount). But after that I did several reboots without any problems - this is my notebook and I turn it on and off several times a day. The second is an unclean shutdown and reboot at Oct 31 19:19:56. At this boot, the filesystem was still mountable: Oct 31 19:19:56 knautsch kernel: [17179602.428000] kjournald starting. Commit interval 5 seconds Oct 31 19:19:56 knautsch kernel: [17179602.432000] EXT3 FS on dm-4, internal journal Oct 31 19:19:56 knautsch kernel: [17179602.432000] EXT3-fs: recovery complete. Oct 31 19:19:56 knautsch kernel: [17179602.440000] EXT3-fs: mounted filesystem with ordered data mode. (here, I'm assuming the "dm-4" number is stable between reboots, correct? - Anyways, there were no error messages on that reboot) The next reboot was the one at 19:48, with the error message quoted above. So, to me it looks like the recovery at 19:19 did something wrong and corrupted the journal. I am just copying the whole filesystem over to another hard disk, so I can do further analysis on that, later. If
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 (device dm-0) 2011/10/14 19:00:52 Location: New York Contact: Contact maksaraswat Website [SOLVED] EXT3-fs error after ext3-fs error (device dm-0) ext3_journal_start_sb detected aborted journal running fsck Quote Postby maksaraswat » 2012/01/31 20:43:31 Hi,For some reason my RAID 6 mount was unmountable and I ext3-fs error fortigate 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 other error http://lkml.iu.edu/hypermail/linux/kernel/0511.0/0129.html 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 analyzing the http://www.centos.org/forums/viewtopic.php?t=24611 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 Moderator Posts: 18276 Joined: 2006/12/13 20:15:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the http://superuser.com/questions/575783/cant-mount-ext4-ssd-jbd-no-valid-journal-superblock-found company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Can't mount ext4 SSD: `JBD: fs error no valid journal superblock found` up vote 1 down vote favorite I have a bit of a problem. I am running Ubuntu 10.04 LTS on my laptop, and about 2 years ago I replaced the aging HDD with a 32 GB SSD. Today I tried to boot my computer, but it couldn't. So I've put the SSD into an external HDD rack and booted a live CD Ubuntu 10.10 to try to recover data detected aborted journal from the SSD. The SSD appears in the drop down menu but it won't mount. Log: ubuntu@ubuntu:~$ dmesg | tail [ 2125.445659] sd 8:0:0:0: [sda] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB) [ 2125.446983] sd 8:0:0:0: [sda] Write Protect is off [ 2125.446988] sd 8:0:0:0: [sda] Mode Sense: 17 00 00 08 [ 2125.446992] sd 8:0:0:0: [sda] Assuming drive cache: write through [ 2125.449084] sd 8:0:0:0: [sda] Assuming drive cache: write through [ 2125.449098] sda: sda1 sda2 < sda5 > [ 2125.454285] sd 8:0:0:0: [sda] Assuming drive cache: write through [ 2125.454293] sd 8:0:0:0: [sda] Attached SCSI disk [ 2125.777836] JBD: no valid journal superblock found [ 2125.777840] EXT4-fs (sda1): error loading journal Is there a way to fix this so I can recover my data? linux ubuntu ssd data-recovery share|improve this question edited Oct 2 at 12:44 Michael Kjörling 18.8k45083 asked Mar 30 '13 at 18:48 Andreja 413 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote Have you tried running fsck on it? From the live boot, try something like: fsck.ext4 -Dcfy -C 0 /dev/sdX# That will: -D - Optimize directories -c - Check for bad sectors -f - Force a check -y - Assumes 'yes' to all questions -C 0 - Prints info to stdout You would just need to m