Had the same problem as imperia777 : data intact, error message and unable to fix it, (though no actual power failure).
Here's fsck output: e2fsck 1.42.9 (4-Feb-2014) myfsname: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on myfsname Final verdict was: defective storage. Data was transferred to a new storage medium with a new filesystem. Problem solved. As additional check, we made a copy from the defective medium to another and observed that fsck could run flawlessly on the sane medium. Looks like fsck is extra cautious and checks if every operations indeed happened, which allowed it to spot the trouble. Anyway, to say it again: "fsck.ext4: unable to set superblock flags on myfsname" meant (at least in my case): change your storage medium. Thank you for your attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/387692 Title: ext4 - data loss after power failure, and unable to recover Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Ubuntu 9.04 , system is (was) up to date, home partition is encrypted with ecryptfs After a power failure I am unable to access the Ubuntu system, booting drops to busybox. From a live CD : [quote]root@ubuntu:~# fsck -y /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sda1 [/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway<y>? yes fsck.ext4: unable to set superblock flags on /dev/sda1[/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway<y>? no Clear journal<y>? no /dev/sda1: clean, 138871/373152 files, 681246/1492029 blocks root@ubuntu:~# fsck -y /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: unable to set superblock flags on /dev/sda1[/quote][quote]root@ubuntu:~# fsck /dev/sda1 fsck 1.41.4 (27-Jan-2009) e2fsck 1.41.4 (27-Jan-2009) /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway<y>? no Clear journal<y>? yes /dev/sda1 was not cleanly unmounted, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/sda1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda1: 138871/373152 files (0.2% non-contiguous), 681246/1492029 blocks[/quote][quote]root@ubuntu:~# mount -t ext4 /dev/sda1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so root@ubuntu:~# dmesg | tail [ 1894.643462] JBD: recovery failed [ 1894.643468] EXT4-fs: error loading journal. [ 1894.645367] sd 0:0:0:0: [sda] 12582912 512-byte hardware sectors: (6.44 GB/6.00 GiB) [ 1894.645385] sd 0:0:0:0: [sda] Write Protect is off [ 1894.645387] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1894.645404] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1894.645422] sd 0:0:0:0: [sda] 12582912 512-byte hardware sectors: (6.44 GB/6.00 GiB) [ 1894.645432] sd 0:0:0:0: [sda] Write Protect is off [ 1894.645434] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1894.645450] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA[/quote][quote]root@ubuntu:~# mke2fs -n /dev/sda1 mke2fs 1.41.4 (27-Jan-2009) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 373152 inodes, 1492029 blocks 74601 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=1530920960 46 block groups 32768 blocks per group, 32768 fragments per group 8112 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736 root@ubuntu:~# e2fsck -b 32768 /dev/sda1 e2fsck 1.41.4 (27-Jan-2009) Superblock needs_recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. /dev/sda1: recovering journal Superblock needs_recovery flag is clear, but journal has data. Recovery flag not set in backup superblock, so running journal anyway. e2fsck: unable to set superblock flags on /dev/sda1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/387692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
