CentOS won't boot since powercut/surge..

killsta · 30 May 2008 at 13:21

Lo all,

I run a home CentOS 5.1 server purely for email with Qmailtoaster.

Seem to have had a powercut/surge last night and now it won't boot.

Errors upon booting are:

No suspend signatures on swap, not resuming.
UFS: Can't find ext3 filesystem on dev dm-0.
mount: error mounting /dev/root on /sysroot as ext3: Invalid arguement
Kernel Panic - not syncing: Attempted to kill init!

Anybody have any ideas how to fix this? Tried rescue mode on CentOS install disk but it can't find any Linux partitions

Don't really want to have to wipe and reinstall

leezer3 · 30 May 2008 at 13:39

Your RAID array is toasted somehow.
Does it even show up in the controller BIOS, because Linux isn't seeing it full-stop?

Cheers

-Leezer-

killsta · 30 May 2008 at 13:41

There is no RAID array and never has been!

tntcoder · 30 May 2008 at 14:33

Hope you have good backups!

Can you try booting to a prompt via live cd or similar, and run fsck on the ext3 partitions? Should report any file system errors.

leezer3 · 30 May 2008 at 14:41

With the references to the dmraid driver & the fact that it's a server, I'd assumed there was probably a RAID array in there somewhere.
The number one problem is that it isn't recognising the root filesystem-

Code:

UFS: Can't find ext3 filesystem on dev dm-0.
mount: error mounting /dev/root on /sysroot as ext3: Invalid arguement

The underlying disk is probably either going to be missing entirely or have had the partition structure damaged by the surge.
First boot from any LiveCD- If the root drive is present, post the partitions list from the command:

Code:

sudo sfdisk -l

If the LiveCD can find & recognise your root partition, things may be recoverable, all depends on precisely what was toasted.

Cheers

-Leezer-

killsta · 30 May 2008 at 14:48

Cheers for the help.

Tried all that and it hda2 just seems to be completely goosed.

Just wiped it and am reinstalling now...only lost a few days worth of mail so not too bad :cool:

brummie · 30 May 2008 at 15:25

I had a similar problem when i used data writeback.
File system screwed and i lost everything. Now only used full journal