Hi
I installed opensuse lvm encrypt and dual boot win 10
my partition:
1:win10 (ntfs)
2:boot/efi (fat)
3:/boot (ext2)
4:lvm encrypt (opensuse)
5:unallocated (empty)
I login with windows and added partition in the windows
after reboot and select opensuse and enter password lvm but not start opensuse freeze screen 3 dot
I test and open lvm encrypted with live cd that is safe not have problem
how to fix?
after input password lvm. only.show 3 lines messages
Reached target Encrypted volumes.
Reached target system initialization.
Reached target basic system.
I think after added partition in the windows. change /dev/disk/by-id
etc/crypttab
how repair /etc/crypttab?
I can access lvm with live cd
how to repair crypttab?
Thanks
my /etc/crypttab
cr_ata-ST1000LM024_HN-M101MBB_S31LJ9EDC04182-part13 /dev/disk/by-id/ata-ST1000LM024_HN-M101MBB_S31LJ9EDC04182-part6 none none
i think crypttab have problem after added partition in the windows
i dont know repaire /etc/crypttab
why crypttab not use UUId?
Please explain what you mean by “add a partition in the windows”???
my table partition is gpt
I had some space (unallocated) in hard disk the Windows operating system created a new partition
After Restart the Sytstm opensuse failed to start
strat grub and select opensuse 42.1
after input password lvm encrypted only show 3 lines messages
[OK]Reached target Encrypted volumes.
[OK]Reached target system initialization.
[OK]Reached target basic system.
I would guess that in the /ect/cryptab content has changed by adding a new partition
If I am correct password is entered incorrectly or not
This messages shows only
[OK]Reached target Encrypted volumes.
[OK]Reached target system initialization.
[OK]Reached target basic system.
[FONT=Lucida Grande]I would guess that in fact, can not mount partition lvm[/FONT]
my partition now
Device Start End Sectors Size Type
/dev/sda1 2048 616447 614400 300M Microsoft basic data
/dev/sda2 616448 821247 204800 100M EFI System
/dev/sda3 821248 1083391 262144 128M Microsoft reserved
/dev/sda4 1083392 106391551 105308160 50.2G Microsoft basic data
/dev/sda5 106391552 106719231 327680 160M Linux filesystem
/dev/sda6 107040768 207079423 100038656 47.7G Linux LVM
/dev/sda7 291561472 449804287 158242816 75.5G Microsoft basic data
/dev/sda8 449804288 884230143 434425856 207.2G Microsoft basic data
/dev/sda9 884230144 1373304831 489074688 233.2G Linux filesystem
/dev/sda10 1373304832 1953523711 580218880 276.7G Microsoft basic data
sda5=/boot(ext2)
sda6= opensuse42.1 (lvm encrypt)
sda10=(added new a partition)
No one to help?
What’s sda9??
It looks like you only put root in the LVM but root is just the OS and there is small reason to encrypt only that. Normally you would put both root and home in the LVM to protect your data. Note that boot partition is a little small should be able to hold 3 kernels at a time I recommend 400-500 meg to be safe. 160 meg seems a bit tigh.
t
I can access lvm live media
168(/boot) is small but 50% is free
sda9 is personal data luks crypted
root and home and sawp are into lvm (sda6)
─sda6 8:7 0 47.7G 0 part │ └─lvm 252:4 0 47.7G 0 crypt
│ ├─system-home 252:5 0 16.2G 0 lvm
│ ├─system-root 252:6 0 29G 0 lvm
│ └─system-swap 252:7 0 2.5G 0 lvm
My system worked before without any problems.
After adding a new partition the problem arose
I never touched a Linux partition and not more or less
root and home and sawp are into lvm (sda6)
[FONT=Tahoma]
[/FONT]├─sda6 8:7 0 47.7G 0 part
│ └─lvm 252:4 0 47.7G 0 crypt
│ ├─system-home 252:5 0 16.2G 0 lvm
│ ├─system-root 252:6 0 29G 0 lvm
│ └─system-swap 252:7 0 2.5G 0 lvm
My system worked before without any problems.
After adding a new partition the problem arose
I never touched a Linux partition and not more or less
I saw your post yesterday, but did not understand the issue.
I think I now understand.
When I add a partition with “gdisk”, it always gets a new partition number. But when Windows adds a partition, it sometimes renumbers existing partitions. Using UUID is supposed to avoid that. But, as you mention, normally UUID is not used in “/etc/crypttab” (at least by opensuse).
Yes, you can use UUID in /etc/crypttab.
Here’s the first entry in my “/etc/crypttab”:
cr_ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F6EFRFHX-part5 /dev/disk/by-id/ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F6EFRFHX-part5 none none
I could change that to:
cr_ata-WDC_WD10EZEX-00BN5A0_WD-WCC3F6EFRFHX-part5 UUID=71b2d921-1218-43cf-9685-0ba76339bf28 none none
Note that it is the second column that I changed. The first column is a virtual name and does not have to match the hardware. If I were actually making that change, I would perhaps also change the first column to something shorter like “cr_wdc_lvm”.
Unfortunately, there’s a catch to all of this. The easy way is to make those changes before Windows messes up your partition table. But once that is happened, you will need to do some repairs.
Boot from rescue media - preferably your install media, but at least it should be the same architecture (ie 32bit or 64bit should match the installed system.
I describe rescuing in a blog post Linux rescues
If your root file system uses “btrfs”, there’s an addition step. See The “btrfs” file system and linux rescues
Then, after doing the “chroot” command into the mounted system, you will need:
# mkinitrd
# grub2-mkconfig -o /boot/grub2/grub.cfg
Do those steps after “fixing” “/etc/crypttab”. And you should use the names from that updated “crypttab” to open and mount the encrypted file system for the rescue repair.
@nrickert
I run recuse live media
I do step to step
but I don’t know how to. update /etc/crypttab?
mount root and edit it.
I run recuse root
1:cryptsetup open --type luks /dev/sda6 lvm
2:mount /dev/mapper/system-root /mnt
3:mount /dev/mapper/system-home /mnt/home
4: mount /dev/sda6 /mnt/boot
5:mount /dev/sda2 /mnt/boot/efi
6:mount --bind /dev /mnt/dev
7:mount --bind /proc /mnt/proc
8:mount --bind /sys /mnt/sys
9:chroot /mnt
10:mkinitrd
11:grub2-mkconfig. -o /boot/grub2/grub.cfg
12 exit then reboot but not work
What I write what alternative into crypttab
how to edit crypttab with treminal?
Did you modify /etc/crypttab as suggested?
No, I do not know how to correct