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 For many more details, say man 8 mount .any clues on this? 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 Thanks for the post! navigate here
No problems with my data! You saved my 2TB disk!🙂 23 bbking on December 8, 2010 said: hi! you saved my busted filesystem and the beast lives again! 127 rihend on December 21, 2013 said: Reblogged this on Henri Sekeladi - Sebuah Catatan Perjalanan. 1 mount: wrong fs type, Glad to hear it worked! 70 nicola on October 1, 2011 said: just now it s running additional passes to resolve blocks claimed by more than one inode.. http://www.linuxquestions.org/questions/linux-general-1/ext2-fs-unable-to-read-superblock-35462/
I can mount another but another is missing superblock. yes Free blocks count wrong for group #368 (32254, counted=27774). My second question is that I am guessing the various backups are from different occasions, is there any way to deduce their order of creation, ie: which is most recent? Can a mathematician review my t-shirt design?
If it's not, repeat the steps, but restore a different backup superblock🙂 Share this:TwitterFacebookGoogleLike this:Like Loading... Add 8192 by the first, and you get the second (8193), add one more, and you got the third, and so on, and so on. Used: $ fsck -b 32768 /dev/sda6 to fix.Should have used "-a" option to automatically accept fixes because it had a gazillion complaints and I had to lean on the "y" key How To Recover Superblock In Linux Not sure where to post this, so figured I'd start here.
You get the picture I suppose .What does that do?screen says this:fsck 1.40 (29-Jun-2007)e2fsck 1.40 (29-Jun-2007)fsck.ext3: No such file or directory while trying to open /dev/sdb1The superblock could not be read Advanced Search Forum Community Help: Check the Help Files, then come here to ask! Use the install cd in rescue mode or a linux bootdisk to access your system. have a peek here Any thoughts?
Low number superblocks give me this error: Code: $ sudo e2fsck -f -b 32768 /dev/VolGroup00/LogVol01 e2fsck 1.42.7 (21-Jan-2013) e2fsck: Attempt to read block from filesystem resulted in short read while trying The Superblock Could Not Be Read Or Does Not Describe A Correct Ext2 Unless I find a different route to go by by the time I am done with file transfers. Got Leenucks? :: Arch: Power in simplicity :: Get Counted! The output you described is the ‘correct' output for a corrupted superblock.
My first question is whether your method above will work for me despite the empty directory structure having been written? More Help I have a LVM2 partition that has become unreadable. E2fsck Bad Magic Number In Superblock Such an accident is almost impossible to fix, and it's easier simply to start again. Bad Magic Number In Superblock Resize2fs Thanks! 122 russ on August 21, 2013 said: thanks a lot!
formaldehyde_spoonSeptember 19th, 2010, 08:28 AMThere is no other route. check over here After that it was the familiar start-up process. e2fsck: bad magic number in super-block while trying to open /dev/VolGroup00/LogVol01 the superblock could not be read or does not describe a correct ext2 filesystem. thanks 101 Botas on May 24, 2012 said: Thanks a lot!! Dumpe2fs: Bad Magic Number In Super-block While Trying To Open
Add 8192 by the first, and you get the second (8193), add one more, and you got the third, and so on, and so on. Another thing which might speed up the process is to start with the latest superblock backup, which I assume is the one with the greater number, what do you think? 68 clean? his comment is here I have 2 major projects on that partition.
Registered Linux User #392717 :: Blog thingy Offline #8 2010-05-22 18:17:54 trusktr Banned From: .earth Registered: 2010-02-18 Posts: 907 Website Re: [Solved] The superblock could not be read hey .:B:. Bad Magic Number In Superblock While Trying To Open /dev/sda2 EXT2-fs: unable to read superblock cramfs: wrong magic FAT: unable to read boot sector isofs_read_super: bread failed, dev=09:00, iso_blknum=16, block=32 Kernal panic: VFS: Unable to mount root fs on 09:00" Does As it is showing some data loss during fsck.
just wanna thank u…🙂 65 evidex on September 22, 2011 said: No problem, glad to hear it helped! 66 christine on September 26, 2011 said: well… i did as was written An Array of Challenges #2: Separate a Nested Array changing location of texmf folder for use across multiple computers (OS X / Apple) How to make a shell read the whole I've done this with NTFS partitions in Windows before, but I'm not sure of a solid procedure in Linux. Ext2fs_open2: Bad Magic Number In Super-block Forum New Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links Today's Posts View Site Leaders What's New?
ebakunin Linux - General 2 06-16-2002 11:37 PM All times are GMT -5. And I'd back up all that data now, while it's working, in case it decides to stop doing so again suddenly. That's why I wanted to know what should the correct output be if the operation succeeds… It still sorted the problem somehow, when I restarted the superblock was good again eventhough weblink anyway, please help.
ubuntu mount hard-disk ext3 share|improve this question edited Jun 15 '13 at 19:41 bahamat 19.1k3681 asked Jun 15 '13 at 18:53 AkshaiShah 1,0362108 add a comment| 3 Answers 3 active oldest Consider it a birthday present😉 75 Amida_Kun on October 14, 2011 said: Estuve por lo menos dos horas intentando recuperar mis datos, ya al final di con tu post, y salvaste In fact, almost all problems I can't fix myself, UF has found a cure🙂 14 MadJestyr on September 6, 2010 said: Thanks! 15 2ma on September 9, 2010 said: hey, I Internet is a better place with you. 48 evidex on May 31, 2011 said: Glad to help mate🙂 49 ilium007 on June 10, 2011 said: Hi - I have tried everythign
I found several articles about using fsck, but until I found your site I hadn't seen anything telling me how to find where the Superblock backups are stored. Any clues?Thanks,Dave--Kernelnewbies: Help each other learn about the Linux kernel.Archive: http://mail.nl.linux.org/kernelnewbies/FAQ: http://kernelnewbies.org/faq/ Jim Bauer 2003-05-23 00:49:48 UTC PermalinkRaw Message Post by David WuerteleI have an EXT2 filesystem on a file that Every single one gives an error: [I]The superblock could not be read or does not describe a correct ext4 filesystem. Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Tags Search LQ Wiki Search Tutorials/Articles Search
i am also having the same message except i am booting from my one and only linux drive.i get that same error message about the superblock thingie. Your sdb1 partition has not been formatted as ext2, hence you can't mount it as ext2. You can find out the current partitioning of a disk using the fdisk command. So she read that this command would destroy all data: dd if=/dev/zero of =/dev/sdd well of course it did delete all the data but also wiped out all the super blocks.
Thx again 115 roger burney on March 21, 2013 said: A friend wanted to erase all the data on her disk. k33bzSeptember 19th, 2010, 09:25 AMThere is no other route. John Mays bobthebear View Public Profile View LQ Blog View Review Entries View HCL Entries Visit bobthebear's homepage! My advice would be to backup the data on your raid, rebuild it, and copy back your data.
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. Closing. What do you think of my time saver to bypass the reboot? Find More Posts by bulliver View Blog 11-14-2002, 03:53 PM #3 bobthebear LQ Newbie Registered: Nov 2002 Posts: 8 Original Poster Rep: As soon as I start the installation.
Can someone give an example ?