1 |
Neil Bothwick wrote: |
2 |
> On Sat, 16 Apr 2022 12:45:20 -0500, Dale wrote: |
3 |
> |
4 |
>>> You're using LVM, so all the drives should be assembled based on their |
5 |
>>> embedded metadata. It is fine to reference whatever temporary device |
6 |
>>> name you're using when running pvmove/pvcreate since that doesn't |
7 |
>>> really get stored anywhere. If you are directly mounting anything |
8 |
>>> without using LVM then it is best to use labels/uuids/etc to identify |
9 |
>>> partitions. |
10 |
>> I have to use sd** when using cryptsetup to decrypt the drive. I |
11 |
>> haven't found a way around that that is easier yet. My command was |
12 |
>> something like cryptsetup open /dev/sdk1 <name> and then it asks for the |
13 |
>> password. |
14 |
> Use /dev/disks/by/partlabel/foo or /dev/disks/by-partuuid/bar. |
15 |
> |
16 |
> |
17 |
|
18 |
That's even more typing than /dev/sdk. Some things I do easily by using |
19 |
tab completion and all. When mounting, I let fstab remember the UUID |
20 |
for it. Very little typing and don't have to remember things. ;-) |
21 |
It's not like UUIDs are made to remember either. :-[ I think I put a |
22 |
label on the drive but things are a bit different when using |
23 |
cryptsetup. At least I think they are. The easiest thing, just having |
24 |
the replacement drive as sdd again and me having sdk as my external |
25 |
drive. I still think a reboot is going to correct this. I can't |
26 |
imagine it not given how the drives are plugged in. I just wish there |
27 |
was a easy solution in the meantime. To be honest, I've had several |
28 |
times where this would come in handy. This is just yet another one. |
29 |
|
30 |
Your way would be consistent tho. If I could script this, it would be |
31 |
the best way to do it. Script it once, done. Of course, we know my |
32 |
scripting skills are minimal at best. If you could say I even have |
33 |
scripting skills. lol |
34 |
|
35 |
Dale |
36 |
|
37 |
:-) :-) |