| 1 |
On 2020-03-19 19:04, Michael wrote: |
| 2 |
> On Thursday, 19 March 2020 17:03:15 GMT Ian Zimmerman wrote: |
| 3 |
>> On 2020-03-19 10:59, n952162 wrote: |
| 4 |
>>> I changed the UUID of all the partitions of the second drive and now |
| 5 |
>>> all my devices are linked to in /dev/disk/by-uuid. I still have |
| 6 |
>>> no/dev/disk/by-label, though. Also, my swap file on a mounted drive |
| 7 |
>>> wasn't mounted, which was my original problem ;-( |
| 8 |
>> Do they in fact have labels? Just checking. |
| 9 |
>> |
| 10 |
>> Also, you're not not clear if your _partition_ still isn't getting |
| 11 |
>> mounted, or just the swap file not getting activated. |
| 12 |
>> |
| 13 |
>> For a problem like this, there _has_ to be something in the log. |
| 14 |
> We're using the term 'partition' here, but to avoid confusion, we have GPT |
| 15 |
> partition table UUIDs (PARTUUID) and we have filesystem UUIDs (UUID). |
| 16 |
> |
| 17 |
> Similarly, we also have filesystem labels and GPT partition labels. |
| 18 |
> |
| 19 |
> Therefore it helps if there is consistency in the IDs being used to mount |
| 20 |
> partitions. |
| 21 |
|
| 22 |
I used the UUID column of blkid(8) on the fstab entry, with UUID=. If |
| 23 |
that is the partition UUID, where, how, and wherefore are filesystem UUIDs? |
Archives