View previous topic :: View next topic |
Author |
Message |
phoenix_me Apprentice
Joined: 24 Dec 2003 Posts: 281 Location: Lubliniec
|
Posted: Thu Jan 12, 2012 11:19 pm Post subject: [RESOLVED] Can't boot after electricity failure |
|
|
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 |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21518
|
Posted: Fri Jan 13, 2012 12:10 am Post subject: |
|
|
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? |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54119 Location: 56N 3W
|
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. |
|
Back to top |
|
|
phoenix_me Apprentice
Joined: 24 Dec 2003 Posts: 281 Location: Lubliniec
|
Posted: Fri Jan 13, 2012 12:17 am Post subject: |
|
|
Hu wrote: | 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
Code: | ....
VFS: Mounted root (ext3 filesystem) readonly on device 8:2
Freeing unused kernel memory: 492 freed
Write protecting the kernel read-only data: 8192k
Freeing unused kernel memory: 884k freed
Freeing unused kernel memory: 468k freed |
Seems like no INIT process starts. I found also that I don't have /etc/inittab file ! _________________ phoenix
___
myslenie ma przyszlosc
___ |
|
Back to top |
|
|
phoenix_me Apprentice
Joined: 24 Dec 2003 Posts: 281 Location: Lubliniec
|
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
___ |
|
Back to top |
|
|
billium Apprentice
Joined: 22 Mar 2003 Posts: 185
|
Posted: Thu Jan 17, 2013 1:43 am Post subject: |
|
|
I'm going to be honest here and admit doing something slightly silly
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. |
|
Back to top |
|
|
alegioit Tux's lil' helper
Joined: 13 Jul 2007 Posts: 78
|
Posted: Mon Jul 08, 2013 7:00 pm Post subject: |
|
|
billium wrote: | I'm going to be honest here and admit doing something slightly silly
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. |
Same here guys! You've saved me about 2 hours of searching and ranting! Thanks! |
|
Back to top |
|
|
enzake n00b
Joined: 08 Oct 2014 Posts: 2
|
Posted: Wed Oct 08, 2014 5:51 am Post subject: |
|
|
billium wrote: | I'm going to be honest here and admit doing something slightly silly
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?
thanks |
|
Back to top |
|
|
Freeky Tux's lil' helper
Joined: 11 Mar 2011 Posts: 129 Location: Novosibirsk, Russia
|
Posted: Wed Oct 08, 2014 9:06 am Post subject: |
|
|
1) Boot from any LiveCD.
1a) Check your partitions (fsck, for example) 2) Chroot to your system.
3) Reemerge sysvinit.
4) Exit from chroot.
5) Reboot to your system from hdd. |
|
Back to top |
|
|
enzake n00b
Joined: 08 Oct 2014 Posts: 2
|
Posted: Wed Oct 08, 2014 9:21 am Post subject: |
|
|
Freeky wrote: | 1) Boot from any LiveCD.
1a) Check your partitions (fsck, for example) 2) Chroot to your system.
3) Reemerge sysvinit.
4) Exit from chroot.
5) Reboot to your system from hdd. |
hello,
i found another thing:
/sbin/rc sysinit
/sbin/rc boot
/sbin/rc default
/sbin/agetty 38400 tty1 linux
it worked to enter on my system and from there i was able to emerge again sysvinit
thanks! |
|
Back to top |
|
|
|