Posts by Shinobi

    Don't sync without doing a diff first and understanding what it is telling you. Reading files from the array during SnapRAID operations is harmless. Adding files during a sync will generate warnings saying you shouldn't do that and suggest running the sync again.

    There are several well written scripts available that perform SnapRAID operations in a recommended order. Most users will find that such a script will satisfy their needs. OMV comes bundled with one.

    Ok thanks. Can you please point me to those scripts or show me where I can find the existing one within OMV. Thanks a lot

    so you do a diff before you sync? I thought it makes sense to do it right after, so it's a confirmation about a successful sync. Does it interfere with a sync, if i watch eg. a movie while the sync is running?


    I have Snapraid configured on my NAS for a while, but I'm still not sure if it is set up the best way possible. My setup looks like this: 2 Data drives, 1 parity

    Most of my data is media, so I have a scheduled "snapraid sync" job running once a week. This seems to work, but when I look in the snapraid log files, it never mentions the weekly sync. Only when I do it manually. Is that normal?

    What about a "diff" or "scrub" job? Should I also do that every week or month? I hope someone can give me a few pointers on them.

    Thanks a lot!

    The issue is explained here and here and is no problem, it simply creates an annoying output, nothing more.

    A simple fix may be to edit /root/.profile and replace

    mesg n || true

    sorry to dig up this old topic... i understand what i have to do, but how can i edit this file with which command? ssh via putty is not the problem, but what then? sorry, i should get more linux knowledge, i know


    i have 3 disks (2 data, 1 parity) in my nas with snapraid and spin them down via hd-idle after 5min. i noticed that my disk spin up multiple times throughtout the day, without me accessing them. how can i find out, what causes that? in the syslog there are no entries and i also disabled s.m.a.r.t. check for now.

    i have some docker running: sonarr & radarr

    Any hints on how to find out or create logs about spinning up would be appreciated.

    Thanks a lot!

    Thanks a lot. I will try and check, but i also have a backup made with dd, that i could use to wipe the drive and restore a working config.

    Thanks. I think it was the rsync push that somebody mentioned. By accident i had the backup rsync set on "on reboot". That would explain it, but how can i get rid of that useless data that occupies the space? Another restart didnt help...

    If you can get it to boot with an older kernel, I would use omv-extras to install the proxmox kernel. If you want to test ahead of time, just boot an Ubuntu 18.04 iso. This is the same kernel for the most part.

    The NAS was not crashing the last 3 days, but I noticed some error messages in the syslog this morning. Any idea what exactly they could mean?
    Also the rrdcached process has/had a problem starting up, when I restarted the NAS today. I can also provide the syslog if that helps.