I have a problem with LVM encrypted disk. The system is openSUSE 13.2 32-bit (NB! it was downgraded Leap 42.1 64-bit system). GRUB gives me a choice booting with kernels 4.1.12, 4.1.15 or 3.16.6 - kernel version 4 do not work a 32-bit computer and doing nothing; kernel 3.1.6.6 asks nicely hard disk password and accept them, but however, are not mounted to the home directory but just hangs with an error message.
I have a need at least to copy the files from home directory to external disk. The username and password of course I know.
At this moment I do not have 64-bit computers available.
Please help!
Downgrading a 64-bit system to a 32-bit system was a bad idea.
In any case, you can access the LVM by booting rescue media (32-bit or 64-bit should not matter).
# cryptsetup luksOpen /dev/sdXy logical_name
# vgchange -a y
# ls /dev/mapper
In the first of those commands, the “/dev/sdXy” will be something like “/dev/sda5” – the device for your encrypted LVM. And “logical_name” is just a handle for referencing it. I typically use “cr_lvm” for that.
The last command should list special devices to access the volumes in the encrypted LVM. Mount one or more of those volumes at a convenient place to get access.
If you want it to work the way you intended, you could try a clean install of 13.2 on that system. At the partitioning section of install, click “create partitioning”. On the next screen, select “custom partitioning”. On the next screen, try clicking “Import mount points” – this will probably allow you to select exact the partitioning that you had been using. It will reformat the root LVM volume, but should preserve home (which I hope is a separate volume). It will also want to reformat “/boot” which you probably have as a separate partition.
Correction to my previous post.
Trying sda2 and it’s works. ls /dev/mapper shows me cr_lvm system-home system-root system-swap but mounting failed (mount.bin: cant find * in /etc/fstab).
I think that fstab are corrupted and this is the reason of the problem.
That does not look to me like a corrupt fstab. Because I can not find any * in my fstab and that is fine. Something tries to use a * where it shouldn’t. Just my idea.
And of course, when you think you have a problem in your fstab, why don’t you post it? Only so can we confirm your conclusion or comment otherwise.
cat /etc/fstab
BTW, better copy/paste the thing complete (prompt, mount command, the output, the next prompt) and no story telling with something that could be an error message or just your memorizing of it. And then of course between CODE tags: the # button in the tool bar of the post editor.
Some remarks on the request I did (imho also on behalf off others here and for the sake of helping you most efficient).
I asked you to post complete: the prompt, the command, the output and the next prompt. We now have from you only the output (which is very different from what you told first and that confirms that we should not believe what people say, but only what the computer says). So where is the rest? Waht did you do? A mount statement, list part of a log? saw it on the screen and copied it by typing?
Same for the fstab. Again a story about vi and what you see instead of the simple cat /etc/fstab I asked for.
that would have looked trustworthy and full of information. It would not require you to tell what you did, because we see it, nor who you where or where you were, because we see the prompt. Even adding your conclusion “it seems to be empty” would’n have been required (though not forbidden).
And after this (I hope you remember next time how to provide info efficient), yes that looks like something (maybe the downgrading, I assume that is not something realy supported, maybe depending on the way you did it) emptied your fstab. Do you have a backup of it? Or are you abble to recontrsuct it yourself? MMaybe by using YaST > Partitioner? Or do you need help in restoring it?
Fine you recovered it. But for those that come here after you because they experience something similar, please explain in short what exactly how you did it.
