My machine has recently upgraded itself to a new kernel and now it won't boot. It fails after several seconds telling me that various UUIDs don't exist. But they're the same devices that another kernel does run from. The new kernel which doesn't work is 3.14.18-3 and the one that does work - I'm using it now - is 3.12.25-3.
I would have said that if the various partitions do exist, then it *should* work so where do I start trying to fault-find this?
On 29/10/14 12:03, Chris Walker wrote:
My machine has recently upgraded itself to a new kernel and now it won't boot. It fails after several seconds telling me that various UUIDs don't exist. But they're the same devices that another kernel does run from. The new kernel which doesn't work is 3.14.18-3 and the one that does work - I'm using it now - is 3.12.25-3.
I would have said that if the various partitions do exist, then it *should* work so where do I start trying to fault-find this?
I've had this sort of problem occasionally too. In the past I've tried uninstalling the new kernel, then rebooting in the old kernel. You can then try reinstalling the new kernel perhaps, or just wait until the next kernel comes out. I think in the past I've had this problem for 2 different reasons - the initramfs has messed up somehow, and I had a kernel that didn't like my hardware - I never could get that one to work and had to wait until the next one came out.
HTH Steve
On Wed, 29 Oct 2014 15:21:01 +0000 steve-ALUG@hst.me.uk wrote:
On 29/10/14 12:03, Chris Walker wrote:
My machine has recently upgraded itself to a new kernel and now it won't boot. It fails after several seconds telling me that various UUIDs don't exist. But they're the same devices that another kernel does run from. The new kernel which doesn't work is 3.14.18-3 and the one that does work - I'm using it now - is 3.12.25-3.
I would have said that if the various partitions do exist, then it *should* work so where do I start trying to fault-find this?
I've had this sort of problem occasionally too. In the past I've tried uninstalling the new kernel, then rebooting in the old kernel. You can then try reinstalling the new kernel perhaps, or just wait until the next kernel comes out. I think in the past I've had this problem for 2 different reasons - the initramfs has messed up somehow, and I had a kernel that didn't like my hardware - I never could get that one to work and had to wait until the next one came out.
I remember in the dim and distant past, one of the ALUG members compiled a kernel for me at one of the meetings at the UEA. Would it be worthwhile doing that again or better to uninstall the latest - non working - version and wait for the next one?
Or can I fix the initramsfs?
On 30/10/14 11:00, Chris Walker wrote:
On Wed, 29 Oct 2014 15:21:01 +0000 steve-ALUG@hst.me.uk wrote:
On 29/10/14 12:03, Chris Walker wrote:
My machine has recently upgraded itself to a new kernel and now it won't boot. It fails after several seconds telling me that various UUIDs don't exist. But they're the same devices that another kernel does run from. The new kernel which doesn't work is 3.14.18-3 and the one that does work - I'm using it now - is 3.12.25-3.
I would have said that if the various partitions do exist, then it *should* work so where do I start trying to fault-find this?
I've had this sort of problem occasionally too. In the past I've tried uninstalling the new kernel, then rebooting in the old kernel. You can then try reinstalling the new kernel perhaps, or just wait until the next kernel comes out. I think in the past I've had this problem for 2 different reasons - the initramfs has messed up somehow, and I had a kernel that didn't like my hardware - I never could get that one to work and had to wait until the next one came out.
I remember in the dim and distant past, one of the ALUG members compiled a kernel for me at one of the meetings at the UEA. Would it be worthwhile doing that again or better to uninstall the latest - non working - version and wait for the next one?
I'd be tempted to uninstall the latest kernel, reboot, then reinstall the latest and see if it works. If it doesn’t, wait for the next one.
Or can I fix the initramsfs?
You can rebuild initramfs. Google update-initramfs and/or mkinitramfs with your distro name.
There's lots of info out there (e.g. http://ubuntugenius.wordpress.com/2010/05/24/fix-a-failed-initramfs-update-d...)
I'd be tempted just to uninstall then reinstall the kernel though, as that should update the initramfs for you automatically (I think, unless I'm hopelessly wrong!)
good luck.
Steve
On Thu, 30 Oct 2014 18:46:50 +0000 steve-ALUG@hst.me.uk wrote:
You can rebuild initramfs. Google update-initramfs and/or mkinitramfs with your distro name.
There's lots of info out there (e.g. http://ubuntugenius.wordpress.com/2010/05/24/fix-a-failed-initramfs-update-d...)
I'd be tempted just to uninstall then reinstall the kernel though, as that should update the initramfs for you automatically (I think, unless I'm hopelessly wrong!)
I did as you suggested and uninstalled the kernel, along with the virtualbox stuff it said had to go and then reinstalled them all after a reboot. It still doesn't work so I'll just have to wait for a later version. Thanks for your ideas.
On 01/11/14 09:45, Chris Walker wrote:
I did as you suggested and uninstalled the kernel, along with the virtualbox stuff it said had to go and then reinstalled them all after a reboot. It still doesn't work so I'll just have to wait for a later version. Thanks for your ideas.
I hope the next kernel fixes this problem for you. Steve
On 02/11/14 11:22, steve-ALUG@hst.me.uk wrote:
On 01/11/14 09:45, Chris Walker wrote:
I did as you suggested and uninstalled the kernel, along with the virtualbox stuff it said had to go and then reinstalled them all after a reboot. It still doesn't work so I'll just have to wait for a later version. Thanks for your ideas.
I hope the next kernel fixes this problem for you. Steve
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.
Steve
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.
On 30/10/14 18:46, steve-ALUG@hst.me.uk wrote:
<snip><a bunch of stuff>
I'd be tempted just to uninstall then reinstall the kernel though, as that should update the initramfs for you automatically (I think, unless I'm hopelessly wrong!)
good luck.
Steve
This might be daft question but how do you get back to the last kernel if the new one causes trouble? I'm thinking this info might prove handy one day.
Bev.
On 14/11/14 11:20, Bev Nicolson wrote:
This might be daft question but how do you get back to the last kernel if the new one causes trouble? I'm thinking this info might prove handy one day.
Bev.
Older versions of Ubuntu showed you a menu at boot time. Newer versions (using Grub 2 or later I think) you have to press a key at the right moment during the boot cycle and it brings up a menu. Not sure which key. Could be Escape, shift, control, or possibly F8. Pressing the wrong key too early though might get you into your BIOS setup menu, which you probably don't want.
Have a google "How to bring up grub boot menu" or something like that.
Haven't got time to do it myself ATM.
HTH Steve
On 14/11/14 11:52, steve-ALUG@hst.me.uk wrote:
On 14/11/14 11:20, Bev Nicolson wrote:
This might be daft question but how do you get back to the last kernel if the new one causes trouble? I'm thinking this info might prove handy one day.
Bev.
Older versions of Ubuntu showed you a menu at boot time. Newer versions (using Grub 2 or later I think) you have to press a key at the right moment during the boot cycle and it brings up a menu. Not sure which key. Could be Escape, shift, control, or possibly F8. Pressing the wrong key too early though might get you into your BIOS setup menu, which you probably don't want.
Have a google "How to bring up grub boot menu" or something like that.
Haven't got time to do it myself ATM.
HTH Steve
That'll do, Steve. Gives me enough to work with.
Bev.
On 14/11/14 12:47, Bev Nicolson wrote:
On 14/11/14 11:52, steve-ALUG@hst.me.uk wrote:
On 14/11/14 11:20, Bev Nicolson wrote:
This might be daft question but how do you get back to the last kernel if the new one causes trouble? I'm thinking this info might prove handy one day.
Bev.
Older versions of Ubuntu showed you a menu at boot time. Newer versions (using Grub 2 or later I think) you have to press a key at the right moment during the boot cycle and it brings up a menu. Not sure which key. Could be Escape, shift, control, or possibly F8. Pressing the wrong key too early though might get you into your BIOS setup menu, which you probably don't want.
Have a google "How to bring up grub boot menu" or something like that.
Haven't got time to do it myself ATM.
HTH Steve
That'll do, Steve. Gives me enough to work with.
Bev.
I've had a quick google and shift seems to be the magic key.
Steve
On 15/11/14 11:32, steve-ALUG@hst.me.uk wrote:
That'll do, Steve. Gives me enough to work with.
Bev.
I've had a quick google and shift seems to be the magic key.
Steve
This looked especially helpful. At least, I post it in case anyone else find it useful. I have it Scrapbooked.
https://help.ubuntu.com/community/Grub2
Bev
-
Bev Nicolson -
Chris Walker -
steve-ALUG＠hst.me.uk