Re: Change for systemd the UUID of the home partition, how to?
On 10/06/15 09:48 AM, Sven Arvidsson wrote: What does your /etc/fstab look like? Like this: file system mount point type options dump pass /dev/mapper/BDS1-root / ext4errors=remount-ro 0 1 /dev/mapper/BDS1-boot /boot ext2defaults0 2 /dev/mapper/BDS1-home_crypt /home ext4defaults0 2 /dev/mapper/BDS1-tmp_crypt /tmpext2defaults0 2 /dev/mapper/BDS1-var /varext4defaults0 2 /dev/mapper/BDS1-swap_crypt noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 UUID=640F-A4A6 /media/fda vfatrw,user,noauto,noatime 0 0 UUID=27AD-9963 /media/fdb vfatrw,user,noauto,noatime 0 0 UUID=FC68-7915 /media/fdc vfatrw,use,rnoauto,noatime 0 0 UUID=E883-A903 /media/fdd vfatrw,user,noauto,noatime 0 0 UUID=9016-4EF8 /media/sdd vfatrw,user,noauto,noatime 0 0 The basic construction is a RAID1 (two 1 tb hard drives) which form the only physical volume for LVM2, and there is only one virtual volume BDS1 in this physical volume. This virtual volume has six logical volumes, all beginning with BDS1. Three of these are encrypted; swap with a random passkey, and /tmp and /home with their own passkeys. When I first installed Jessie in the box, I assigned all the space in the virtual volume to these six logical volumes. At the partitioning phase of the installation the space assigned to the /var partition I based on what I had done for Squeeze and Wheezy. That size proved too small for Jessie. To enlarge the size for the /var for Jessie I first had to reduce the size for /home. I found on line instructions as to how to do so. Those instructions unfortunately did not tell me that the crypt has to be resized as well as the file system and the logical volume. The result was that the all the data in the /home partition were obliterated. Fortunately I had backed up all of them. The new encrypted /home partition that I now had to create has a different UUID. I copied it to file /etc/crypttab which now reads as follows: #BDS1-home_crypt UUID=5ea1826e-2824-4544-a33b-e2c72d65e60e none luks BDS1-home_crypt UUID=29aeb184-8d5c-4165-824a-2b8a11e477e9 none luks #BDS1-home_crypt UUID=e59565df-6a23-45fd-af55-5c0b7040eedd none luks BDS1-swap_crypt /dev/mapper/BDS1-swap /dev/urandom cipher=aes- xts-plain64,size=256,swap BDS1-tmp_crypt UUID=a9360e7f-7ddb-41c4-9dfe-51a8a41db7e4 none luks The first line above is commented out because it is the UUID for BSD1-home_crypt which I entered in error. The UUID I entered in the second line is I assume the correct UUID to open BDS1-home_crypt, being in fact the UUID listed by blkid (quoted below) as the UUID for BDS1-home. The third line, commented out, was the UUID of the /home partition before it was resized. The last two lines for swap and /tmp, which I left unchanged. After resizing the /home and /tmp partitions and rebooting I was not asked to enter the passkeys for these two partitions. Instead the process went to recovery mode. I consequently entered the root password and ran 'journalctl -xb. Here are the major error messages I received: BSD system-crypt-generator [185]: Failed to create init file /run/systemd/generator.systemd-crypt-setup@BSD1. BSD systemd [182]: /lib/systemd/system-generator/systemd-cryptsetup-generator failed with error 1. Then later were two more: BDS system [1]: Job dev-mapper-BDS1\x2dtmpcrypt.device/start timed out BDS system [1]: Timed out waiting for device dev-mapper-BDS1\x2dtmp_crypt.device. These last two were repeated two more times with different device names, \x2dhome_crypt.device and \x2dswap_crypt.device. So, as I said in my second post, I need to do something to make systemd recognize the UUIDs in the /etc/crypttab file. The last error message was about something quite different: BDS system [1]: Failed to start Console System Startup Logging. Since no logging is being done in a syslog file I take this message to mean that in resizing the /var partition that process was broken. That result may have been caused by the fact that merely booting the computer causes the /var partition to be busy. The only way I could unmount it was by commenting out the /var line in file /etc/fstab and reboot. I could then resize it. Afterwards I commented the /var/ line back in again, thereby causing it to be remounted. So I now also need to know how to reactivate the Console System Startup Logging. After all these changes I was able to open both the /home and /tmp partitions by running cryptsetup luksOpen. After doing so command blkid produced the following. /dev/sdb1: UUID=8819eaea-bac1-3907-cbc0-90413f1d9bdb UUID_SUB=884424dc-ea70-d13c-6c86-4416cb54c39e LABEL=BDS:0 TYPE=linux_raid_member PARTUUID=0007499e-01
Re: Change for systemd the UUID of the home partition, how to?
On Thu, 11 Jun 2015 00:02:02 -0400 Ken Heard kensli...@teksavvy.com wrote: On 2015-06-10 13:17, Don Armstrong wrote: On Tue, 09 Jun 2015, Ken Heard wrote: After some research I found file /etc/crypttab which contains a list of the UUIDs for encrypted partitions, /home in my case. I thought it would be a simple matter of changing the relevant UUID to the current one. It is apparently not. Did you rebuild the initramfs at this stage? If not, you'll need to do that first. Yes, that needed to be done; and I did so. Putting the relevant UUIDs in file /etc/crypttab, which I also did, however is not enough to have the boot process ask for the passkey for encrypted partitions and so to allow mounting of them, in my case /home and /tmp. Systemd requires some other rebuilding to allow it to use the information in file /etc/crypttab. So, unless someone on the list knows enough about systemd to tell me what to that process is and how to do it, I am reduced to two choices: either take the time (how long?) to learn about systemd, or to reinstall Jessie in the box. If the latter, which probably will be quicker, it will be the third time I had to do so since mid-April when I first installed Jessie in this box. Like Sven has asked, what does your /etc/fstab look like? Petter -- I'm ionized Are you sure? I'm positive. pgp6zOmXfG17a.pgp Description: OpenPGP digital signature
Re: Change for systemd the UUID of the home partition, how to?
On Tue, 2015-06-09 at 13:37 -0400, Ken Heard wrote: On 2015-06-09 11:18, Ken Heard wrote: For reasons which I won't go into now my encrypted home partition was obliterated. (Yes, all the data thereon had been backed up.) I created a new one, but of course it does not have the same UUID as the previous one. Jessie's systemd however on boot continues to look for the old UUID for that partition. Consequently the encrypted home partition can no longer be opened during the boot. I would be grateful if anyone can tell me where the UUIDs of the encrypted partitions to be opened on boot, such as tmp and home, are stored so that systemd can find them during the boot? After some research I found file /etc/crypttab which contains a list of the UUIDs for encrypted partitions, /home in my case. I thought it would be a simple matter of changing the relevant UUID to the current one. It is apparently not. I have never had to do any systemd-specific configuration for my encrypted partitions. (Then again, I haven't changed UUID either) /etc/crypttab is usually included in the boot (when you build an initramfs) at least when / is encrypted, I'm not sure about /home. What does your /etc/fstab look like? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 6FAB5CD5 signature.asc Description: This is a digitally signed message part
Re: Change for systemd the UUID of the home partition, how to?
On Tue, 09 Jun 2015, Ken Heard wrote: After some research I found file /etc/crypttab which contains a list of the UUIDs for encrypted partitions, /home in my case. I thought it would be a simple matter of changing the relevant UUID to the current one. It is apparently not. Did you rebuild the initramfs at this stage? If not, you'll need to do that first. -- Don Armstrong http://www.donarmstrong.com I really wanted to talk to her. I just couldn't find an algorithm that fit. -- Peter Watts _Blindsight_ p294 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150610171722.GO23250@geta
Re: Change for systemd the UUID of the home partition, how to?
On 2015-06-10 13:17, Don Armstrong wrote: On Tue, 09 Jun 2015, Ken Heard wrote: After some research I found file /etc/crypttab which contains a list of the UUIDs for encrypted partitions, /home in my case. I thought it would be a simple matter of changing the relevant UUID to the current one. It is apparently not. Did you rebuild the initramfs at this stage? If not, you'll need to do that first. Yes, that needed to be done; and I did so. Putting the relevant UUIDs in file /etc/crypttab, which I also did, however is not enough to have the boot process ask for the passkey for encrypted partitions and so to allow mounting of them, in my case /home and /tmp. Systemd requires some other rebuilding to allow it to use the information in file /etc/crypttab. So, unless someone on the list knows enough about systemd to tell me what to that process is and how to do it, I am reduced to two choices: either take the time (how long?) to learn about systemd, or to reinstall Jessie in the box. If the latter, which probably will be quicker, it will be the third time I had to do so since mid-April when I first installed Jessie in this box. Regards, Ken -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5579083a.5050...@teksavvy.com
Change for systemd the UUID of the home partition, how to?
For reasons which I won't go into now my encrypted home partition was obliterated. (Yes, all the data thereon had been backed up.) I created a new one, but of course it does not have the same UUID as the previous one. Jessie's systemd however on boot continues to look for the old UUID for that partition. Consequently the encrypted home partition can no longer be opened during the boot. I would be grateful if anyone can tell me where the UUIDs of the encrypted partitions to be opened on boot, such as tmp and home, are stored so that systemd can find them during the boot? Regards, Ken -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557703b6.6010...@teksavvy.com
Re: Change for systemd the UUID of the home partition, how to?
On 2015-06-09 11:18, Ken Heard wrote: For reasons which I won't go into now my encrypted home partition was obliterated. (Yes, all the data thereon had been backed up.) I created a new one, but of course it does not have the same UUID as the previous one. Jessie's systemd however on boot continues to look for the old UUID for that partition. Consequently the encrypted home partition can no longer be opened during the boot. I would be grateful if anyone can tell me where the UUIDs of the encrypted partitions to be opened on boot, such as tmp and home, are stored so that systemd can find them during the boot? After some research I found file /etc/crypttab which contains a list of the UUIDs for encrypted partitions, /home in my case. I thought it would be a simple matter of changing the relevant UUID to the current one. It is apparently not. I found a reference to systemd-cryptsetup-generator, the manual for which makes reference to further steps which I do not understand. Systemd-cryptsetup-generator does not seem to be a command. After changing the relevant UUID in the crypttab file I discovered that a reboot caused the /home directory to be opened without my entering the passkey. The computer however did not go on the install the DE; instead it went to recovery mode. Regards, Ken -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55772473.2070...@teksavvy.com
