Home > Could Not > Could Not Set Up Superblock

Could Not Set Up Superblock

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 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 Free blocks count through no fault but my own I killed my partition table and the was unable get to any of my data. (4tb worth) because of the is how to and the Powered by vBulletin Version 4.2.2 Copyright © 2016 vBulletin Solutions, Inc. http://strobelfilms.com/could-not/could-not-set-up-superblock-mkfs-ext3.html

It worked for me several months ago. I'm still somewhat new to linux so to play with it and to help me learn more about it I use Kubuntu on an external hard drive connected via USB. Installing RPM Fusion, Multimedia Playback & Browser Plugins Trouble with graphic drivers? cheers.

Thank you, thank you! 8 Swamprat on July 11, 2010 said: I do believe I'm in business again. 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 Try at least 1.34 or preferably 1.35.

Fix? Anyway, I still have a problem : my disk was bootable and the partition is still displayed as bootable but it doesn't do anything When booting, it shows a black screen That maybe the superblock for the md device though. >.< Might be worth trying a few more superblocks, and trying to mount the raid device between attempts. 89 qurczak on January Getting nVidia or ATi cards working Are you a developer?

It worked for my 250GB SATA drive. Bug569259 - mkfs.ext2: Could not allocate block in ext2 filesystem while trying to allocate filesystem tables Summary: mkfs.ext2: Could not allocate block in ext2 filesystem while trying to alloca... My machine is back to like. 55 evidex on June 20, 2011 said: Great to hear!🙂 56 Rogério Madureira on July 4, 2011 said: All my nightmare is registered here: http://goo.gl/WWg9x And afterwards we can't boot the system anymore.

What do you think of my time saver to bypass the reboot? After the boot has finished then plug in the data connector for the SATA HD. I followed until "sudo fsck.ext4 -v /dev/xxx," which asked for fixes. Does having a finite number of generators with finite order imply that the group is finite?

The impression I got from other articles is once you've tried a valid backup superblock you've tried them all. The ‘process ID for the mount process is ‘ps -A | grep -i mount'. Please do not send me a PM asking for help... Again, I don't run that stuff.

Hardware mkfs question: Not enough space to build proposed filesystem while setting up superbl If this is your first visit, be sure to check out the FAQ by clicking the link 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 You saved my 2TB disk!🙂 23 bbking on December 8, 2010 said: hi! Uffffffff 90 braikar on January 21, 2012 said: What should be the output of a successful ‘sudo e2fsck -b block_number /dev/xxx' ?

How much effort (and why) should consumers put into protecting their credit card numbers? 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. Aborting without trying to recover. Please read the search suggestion thread in JL Ideas Reply With Quote 04-24-2004,12:31 AM #11 Bubba56 View Profile View Forum Posts Registered User Join Date Apr 2003 Location Land of Farve

Reply With Quote 04-21-2004,11:27 PM #5 Bubba56 View Profile View Forum Posts Registered User Join Date Apr 2003 Location Land of Farve and cheese Posts 153 HHmmm I also have a 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, I want to know if there is any command by that I can know the size of the file system before and after fsck run.

Last edited by Peasantoid (2010-01-27 00:12:57) Offline #4 2010-01-27 08:00:17 johnrl Member Registered: 2010-01-23 Posts: 12 Re: [SOLVED] "Superblock could not be read" error on install /etc/fstab (only uncommented lines):

Reply Link rick October 29, 2009, 6:42 pmDoes not seem to work, when I run dumpefs all it says:"Bad magic number in super-block while trying to open…"I already know the superblock If your raid isn't being detected, perhaps it's an issue with the other partitions/devices in the raid. I just wanted the OS to boot. I always found them problematic due to the particular packagers implementation in making the package.

For months I tried to find a solution to recover my data and you made my day. Before doign the following ‘su' to root. My wife did not make any backup the last 2 weeks (she is teacher) and everything is now against accessible. I can run ‘tail /var/log/messages' to watch for any errors that occur while the system attempts to mount the HD.

To find your UUID look in /dev/disk/by-uuid and use readlink to find the equivalent sdXX. Ask questions about Fedora that do not belong in any other forum. There is nothing wrong with that, but this is larger than 1024,... How can we recover from that? 116 evidex on March 21, 2013 said: If the data isn't important, use GParted or similar to delete the partition and recreate it with a

So the 'superblock' error is nothing to do with the disk size, integrity, or partition size - it's just the formatting process simply doesn't have enough memory. If no error occurs I should be able to immediately see if the repair process worked by viewing my data. The output you described is the ‘correct' output for a corrupted superblock. The issue, on my E3000 Linksys router, is lack of memory.

Find all posts by jhetrick62 #9 6th June 2006, 03:26 AM jhetrick62 Offline Registered User Join Date: Feb 2005 Location: Buffalo, Ny Posts: 875 Firewing is far more Browse other questions tagged partitioning fdisk or ask your own question. What is Extended Partition share|improve this answer edited Feb 25 '14 at 4:52 answered Feb 25 '14 at 4:41 Danatela 6,81892656 add a comment| Your Answer draft saved draft discarded Thanks.

Additional info: if we remove -g option in mkfs.ext2 while creating fs, it is success. However, the output of fsck.ext4 was different: [email protected]:~$ sudo fsck.ext4 -v /dev/sdc1 e2fsck 1.41.11 (14-Mar-2010) fsck.ext4: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc1 For me it was not so easy, when I was trying to use backup super block, it always failed for all backups with same error: ########## sudo e2fsck -b 229376 /dev/sdb2 thank you for your help and guidance. 2 evidex on May 10, 2010 said: Wow, that would be a lot of data to lose!

Run sudo mke2fs -n /dev/xxx which will give you a list of alternate superblocks to use, down at the very bottom. Your disk is 3TB in size. 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. 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

It looks like this Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208 Pick a superblock and run sudo e2fsck -b block_number /dev/xxx replacing the block_number Yes i know hdparm but dd schould be ab better test, i think i read of it anywhere. 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. Notes on my issue are belowI was getting following error when mounting.