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:

Code:

sh: cannot set terminal process group (-1): Inappropriate ioctl for device
sh: no job control in this shell
sh-4.2# _

I have no idea what to do and what's wrong ! Please help._________________phoenix
___
myslenie ma przyszlosc
___

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

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?

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?

It was sleep mode (hibernate-ram). The system was in sleep mode for some time and then there was a power failure.
Last lines from dmesg

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.

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.

Hello,

I have the same problem, my system don't want to boot anymore and i remember that i've uninstalled something that was blocking something else with a name like sysinit etc when i was emerge world. So when the power went down the problem is here. how can i reinstall that sysvinit again or what i must do to make my gentoo work/boot again without this error?