Re: Upgrade to Lenny (+Lenny-test).
- To: firstname.lastname@example.org
- Subject: Re: Upgrade to Lenny (+Lenny-test).
- From: Vagrant Cascadian <email@example.com>
- Date: Sun, 16 Nov 2008 09:21:55 -0800
- Message-id: <20081116172155.GI8315@ryukin.fglan>
- In-reply-to: <11D57292EE044F7EA071D6E18AFB4BE8@static00>
- References: <7B069DBF53364414960CC9F58D771AE7@static00> <11D57292EE044F7EA071D6E18AFB4BE8@static00>
On Fri, Nov 14, 2008 at 09:30:24PM +0200, Oded Naveh wrote:
> Now I'm facing a problem which blocks me from making farther progress, The
> thin clients fail to load, the same problem occurred on my system upgraded
> from Etch via web:
> > 3) Thin Clients don't start:
> > After "Booting the kernel.", "IP-Config:" seems correct, but:
> > "Error: Connect: Connection refused", consequent mounts fail:
> mount: mounting aufs on /root failed: No such device
> mount: mounting /rofs on /root/rofs failed: Invalid argument
> mount: mounting /dev on /root/dev failed: No such file or directory
> mount: mounting /sys on /root/sys failed: No such file or directory
> mount: mounting /proc on /root/proc failed: No such file or directory
> > therefore "No init found." and end up with BusyBox.
> Please see details for bug 1320 at http://bugs.skolelinux.no/cgi-bin/bugzilla/show_bug.cgi?id=1320
> Could that be NBD message not NFS?
> Is it possible the thin clients try to mount a root filesystem via NBD?
seems like you've got an outdated /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default ...
should contain "boot=nfs", if it doesn't, it'll fall back to the NBD related
hooks, which are not default on Debian.
if that doesn't update it...
if you've got an /opt/ltsp/i386/etc/update-kernels.conf, you may need to update
(add boot=nfs to BOOTPROMPT_OPTS) it and run:
chroot /opt/ltsp/i386 /usr/lib/ltsp/update-kernels
if you've got a /etc/ltsp/ltsp-update-kernels.conf, update it (add boot=nfs to
BOOTPROMPT_OPTS) and run: