[RESOLVED] Can't boot after electricity failure

phoenix_me · Last edited by phoenix_me on Fri Jan 13, 2012 12:41 am; edited 1 time in total

My PC was hibernated. (hibernate-ram). During the hibernation there was an electricity failure (shortage). Right now when I am trying to boot the kernel is booting and then I have the following message:

Hu · Watchman Joined: 06 Mar 2007 Posts: 7679

We need more information. What kernel version are you running? What else is shown on screen before that? Do you use a custom initramfs or was it generated for you? Were you hibernating or sleeping? You say hibernate, but then you say you used the command that puts the system into a suspend-to-RAM ("sleep") state. Was the power failure while the system was entering sleep mode or while it was sleeping?

NeddySeagoon · Posted: Fri Jan 13, 2012 12:13 am Post subject:

phoenix_me,

Your system died with files open, as hibernate preserves the system state in RAM, so it can be resumed.

Boot with a liveCD. Do not mount any of your filesystems.
Run fsck on your root partition but do not allow fsck to 'fix' anything.
Just report the problems it finds.

fsck can often make matters worse.

What happens next, and if it can be recovered in place depends on the errors any your filesystem type.
Having a disk image or a full backup is a really good idea.

You really need an undo facility before you allow fsck to change your damaged filesystem.

Its safe to attempt mount -o ro /dev/sda3 /mnt/gentoo so you can have a look around and copy files off.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

phoenix_me · Posted: Fri Jan 13, 2012 12:17 am Post subject:

phoenix_me · Posted: Fri Jan 13, 2012 12:41 am Post subject:

I found the issue!
There was TWO issues at the time.
The first was electricity failure and I thought that it was main reason but it wasn't.
Seems like during the hibernate-ram system was doing emerge ! And is seems like the old sysvinit package was deleted and new one was not deployed yet. Then the hibernate-ram happened. There should be everything ok when resumed from sleep state but unfortunately there was a power issue and my system left without a sysvinit package.
Now I already reinstalled it and everything is working like a charm.

thanks...
_________________
phoenix
___
myslenie ma przyszlosc
___

billium · Apprentice Joined: 22 Mar 2003 Posts: 167

I'm going to be honest here and admit doing something slightly silly :oops:

Just did a world update and there was a block with sysvinit, so I thought I would unmerge the current sysvinit, then re-emerge.
Sadly I forgot to re-emerge sysvinit and got this error.

Fortunately I had another Gentoo with the sysvinit tarball.

All working now though.