The Hardy netboot issues can be debugged by booting with break=mount debug=y, then running t=/dev/tty2; sh <$t >$t 2>$t & # repeat for tty3 if you want exit
boot will continue, and hang because the network is down. You can debug by switching to another console and looking at /casper.log (where stdout and stderr are redirected). Some script tries to switch to manual mode when nfsroot booting, so ifup doesn't screw it up later. I guess if you don't put ip=something (other than dhcp) on the commandline, Hardy won't nfsroot boot. This is not the NetworkManager issue, and is not present in Intrepid. I only mention it because Hardy is an LTS release, so it people may be trying to mess around with it on servers for a while... Hmm, Hardy might be failing because it tries to use eth0, while the network cable is plugged in to eth1, according to its detection order. (I haven't tried netbooting Hardy at home, only on a Dell PE1950 with dual bnx2 NICs.) Intrepid detects the ports in the opposite order, with eth0 as the port marked GbE 1 (of 2) on the back, and which has the lower MAC address. I plugged my cables into GbE 1 since the BIOS defaults to netbooting from that interface, but not the other one, among other reasons. So anyway, maybe it's just Hardy's bad luck, and Intrepid would have the same problem if it needed to use eth1. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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/listinfo/ubuntu-bugs
