OMV died just after one week of running - What happened?

1. offizieller Beitrag

    Hello, newbie here.


    I got OMV up and running, setting everything up. Let'sencrypt, nginx web server, deluge in docker, plex server as apt-get install, fail 2 ban as apt-get too (some plugins wasn't working etc). Took me some days.


    Anyway today when I was to log into deluge webui I notice I cannot connect. I check that OMV is still running, but seem a bit sluggish. I reboot and can't login at all. Something has gone corrupt.


    By chance I had an ssh session open. At 13:57 something happened. That's my question:


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.352998] Internal error: Oops - BUG: 0 [#1] SMP ARM


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.508091] Process mount (pid: 16127, stack limit = 0x35e4d873)


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.514181] Stack: (0xda91b918 to 0xda91c000)


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.518597] b900: 00000000 10000000


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.526894] b920: 00000000 c04508d8 da91b94c ffffffff 00007fff c09980c8 ffffffff 1000ffff


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.535191] b940: da91b96c 2ff987aa dac5da48 ffffffff dee88018 00007fff 00000000 0000ffff


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.543488] b960: da91b9bc da91b970 c044f8bc c0459f50 ffffffff 0000ffff 00000002 c024c99c


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.551784] b980: da91b9b4 0000b73a d878c6c0 0000ffff dd438000 00000000 00000000 00000000


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.560081] b9a0: 00000000 03b87fff 00000000 00000000 da91ba14 da91b9c0 c04508d8 c044f76c


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.568378] b9c0: 03b87fff 00000000 00000000 00000000 c1059440 dee87784 00000000 00000000


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.576674] b9e0: dac5da48 d78a6d00 da91ba0c dac5da48 da91bb60 c1004d88 00000000 00000000


    Message from syslogd@raspberrypi at Oct 9 13:57:18 ...
    kernel:[ 4624.584971] ba00: 00000001 00000000 da91baec da91ba18 c0454b60 c0450788 da91ba68 da91ba80


    [... it keeps going like this until the session terminates because of broken pipe]


    What the hell happened here? System was just "idling" at that time. Please help.


    Raspberry Pi 4b 2GB ram, 64GB UHC class 10 quality card. I had just got an 8 GB card yesterday as I was thinking of shrinking my backup image so it would be easier to manage. Guess I could start over on that card now.


    Any insight into what might have happened appreceated. :) Also is v5 stable enough? From my own tinkering I would never use OMV 4 for any serious production. I love it but too bad that it doesn't run smooth with this hardware at least. Keep up the good work. :)


    :D Thank you



    Update edit: The system finally booted but it took a very long time.

    • Offizieller Beitrag

    It sounds like you had other very serious problems? Fail2ban? Some plug-ins not working?


    Once you have a nice basic config working, and everything updated, clone the SD card. Only then start adding extra stuff. And clone again when things look stable. Or revert to a previous working config if something messes stuff up and you can't fix it. Don't try to pave things over or let bugs slide. It often comes back to bite you.


    And if there is a choice between using docker and apt install, use docker.


    Where was your docker base path? Make sure to set it to some better location than /var/lib/docker. A hdd or a ssd. And if you install something, make sure not to use /var/lib for storage of metadata and stuff.

    Thanks for the feedback! You are right. Better reinstall everything. Should go quick now when I kind of know what I am doing.


    I am not sure what you mean by docker base path? Do you mean the /config path? I had those on a separate usb stick. Used only for docker appdata.


    Maybe you mean something different? If so, how do I go about changing the path?


    Yes I have had some problems from the get go. But it's half the fun innit? ;)


    Was about to backup but realized the 64GB was a tad bit too big. Again. Thank you sir. Anyway the current install is not to be trusted I feel. Kernel errors don't give me any confidence in this hehe.


    And yes. Some plugins would not work. Therefor the workaround with fail2ban etc. Replicati plugin not working. Tried docker but could not even login to the webui so ditched that idea.

    • Offizieller Beitrag

    In the GUI for docker you can set the docker base path. But you need to do it before you install any dockers.


    There is nothing wrong with a 32 or 64 GB card. Sure, you only need around 8 GB, but the extra unused storage is not actually wasted. SD cards use wear leveling to increase the longevity of the card. When you write to the card the writes are not written to the same physical memory locations, but rotated to distribute the wear. So a 64 GB card you only use 8 GB of can be expected to last much longer than a 8 or 16 GB card.


    And there is no longer much of a price penalty for a 64 GB card over a 32 or 16 GB card. And you may have problems even finding a high performance A1 or A2 class 8 GB SD card...

Jetzt mitmachen!

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

Benutzerkonto erstellen Anmelden