Posts by idanp

  • OMV crashing during big file transfers, locking up gui and ssh access

    memtest run for over 6 hours, 10 cycles with zero errors. I ordered an ssd, but it'll take a while to get here.
    This is a one time transfer of ~5TiB, regular transfers would be between 3 and 30 TiBs at a time so it shouldn't be a problem...
    I'm almost tempted to take the hdds out and plug'em in the win machine just to get it over with...


    BTW - can you recommend a program/app/plugin to verify the integrity of transferred files? (CRC, md5 or any other...)


    Thanks for your help guys! appreciate it.

  • OMV crashing during big file transfers, locking up gui and ssh access

    OK, so I applied both tips - I've installed the the backports kernel, and tried WinSCP over FTP protocol, after a little tinkering I was able to get back to almost the same transfer speed as before, and it worked longer before it died. but it still turned belly up after a few hours, only this time I got two mails from monit:

    Quote

    monit alert -- Resource limit matched localhost [nas.local]
    Resource limit matched Service localhost Date: Thu, 28 Jan 2016 06:46:17 Action: alert Host: nas.local Description: loadavg(5min) of 3.2 matches resource limit [loadavg(5min)>2.0]Your faithful employee,Monit


    and

    Quote

    monit alert -- Resource limit succeeded localhost [nas.local]
    Resource limit succeeded Service localhost Date: Thu, 28 Jan 2016 06:49:17 Action: alert Host: nas.local Description: 'localhost' loadavg(1min) check succeeded [current loadavg(1min)=3.4]Your faithful employee,Monit


    What should I do about this?

  • OMV crashing during big file transfers, locking up gui and ssh access

    As a photographer I'm pretty much bound to use windows or mac, and windows is way cheaper for the same hardware... so, I wish, but no can do. :/

    Code
    root@nas:~# mergerfs -v
mergerfs version: 2.8.0
FUSE library version: 2.9.0
fusermount version: 2.9.0
using FUSE kernel interface version 7.18


    but as I said earlier, I tried to copy files to the seagate HDD which is mounted and shared as is, not behind the snapRAID nor the mergerfs.


    EDIT: maybe I'll try other protocols like BTsync or rsync. this is very annoying though, it's the most basic task of the NAS, why can't it do it right?

  • OMV crashing during big file transfers, locking up gui and ssh access

    Quote from ryecoaaron

    Is OMV installed on the usb stick? If so, do you have openmediavault-flashmemory installed? If not, your usb stick is probably failing. Find a new one or use a rotating drive/ssd.


    thanks for the quick response!


    OMV is installed on the USB stick (new stick, reformatted and zeroed (dd'ed) it in order to install GRUB correctly), and more importantly - Flash Memory is up and running as well.


    any other ideas?
    TIA!

  • OMV crashing during big file transfers, locking up gui and ssh access

    Hi guys, Noob here so bare with me please :)


    Yesterday I installed OMV for the first time, I configured the system to my liking (more or less) and made a shared folder to backup my photos into (a few TiBs of data).
    A minute or so into the transfer (from a windows 10 pro 64bit PC using TeraCopy) the Nas freezes, the network drive is no longer accessible, the gui can't be reached and even ssh is unreachable.


    here are the rig's specs:
    Gigabyte GA-B150M-HD3
    Intel Pentium G4400
    G.Skill 8GB DDR3 (run clean 10 memtest cycles)
    WD red 3TB x 4
    An old 1TB seagate
    SanDisk cruzer fit 16GB


    I'm using SnapRAID and mergerfs for pooling the data drives, but I ruled out SnapRAID as the cause by trying to transfer files into the simply mounted Seagate (ext4) as well.


    can anyone point me into the right direction as to how to isolate the cause and fix this?
    Thanks in advance!

  • snapRAID pool as a shared folder?

    Hi guys,
    I'm a beginner with the OS - installed my first OMV yesterday, but I know my way around a computer and built a few servers over the years.
    At first I started with a RAID5 setup (RAIDed 4 * 3TB WD red drives), but than, after installing the extras, I stumbled upon SnapRAID and got intrigued...


    I didn't even let the system finish with the raid initialization. Instead I setup the drives as 4 separate ext4 disks, mounted and configured them (d1 as parity, and d2-4 as content+data).


    At a first glance I though I'll be able to share the disks as a single shared folder, ticked the "Enable Pool" on the Settings tab, but nothing happened (no new Shared Folders etc)...
    So after reading the snapRAID manual and here in the forums (here for example), I now know I need something to "bridge the gap", and so I'm turning to you with hopes for a good advice on how to pool the HDDs and make a shared folder?


    I'll be using this as (another) backup for my photos and videos, and I want to retain the ability to access the files on the remaining disks should more than one HDD fail, so a simple JBOD may work, but maybe there's a better solution(?)


    Thanks in advance!