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