<div dir="ltr"><p>I have never done this so YMMV...</p><p>It appears that Grub does not do raid1 but the way round this is to specify one of the 2 /boot partitions as a normal device.</p><p>if /dev/md0 consists of /dev/sda1 and /dev/sdb1 then specify either /dev/sda1 or /dev/sdb1 as the boot partition.</p>
<p>It is also a good idea to put a fallback entry in grub to boot of the other partition in case of error.</p><p><br></p><p>The other cause of error may be that your initramfs is not loading the dmraid kernel module so check that as well.</p>
<p><br></p><p>This link may help you...</p><p><a href="http://www.howtoforge.com/software-raid1-grub-boot-debian-etch-p2">http://www.howtoforge.com/software-raid1-grub-boot-debian-etch-p2</a><br></p><p><br></p><p>Paul</p>
<p><br></p>
<div class="gmail_quote">On 14 Mar 2014 20:14, "Ben Whyall" <<a href="mailto:ben@whyall-systems.co.uk" target="_blank">ben@whyall-systems.co.uk</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi<br>
<br>
How do I get a list of uuid from grub command line.<br>
<br>
I have tried setting root=/dev/md0 which is where the /boot is but that just sits at loading initial ramdisk .... and doesnt seem to do anything.<br>
<br>
Ben<br>
<br>
<br>
<br>
On 14/03/14 10:46, Mike Brodbelt wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
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.<br>
<br>
Mike<br>
<br>
On 14 March 2014 09:12:18 GMT+00:00, Ben Whyall <<a href="mailto:ben@whyall-systems.co.uk" target="_blank">ben@whyall-systems.co.uk</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On 14/03/2014 09:05, Chris Bell wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
On Fri 14 Mar, Ben Whyall wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi<br>
<br>
Its Debian unstable not recently installed but possibly the first<br>
</blockquote></blockquote>
time<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
its been rebooted since kernel upgrade. Although none of the old<br>
kernels boot either.<br>
<br>
Interestingly when you look at the blkid that uuid exists its one of<br>
</blockquote></blockquote>
the<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
inactive lvm logical volumes.<br>
<br>
Ben<br>
<br>
</blockquote>
<br>
Have you tried updating grub?<br>
Not sure whether this is relevant. There has been some frenzied<br>
</blockquote>
activity<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
relating to Debian Testing and Unstable because even the installer<br>
</blockquote>
discs<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
have given problems. It seems that in an attempt to check other<br>
</blockquote>
possible<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
locations the correct location is sometimes missed and/or there is a<br>
</blockquote>
hang.<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
</blockquote>
<br>
Hi<br>
<br>
I have tried updating grub but not managed to get it to run<br>
successfully. I have not managed to get to a point where I have the<br>
boot partition and enough of the lvm partitions available to be able to<br>
<br>
update grub.<br>
<br>
How would I go about getting to a point where I can run the update-grub<br>
<br>
with the relevant file systems up ?<br>
<br>
Ben<br>
<br>
______________________________<u></u>_________________<br>
GLLUG mailing list<br>
<a href="mailto:GLLUG@mailman.lug.org.uk" target="_blank">GLLUG@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/gllug" target="_blank">https://mailman.lug.org.uk/<u></u>mailman/listinfo/gllug</a><br>
</blockquote>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
GLLUG mailing list<br>
<a href="mailto:GLLUG@mailman.lug.org.uk" target="_blank">GLLUG@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/gllug" target="_blank">https://mailman.lug.org.uk/<u></u>mailman/listinfo/gllug</a><br>
</blockquote></div>
</div>