Error when installing via packages

  • Hello,


    I've been trying to install omv from the provided package repository (https://packages.openmediavault.org) on a fresh Debian 10 install.


    An error occurs when running the postinst script from the openmediavault package:



    The server is a server hosted in OVH, with 1x500GB nvme for OS (that's where Debian is stored) and 4x4TB HDD disks that are, for now, unpartitionned (thus unmounted and not even mentioned in /etc/fstab).


    I've had a look at the corresponding file, and it seems related to searching for "non rotational" disks, could the fact that I'm running under a nvme disk be the problem here?


    I also did an extensive search on Google but I didn't find anything except for some things about the YAML parser and Salt.


    Is there someone here that could help me on such an error?


    Best regards

    • Offizieller Beitrag

    I've been trying to install omv from the provided package repository (https://packages.openmediavault.org) on a fresh Debian 10 install.

    Have you tried this approach as well?

    https://github.com/OpenMediaVa…-Developers/installScript

  • Hello


    votdev: wow thanks for the fix, I didn't expect to have something done so quickly. Is there a way for me to test if the fix is good without waiting for the packages database to be updated?


    macom I haven't tried it, it seemed at the time more related to "local" installations like on a SBC, whereas I'm trying to install it on a dedicated server in a datacenter. Also from what I'm seeing from the script file, around line 171, it seems to install OMV also from the packages repository, so I think I'll hit the same hurdle by using the script, as the error occurs during the package postinst phase.


    In any case thanks for having a look at my problem, I'm eager to look at OMV once I can fix this. :)

  • Hello votdev


    I waited for the new release, and saw today that the 5.5.4-1 package was available on the Github repository.


    Unfortunately on my configuration, it didn't fix my problem, and only moved the error line after the 3 you added:


    Here are more information if it can help:

    Code
    $ sudo cat /etc/fstab
    UUID="9f51e591-9764-4476-91d5-e4df1cc7cb78" / ext4 defaults 0 0
    UUID="a683543e-f827-41e3-a145-aa68e1922057" swap swap defaults 0 0
    LABEL=EFI_SYSPART /boot/efi vfat defaults 0 0

    I enabled the debug logging on the Salt minion but nothing more related to this error appears in the logfile so I don't think it'll help. I'd be happy to help debug it in any way I can.


    Do tell if you want me to open a Github Issue instead for better tracking of this beast.

  • Hello votdev,


    I kept investigating on this bug as it prevents me to finish the setup of my OVH server, and I think I found the origin of the issue.


    As you can see on my sudo salt-call mount.fstab, my root partition is defined on the device UUID="9f51e591-9764-4476-91d5-e4df1cc7cb78". And I think you'll see where the problem is if I highlight that this string has quotes.


    I ran through my debug log of salt minion and found the rendered YAML of the default.sls file:


    As you can see, and as Yaml online parser confirms, as the quotes are not escaped in the rendered YAML, the parsing fails completely and the script doesn't go further.


    As I see it, I have two ways to fix it:

    - Either change my /etc/fstab initial file to use something else than the UUID to describe my entries.

    - Or change the sls file to handle output from mount.fstab that contain quotes.


    Given that using UUIDs in /etc/fstab is not unusual, I think the latter is the better solution. If you want, I could go on and send a PR your way once I remind myself with Jinja and Yaml and find how to fix it.


    Best regards

    • Offizieller Beitrag

    Given that using UUIDs in /etc/fstab is not unusual,

    While I agree the code should be fixed to handle the quotes, the default OMV install does not use quotes around the UUID in fstab. If you just remove the quotes, I would guess your system would be fine.

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

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • Hello ryecoaaron,


    You are right, when I wrote my message I had forgotten that UUIDs can be used without quotes in fstab. That's actually what I ended up doing, and I can confirm the installation goes to completion afterwards.


    In a way we could blame all of this on the error message of the YAML parser that was very cryptic and not helpful at all. Being a developer myself I get so frustrated when you have such error messages. To think that, if the message mentioned the quotes, this thread wouldn't have existed... Oh well.


    Sorry for the inconvenience, votdev you can still tell me if you'd like a PR from me, I'd be glad to have a go at it :)


    Best regards,

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!