| View previous topic :: View next topic |
| Author |
Message |
win_hater
n00b
Joined: 22 Feb 2004
Posts: 26
Location: US, Florida
|
 Posted: Fri Sep 10, 2004 8:07 am Post subject: Hard drive trouble |
 |
|
I live in Florida and I'm in an area that experienced a blackout. after I got my computer back up and running I get this error upon boot:
| Code: | vfs: Cannot open root device "hdc3" or ~[:12
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on ~[:12
|
and my root partition can't be loaded from the live cd.
I get the message | Code: | mount: wrong fs type, bad option, bad superblock on /dev/hdc3,
or too many mounted file systems
|
I know that I've got the right fs(ext2) and I can mount my boot(hdc1)
I think that my root partition might have become corrupted somehow during the power outage, I need to know what I can do to fix this, or how I can pull the important files off(got a research paper on it!).
_________________
My F@vorite software oxymoron : Microsoft Works |
|
| Back to top |
|
 |
golloza
Guru
Joined: 14 Mar 2004
Posts: 427
|
| Posted: Fri Sep 10, 2004 8:08 am Post subject: |
|
|
fsck it  |
|
| Back to top |
|
|
win_hater
n00b
Joined: 22 Feb 2004
Posts: 26
Location: US, Florida
|
| Posted: Fri Sep 10, 2004 8:30 am Post subject: |
|
|
this is what it said when I ran fsck /dev/hdc3
| Code: | Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/hdc3
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 |
_________________
My F@vorite software oxymoron : Microsoft Works |
|
| Back to top |
|
|
golloza
Guru
Joined: 14 Mar 2004
Posts: 427
|
| Posted: Fri Sep 10, 2004 9:13 am Post subject: |
|
|
man e2fsck:
| Quote: | -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 block-
size. 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.
If an alternative superblock is specified and the filesystem is not opened read-only, e2fsck will make sure that the primary
superblock is updated appropriately upon completion of the filesystem check.
|
Check your blocksize with tune2fs. |
|
| Back to top |
|
|
win_hater
n00b
Joined: 22 Feb 2004
Posts: 26
Location: US, Florida
|
| Posted: Fri Sep 10, 2004 7:12 pm Post subject: |
|
|
thanks, that did the trick. 
_________________
My F@vorite software oxymoron : Microsoft Works |
|
| Back to top |
|
|
|
Kernel & Hardware
