On Tue, Dec 06, 2005 at 08:03:55AM -0500, Michael George wrote:
> On Mon, Dec 05, 2005 at 05:29:19PM -0300, Arturo 'Buanzo' Busleiman wrote:
> > Michael George wrote:
> > > If anyone has any suggestions, I'd like to find a way out of this other
> > > than reinstalling the system. Such a thing might happen again in the
> > > future to a non-development system and I'd like to know the way to get it
> > > working again.
> >
> > Any kernel messages or syslog entries during the chrooted work?
>
> Embarassingly, I didn't think to check that... I am out with meetings
> today but I should be able to get to it again tomorrow and try it.
>
> Thanks for all your suggestions and comments! When I have more info, I
> will report back to this thread. Hopefully we can solve it w/o a
> reinstall.
Okay, I have to oddities:
1. system will not proceed in boot process beyond the "configuring
system to use udev"
2. when chrooting into the system, some ports will not build. Notably,
udev will not (re)build.
I booted the system (to the 2005.1 Live/Universal CD), chrooted, and I'm
trying to re-emerge udev. Using debug mode on the emerge, I get:
livecd / # emerge -vd udev
Calculating dependencies
Parent: None
Depstring: sys-fs/udev
Candidates: ['sys-fs/udev']
ebuild: sys-fs/udev-070-r1
binpkg: None
-
Parent: ebuild / sys-fs/udev-070-r1 merge
Depstring: sys-apps/hotplug-base !bootstrap? ( sys-devel/patch )
!bootstrap? ( sys-devel/patch ) sys-apps/hotplug-base
>=sys-apps/baselayout-1.8.6.12-r3
Exiting... None
...done!
>>> emerge (1 of 1) sys-fs/udev-070-r1 to /
/var/log/messages (outside the chroot) has nothing written to it to
indicate disk errors or anything.
dmesg also shows no new entries.
I can, though emerge other ports, like hotplug, with no problem.
Back to problem #1:
Another thing I noticed is that "route" inside the chroot will not
complete. It prints the headers and then sits there doing nothing.
I checked the logs for the system on the HDD, and it appears that the
boot process cannot open /dev/console and agetty cannot open any of the
/dev/ttyX devices.
I am running baselayout 1.11.13-r1, so it's not supposed to have
problems if the files aren't there. In addition /dev on that partition
is fully populated (though /dev/console has 600 perms, not 660)...
--
-M
There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.
--
gentoo-user@gentoo.org mailing list
