LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   cant mount old partition (https://www.linuxquestions.org/questions/linux-newbie-8/cant-mount-old-partition-51403/)

hydro 03-23-2003 11:21 PM

cant mount old partition
 
Hello,

This partition contains my old system(linux redhat 8.0), by old i mean couple of months

parted-> print shows

Disk geometry for /dev/hda: 0.000-19077.187 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 101.975 primary ext3 boot
2 101.975 6997.060 primary ext3
4 6997.061 18567.312 extended lba
5 6997.091 18567.312 logical ext3
3 18567.312 19077.187 primary linux-swap

[root@Apophis pavel]# /sbin/fsck -t ext3 -V /dev/hda2
fsck 1.27 (8-Mar-2002)
[/sbin/fsck.ext3 (1) -- /dev/hda2] fsck.ext3 /dev/hda2
e2fsck 1.27 (8-Mar-2002)
Group descriptors look bad... trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/hda2
The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

how can i get it back?

/dev/hda2 is the nonworking drive

Mara 03-24-2003 11:07 AM

fsck suggests it to you:
Quote:

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 alternate superblock:
e2fsck -b 8193 <device>
It's a good suggestion. Try
e2fsck -b 8193 /dev/hda2
It will try to read backup superblock.

hydro 03-24-2003 12:06 PM

even though its ext3 not ext2, running the command u gave me returns the same exact error message, asking me to do e2fsck -b 8193

Mara 03-24-2003 12:12 PM

So there are more to try:
-b 16384
-b 32768
There's no difference between ext2 and ext3 at this point, AFAIK.

hydro 03-24-2003 01:34 PM

nope still get the bad magic number error like in the top

Mara 03-24-2003 01:44 PM

Are you sure it's really ext2/ext3? Maybe you installed Reiser? Or maybe you formatted it later?

fsbooks 03-24-2003 06:34 PM

8193 is a number hardcoded into the error message, and is likely not the correct number for any particular disk. The actual location is dependent on the blocksize, and there are more than one alternative location. I suggest reading the manpage for e2fsck. Someone wrote these manpages for a reason, you know :-) I have, however, included (as least some of) the relevant parts from it below:

-b superblock
Instead of using the normal superblock, use an
alternative superblock specified by superblock.
This option is normally used when the primary
superblock has been corrupted. The location of the
backup superblock is dependent on the filesystem's
blocksize. For filesystems with 1k blocksizes, a
backup superblock can be found at block 8193; for
filesystems with 2k blocksizes, at block 16384; and
for 4k blocksizes, at block 32768.

Additional backup superblocks can be determined by
using the mke2fs program using the -n option to
print out where the superblocks were created. The
-b option to mke2fs, which specifies blocksize of
the filesystem must be specified in order for the
superblock locations that are printed out to be
accurate.

hydro 03-25-2003 02:54 PM

sadly none of the mke2fs -n superblocks it listed worked :/

netfire4 08-30-2005 01:31 PM

same exact problem
 
New linux user

I understand what I did and I was an idiot but it might help for you to know ... lightswitch runs computer
I mounted my sata drive and then halted the computer and walked away i think i flipped the switch before it finished shutting down... I am running fedora 4
the drive i currupted is a ntfs with a windows partition on it that i was only using for music is there any way to get my music back error messages....

[root@localhost ~]# e2fsck -b 8193 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>
[root@localhost ~]#
[root@localhost ~]# mke2fs -n /dev/sdb1
mke2fs 1.37 (21-Mar-2005)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
24903680 inodes, 49783419 blocks
2489170 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=50331648
1520 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872

[root@localhost ~]# e2fsck -b 32768 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

[root@localhost ~]# e2fsck -b 98304 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

[root@localhost ~]# e2fsck -b 163840 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

[root@localhost ~]# e2fsck -b 229376 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

[root@localhost ~]# e2fsck -b 294912 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>

[root@localhost ~]# e2fsck -b 819200 /dev/sdb1
e2fsck 1.37 (21-Mar-2005)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct 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 alternate superblock:
e2fsck -b 8193 <device>
....
thanks for the help in advance
ps would it be better to just wait for a xp restore disk and fuck with it on the xp side


All times are GMT -5. The time now is 06:45 PM.