Sponsored Content
Operating Systems Linux Help! Boot failure - corrupt superblock Post 51890 by alarmcall on Friday 4th of June 2004 02:22:43 PM
Old 06-04-2004
Help! Boot failure - corrupt superblock

Hi everyone,

OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here.

Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake OS wouldn't boot!

I've got an ATA disc that is dual booted with windows 2000 and Mandrake 9.0. During boot time I get as far as selecting the Mandrake OS and then it starts to check the filesystem...I get the following error message:

<snip>

/dev/hda13: The superblock could not be read or does not describe a current ext2 filesystem. 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 with an alternative superblock:

e2fsck -b 8193 <device>

</snip>

I am then given the option of "repairing the errors"...

<snip>

fsck.ext3: invalid argument while trying to open /dev/hda13

</snip>

All other devices (partitions) are recovered and given a "clean" status. It then prompts with:

Failed to check filesystem. Do you want to repair (Y/N)?

At which point i can get a command prompt.

Now I tried the suggested method (e2fsck) without success using several different superblock location pointers(?) - i.e. 8193, 16387 and other multiples of 8193.

I also tried to use the rescue mode with the mandrake 9.0 installation CD1 and can mount all partitions (apart from hda13 - my /home partition) under /mnt. I did also try commenting out the relevant mount command of the /home partition in fstab, but it still did not boot.

Now I'm a relative newcomer to linux and am (more than) a bit stuck. Can anyone help me recover this situation or point me in the right direction?

Thanks in advance for any thoughts on this!
 

9 More Discussions You Might Find Interesting

1. Solaris

How to corrupt a superblock?

I need to corrupt a superblock of a mounted device in a soalris m/c and check recovery from an alternate superblock. How can this be done? (2 Replies)
Discussion started by: sujathan
2 Replies

2. Linux

Boot failure

Hi all I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
Discussion started by: joshighanshyam
2 Replies

3. Solaris

ultra 10 boot warning---corrupt label

Hi All, Any idea why i'm having this warning during boot: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0 (dad1): corrupt label - wrong magic number This happens after I added another ide HD and reinstall it from solaris 10 to solaris 8. Thanks in advance. (7 Replies)
Discussion started by: itik
7 Replies

4. Solaris

INT18 boot failure

I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
Discussion started by: priky
3 Replies

5. Solaris

Boot failure

I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot. SunOS Release 5.10 Version Generic_127128_11 32-bit Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved. Use... (3 Replies)
Discussion started by: Sesha
3 Replies

6. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies

7. UNIX for Advanced & Expert Users

Linux on vmware won't boot due to corrupt library file!

We have an issue here: The libc.so.6 file (link) is corrupted and it causes the system unbootable. It even doesn't boot to single user mode. How can we boot the system to fix the library file? Or is there any other solutions for this issue? Here are some boot messages:... (6 Replies)
Discussion started by: aixlover
6 Replies

8. Solaris

Failure to boot v445

Hi Guys, I have a small problem with a v445 which I have been informed will only boot with the reconfigure option enabled. It is attached to HP SAN storage using qla2300 FCA's with a Veritas encapsulated rootvoldg (No Laughing here please) when I try a reboot I get the following error. ... (5 Replies)
Discussion started by: gull04
5 Replies

9. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
DUMPE2FS(8)						      System Manager's Manual						       DUMPE2FS(8)

NAME
dumpe2fs - dump ext2/ext3/ext4 filesystem information SYNOPSIS
dumpe2fs [ -bfghixV ] [ -o superblock=superblock ] [ -o blocksize=blocksize ] device DESCRIPTION
dumpe2fs prints the super block and blocks group information for the filesystem present on device. Note: When used with a mounted filesystem, the printed information may be old or inconsistent. OPTIONS
-b print the blocks which are reserved as bad in the filesystem. -o superblock=superblock use the block superblock when examining the filesystem. This option is not usually needed except by a filesystem wizard who is examining the remains of a very badly corrupted filesystem. -o blocksize=blocksize use blocks of blocksize bytes when examining the filesystem. This option is not usually needed except by a filesystem wizard who is examining the remains of a very badly corrupted filesystem. -f force dumpe2fs to display a filesystem even though it may have some filesystem feature flags which dumpe2fs may not understand (and which can cause some of dumpe2fs's display to be suspect). -g display the group descriptor information in a machine readable colon-separated value format. The fields displayed are the group number; the number of the first block in the group; the superblock location (or -1 if not present); the range of blocks used by the group descriptors (or -1 if not present); the block bitmap location; the inode bitmap location; and the range of blocks used by the inode table. -h only display the superblock information and not any of the block group descriptor detail information. -i display the filesystem data from an image file created by e2image, using device as the pathname to the image file. -x print the detailed group information block numbers in hexadecimal format -V print the version number of dumpe2fs and exit. BUGS
You need to know the physical filesystem structure to understand the output. AUTHOR
dumpe2fs was written by Remy Card <Remy.Card@linux.org>. It is currently being maintained by Theodore Ts'o <tytso@alum.mit.edu>. AVAILABILITY
dumpe2fs is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net. SEE ALSO
e2fsck(8), mke2fs(8), tune2fs(8). ext4(5) E2fsprogs version 1.44.1 March 2018 DUMPE2FS(8)
All times are GMT -4. The time now is 01:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy