Posts by g13092

    crashtest - excellent feedback and explanation. Thanks for going into such depth. I DO have 4 windows workstations. I guess I didn't realize the dedup process went that deep.

    In the case of fire, there would be no machines left to restore their full backups to.

    Very fair point. I had always played it ultra conservative, assuming that if I save everything, I'm sure to be able to recover what I want, even stuff that doesn't laned in the user directories. But, I suppose that's a minor inconvenience compared to a house fire...


    What is truly important is the user data stored on the workstation (not the OS which can be rebuilt).

    - Windows Task Scheduler and / or Sync center could be set to sync data between a workstation and a server. Various methods ->here. Setting a sync on wks shutdown seems to make sense.

    You've convinced me of this. It's easy enough and won't take up much space on the portable drives, especially compared to the urbackup set. I love the simplicity.

    If your off-site place has fast internet access

    KM0201, Safe deposit box, no internet :D I could put a single board in the garage, which is detached, but only connected by wifi... I'll have to give this some thought.


    Thank you both!

    I regularly backup the media and documents stored on my server to a portable HD, and then take it offsite. I rotate a few portables into this mix, so I'm mostly following the 3-2-1 rule. Recently I realized that the backups of the windows PCs I run via Urbackup are not included in that drive rotation scheme. This means there are only 2 copies of that data and both are onsite. If my house burns down, I'm partially screwed.


    So the other day, I tried to include the Urbackup folder in the OMV USB-backup sync I've been using. Unfortunately, it went on for days (even using usb3) and the result was HUGE, 4x the size on the server. So, I'm lost as how to make this more efficient. What could I leave out of the Urbackup dataset that would make this manageable and still allow me to recover the PCs data if my house burned down?


    Side note, I use Snapraid. When setting up Snapraid, I tried to include my backup directory and found it impossible. The memory usage was massive and it chewed up space way more space than I expected on the parity drive. Eventually, I found that Urbackup makes a metric crap ton of little files and directories and all those little files and folders were a huge burden. I have a feeling I'm running into the same issue here...:/

    Well, I should delete this thread. Feeling pretty silly for as long as I've been goofing around with computers....


    In this pic

    you can see the kingston is not even available as a boot drive in the priority list. Yet, I could select it from the bios boot pop-up menu when you hit f8 (gives you a selector menu, but not loading the whole bios menu)


    In this pic,

    you can see the kingston listed last. I've never used this menu before on this machine. The drives were always all available in the former list, so I never needed to go here. But I also never had 5 drives. I moved the kingston up to 1st drive, it became available in the priority list, I set it as 1st priority, problem solved.


    I still don't get the need for this 'second' list, but whatever. Thank you guys for making me look closer at the bios. I was so sure I mucked something up when moving them image over from the old hd to the ssd...

    I recently moved my system drive over to an ssd. Like a dummy, I bought an ssd a little smaller than the original system drive. After a bunch of goofing around with clonezilla, I was able to get the machine running on the ssd, but with one exception - during the boot process, I have to use the bios boot selector function (hit F8 on this machine) to select the ssd for boot. Only then will it start normally. If I don't do this step, I just get a single blinking cursor, nothing else happens or can be done, expect cycle power. The bios recognizes the ssd and allows me to set it in the boot order priority list. I've removed other drives from the boot order list.


    You'll see below that the boot flag is set on sda. The only thing that stands out to me is that sda has a disklabel type of dos, while the others are gpt. BTW, sdf is a usb drive for a backup that is running right now. It's normally not connected when booting.


    Any ideas on how I can get it to boot without user intervention? :/

    Updated snapraid to 11.5 from 11.3. Repeated delete pairity file, content files, and rescan. Still ran out of pairity.


    5194 MiB used? I only have 1.4T of data... This thing was supposed to use 1G mem for 16T of data. I'm confused :(


    Log file starts.



    Middle of the of the log file, after scanning the disks, until outofpairity is reached:


    ~~~

    I'm crashing snapraid. This is in OMV5. I did test runs on the system with a 1T drive as the pairity and only the 500 and 700g as data & content, and things worked ok.


    I upgraded drives and now have 3 drives for data and content (500Gb, 700Gb, and 3T) and one 3T drive for pairity. Since then, every time I run sync it uses all the memory and crashes oom error, unless I turn on swap, in which case it swaps its ass off and never completes the sync. I just started 'fresh' with block size increased from 256 to 512, deleted pairty & content files, and ran a new sync. Same thing this time, high mem usage and load for hours, but now the the pairity drive filed up completely. I don't get it, as I only have 1.5T of data, mostly music and movies. I shouldn't be using this much memory or pairity space.


    Union1 is simply a mergerfs pool of the 3 data drives, not included in the snapraid config.


    snapraid config from omv interface

    What the heck am I doing wrong?

    Wow. How are those Pis so good? Seems like they can run a lot of stuff pretty efficiently.


    My old junk dual core 4G ram is getting slower by the day. Feels like I have a tire slowly leaking air :D

    These guys are a helpful bunch and there's a lot of good info here.


    What you are building sound like what I built, but better. My core2duo with 4G ram and a few random drives got me going. I added a few new 3T drives to get something with low hours into the machine. One of those is my snapraid parity drive. I worry less about the most recent changes not being 'covered' by a snapraid sync. And as ryecoaaron said, do rsync 'between' snapraid syncs.


    I think you should be fine, but I am having load issues when channels dvr, plex, urbackup, and snapraid are trying to work at the same time. I'm considering a bit more ram. I've had no issues serving other types of files in addition to the media I have stored.


    I am not doing any real transcoding on the machine. But, you could get a reasonable video card for $40 and off-load those duties.


    Have fun!

    macom, let's say it wasn't an environmental variable.


    example, I ran my plex container recently using

    Code
    docker run --health-timeout 30s a0ffee54489d

    which greatly reduced timeout related log entries under heavy cpu load (when snapraid is working). But, I can't figure out how to set up the same health timeout via the portainer interface. Any experience with this? I messed around with the command and entrypoint, but was not successful.

    Docker CLI is pretty deep geek IMO :) I have the same struggle with docker, but somehow get along ok with OMV.


    Good luck garyi.


    I found your thread looking for the same sort of info - something I ran from docker command line 'works', where as when I try to kick it off using the portainer interface, the results are not as positive. So much to learn...

    ok, for the record...


    I realized I can GIVE the swap any UUID, so I gave it the original UUID it had before I turned on folder2ram. I uncommented the original line in fstab. no error at reboot, no log entries every 30 min about swap. There had to be something else still looking for that original UUID at boot. And, damn, it's handy. Snapraid used the shit out of the swap yesterday for a full sync. Really glad I got it back.


    bob is now my uncle :)

    maybe I don't. But I was needlessly running folder2ram when I have the system on a standard hd. I'm running on 4. When Snapraid is cranking through a sync, I would often get into out of memory situations. Right now, with a bit of swap, it seems happy with a sync running.


    Its funny, swap is active and functioning, but the syslog is still showing those swap/start failed with dependency errors every 30 minutes

    gderf, no resume file. Per the Flash Memory plugin 'optional' instructions:


    7. If you disable swap, initramfs resume should fixed to avoid mdadm messages.

    1. Remove the resume file:

    rm /etc/initramfs-tools/conf.d/resume Update initramfs:update-initramfs -u

    Which, I did :rolleyes: seemed like a good idea at the time.


    ryecoaaron, that's how I got the UUID back for sda5. before, it was just sitting there, no UUID, just a PartID. It has no LABEL, if that matters. So this time, I did swapoff, then mkswap -L swap -U "put-in-the-uuid-I-already-had" and it succeeded. Then, swapon gave me an error, couldn't find the swap device. So, I did swap on, using the -L swap option and -f, which is some sort of reinitialize. Seems to be working, but no idea yet if it holds through a reboot.