[ale] Unable to mount disks with UUID

[Alex Carver]

Honestly no idea.  I always used /dev/sdaxx in the fstab.  The recently
refreshed machine, I started with /dev/sdaxx then I updated the kernel
which swapped it out for UUIDs and it died on the spot.

For this machine that crashed I can't remember how long it may have had
UUIDs.  I don't think very long.  It did mount the root drive using a
UUID but it just failed to mount a secondary drive (I have sda and sdb,
sda mounted all its partitions fine, sdb has only one partition and it
didn't mount).


On 2015-12-15 20:28, Jim Kinney wrote:
> Sounds like a bad kernel or initrd has no UUID capability.
> 
> Does another kernel boot it?
> 
> On December 15, 2015 9:57:21 PM EST, Alex Carver <agcarver+ale at acarver.net> wrote:
>> Yes, it was autogenerated during various kernel installs.  I have not
>> edited fstab to add UUID on either system that had an issue.
>>
>> On 2015-12-15 18:56, Jeff Hubbs wrote:
>>> Do you have the syntax sorted? the rightmost column is supposed to
>> look
>>> like
>>>
>>> UUID=d88c0ab0-320c-4093-8316-e6dde520e2c1
>>>
>>> No quotes.
>>>
>>> On 12/15/15 9:48 PM, Alex Carver wrote:
>>>> Ok, I just had a machine crash and need a reboot.  When it came up
>> it
>>>> was waiting for a password (so it sat all day waiting for me to get
>> back
>>>> to find that) and then it proceeded to fail to mount any of the
>> other
>>>> disks in the system because the UUIDs wouldn't work.  Running blkid
>> on
>>>> the partitions shows the right UUID which matches what is in fstab
>> but
>>>> didn't work.  Using the /dev/sdxy references worked fine so I
>> switched
>>>> the fstab to use those but fstab will likely get rewritten by
>> another
>>>> kernel update (like it did already) so I need to figure out why UUID
>>>> mounting is failing.
>>>>
>>>> Anyone seen this before?  It also happened on another machine that I
>>>> refreshed recently.  It couldn't boot its own root partition and I
>> had
>>>> to go in and fix the fstab to point to /dev/sdxy.