No Boot on F12, saying something like: xxx already mounted

Place to discuss Fedora and/or Red Hat
Post Reply
User avatar
Basher52
guru
guru
Posts: 919
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

No Boot on F12, saying something like: xxx already mounted

Post by Basher52 » Sun Aug 01, 2010 12:55 pm

This is after I had an error on my last boot disk so I 'dd' it to an image then created a new disk(of same size, 200G).
Even tried rescue CD(from using the network start disk if that may make any difference) and that said that it can't find any Linux system at all.

I got an error at about 137M of the 'dd' so I KNEW some error might show up, but this......
I'm totally stumped, what do I do now?

User avatar
Basher52
guru
guru
Posts: 919
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Mon Aug 02, 2010 1:29 pm

Got some more info:

Last thing before the errors shows up;

EXT3-fs: mounted filesystem with ordered data mode.
mount: /dev/sda2 already mounted or /sysroot busy
mount: according to mtab /dev/sda2 is already mounted on /sysroot

the "mount:" lines repeats itself about 20 times then comes this;
Can't mount root filesystem
mapscrn: cannot open map file _iso15_

then come the "mount:" lines again for about 15-20 times and then last;

Can't mount root filesystem
Boot has failed, sleeping forever.

User avatar
Basher52
guru
guru
Posts: 919
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Tue Aug 03, 2010 4:55 pm

using parted I get this info of the disk:

Code: Select all

Number  Start    End       Size     Type     File system  Flags
 1          32.3kB  107MB   107Mb  primary ext3            boot
 2          107Mb  17GB     17.5Gb  primary ext3
 3          17.5GB  18.7GB 1078Mb  primary                  swap
 4          18.7GB  124GB  105Gb  primary
Trying to mount -t ext3 on /dev/sdc4 says:

mount: wrong fs type, bad option, bad superblock on /dev/sdc4,
missing codepage or helper prorgam, or other error
In some cases useful into is found in syslog - try
dmesg | tail or so

User avatar
Basher52
guru
guru
Posts: 919
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Wed Aug 04, 2010 11:03 am

Tried the other superblocks this is what it showed me:

Code: Select all

[root@kgdubben /]# fsck.ext3 -b 2654208 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Invalid argument while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 1605632 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Invalid argument while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 884736 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Invalid argument while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 819200 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Invalid argument while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 294912 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Invalid argument while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 229376 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 163840 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdc2

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@kgdubben /]# fsck.ext3 -b 98304 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdc2

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>

then I tried superblock 0 again and that gave me this:

Code: Select all

[root@kgdubben /]# fsck.ext3 -b 0 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
Superblock has an invalid journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

/1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data.  Clear<y>? yes

Inode 2 has a bad extended attribute block 34854.  Clear<y>? 
here I canceled that and tried some other super block again and that kinda gave me the same thing...:

Code: Select all

[root@kgdubben /]# fsck.ext3 -b 4096000 /dev/sdc2
e2fsck 1.41.9 (22-Aug-2009)
/1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 2 has a bad extended attribute block 34854.  Clear<y>? yes

Inode 2, i_blocks is 16, should be 8.  Fix<y>? yes

Inode 11 has a bad extended attribute block 34856.  Clear<y>? yes

Inode 11, i_blocks is 16, should be 8.  Fix<y>? yes

Inode 16 has a bad extended attribute block 34865.  Clear<y>? yes

Inode 16, i_blocks is 16, should be 8.  Fix<y>? yes

Inode 17 has a bad extended attribute block 34867.  Clear<y>? yes

Inode 17, i_blocks is 16, should be 8.  Fix<y>? yes

Inode 66 has a bad extended attribute block 34867.  Clear<y>? yes

Inode 66, i_blocks is 16, should be 8.  Fix<y>? 

/1: e2fsck canceled.

tried parted and that now showed the sdc2 as ext2:

Code: Select all

[root@kgdubben /]# parted /dev/sdc
GNU Parted 1.9.0
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: ATA WDC WD2000JD-00H (scsi)
Disk /dev/sdc: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  107MB   107MB   primary  ext3         boot
 2      107MB   17.6GB  17.5GB  primary  ext2
 3      17.6GB  18.7GB  1078MB  primary               swap
 4      18.7GB  124GB   105GB   primary
(parted) q

and the errors I showed up here is the one I had loooots of.
after I let that run for the hour and a half no errors was left and all I saw was files in 'lost+found'
all marked as #nnnnnnn where the n is just a number.

any suggestions?

User avatar
Basher52
guru
guru
Posts: 919
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Mon Aug 16, 2010 8:09 am

I added on old partition backup and then replaced some config files and we're back again :)

Post Reply