Fresh installation and : "systemctl maintenance"

  • Hi :D




    I have a problem with my fresh arrakis installation !



    When I reboot, arrakis say I'm on maintenance mode and I can see log or continu booting. So i continu booting and all start "normaly" exept my raid volume doesn't mount ! I have to mount it on the GUI.




    Have you got any idees to fix my issue ?


    Thx :

    • Offizieller Beitrag

    Your raid array isn't assembling correctly for some unknown reason. This why it stops at the maintenance prompt. If you don't fix your array, it will keep doing this.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Hi !



    After boot and manualy mount my raid, I go on the GUI I can see the raid statut and the statut is "clean".
    The detail :


    How can I check the raid area ?



    THX

    • Offizieller Beitrag

    How can I check the raid area ?

    The array is clean. Maybe it isn't assembling fast enough during boot? Are these usb drives and/or is this an RPi?


    I would run omv-mkconf mdadm as root to see if it helps.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • I use a n56 microserver and OMV is install on a SSD.
    I run
    omv-mkconf mdadm :


    update-initramfs: Generating /boot/initrd.img-4.18.0-0.bpo.1-amd64update-initramfs: Generating /boot/initrd.img-4.14.0-0.bpo.3-amd64



    I try to reboot ?

    • Offizieller Beitrag

    yes

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

    • Offizieller Beitrag

    Your array still isn't assembling in time. Hard to say why. Look through boot logs to see if something is obvious. This is one of the reasons why I think most people shouldn't use raid.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Okay, I run
    systemctl list-units --failed :



    UNIT LOAD ACTIVE SUB DESCRIPTION



    ● mdmonitor.service loaded failed failed MD array monitor
    ● systemd-fsck@dev-disk-by\x2dlabel-Data.service loaded failed failed File System Check on /dev/disk/by-label/Data



    LOAD = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
    SUB = The low-level unit activation state, values depend on unit type.



    2 loaded units listed. Pass --all to see loaded but inactive units, too.
    To show all installed unit files use 'systemctl list-unit-files'.



    Do you think it's a clue ?

    • Offizieller Beitrag

    Do you think it's a clue ?

    No. Both of those probably failed because your array isn't assembling.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

Jetzt mitmachen!

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