[GLLUG] problem with grub

[Mike Brodbelt]

It sounds to me from your description that grub is attempting to use the wrong disk. You say the uuid it appears to be trying to find the kernel on is in fact the uuid of one of your LVM volumes. I suspect all you need to do is enumerate the disks visible to the grub shell, and point it at the uuid of your actual /boot partition, in order to boot successfully. You'll then need to correct the grub config. Be aware that the grub "root" is the device where it expects to find the kernel (i.e. /boot) and not your root filesystem.

Mike

On 14 March 2014 09:12:18 GMT+00:00, Ben Whyall <ben at whyall-systems.co.uk> wrote:
>On 14/03/2014 09:05, Chris Bell wrote:
>> On Fri 14 Mar, Ben Whyall wrote:
>>
>>> Hi
>>>
>>> Its Debian unstable not recently installed but possibly the first
>time
>>> its been rebooted since kernel upgrade.  Although none of the old
>>> kernels boot either.
>>>
>>> Interestingly when you look at the blkid that uuid exists its one of
>the
>>> inactive lvm logical volumes.
>>>
>>> Ben
>>>
>>
>>     Have you tried updating grub?
>>     Not sure whether this is relevant. There has been some frenzied
>activity
>> relating to Debian Testing and Unstable because even the installer
>discs
>> have given problems. It seems that in an attempt to check other
>possible
>> locations the correct location is sometimes missed and/or there is a
>hang.
>>
>
>Hi
>
>I have tried updating grub but not managed to get it to run 
>successfully.  I have not managed to get to a point where I have the 
>boot partition and enough of the lvm partitions available to be able to
>
>update grub.
>
>How would I go about getting to a point where I can run the update-grub
>
>with the relevant file systems up ?
>
>Ben
>
>_______________________________________________
>GLLUG mailing list
>GLLUG at mailman.lug.org.uk
>https://mailman.lug.org.uk/mailman/listinfo/gllug

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.