New (wrong!) mountpoint after decrypting with Luks encryption and the filesystem has no data anymore

  • Hello :)

    I have some problems with the Luks plugin, or file system: after each reboot the disk is encrypted. Should be so. But after decrypting, the file system is mounted at a new mountpoint! The old one (before reboot) is shown as missing... all references point to the old, missing one.


    So I have no chance to access my data.


    Details to reproduce the error:

    1. install OMV clean (or existing installation)

    2. install Luks encryption plugin

    3. encrypt empty disk, unlock and create a filesystem (without raid. With raid everything works as it should ??)

    4. restart OMV, decrypt the disk. Now the original file system is shown as missing, but a new, empty one exists.


    The whole behavior really doesn't give me confidence in OMV - I almost lost 3 disks (all luks-encrypted. In case of need a backup would have been available).

    As a workaround I am now testing OMV 6...


    Does anyone know more about this behavior? With OMV raids (mirror) everything worked fine, only with a single disk with btrfs system it doesn't work....



    System:

    -Hp Desktop PC with i5 CPU

    -OMV 5.6.13

    -Various hard disks tested




    edit: It seemed like it's a Luks bug and I wasn't able to find a quick-fix. However, I upgraded to OMV 6 and was able to read all discs, aswell as setting everything up again. I'm currently using OMV 6.0-34 with LUKS and everything is working stable.

    Edited 5 times, last by apricot: final findings: ().

  • apricot

    Changed the title of the thread from “Neuer (falscher!) Mountpoint nach dem entschlüsseln mit Luks encryption und das Dateisystem hat keine Daten mehr” to “New (wrong!) mountpoint after decrypting with Luks encryption and the filesystem has no data anymore”.
  • OMV 6 seems to be better now... but I'm still testing it


    edit: Ok, looks like I'm going with OMV 6 then... luckily it's working there - otherwhise I must have switched away from OMV :(

    • Official Post

    Must have been something weird on your system. Just tried with OMV5 in a VM and works as expected.

    As there are no other reports of this behavior most likely there has been something wrong on your try with OMV5.


    Glad it is working for you now on OMV6. Is the better choice anyway in my opinion as OMV5 will soon be end of life.

  • macom

    Added the Label resolved
    • Official Post

    otherwhise I must have switched away from OMV

    This isn't an OMV issue. It is possibly an issue with the LUKS plugin (which isn't even core OMV). You shouldn't give up on something so fast because of a bug. I maintain that plugin and while I know LUKS well, I don't use the plugin. I need help from users who find issues and help fix them.

    omv 7.4.17-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.2.16 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • This isn't an OMV issue. It is possibly an issue with the LUKS plugin (which isn't even core OMV). You shouldn't give up on something so fast because of a bug. I maintain that plugin and while I know LUKS well, I don't use the plugin. I need help from users who find issues and help fix them.

    I know it's most likely a luks bug. But I need a stable, encrypted server - and as long as there's no bugfix, OMV isn't the right thing for me, as much as I enjoy OMV.

    I'm using OMV for a small sized business and for recording a live-strem, those where the reasons I was searching for a quick fix (or quick alternative). After switching to OMV 6 today, everything seems to be going well. OMV 6 seems more stable on this topic and even my faulty drives are working like a charm.


    Thanks for your reply. I'm very happy OMV 6 is working just perfect (except hot-swap, but it's not a big problem). I hope it helps everyone with a similar problem. And ryecoaaron: thanks for working on this great plugin :)

    • Official Post

    and as long as there's no bugfix, OMV isn't the right thing for me

    Can't fix bugs that I don't know about or reproduce.

    I'm using OMV for a small sized business and for recording a live-strem, those where the reasons I was searching for a quick fix (or quick alternative).

    Just curious why server encryption is a requirement? I work in the enterprise (healthcare at that) and almost nothing we have is encrypted.

    omv 7.4.17-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.2.16 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Just curious why server encryption is a requirement? I work in the enterprise (healthcare at that) and almost nothing we have is encrypted.

    I wanted it as a prerequisite since customer and company data is on the server. Not critical, but I wanted to protect them in case the server is stolen (small server).

    But is partly certainly also joy of technology.


    However, I'm a bit surprised that the server in the health care system is not also encrypted - but maybe I'm too strict.


    Finally, I like OMV 6 a lot, has been very stable and nice to use so far.

    • Official Post

    But is partly certainly also joy of technology.

    That joy turns to horror when your LUKS device becomes corrupt or you lose your password.


    I'm a bit surprised that the server in the health care system is not also encrypted - but maybe I'm too strict.

    The drives on the storage arrays are encrypted at rest but that means very little since you would have a tough time stealing an array. Data is usually not physically stolen but is stolen via hacks when drives would be unlocked. That means encryption is not helping much.


    Finally, I like OMV 6 a lot, has been very stable and nice to use so far.

    Glad to hear. I've been using it for months. I have had no issues. Most of the issues people bring up are nitpicks from the framework change.

    omv 7.4.17-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.2.16 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!