nfsroot not working anymore in 9.10

[SteF]

After trying to run correctly a PXE/NFSroot Ubuntu 9.10 I gave up.

Until now, it was running fine with other Ubuntu version 8.04, 8.10, 9.04, but now I'm not able to mount automatically /home anymore, and the root fs is mounted on ip_server:/home/nfsroot/ubuntu-9.10-desktop-i386 instead of /dev/nfs.

I follow the same procedure (https://help.ubuntu.com/community/DisklessUbuntuHowto) as before for booting by PXE the Ubuntu 9.10, and installing the system by NFS, but no way to get rid of it.

My old 9.04 stills work fine with the same server, and same target (PXE client).

Something change in the init procedure from 9.04 to 9.10, but I not able to find out what.

If somebody is interested in resolving it, I can provide more details, and reproduce it again.

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage , so I have classified this bug as a bug in nfs-utils package.

[SteF (nexus6-luceo)]

Ok thanks.

Regards

On Wed, 16 Dec 2009 20:33:31 -0000, Kamus <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This bug did not have a package associated with it, which
> is important for ensuring that it gets looked at by the proper
> developers. You can learn more about finding the right package at
> https://wiki.ubuntu.com/Bugs/FindRightPackage , so I have classified
> this bug as a bug in nfs-utils package.
>
> ** Package changed: ubuntu => nfs-utils (Ubuntu)

--
We can change

[Steve Langasek (vorlon)]

> the root fs is mounted on ip_server:/home/nfsroot/ubuntu-9.10-desktop-i386 instead of /dev/nfs.

Why is this a problem, exactly?

What does the client's fstab look like?

[SteF (nexus6-luceo)]

Hello Steve,

on my running Ubuntu 9.04 PXE system, I got :
---------------------------------------------
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/nfs / nfs defaults 1 1
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0
0
/dev/scd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
hal9000:/home /home nfs hard 0 0

$ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 1677788 0 1677788 0% /lib/init/rw
varrun 1677788 360 1677428 1% /var/run
varlock 1677788 0 1677788 0% /var/lock
udev 1677788 128 1677660 1% /dev
tmpfs 1677788 708 1677080 1% /dev/shm
rootfs 480719104 304585728 151714048 67% /
lrm 1677788 2192 1675596 1%
/lib/modules/2.6.28-17-generic/volatile
hal9000:/home 480719104 304585728 151714048 67% /home

$ uname -a
Linux tron 2.6.28-17-generic #58-Ubuntu SMP Tue Dec 1 18:57:07 UTC 2009
i686 GNU/Linux

The same system booting Ubuntu 9.10, I got :
---------------------------------------------
$ cat fstab
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/nfs / nfs defaults 1 1
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0
0
/dev/scd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0
hal9000:/home /home nfs hard 0 0

The 'df' can't be done as like this system is not booting, he can go
further when booted in single user mode from TFTP server.

1) So when booting in normal mode the system is waiting indefinitively
with error :
-----------------------error------------------------
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home:waiting fr hal9000:/home

modem-manager: Loaded plugin Gobi
blablabla

^C
mountall: Cancelled

still waiting and nothing more, the only thing I can do is a Ctrl+Alt+Del
:-(
----------------------error-------------------------

2) but booting in single user mode the system is going further, and
prupose to me the "Recovery Menu", I choose "resume", and then it comes to
the login prompt, I enter as root.

# df
Filesystem 1K-blocks Used Available Use% Mounted on
192.168.101.199:/nfsroot/ubuntu-9.10-desktop-i386
                     48071910...

[Diederen (jjhdiederen)]

I have the same problem. I try to mount a NFS share. I see that there is no /etc/init.d/nfs-common entry...I don't seem to start any NFS service on the Karmic client machine.

from my /etc/fstab

10:0.0.15:/home/shared /mnt/shared nfs _netdev,auto 0 0

at boot there is nothing in /mnt/shared

this works though:

sudo mount -t nfs -o proto=tcp,port=2049 10.0.0.15:/home/shared /mnt/shared

[Diederen (jjhdiederen)]

By the way, I am in an updated Karmic environment.

[Diederen (jjhdiederen)]

If one installs nfs-common the following happens:

he following NEW packages will be installed:
  nfs-common
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/211kB of archives.
After this operation, 602kB of additional disk space will be used.
sh: getcwd() failed: No such file or directory
sh: getcwd() failed: No such file or directory
sh: getcwd() failed: No such file or directory
Selecting previously deselected package nfs-common.
(Reading database ... 177060 files and directories currently installed.)
Unpacking nfs-common (from .../nfs-common_1%3a1.2.0-2ubuntu8_i386.deb) ...
Processing triggers for ureadahead ...
Processing triggers for man-db ...
Setting up nfs-common (1:1.2.0-2ubuntu8) ...
statd start/running, process 4249
gssd stop/pre-start, process 4274
idmapd stop/waiting

[Steve Langasek (vorlon)]

SteF,

> One or more of the mounts listed in /etc/fstab cannot yet be mounted:
> (ESC for recovery shell)
> /home:waiting fr hal9000:/home

This looks a lot like a typical dependency loop between the network being fully configured, and /home being mounted so that the boot can continue.

Is hal9000 the same machine as 192.168.101.199? If not the same machine, are the two machines both on the same local segment with the client? How are your network interfaces managed from within the system - is NetworkManager running, or do you have configuration options set in /etc/network/interfaces?

[Steve Langasek (vorlon)]

Diederen,

You don't mention that you're running nfsroot, and the problem you describe doesn't relate to nfsroot. I think you should file a new bug report for your issue.

[SteF (nexus6-luceo)]

Steve,

sorry for the time to answer :-(

hal9000 is the same server (TFTPBOOT, NFS root and so on).

There is no NetworkManager running :
------------------------------------------------
tron:~$ ps ax | grep Net
 1984 pts/1 S+ 0:00 grep --color=auto Net
tron:~$
------------------------------------------------

Here is my /etc/network/interfaces :
----------------------
auto lo
iface lo inet loopback
iface eth0 inet manual
----------------------

Here an output of cat /proc/mounts :
---------------------------------------------------
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev tmpfs rw,relatime,mode=755 0 0
192.168.101.199:/nfsroot/ubuntu-9.10-desktop-i386 / nfs
rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,nolock,proto=tcp,timeo=7,retrans=10,sec=sys,addr=192.168.101.199
0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
0 0
none /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /var/run tmpfs rw,nosuid,relatime,mode=755 0 0
none /var/lock tmpfs rw,nosuid,nodev,noexec,relatime 0 0
none /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc
rw,nosuid,nodev,noexec,relatime 0 0
gvfs-fuse-daemon /home/sab/.gvfs fuse.gvfs-fuse-daemon
rw,nosuid,nodev,relatime,user_id=1000,group_id=1000 0 0
----------------------------------------------------

Cheers

SteF

On Tue, 22 Dec 2009 09:47:11 -0000, Steve Langasek
<email address hidden> wrote:
> SteF,
>
>> One or more of the mounts listed in /etc/fstab cannot yet be mounted:
>> (ESC for recovery shell)
>> /home:waiting fr hal9000:/home
>
> This looks a lot like a typical dependency loop between the network
> being fully configured, and /home being mounted so that the boot can
> continue.
>
> Is hal9000 the same machine as 192.168.101.199? If not the same
> machine, are the two machines both on the same local segment with the
> client? How are your network interfaces managed from within the system
> - is NetworkManager running, or do you have configuration options set in
> /etc/network/interfaces?

--
We can change

[Bret Towe (magnade)]

I've gotten nfsroot working for me with a 9.10 install
it was an update of an existing install also for what it matters

the item I think is what was required for me to get it to working was
to add the following line to fstab in the nfsroot
/dev/nfs / nfs nolock,proto=tcp 0 0

I might of done something so statd or lockd was loaded on server its been a couple weeks
and I forgot all that I had tired

the fstab entry i think was off this bug: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/452686

[SteF (nexus6-luceo)]

Hi Bret,

I've tried all the tricks purposed in bug 452686, without any success. :-(
On both side, /etc/fstab or pxelinux.cfg/default .

No way, I still with mounting the root as nfs partition instead of rootfs.

If I try to enable /home in /etc/fstab as nfs the boot process get stuck
(waiting to mount).

I'd like to remind my 9.04 works perfectly on same server.

May you give me your pxeconf and fstab for your 9.10, to give a try?

Thanks for all.

SteF

On Thu, 28 Jan 2010 20:01:41 -0000, Bret Towe <email address hidden> wrote:
> I've gotten nfsroot working for me with a 9.10 install
> it was an update of an existing install also for what it matters
>
> the item I think is what was required for me to get it to working was
> to add the following line to fstab in the nfsroot
> /dev/nfs / nfs nolock,proto=tcp 0
0
>
> I might of done something so statd or lockd was loaded on server its
been
> a couple weeks
> and I forgot all that I had tired
>
> the fstab entry i think was off this bug:
> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/452686

--
We can change

[Bret Towe (magnade)]

fstab isnt anythign special just the line i pasted before and /proc and such

the important pxe bits look like the below
APPEND initrd=ubu-init root=/dev/nfs nfsroot=192.168.1.21:/home/ubufs,nolock,rsize=8192,wsize=8192 ip=dhcp

if /home is all thats stopping you I think there was another bug related to that kind of hold up
i think its related to this bug: https://bugs.launchpad.net/ubuntu-release-notes/+bug/470776

[SteF (nexus6-luceo)]

Hi Bret,

thanks for your answer.

The second part about /home will be fixed in Lucid, so I can wait a bit
more.

But for the first one, I can't get it working, so, I tried you workaround
in PXE conf but no way, it doesn't work for me for a fresh 9.10 i386
desktop install.

I hope it will be fixed on Lucid, I think it worth it on a LTS version.

Cheers.

Stephane

On Sun, 31 Jan 2010 04:38:27 -0000, Bret Towe <email address hidden> wrote:
> fstab isnt anythign special just the line i pasted before and /proc and
> such
>
> the important pxe bits look like the below
> APPEND initrd=ubu-init root=/dev/nfs
> nfsroot=192.168.1.21:/home/ubufs,nolock,rsize=8192,wsize=8192 ip=dhcp
>
>
> if /home is all thats stopping you I think there was another bug related
> to that kind of hold up
> i think its related to this bug:
> https://bugs.launchpad.net/ubuntu-release-notes/+bug/470776

--
We can change