nfsboot ubuntu desktop fails with errors creating /dev/null
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Incomplete
|
Undecided
|
Nanley Chery |
Bug Description
I installed Ubuntu Fesity desktop with the aim of creating an nfsboot system, the files being stored on a server on the LAN. The client machine (mostly) comes up, I do get a login prompt for a very short period of time before more services decide to load and then the error regarding /dev/null appears.
I checked on the server side, /dev/null does exist in the client image and seems to have the correct permissions.
I do not really know if this is a bug or an error with my config; I'm fairly confident my setup is correct...
Stuff done:
(On the client)
Created /mnt/edam
Mounted 192.168.
cp -ax /. /mnt/edam/. (Created the NFS boot image)
[edit boot image on 192.168.0.15]
Edited fstab - remove entry for /
- Add entries for proc and sys
Edited /etc/network/
- Removed all entries except loopback
[add entry to /boot on the VM]
cd /etc/initramfstools
vim initramfs.conf (Change from "local" to "nfs")
update-initramfs
vim initramfs.conf (Change back to "local")
mv new.initramfs to newramfs-NFS
mv new.initramfs.bak to newramfs
add entry to grub.lst
[Try it and see :o]
- still problems with /dev/ (Can't create /dev/null(!))
- Errors after the /dev/null one:
/etc/init.d/rc: 2: sed: Input/output error. (Repeated for a few screens).
I'm having the same trouble except that I don't see the /dev/null error, although it may flash by too fast for me to read. I get a slew of complaints about sed before the system hangs.
I added "single" to the boot options of my nfs bootup, and successfully got to a root prompt. The only problem I had during the boot (that I could catch) was a timeout trying to mount my samba share. From there I could do pretty much anything that I wanted. The network was up, I had internet access, I could nfs share other file systems, I could start X and get a full desktop etc.
Once I verifiied everything was looking good, I went back to the root prompt and entered "telinit 2". From there it was all bad. Avahi timed out, so I removed that from the startup and tried again, and next the "network manager" (i think it was called) failed after that. Once that happened I got a flash of messages, and the last screen was full of startup script failures complaining they couldn't find "sed" (it's in /bin and does exist on the system). Since the system hangs at that point I can only guess what went wrong. I assume something is blowing away my root file system.
Next I'll start manually running the rc2.d scripts and see if I can narrow down what's causing all the fuss.