Posts by y2kdread

    It seems to be a hardware stability problem. Is the cpu overclocked? Have you updated to the latest bios? Maybe the power supply is having issues under high load? Hard to say.

    Turns out it was the power supply! I wasn't overclocking and I don't think it had to deal with a high load. I hooked up a kill-a-watt to the machine and the max I saw it pulling was 85 watts and the supply is rated for 450 watts. I ended up buying a higher end power supply and the problem went away. It's strange that the hanging happened with a specific set of criteria. I would think a power supply issue would be random.


    Either way, I hope this thread helps people out of they see the same thing in the future.


    Thanks for your help!

    Fully updated OMV 4?
    Did you try the proxmox kernel that you can install from the Kernel tab of omv-extras?
    Did you run memtest to make sure the memory is ok?

    I ran memtest, switched to the proxmox kernel, and finally was able done making changes. Sadly, the issue reoccured. I did have the terminal up and got the following error:


    Code
    Message from syslogd@booknas at Apr 16 02:59:28 ...
    kernel:[209987.536806] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [kworker/u64:0:23400]

    Would this be due to a bad CPU or unrelated?

    I am running 4.1.21 which I believe is the latest version.


    I haven't ran memtest on this latest memory, but I'll do that to double check.


    I also haven't tried the proxmox kernel, what's different about that kernel?

    Hi Everyone,


    I recently built a new server for OMV and have been experiencing Nightly hangs. The server is unresponsive and needs a manual reboot in order to come back up. I've swapped out several components and performed a fresh install of OMV every time. The hangs don't seem to happen if I reboot the server in the afternoon/evening. For example. I rebooted the server yesterday around 19:30 last night and didn't see the behavior. My server setup is as follows:


    CPU: AMD Ryzen 5 1600
    Motherboard: B450I Gaming Plus AC (also tried using a ASRock Mobo)
    Memory: G.SKILL FORTIS Series 16GB (8GB x 2) (also tried Crucial and Patriot memory)
    SSD Drive: ADATA SU800 M.2 2280
    SATA Drives: Hitachi HDS72303 x 4
    USB Drive: WD My Passport 2599


    Last time the hang happened I saw the following logs:


    daemon.log

    Code
    Apr 10 06:26:13 booknas systemd[1]: Starting Daily apt upgrade and clean activities...
    Apr 10 06:26:14 booknas systemd[1]: Started Daily apt upgrade and clean activities.
    Apr 10 06:26:14 booknas systemd[1]: apt-daily-upgrade.timer: Adding 22min 22.439752s random time.
    Apr 10 06:26:14 booknas systemd[1]: apt-daily-upgrade.timer: Adding 40min 16.960270s random time.


    debug

    Code
    Apr 10 05:21:26 booknas rrdcached[1118]: started new journal /var/lib/rrdcached/journal/rrd.journal.1554891686.354734
    Apr 10 05:21:26 booknas rrdcached[1118]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1554884486.354732
    Apr 10 06:21:26 booknas rrdcached[1118]: flushing old values
    Apr 10 06:21:26 booknas rrdcached[1118]: rotating journals
    Apr 10 06:21:26 booknas rrdcached[1118]: started new journal /var/lib/rrdcached/journal/rrd.journal.1554895286.354742
    Apr 10 06:21:26 booknas rrdcached[1118]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1554888086.354727

    syslog

    Code
    Apr 10 06:21:26 booknas rrdcached[1118]: flushing old values
    Apr 10 06:21:26 booknas rrdcached[1118]: rotating journals
    Apr 10 06:21:26 booknas rrdcached[1118]: started new journal /var/lib/rrdcached/journal/rrd.journal.1554895286.354742
    Apr 10 06:21:26 booknas rrdcached[1118]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1554888086.354727
    Apr 10 06:25:01 booknas CRON[23598]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
    Apr 10 06:26:13 booknas systemd[1]: Starting Daily apt upgrade and clean activities...
    Apr 10 06:26:14 booknas systemd[1]: Started Daily apt upgrade and clean activities.
    Apr 10 06:26:14 booknas systemd[1]: apt-daily-upgrade.timer: Adding 22min 22.439752s random time.
    Apr 10 06:26:14 booknas systemd[1]: apt-daily-upgrade.timer: Adding 40min 16.960270s random time.
    Apr 10 06:30:01 booknas CRON[23795]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)


    Does anyone have any ideas on where else to look or something else to try?


    Thanks!

    In what way? Having just moved over to using mergerfs and snapraid I've not had a problem, I have 4 drives one is for the snapraid parity the other 3 are set under mergerfs with mount name home. Each share I create I create under that mount, so when I create an smb share say for music the shared folder selected is Music [on home, Music/]
    If you are referring to /sharedfolders rather than the absolute path /srv/<fuse mount>/sharename then yes there can be a problem if you try to reference those in some way. There is a long thread here regarding /sharedfolders and mergerfs, but I've had no issue as I don't reference those for instance in docker I use /srv.

    I am infact using /sharedfolders/ rather then the absolute path and have noticed a lot of problem with that. I was wondering how the shared folders work so I can possibly come up with a work around, but that thread seems to have a lot of good information.


    Where do you keep your docker config? Ideally, I would like to keep it on mergerfs but it doesn't seem like a great option due to the issues with shared folders.


    Also, if you need to rebuild do you just adjust the /srv/<fuse mount> in fstab to match the old GUID so you don't have to manually re-configure everything?

    Hi Everyone,


    How exactly do shared folders work within OMV? I don't see entries for mounts in the fstab file or anything like that.


    For a bit of background - I've been having issues with shared folders not working correctly when they point to a UnionFS filessystem. Instead of writing to the UnionFS path, they end up writing to my root install filesystem after a reboot. If I delete and re-create the shared folder, things work fine until my next reboot. I am tempted just to switch what I can over to manually created mounts in the fstab file, but would rather just do everything through OMV as designed.


    Thanks!

    From my understanding you have to use the absolute path i.e. /srv/dev-etc rather than the relative path /sharedolders

    I gave that a shot and it looks like it doesn't work for a select few apps. When I put my sonarr/radarr configs on the UnionFS path, it gives me errors about the database being corrupt. I also can't put a handful of other things on the UnionFS shared path.

    Hi Everyone,


    I've recently started to use a combo of SnapRAID and UnionFS and have been seeing some strange stuff. Is it possible to host things like the docker config on a shared folder hosted on UnionFS? It hasn't been working for me.


    Also, I've noticed a few issues putting various docker container config directories on shares hosted on UnionFS as well (mainly Sonarr and Radarr). Is this nomral?


    Thanks!

    What did you end up going with? Did you install any extra vent fans or get a different heatsink for your CPU?

    Just to chime in. I have an N40L as you do which is still running albeit slow.
    I also purchased a helios4 as a backup.
    I’m trying to weigh up if it is worth migrating omv from the N40L to the Helios.
    It’s one of those things I haven’t gotten around to doing

    That would be interesting to see how it works out.

    Thanks!

    Personally, I use the MergerFS and SnapRAID plugins to address the availability issue.

    Do you have any guidance/best practices on how to set this up? I backup the data I need of my array, but the bulk of it is stuff I can obtain again. I am a home user, so i don't need 24x7 up-time or anything like that. I am all for setting things up and managing them in easier ways.


    Really, the only reason I want hardware backed RAID is due to having an experience with a drive dying while re-striping the data and having another drive die while that occurred. If there is a better way of running things, I am open to it!

    You still haven't talked about how many HDDs you (want to) use and whether energy efficiency or data integrity is an issue for you or not. Without stuff like this what recommendations do you expect?


    Ideally I am looking for something with the following:


    • 4 pluggable drives (running RAID 5)
    • 1 separate OS drive
    • supports at at least 8 GB of RAM (I don't have a preference on ECC)
    • supports quad core processor
    • 150 - 300 watt power supply
    • smallish form factor
    • supports hardware backed RAID


    I know that HP makes newer versions of the their Microservers, but I figured that I might be able to get more for my money elsewhere.

    Hi Everyone,


    I have a 7 year old HP ProLiant N40L mini server that's been running strong and I am starting to think about upgrading it. I use it for my NAS, Docker, and VirtualBox. I would like to try to get something with more horsepower and possibly with hardware RAID. What are some comparable options that won't break the bank (no more then $500 USD)?


    I plan on reusing my disks, so that cuts down the budget big time.