On Sun, 02 Nov 2014 14:35:54 +0000 steve-ALUG@hst.me.uk wrote:
Just a thought. Is your FSTab using device numbers (e.g. sd1) or is it using uuids? I presume it's using uuids because of what you describe the error message as. However, if you're still using the other way, then you may be having a problem that I've had before: I have a printer with a SD card socket and when it was on when I booted the the computer, the computer decided that my hard disks had changed letters, so it wouldn't boot. This took me a long time to work out what was wrong. Once I worked it out, I swapped to using uuids in fstab, and the problem went away.
The first couple of lines of fstab are shown below :- # Entry for /dev/sdb1 : UUID=8420efbc-b416-46af-90ee-9ed61b39c580 / ext4 acl,relatime 1 1 # Entry for /dev/sdb8 : UUID=b9c44d99-d286-4eee-b2cd-59fc007a1eb1 /home ext4 acl,relatime 1 2
As a temporary 'fix', I'm just going to edit the boot commands to remove everything execpt the line that works. That way I won't be tempted to press the wrong entry and then have to wait for it to fall over before rebooting.
I'll just wait for a new kernel to appear.
Thanks very much for all the ideas.