Never mind, what I'm seeing is Bug #537133.
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
I've just installed lucid on a diskless system. It boots from a usb key,
not pxe, but has an nfs root. It hangs in or just after init-bottom,
apparently because statd and portmap both exit immediately after
starting. My "fix" was to disable them both then add "nolock" to the
root mount options in f
I updated my nfs root Karmic install and tried again - same problem
persists.
Similarly, all of my Karmix systems are having troubles with NFS mounts
at boot time. Since Jaunty, IIRC, they all initially indicate that
they've failed to mount nfs volumes at boot time - usually with that
"hit esc to
I'm getting the same problem with lucid.
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Ever since Karmic was released, I have not been able to upgrade my
Jaunty root over nfs system. I get the message "inotify_add_watch
failed: bad address." as others have. I've tried manually upgrading the
mountall package to versions 1.8 and 2.2 with no luck. I'm running
kernel 2.6.31 that I compil
I'm still seeing this issue with mountall 1.0 in Karmic on an nfsroot, just as
Dolganov.
mountall freezes trying to remount root and the other nfs shares listed in
fstab, it won't work
as the neither portmap nor statd has started yet.
I haven't looked enough at the mountall sources, but it appea
I have "mountall 1.0" in karmic root upgraded from jaunty, and I can't boot
ltsp clients because of this bug
PS: Sorry for my english :)
Just like (http://www.mail-archive.com/ltsp-
disc...@lists.sourceforge.net/msg37462.html):
When I switch the new chroot to nfs (still basically
according to ht
Problem solved. Nice work!
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
This bug was fixed in the package mountall - 0.1.8
---
mountall (0.1.8) karmic; urgency=low
[ Scott James Remnant ]
* Further work on the fix from the previous version where the root
filesystem would always be considered "local", retain that from the
POV of the {virtual,lo
The one on the ubuntu-boot PPA works great. The one in Main does not.
I upgraded to the one in Main and it stalled at the same point it always
has. I manually "downgraded" to the one in the PPA and it booted it
fine.
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You rece
Thanks for that fix -- I will test it once I have backed up root and
report back later today :-)
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Yeah, phew. It works.
By the time I got to it a new mountall in Main had already superseded
your PPA version. And despite printing out ‹apt-cache policy mountall› I
didn’t realise what was going on. Sometimes you’re just struck by
blindness in the morning.
So, thank you Scott!
--
NFS root devic
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
The ubuntu-boot PPA has a new version of mountall which I hope will fix
this problem, please install that and let me know how it works out.
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
** Changed in: mountall (Ubuntu Karmic)
Status: In Progress => Fix Committed
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
** Changed in: mountall (Ubuntu Karmic)
Milestone: None => ubuntu-9.10-beta
--
NFS root device never ready
https://bugs.launchpad.net/bugs/430348
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
I too have this problem. although in a slightly different form. I have
/boot on a CompactFlash and root on an NFS server.
The entry in grub reads as follows:
title Ubuntu 9.10 kernel 2.6.31-6-generic NETBOOT
root(hd0,0)
kernel /vmlinuz-2.6.31-6-generic root=/dev/nfs
In case the people debugging this don't have a diskless pxe system to
work from, I wonder if the difference between what the mtab says and
what the fstab says is confusing mountall. Example:
fstab:
/dev/nfs/ nfs defaults0 0
mtab:
192.168.23.2:/export/diskless/fa
On Do, 2009-09-17 at 22:02 +, Lou Ruppert wrote:
> How did you get the sulogin to work for ctrl alt del?
I just looked around and made a minor edit. See the attachment.
** Attachment added: "control-alt-delete.conf"
http://launchpadlibrarian.net/31989770/control-alt-delete.conf
--
NFS r
How did you get the sulogin to work for ctrl alt del? I tried replacing
the shutdown line in the conf file for upstart with 'exec sulogin' but
it doesn't spawn the login. Also tried dash -i. I'm trying to debug
this problem as well, but you've gotten farther along on it than I have.
--
NFS roo
** Changed in: mountall (Ubuntu)
Status: Incomplete => In Progress
** Changed in: mountall (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Also affects: mountall (Ubuntu Karmic)
Importance: High
Assignee: Scott James Remnant (scott)
Status: In Progress
21 matches
Mail list logo
