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
----------------------
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?
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 : ------- ------- ------- ------- ------- ------- -- nodev,noexec, relatime 0 0 nodev,noexec, relatime 0 0 mode=755 0 0 101.199: /nfsroot/ ubuntu- 9.10-desktop- i386 / nfs vers=3, rsize=262144, wsize=262144, namlen= 255,hard, nolock, proto=tcp, timeo=7, retrans= 10,sec= sys,addr= 192.168. 101.199 security securityfs rw,relatime 0 0 fuse/connection s fusectl rw,relatime 0 0 noexec, relatime, gid=5,mode= 620,ptmxmode= 000 nodev,relatime 0 0 relatime, mode=755 0 0 nodev,noexec, relatime 0 0 relatime, mode=755 0 0 fs/binfmt_ misc binfmt_misc nodev,noexec, relatime 0 0 fuse-daemon nodev,relatime, user_id= 1000,group_ id=1000 0 0 ------- ------- ------- ------- ------- ------- ---
-------
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,
none /proc proc rw,nosuid,
udev /dev tmpfs rw,relatime,
192.168.
rw,relatime,
0 0
none /sys/kernel/
none /sys/fs/
none /sys/kernel/debug debugfs rw,relatime 0 0
none /dev/pts devpts rw,nosuid,
0 0
none /dev/shm tmpfs rw,nosuid,
none /var/run tmpfs rw,nosuid,
none /var/lock tmpfs rw,nosuid,
none /lib/init/rw tmpfs rw,nosuid,
binfmt_misc /proc/sys/
rw,nosuid,
gvfs-fuse-daemon /home/sab/.gvfs fuse.gvfs-
rw,nosuid,
-------
Cheers
SteF
On Tue, 22 Dec 2009 09:47:11 -0000, Steve Langasek interfaces?
<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/
--
We can change