Re: odd name of LUKS partition

2022-07-07 Thread David
On Fri, 8 Jul 2022 at 07:25, Piscium wrote: > On Wed, 6 Jul 2022 at 03:19, Piscium wrote: > > I won't bother changing the name, I was just curious. > > In the end I changed the name of the LUKS partition. It was easy. I am > posting here the commands in case someone else is interested. > > As ro

Re: odd name of LUKS partition

2022-07-07 Thread Piscium
On Wed, 6 Jul 2022 at 03:19, Piscium wrote: > I won't bother changing the name, I was just curious. In the end I changed the name of the LUKS partition. It was easy. I am posting here the commands in case someone else is interested. As root: 1. dmsetup rename /dev/mapper/oldname newname 2. edit

Re: odd name of LUKS partition

2022-07-06 Thread Piscium
On Wed, 6 Jul 2022 at 03:35, David Wright wrote: > A dozen or so lines from the end of /var/log/installer/syslog, > you'll probably see a line like: > > Apr 17 01:43:04 cdrom-detect: Unmounting and ejecting '/dev/sdXn' > > which is the d-i "ejecting" the "CD" that the installer was on. Thanks, D

Re: odd name of LUKS partition

2022-07-05 Thread David Wright
On Wed 06 Jul 2022 at 03:19:20 (+0100), Piscium wrote: > On Wed, 6 Jul 2022 at 03:06, David wrote: > > > > Because the drive with the LUKS partition was identified as sdb > > when the installer was running. Perhaps the installer was running > > from sda. This name 'sdb3_crypt' is just an arbitrary

Re: odd name of LUKS partition

2022-07-05 Thread Piscium
On Wed, 6 Jul 2022 at 03:06, David wrote: > > Because the drive with the LUKS partition was identified as sdb > when the installer was running. Perhaps the installer was running > from sda. This name 'sdb3_crypt' is just an arbitrary string used > to name the LUKS volume in /etc/crypttab. You can'

Re: odd name of LUKS partition

2022-07-05 Thread David
On Wed, 6 Jul 2022 at 11:58, Piscium wrote: Hi, > Recently I installed bullseye on a PC using netinst. During > installation I used the automatic installer and chose encrypted mode > with some space left empty. This is what I got: > > root@backup-server:~# lsblk > NAME