I tried to debug this a little bit more.
The initrd is executed without any problems (only some warnings because
/root/etc/hostname cannot be written to) and control is passed to
/sbin/init on the now NFS mounted real root fs.
The problem occurs when init executes /etc/init/mountall.conf. At this
point, /etc/fstab is still empty, but mountall nevertheless tries to
mount some file systems and then fails.
I changed /etc/init/mountall.conf to print out /etc/fstab before calling
mountall:
script
. /etc/default/rcS
[ -f /forcefsck ] && force_fsck="--force-fsck"
[ "$FSCKFIX" = "yes" ] && fsck_fix="--fsck-fix"
[ -n "$TMPTIME" ] && tmptome="--tmptime=$TMPTIME"
cat /etc/fstab
exec mountall --daemon -v $force_fsck $fsck_fix $tmptime
end script
Attached is a screenshot of the output.
I guess the crucial question is now: why is mountall trying to mount
something if /etc/fstab is empty? And where does it get the information
about what it is supposed to mount?
** Attachment added: "msgs-1.png"
http://launchpadlibrarian.net/37137372/msgs-1.png
--
karmic ltsp client stops boot on nfsroot mount with mountall exit code 1
https://bugs.launchpad.net/bugs/485709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
