<div dir="ltr">Tagging this fixed. We got lucky. For the life of me I don't really understand why, but somehow the machine lost the ability to see the disc by UUID, but could still see it by device name. <div><br></div><div>changing /etc/grub/grub.conf from </div><div>linux /vmlinuz-3.16.0-0.bpo.4-amd64 root=UUID ro quiet</div><div>to</div><div>linux /vmlinuz-3.16.0-0.bpo.4-amd64 root=/dev/mapper/rootvg-rootlv ro quiet</div><div><br></div><div>somehow fixed the issue. (after running update-grub).</div><div><br></div><div>(whew)</div><div><br></div><div><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 12, 2016 at 9:54 AM, Mike Bean <span dir="ltr"><<a href="mailto:beandaemon@gmail.com" target="_blank">beandaemon@gmail.com</a>></span> 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"><div dir="ltr">Well, the UUID it's referencing is our root LVM group. But it would make sense for it to be a problem with boot partition.</div><div class=""><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 12, 2016 at 9:51 AM, Charles Burton <span dir="ltr"><<a href="mailto:charles.d.burton@gmail.com" target="_blank">charles.d.burton@gmail.com</a>></span> 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"><div dir="ltr">Are you sure you're using it with LVM? At boot LVM scans all the disks and looks for the metadata, it generally doesn't care much about UUID other than for internal accounting. Likely it's your boot partition.<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Apr 12, 2016 at 3:33 PM, Mike Bean <span dir="ltr"><<a href="mailto:beandaemon@gmail.com" target="_blank">beandaemon@gmail.com</a>></span> wrote:<br></div></div><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"><div><div><div dir="ltr"><br><div>We have a fairly major system at work that somehow lost track of a disk</div><div>ALERT! /dev/disk/by-uuid/(some id) does not exist. Dropping to a shell</div><div><br></div><div>Booting to recovery mode gets the same result. </div><div>Booting to a debian disk on rescue mode sees the disk. the UUID in question is the root VG</div><div><br></div><div>Must admit, my google-fu has failed me. I have no idea. I have a snapshot I can revert to, but it's an old one, and the users will lose allot of their work.</div><div><br></div><div>Mike B</div></div>
<br></div></div>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org" target="_blank">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" rel="noreferrer" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div></div>