Debian Bug report logs - #637926
[ltsp-server] Ltsp-Client fails to boot

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Lorenz Wenner <lorenz@wenner.info>

To: submit@bugs.debian.org

Subject: [ltsp-server] Ltsp-Client fails to boot

Date: Mon, 15 Aug 2011 21:35:42 +0200

Package: ltsp-server
Version: 5.2.8-1
Severity: normal

--- Please enter the report below this line. ---
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. 

############# cut ############

MAC: 08:00:27:6B:F1:BF UUID: 56424f58-0000-0000-0000-0800276bf1bf
Searching for server (DHCP).....
Me: 192.168.2.20, DHCP: 192.168.2.1, Gateway 192.168.2.1
Loading 192.168.2.1:/ltsp/i386/pxelinux.0....(PXE)..............done

PXELINUX 4.04 20110711  Copyright (C) 1994-2011 H. Peter Anvin et al
!PXE entry point found (we hope) at 9F00:0680 via plan A
UNDI code segment at 9F00 len 0B1D
UNDI data segment at 9E00 len 1000
Getting cached packet  01 02 03
My IP address seems to be C0A80214 192.168.2.20
ip=192.168.2.20:192.168.2.1:192.168.2.1:255.255.255.0
B00TIF=01-08-00-27-6b-f1-bf
SYSUUID=56424f58-0000-0000-0000-0800276bf1bf
FTP prefix: /ltsp/i386/
Trying to load: pxelinux.cfg/default                        ok
Loading, please wait.
IP-Config: eth0 hardware address 08:00:27:6b:f1:bf mtu 1500 DHCP RARP
IP-Config: eth0 complete (from 192.168.2.1):
address: 192.168.2.20    broadcast: 192.168.2.255   netmask: 255.255.255.0
gateway: 192.168.2.1     dns0    : 192.168.2.1     dns1   : 0.0.0.0
domain: example.com
rootserver: 192.168.2.1 rootpath: /opt/ltsp/i386
filename  : /ltsp/i386/nbi.img
Negotiation:  ..size = 313MB
bs=1024, sz=329195520 bytes
[    5.073687] nbd0: Wrong magic (0x25609513)
[    5.112058] end_request:  I/O error, dev nbd0, sector 6
[    5.113007] Buffer I/O error on device nbd0,  logical block 3
[    5.141633] end_request:  I/O error, dev nbd0, sector 4
[    5.142046] Buffer I/O error on device nbd0,  logical block 2
[    5.142652] end_request:  I/O error, dev nbd0, sector 2
[    5.143115] Buffer I/O error on device nbd0,  logical block 1
[    5.143613] end_request:  I/O error, dev nbd0, sector 0
[    5.144008] Buffer I/O error on device nbd0,  logical block 0
[    5.162789] nbd0: Attempted send on closed socket
[    5.164726] end_request:  I/O error, dev nbd0, sector 0
[    5.165125] Buffer I/O error on device nbd0,  logical block 0
[    5.168431] nbd0: Attempted send on closed socket
[    5.170920] end_request:  I/O error, dev nbd0, sector 2
[    5.171313] Buffer I/O error on device nbd0,  logical block 1
[    5.195783] nbd0: Attempted send on closed socket
[    5.196291] end_request:  I/O error, dev nbd0, sector 4
[    5.196680] Buffer I/O error on device nbd0,  logical block 2
[    5.197561] nbd0: Attempted send on closed socket
[    5.197940] end_request:  I/O error, dev nbd0, sector 6
[    5.198310] Buffer I/O error on device nbd0,  logical block 3
[    5.207988] nbd0: Attempted send on closed socket
[    5.222849] end_request:  I/O error, dev nbd0, sector 0
[    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.



BusyBox v1 18.5 (Debian 1:1.18.5-1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

bin/sh: can't access tty; job control turned off
(initramfs)

########### cut ###########

--- System information. ---
Architecture: i386
Kernel:       Linux 3.0.0-1-686-pae

Debian Release: wheezy/sid
  500 testing         www.debian-multimedia.org 
  500 testing         ftp.de.debian.org 
  500 squeeze         www.lamaresh.net 

--- Package information. ---
Depends                (Version) | Installed
================================-+-===========
debconf                (>= 0.5)  | 1.5.40
 OR debconf-2.0                  | 
debootstrap                      | 1.0.34
lsb-release                      | 3.2-27
openssh-client                   | 1:5.8p1-7
iproute                          | 20110629-1
 OR freebsd-net-tools            | 
debconf-utils                    | 1.5.40
python                  (>= 2.4) | 2.6.7-2
update-inetd                     | 4.38+nmu1
tcpd                             | 7.6.q-21
gettext-base                     | 0.18.1.1-3


Recommends                 (Version) | Installed
====================================-+-===============
nfs-kernel-server                    | 1:1.2.4-1
squashfs-tools                       | 1:4.2-4
nbd-server            (>= 1:2.9.6-2) | 1:2.9.23-3
openssh-server                       | 1:5.8p1-7
tftpd-hpa                            | 5.1-1
 OR atftpd                           | 
 OR dnsmasq                (>= 2.41) | 
openbsd-inetd                        | 0.20091229-1
 OR inet-superserver                 | 


Suggests                      (Version) | Installed
=======================================-+-===========
isc-dhcp-server                         | 4.1.1-P1-17
 OR dhcp3-server                        | 
 OR dnsmasq                             | 
libasound2-plugins                      | 1.0.24-2
ltspfs                                  | 0.7-2
xauth                                   | 1:1.0.6-1
gnome-session                           | 
 OR x-session-manager                   | 
 OR x-window-manager                    | 
ldm-server                              | 2:2.2.2-2
sdm                                     | 
audiooss                                | 
pulseaudio-esound-compat                | 0.9.23-1
 OR esound-clients                      | 
 OR nas-bin                             | 
ltsp-docs                               | 0.99+bzr120-1
x11-utils                               | 7.6+3
qemu-user-static                        | 



--- Output from package bug script ---
chroot information: /opt/ltsp/i386

packages in chroot: /opt/ltsp/i386
ii ldm 2:2.2.2-2
ii ltsp-client 5.2.8-1
ii ltsp-client-core 5.2.8-1
ii ltspfsd 0.7-2
ii ltspfsd-core 0.7-2

found: /opt/ltsp/i386/etc/lts.conf
# This is the default lts.conf file for ltsp 5.  For more information about
# valid options please see lts.conf(5) man page, available in the ltsp-docs
# package.
#
# Note that things like sound and local device support are auto-enabled if the
# corresponding packages are installed, there is no need to manually set these
# options anymore.

[default] 
    LTSP_CONFIG=True
    #SOUND=False
    #LOCALDEV=False
    #CONFIGURE_X=False

found image: /opt/ltsp/images/i386.img
/opt/ltsp/images/i386.img: Squashfs filesystem, little endian, version 4.0, 
84093421311 bytes, 30023 inodes, blocksize: 19 bytes, created: Sun Jun 30 
02:19:12 1918

Message #10 received at 637926@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@freegeek.org>

To: 637926-submitter@bugs.debian.org

Cc: 637926@bugs.debian.org

Subject: Bug#637926: [ltsp-server] Ltsp-Client fails to boot

Date: Fri, 19 Aug 2011 12:44:25 -0700

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

Message #20 received at 637926-done@bugs.debian.org (full text, mbox, reply):

From: Vagrant Cascadian <vagrant@debian.org>

To: 637926-done@bugs.debian.org

Subject: Re: Bug#637926: [ltsp-server] Ltsp-Client fails to boot

Date: Fri, 11 Apr 2014 09:42:13 -0700

[Message part 1 (text/plain, inline)]

On Fri, Aug 19, 2011 at 12:44:25PM -0700, Vagrant Cascadian wrote:
> 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. 
... 
> did you intentionally configure it to use NBD? the default should be to use 
> NFS.

No response after several years, resolving.

live well,
  vagrant

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.