To that this works, you can boot from your primary HD or rescue with the damaged HD disconnected. my root partition was on a failing drive! If you were making changes then that might give a clue as to where to look. We Acted. http://netfiscal.com/bad-magic/e2fsck-unable-to-set-superblock-flags-on-dev-md0.html
sudo kill xxxx Where xxxx is number of process you want to kill. I'm not really sure I can help, but my best advice would be to stop using the drive until you get some help over there, to minimise the possiblity of overwriting If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck yes
Free blocks count wrong for group #33 (248, counted=251).
Inode 151946 was part of the orphaned inode list. If it's any comfort (and I doubt it will be), the exact same thing could have just as easily happened with ext3. I've also ran a testdisk deep search if anyone can decypher the log. yes
Free blocks count wrong for group #1 (62, counted=70).
Free blocks count wrong for group #182 (485, counted=482).
Free blocks count wrong for group #78 (9262, counted=9269).
Free blocks count wrong for group #59 (89, counted=87).
Free inodes count wrong for group #0 (5, counted=10).
Testdisk can be found on the Parted Magic disk, the link to which is above. Dumpe2fs: Bad Magic Number In Super-block While Trying To Open I do not know if e2fsck is really any different than fsck. #From liveDVD/Flash so everything is unmounted,swap off if necessary, change example shown with partition sdb1 to your partition(s) #e2fsck no
The root / partition was suddenly mounted read only! http://serverfault.com/questions/168046/failed-mdadm-array-with-ext-4-partition-e2fsck-unable-to-set-superblock-flag you really saved me, was about to reinstall it entirely and reinstalling all the applications would have been a nightmare.. 11 evidex on July 16, 2010 said: I can't count how Superblock Needs_recovery Flag Is Clear, But Journal Has Data. Boot from that, and you'll access to a number of useful tools. E2fsck Bad Magic Number In Superblock yes
Free blocks count wrong for group #76 (11417, counted=11416).
on January 5, 2012 said: Thanks for posting this how-to. navigate here It seams that e2fsck does nothing at all. 80 Jorge Henriquez on November 30, 2011 said: A HUGE Thank to you! First off you may have a real disk problem. Output integers in negative order, increase the maximum integer everytime Is there a non-medical name for the curve where index finger and thumb meet? Unable To Set Superblock Flags On Root
The RAID1 is "mirrored" although I set it as not backed up when I installed it on my home server - so it is a mirror with only one member. sudo kill xxxx Where xxxx is number of process you want to kill. yes
Free blocks count wrong for group #2 (272, counted=263).
Free inodes count wrong for group #16 (1, counted=3).
that's interesting. How To Recover Superblock In Linux I just wanted the OS to boot. Terminal won't even open, nor will anything else, though the mouse can still be moved and items can be clicked (with no visible results).
Inode 156698 was part of the orphaned inode list. FIXED.
Inode 9769 was part of the orphaned inode list. FIXED.
Inode 152371 was part of the orphaned inode list. Bad Magic Number In Superblock While Trying To Open /dev/sda2 As for how exactly the superblocks work, and whether they're from different times, I'm not quite sure.
i love you!!😀 102 evidex on May 25, 2012 said: Glad to hear it helped🙂 103 Olivier on June 4, 2012 said: Hey, thanks a lot, I can now access my More info - when running ‘sudo fsck -v /dev/sdb' it may only take 30 seconds for the command to output the results were as when you run the command on the After running ‘sudo e2fsck -b 32768 /dev/sdb1', which took 15 minutes the message I received was: /dev/sdb1: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sdb1: 246122/61054976 files (1.1% non-contiguous), 39505694/244190390 blocks Error this contact form yes
Free blocks count wrong for group #211 (1070, counted=1071).
which url is the ubuntuforum? 36 evidex on December 30, 2010 said: The link is in my above reply, though if it's not there for you; http://www.ubuntuforums.org/ 37 dalembert on January Since it did this on the root partition, that may have been the kick needed to get past busybox and let the automatic check fix the home partition. FIXED.
Inode 151521 was part of the orphaned inode list. Anyway, everytime that I boot my system it asks me to type S to skip mounting, and after it it loads /root and /home at an extended partition.
So there must be something wrong with the partition table, which in turn is throwing off the logical block offsets in the filesystem causing fsck to not be able to find I hope you keep posting useful articles like this!! 86 evidex on January 5, 2012 said: Glad to help! 87 k w b on January 8, 2012 said: Well, I can't FIXED.
Inode 218712 was part of the orphaned inode list. yes
Inode 133351, i_blocks is 880, should be 888.
Sense: Unrecovered read error - auto reallocate failed
[26567.600333] sd 0:0:0:0: [sda] CDB: Write(10): 2a 00 03 80 00 9f 00 00 08 00
[26567.600349] end_request: I/O error, dev sda, sector With this tutorial (very good indeed) I managed to get the folder lost+found really full of my files but it starts with # and I can not do anytinh g with We Acted. yes
Free blocks count wrong for group #207 (1662, counted=2047).
Free blocks count wrong for group #84 (11007, counted=11010).
Inode 133960 was part of the orphaned inode list. This is actually the second time the HDD has run into this "unable to set superblock flags" issue - the previous time being two days ago - but the first time With a laptop that's somewhere around five years old now, this seems somewhat likely as an additional culprit, and it may simply be luck and persistence that save it.
It's been a great resource, and up until now I've been able to solve all of my own problems with just a bit of searching, but it seems luck's run out And i'm missing an EASY way to CHOOSE during the install to use ext3 and grub0.95 INSTEAD of ext4 and grub2. I don't have access to my terminal logs at the moment, but I can pull up any that are needed by request, to try and help shed some light on things. I was glad I've found your site in the hope of getting my hdd going again.