Gentoo and upgrading to baselayout-1.8.6.10-r1
I installed Gentoo and updated using
emerge rsync
emerge -u portage
emerge -u world
I found the etc-update command and used it to overwrite the existing conf files. Merrily went on my way installing mysql, php, apache etc. and got everything working together.
Until I rebooted my linode - I then had no access to it.
To cut a long story short I was able to pinpoint the problem down to updating baselayout. This presents me with 20 files that need to be updated:
/etc/DIR_COLORS
/etc/fstab
/etc/hosts
/etc/inputrc
/etc/issue
/etc/rc.conf
/etc/services
/etc/shells
/etc/conf.d/net
/etc/init.d/bootmisc
/etc/init.d/checkfs
/etc/init.d/checkroot
/etc/init.d/clock
/etc/init.d/consolefont
/etc/init.d/domainname
/etc/init.d/halt.sh
/etc/init.d/keymaps
/etc/init.d/modules
/etc/init.d/net.eth0
/etc/init.d/serial
I thought I had found the problem in conf.d/net so I replaced that with the original file - no luck. I couldn't see anything in the other files that could be causing problems - I tried replacing init.d/net.eth0 with the original file as well - but still no go.
I have a small 300 MB Debian configuration I used to mount the Gentoo disk, but could find no errors reported in the log files.
I guess I could take my dentists advice when I told him it hurt when I stuck my finger nail into the base of one of my teeth - "Well don't do that then!" - and just not update baselayout, but they seems like the easy way out.
Has anyone out there any ideas on what I'm missing?
Thanks
Geoff
4 Replies
caker
Linode Staff
Have you tried using the console to view the boot messages to see what's going wrong?
Does your new Gentoo profile stay running, even though you can't connect to it? If that's the case, you will be able to connect using the console. Check your ethernet settings, make sure you're using dhcp or you've setup static network settings…
If it boots and then is marked 'shutdown' after a minute or so, you might have to time connecting to the console right to catch the boot messages…
-Chris
It looks like I've mucked up file system check at boot up:
> * Starting devfsd…Started device management daemon v1.3.25 for /dev
[ ok ]
- Activating (possible) swap…modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
[ ok ]
- Remounting root filesystem read-only (if necessary)…modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
[ ok ]
- Checking root filesystem…fsck: fsck.xfs: not found
fsck: Error 2 while executing fsck.xfs for /dev/ROOT
[ ok ]
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
- Remounting root filesystem read/write…modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
[ ok ]
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
Setting hostname to geoffmeans… [ ok ]
Starting up RAID devices: … * Checking all filesystems…modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
modprobe: Can't open dependencies file /lib/modules/2.4.22-linode9-3um/modules.dep (No such file or directory)
fsck.ext2: No such file or directory while trying to open /dev/BOOT
/dev/BOOT:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
* Fsck could not correct all errors, manual repair needed [ !! ]
Give root password for maintenance
(or type Control-D for normal startup):
Ctrl-D completed the login with more complaints about not finding modules.dep, but the system is now up.
I'll have a closer look at the changes to /etc/init.d/checkfs and /etc/init.d/checkroot.
Thanks for your help
Geoff
caker
Linode Staff
You can also ignore the modprobe warnings – it's just the distro's init scripts trying to discover/load modules in a kernel that doesn't support (or need) them.
-Chris
Thanks
Geoff