pentoo / pentoo-historical

read-only historical backup of pentoo from googlecode
https://code.google.com/p/pentoo/
2 stars 1 forks source link

Failed to boot after doing the PentooUpdater script #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install Pentoo 2013.0 RC1.1 on a box with nVidia display card
2. Do the update according to 
https://code.google.com/p/pentoo/wiki/PentooUpdater, but did not do the "For 
the First time" as I do not know how to change it and worried with break the 
system.
3. Then, follow the "On regular basis" step.
4. When running "etc-update", I select "-3" and remove the old files.
5. After that, I reboot the box and it halt and find the following message on 
the screen :

INIT: cannot execute "/sbin/mingetty"
INIT: ld "c4" respawning too fast: disabled for 5 minutes

What is the expected output? What do you see instead?

Boot to the prompt and waiting for typing "startx" to go to the desktop.

What version of the product are you using? On what operating system?

Pentoo 2013.0 RC1.1

Please provide any additional information below.

I install the Pentoo 2013.0 RC1.1 in this way :

http://samiux.blogspot.com/2013/03/howto-pentoo-20130-rc11-on-asus.html

Original issue reported on code.google.com by runner...@gmail.com on 30 Mar 2013 at 3:56

GoogleCodeExporter commented 9 years ago
You need to be a little more cautious for the first time you converting livecd 
into a proper install. As the warning says, read the errors during update and 
act accordingly.

I smell that you missed one of important steps. For example, forgot to run 
"deepclean" or revdep-rebuild.

Please reboot from livecd again, mount disk partitions to /mnt/gentoo in the 
right order (root, boot), swap and chroot to your pentoo setup on a harddisk 
(http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=6) and run 
the update steps again.
Post "rc-udate show" output here after that.

You can also review /var/log/portage/elog/summary.log for errors or 
recommendations you might missed.

FYI, I don't have that file either, but it boots just fine.

Original comment by blshkv on 30 Mar 2013 at 7:04

GoogleCodeExporter commented 9 years ago
ok, the /etc/inittab file (with faulty mingetty) is getting generated by 
"fixinittab" livecd script.
Once you have your chroot env ready, try the following:

disable fixinittab from rc-update:
 rc-update delete fixinittab
re-emerge inittab:
 emerge -1 sys-apps/sysvinit && etc-update

I'm checking if "emerge --depclean" suppose to clean up the livecd start up 
services..

Original comment by blshkv on 30 Mar 2013 at 7:45

GoogleCodeExporter commented 9 years ago
To answer your question on the IRC:
no, you don't need to reinstall even the new env is no longer bootable.
You can boot from liveusb and chroot to your pentoo on the harddisk.

I have started a new wiki page with suggestions above. Feel free to expand it 
with your experience: https://code.google.com/p/pentoo/wiki/PentooInstaller

Original comment by blshkv on 30 Mar 2013 at 8:30

GoogleCodeExporter commented 9 years ago
FYI, I tried upgrading rc1.1 by following the upgrading steps and I didn't have 
to rebuild anything manually.

I'll keep in the wiki just in case anyways. Hope it works for you too.

Original comment by blshkv on 31 Mar 2013 at 1:59

GoogleCodeExporter commented 9 years ago
Issue 131 has been merged into this issue.

Original comment by blshkv on 15 Apr 2013 at 11:53

GoogleCodeExporter commented 9 years ago
Re-opening, since the issue hasn't been resolved for the user

Original comment by blshkv on 15 Apr 2013 at 11:54

GoogleCodeExporter commented 9 years ago
seems false positive. Closing again

Original comment by blshkv on 16 Apr 2013 at 2:39