Comment 7 for bug 501078

This remains a bug. I was very lucky to realise this was what caused it, as it resulted in no video feed (kernel or X windows) and no SSH access, the most shockingly poor position Ive been in so far (haven't used Linux for that long so I was lucky to be able to take control of such a situation).

Is this what a kernel panic looks like?

The fstab manpage talks about using '\040' to represent spaces in paths and labels, so I used this - works perfectly after boot, but complete death during boot.

As a workaround, I have replaced all spaces with underscores.

When the failure happens, NOTHING is logged. I was shocked to see nothing in all the various files in /var/log, which I dont really understand. There is nothing in '/var/crash'.

The problem is trivial to reproduce - happens every time. A detail that may be of use - my OS drive is RAID 1'd via mdadm, courtesy of the Ubuntu Server installer wizard.

===========================================================

All packages uptodate.

Ubuntu Server 10.04

uname -a: Linux 2.6.32-24-server #39-Ubuntu SMP Wed Jul 28 06:21:40 UTC 2010 x86_64 GNU/Linux

mountall version: 2.15