Posts by Shinobi

Quote from gderf

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

Quote from jollyrogr

Best setup is whatever works for you. I run all my snapraid jobs manually so I know it won't sync when it shouldn't.

I always run snapraid diff to make sure a bunch of files aren't missing or got wiped out, then run the sync.

Then periodically run status and do a scrub if needed.

Others do it differently and it works for them.

Display More

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?

Hi,

is there a simple way to sync all photos from google photos to my local OMV NAS? I would prefer to have the photos stored in two seperate locations.

Thanks for some help!

Hi,

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!

ok i already figured it out.

Quote from votdev

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

Bash

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

Quote from KM0201

Otherwise you will just get command not round.

Square commands are the worst Sorry, I couldn't resist...

Looking forward to the official release

Thanks i will try that and see what comes up.

Hi,

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!

i also switched to ext4... i now have 3x 8TB and just use snapraid once a week for parity sync.

Quote from Adoby

That depends on where you, by mistake, had rsync put the junk files. That is most likely where they are.

But: The files are most likely somewhere where devices are mounted. Sub directories to /srv comes to mind.

You can (should!) double check if you are ever so slightly unsure by comparing the folders when the rootfs is running or not. If there are different files there when the rootfs is running compared to when it is not, then the files there when the rootfs is not running are most likely junk files.

If you find this difficult or time consuming you could just reinstall from scratch. And not run rsync before (remote?) devices are mounted.

I would boot Ubuntu from the thumb drive. And after boot install Midnight Commander to make navigating the rootfs easier.

Display More

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.

ok, so booting the NAS from a USB stick with (eg.) gparted should give me access to the system partition of the nvme, right? any more details, where i could exactly find the files?

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...

The disk usage in the performance statistics shows a different picture. Everything seems ok here, but the disk itself says it only has 1,5GB free anymore.

Hi,

my NVME system disk jumped after the restart to over 85% disk usage. How can I check what causes that? Maybe some log files? Yesterday the disk usage was much lower

Thanks guys

Yes, thats whats i thought... Ok, i will check my available options.

Btw: please don't touch my car

Hi,

in the FTP log I'm noticing strange FTP sessions... Are these bad people, trying to get into my server or what else could it be? Which settings could prevent that?

Thanks guys!

Seems like it was the virtualbox plugin. I deactivated it and syslog looks much better now... Maybe a reinstall will help

Quote from ryecoaaron

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.

ok i believe you. Thanks for educating me