[Bug 457702] Re: nbd+squashfs errors when rebooting ltsp thin clients

[Stéphane Graber]

Please note that in Lucid, a upstart script exists for both reboot and
shutdown that triggers a forced shutdown/reboot and bypass the regular
shutdown sequence.

These two scripts issues a "sync" then reboot or shutdown depending on the runlevel.
/etc/init.d/sendsigs will then never be called at shutdown or reboot making updating the process blacklist useless in this case.

That new LTSP including updated upstart jobs and other upstream fixes
will be uploaded later today.

-- 
nbd+squashfs errors when rebooting ltsp thin clients
https://bugs.launchpad.net/bugs/457702
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “ldm” package in Ubuntu: Invalid
Status in “ltsp” package in Ubuntu: Confirmed

Bug description:
Testing done on ltsp image built on Karmic from the newest packages available in the repos.

Server: Karmic amd64
Thin client: Karmic i386
Image built with command: ltsp-build-client --arch=i386

After building a fresh image with newest Karmic packages, the ltsp thin clients do not reboot properly, but throw nbd+squashfs related errors on the console. After the errors are shown, the thin client is frozen and it does not reboot automatically. Shutdown works properly with no error messages. The same error happens on every boot and this has happened on multiple thin clients.

Attached is logfile for the entire session when the thin client boots from network and reboot is selected from ldm menu. The logfile is captured from serial console.

The shutdown part gives out these messages:

init: hal main process (856) terminated with status 1
init: cron main process (2247) killed by TERM signal
init: tty1 main process (3341) killed by TERM signal
init: Disconnected from system bus
init: rsyslog-kmsg main process (444) killed by TERM signal
 * Asking all remaining processes to terminate...        init: hwclock-save main process (3406) killed by TERM signal
[   57.931304] nbd0: Receive control failed (result -4)
[   57.955127] nbd0: Attempted send on closed socket
[   57.959994] end_request: I/O error, dev nbd0, sector 416250
[   57.965709] SQUASHFS error: squashfs_read_data failed to read block 0xcb3f6c9
[   57.972983] SQUASHFS error: Unable to read metadata cache entry [cb3f6c9]
[   57.979941] SQUASHFS error: Unable to read directory block [cb3f6c9:193c]
[   57.986973] SQUASHFS error: Unable to read metadata cache entry [cb3f6c9]
[   57.993887] SQUASHFS error: Unable to read directory block [cb3f6c9:193c]
[   58.000885] SQUASHFS error: Unable to read metadata cache entry [cb3f6c9]
...