FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 04-12-2008, 07:58 PM
Warren Togami
 
Default Stuck at NFS root boot in F9

Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys

At this point during NFS root boot it gets stuck.

http://people.redhat.com/wtogami/temp/nfsrootboot.txt
Here is console redirected to serial and a SysRQ-T after it got stuck.

Should nash-hotplug still be running at this point?

init=/test.sh containing "exec /bin/bash -l -i" successfully drops me to
a shell, confirming that it did actually mount the filesystem and run
init. In this shell I see a process running "/bin/nash /init auto".
Should I still be seeing this after switchroot?

This problem utterly breaks LTSP so I really hope we can figure out what
is going on before F9.

I am uncertain when this problem began. Prior to April 5th I was
running Fedora 8 on my LTSP development laptop. Both F-8 and F-9
chroots were PXE and NFS root booting from the F-8 host to thin clients
and virtual machines just fine. Now with F-9 host, F-8 chroots continue
to boot fine, but I see this F-9 problem.

Any ideas what could possibly be going on? I am not even sure what
component to file against. I tried F-9 kernel/mkinitrd/upstream going
back until mid-March in the F-9 chroot and it doesn't seem to change
this behavior.

Warren Togami
wtogami@redhat.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-13-2008, 07:41 AM
Callum Lerwick
 
Default Stuck at NFS root boot in F9

On Sat, 2008-04-12 at 15:58 -0400, Warren Togami wrote:
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
>
> At this point during NFS root boot it gets stuck.

> Should nash-hotplug still be running at this point?
>
> init=/test.sh containing "exec /bin/bash -l -i" successfully drops me to
> a shell, confirming that it did actually mount the filesystem and run
> init. In this shell I see a process running "/bin/nash /init auto".
> Should I still be seeing this after switchroot?
>
> This problem utterly breaks LTSP so I really hope we can figure out what
> is going on before F9.
>
> I am uncertain when this problem began. Prior to April 5th I was
> running Fedora 8 on my LTSP development laptop. Both F-8 and F-9
> chroots were PXE and NFS root booting from the F-8 host to thin clients
> and virtual machines just fine. Now with F-9 host, F-8 chroots continue
> to boot fine, but I see this F-9 problem.
>
> Any ideas what could possibly be going on? I am not even sure what
> component to file against. I tried F-9 kernel/mkinitrd/upstream going
> back until mid-March in the F-9 chroot and it doesn't seem to change
> this behavior.

I tried upgrading my laptop from F8 to F9-beta, which only resulted in
this *exact* same behavior. It hangs at the same point. Will start a
shell if I put init=/bin/bash on the command line. nash-hotplug is still
running. It does this even if I boot with the previously working F8
kernel.

So all this would indicate that this problem is not specific to PXE/NFS
boot, and is not specific to any kernel. Is upstart b0rked somehow? Or
is it a hotplug problem?

In the mean time my laptop is out of commission, and I am at a loss as
to how to diagnose this problem. Which is highly inconvenient to getting
any work done. Silly me, thinking that a beta would at least make it as
far as starting init. Babies eaten: check.

Note that I can boot a rescue disk. I've tried updating it many times
over the past week, with no luck. I've tried nuking and reinstalling
upstart, initscripts and the kernel several times, no luck there either.
I've tried relabeling the filesystem, and tried booting with selinux
disabled, still won't boot.

Help?
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-13-2008, 03:20 PM
Warren Togami
 
Default Stuck at NFS root boot in F9

I figured out that this problem is being caused by a missing package in
the chroot because LTSP tries to be as minimal as possible.


Eric Harrison figured out that it was event-compat-sysv.

Is it a bug that nothing in the base system has a dependency on
event-compat-sysv? Relying on comps groups alone isn't entirely robust.
This seems to be also how some F8 to F9 upgrade failures are getting
stuck during boot as well.


Perhaps initscripts should Requires event-compat-sysv? It doesn't seem
to boot at all without it.


Warren Togami
wtogami@redhat.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-14-2008, 01:42 AM
Warren Togami
 
Default Stuck at NFS root boot in F9

Callum Lerwick wrote:

On Sun, 2008-04-13 at 11:20 -0400, Warren Togami wrote:
I figured out that this problem is being caused by a missing package in
the chroot because LTSP tries to be as minimal as possible.


Eric Harrison figured out that it was event-compat-sysv.


That did it!

Is it a bug that nothing in the base system has a dependency on
event-compat-sysv? Relying on comps groups alone isn't entirely robust.
This seems to be also how some F8 to F9 upgrade failures are getting
stuck during boot as well.


Seems like a bug to me. This breaks yum upgrades.



https://bugzilla.redhat.com/show_bug.cgi?id=442291
Yeah, it seems nothing requires event-compat-sysv. I requested that we
add a dependency on it for Fedora 9. We should keep that dependency at
least until we no longer need it (and the OS actually boots without it).


Warren Togami
wtogami@redhat.com

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-14-2008, 06:39 AM
Callum Lerwick
 
Default Stuck at NFS root boot in F9

On Sun, 2008-04-13 at 11:20 -0400, Warren Togami wrote:
> I figured out that this problem is being caused by a missing package in
> the chroot because LTSP tries to be as minimal as possible.
>
> Eric Harrison figured out that it was event-compat-sysv.

That did it!

> Is it a bug that nothing in the base system has a dependency on
> event-compat-sysv? Relying on comps groups alone isn't entirely robust.
> This seems to be also how some F8 to F9 upgrade failures are getting
> stuck during boot as well.

Seems like a bug to me. This breaks yum upgrades.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-14-2008, 05:13 PM
Bill Nottingham
 
Default Stuck at NFS root boot in F9

Callum Lerwick (seg@haxxed.com) said:
> > Is it a bug that nothing in the base system has a dependency on
> > event-compat-sysv? Relying on comps groups alone isn't entirely robust.
> > This seems to be also how some F8 to F9 upgrade failures are getting
> > stuck during boot as well.
>
> Seems like a bug to me. This breaks yum upgrades.

Do you have your yum/upgrade log? There's no reason it shouldn't be
pulled in on upgrades.

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-16-2008, 12:20 AM
Callum Lerwick
 
Default Stuck at NFS root boot in F9

On Mon, 2008-04-14 at 13:13 -0400, Bill Nottingham wrote:
> Callum Lerwick (seg@haxxed.com) said:
> > > Is it a bug that nothing in the base system has a dependency on
> > > event-compat-sysv? Relying on comps groups alone isn't entirely robust.
> > > This seems to be also how some F8 to F9 upgrade failures are getting
> > > stuck during boot as well.
> >
> > Seems like a bug to me. This breaks yum upgrades.
>
> Do you have your yum/upgrade log? There's no reason it shouldn't be
> pulled in on upgrades.

No, but I have 5 other machines to upgrade now that I know the
problem...

On another machine, if I do a full "yum upgrade", event-compat-sysv does
indeed get pulled in. ...But that's not what I did. My laptop is rather
limited in resources, "only" 512mb RAM and a couple GB free, so I
figured it would be best to do a staged upgrade. First I decided to
upgrade my key applications, "yum update galeon evolution". Through a
long convoluted chain of dependencies, this ends up upgrading mkinitrd,
which requires updating initscripts, which pulls in upstart. This
resulted in a raft of file collisions with sysvinit, and fails during
the transaction test. To get around it, I just "rpm -e --nodeps
sysvinit" figuring upstart was supposed to replace it anyway. I assumed
package dependencies would do their job and fix things or at the very
least alert me to any problems. Obviously, this did not happen. After
the first run, I did a full "yum update" to get the rest of the
packages, this fails to bring in event-compat-sysv since I manually
removed sysvinit, leaving you with an un-bootable system even though
"package-cleanup --problems" indicates no problems.
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 
Old 04-16-2008, 12:49 AM
Bill Nottingham
 
Default Stuck at NFS root boot in F9

Callum Lerwick (seg@haxxed.com) said:
> the transaction test. To get around it, I just "rpm -e --nodeps
> sysvinit" figuring upstart was supposed to replace it anyway.

Well, that's the issue, then. Don't do that.
(Seriously, this would happen if you did a --nodeps removal
of any package that is obsoleted by something in the next
release.)

Bill

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
 

Thread Tools




All times are GMT. The time now is 10:17 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org