On Mon, Aug 15, 2011 at 09:35:42PM +0200, Lorenz Wenner wrote: > I installed the package ltsp-server-standalone in wheezy and am using > virtualbox for testing the configuration with a virtual Thinclient. I could > extract the output of the clients "booting" but do not really know, what the > lines mean or if it is maybe an nbd-error.
> [ 5.223244] Buffer I/O error on device nbd0, logical block 0 > /dev/nbd0: I/O error > Warning: unable to detect filesystem, assuming squashfs. > [ 5.260450] nbd0: Attempted send on closed socket > [ 5.260870] end_request: I/O error, dev nbd0, sector 0 > [ 5.269567] SQUASHFS error: squashfs_read_data failed to read block 0x0 > [ 5.270057] SQUASHFS error: unable to read squashfs_super_block > mount: mounting /dev/nbd0 on /rofs failed: Input/output error > [ 5.298968] aufs test_add:232:exe[131]: unsupported filesystem, /rofs > (rootfs > ) > mount: mounting aufs on /root failed: Invalid argument > 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 > Target filesystem doesn't have requested /sbin/init. > No init found. Try passing init= bootarg. did you intentionally configure it to use NBD? the default should be to use NFS. sometimes people follow documentation for Ubuntu, and run ltsp-update-image, but you should not need to run this with Debian. unfortunately, running ltsp-update-image *partially* switches over the configuration to use NBD. to switch back to NFS: rm /opt/ltsp/i386/etc/ltsp/update-kernels.conf ltsp-chroot /usr/share/ltsp/update-kernels ltsp-update-kernels live well, vagrant -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
