F12 & Boot up problem
 

On my gateway server 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 just said that it can't find any Linux system at all.

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


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_ (think this is an old obsolete thing)

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

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


Anyone know how to fix this?

Did you get an error while dumping your disk with 'dd'? But you ignored the error and created a new disk anyway?

There is no other way (that I know of) than fsck to repair a corrupted ext3 disk, except professionell data recovery services.

/Tobias

I think your had a problem with your master boot record

I had faced the same problem before.
I couldn't find any partition on my hard disk driver
so I couldn't mount any of the old sda2 or sda5 ......
if you got the same problem as I did.
restore your mbr by using windows cd and type FDISK /MBR
it will let you see the partition,
after that you could mount them
hope that it could help you.
I use both windows and linux on my PC

@TobiasH Yeah there was an error while doing 'dd' but I had that last time i had some boot disk error too and it worked anyways.

@hoanglong1712, If I do this won't the grub boot be overwritten with windows's?


I can mount it using another Fedora computer and it's that one I 'dd' it to another physical disk and in there I could see all partitions
but not while using the recovery CD. I'll try TobaiasH's version first cos I think that seems less harmful for the grub boot :P

I tried fsck and it took me like 1 & ½ hour and it was showing errors on it seemed everything.
After that no errors at all, but I still get the same problem.
I don't wanna reinstall all the crap since I'll take me WAY more time and I can't even say I would remember it all lol

using parted I get this info of the disk:



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

You could try this:

Recover Corrupted Partition From A Bad Superblock:
http://www.cyberciti.biz/faq/recover...ted-partition/

/Tobias

Tried that and this is what it showed me:

[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:

[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...:

[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:

[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 more things you can suggest?
pleeeease :P

I believe your 'dd'-copy couldn't copy your original data because of a corruption on the disk. Now your copy is missing data because the original disk was corrupted.

I think this is the time when you'll have to reinstall the OS and restore the data from your offline backup.

Option 2: Leave the disk to Ibas or similar company to possibly retrieve your data = very expensive.

Sorry!

Well, I took an old 'dd' copy from April and used that.
Added all updates and since I every night pack conf files and stuff together and mail that to my mail account, I added those too.
Seems to be running perfect now :)
Let's see how long THIS disk will hold since it ain't new this either lol

It certainly pays off to have (regular) backups.

That sounds great!!! :D

I'm glad you got the system up'n running again!