Jump to content

lionceau

Members
  • Posts

    70
  • Joined

  • Last visited

Posts posted by lionceau

  1. My e3-1225v3 machine currently has 15W higher idle power consumption in unRAID than in Windows, primarily because of better iGPU power management under Win.

     

    I wonder if passing the iGPU through to a Windows VM would lower power consumption.

    Has anybody tried this? I only have this one machine and would rather not install a RC for testing.

  2. can you please add powertop to the nerdpack? that would be very useful to reduce idle power consumption.

    This won't work with unRAID. The required kernel modules aren't present. Also isn't this for a laptop/desktop system running on a battery?

     

    There are some power managment related tweaks that are useful for normal desktops/servers.

    The powertop tweaks (more aggressive pci power savings, etc) lower my idle wattage from 21 to 15 watts with open media vault. Its not the end of the world but it would have been nice to have.

     

    Unraid idles at 31 watts, presumably because I can't figure out how to enable the kernel mode setting for the intel GPU and powertop is not available.

  3. Hello, my Dell T20 with a Xeon 1225v3 uses 30W idle with all drives spun down. The same machine idles at 15W with another debian based NAS distro.

     

    Apparently it is vital to enable Kernel Mode Setting so that the iGPU can enter sleep states and save power.

     

    Does anybody know if unRAID uses KMS by default or how I can activate it?

  4. Yes, cache_dirs was installed and working throughout all tests.

     

    I thought about whether or not this is intended behaviour and came to the conclusion that it probably is not because when I choose default "All Disks" with "Cache: prefered", no disk spins up.

     

    If it was intended behaviour then all disks would have to spin up as the data could be anywhere. Obviously that would be very counterproductive.

     

    It's not a huge bug but I spent more time trying to troubleshoot these random spinups (which I suspected to come from a plugin or docker container — so I double and triple checked those...) than I spent setting up unRAID altogether.

  5. Description:

     

    Specifying a Disk to be included in the share settings and enabling cache afterwards causes small disk accesses to it even though cache is enabled.

     

    How to reproduce:

     

    create a share "test", open share settings, pick any one disk (e.g. disk3) in the Included Disk(s), set Use cache disk: to "Prefer".

     

    Expected results:

     

    reads/writes to share "test" get buffered by the cache, disk3 stays spun down

     

    Actual results:

     

    reads/writes on share "test" cause disk3 to be accessed which keeps the disk spinning, even though my cache drive had >75% free space.

     

    inotifywatch -mr /mnt/disk3 showed:

     

    /mnt/disk3/ ACCESS,ISDIR 
    /mnt/disk3/ CLOSE_NOWRITE,CLOSE,ISDIR 
    /mnt/disk3/ OPEN,ISDIR 
    /mnt/disk3/ ACCESS,ISDIR 
    /mnt/disk3/ CLOSE_NOWRITE,CLOSE,ISDIR 
    /mnt/disk3/ OPEN,ISDIR 
    /mnt/disk3/ ACCESS,ISDIR 
    /mnt/disk3/ CLOSE_NOWRITE,CLOSE,ISDIR 
    /mnt/disk3/ OPEN,ISDIR 
    /mnt/disk3/ ACCESS,ISDIR 
    /mnt/disk3/ CLOSE_NOWRITE,CLOSE,ISDIR 
    

    (roughly one open/access/close every 10 sec)

     

    but lsof /mnt/disk3 showed nothing.

     

    edit: after some more testing this seems to happen when disk3 and cache contain a copy of the same folders/data, as was the case with my appdata folder which was in the cache and on disk3.

    edit redacted: it seems I was wrong, it still happens when there's no data at all on disk3.

     

    Other information:

     

    I had an issue with my disk3 not spinning down even though I had no docker containers, exported shares or other programs with access to shares on it.

     

    My appdata share was set to "Include Disk: disk3" and "cache: prefer" because I read on here that supposedly this allows the appdata to "overflow" onto the disk3 when the cache drive gets full.

     

    However it seems that specifying (e.g. disk3) to be included in a share before turning on the cache will cause random small accesses to /mnt/disk3 even though the cache is enabled.

     

    Now that Include Disk: is set to "All" and cache: prefer, disk3 hasn't spun up in over 12 hours.

  6. Hello!

     

    I'm trying to make myself a docker image which I can use to access a certain share remotely via SSH/SFTP without having to access it through unRAID's sshd.

     

    Unfortunately I'm having a very hard time grasping Docker and figuring out the easiest "workflow" to get the container set up perfectly from a dockerfile.

     

    Is it viable for me to create one persistent docker container, configure it to my liking, save it as an image and just update that with apt-get as I would with a VM?

    From what I gather this is frowned upon by the community but I don't plan to move or distribute the docker image.

     

    Normally I'd just use a VM for this but I found that the io performance of 9p virtio is much worse than what a docker container can do.

  7. Yes thank you, I checked that before making the VM. Unfortunately they are all socket based and none of them include ssh for tunneling.

     

    I'd like to use unison over ssh (exposed to the internet) so I can sync remotely without having to resort to a VPN.

    Syncing with the socket method over the internet in plain text is a bad idea.

  8. Hello,

     

    I'm trying to run unison (a sync tool similar to rsync) on unRAID. I'm not talented enough to package it into a docker and keep it maintained. Instead I set up an Ubuntu VM, configured everything up to my liking and mounted the target share via virtio 9p.

     

    Everything worked out of the box but performance is far lower than what I hoped.

    My dd zero throughput from the Ubuntu VM to the SSD cached share is ~70 MB/s. The same from the unRAID host returns ~430 MB/s.

     

    A (io-heavy) sync which took 0.960 seconds on my C2D Mac Mini + 8 year old Drobo now takes 22.638s seconds on the new box and utilizes 60% of all CPU cores for the duration.

    This is worrying as I've got a cronjob that executes this sync every 15 minutes on all of my machines.

    CPU usage inside the VM is actually low.

     

    Dell T20 + UnRAID 6.2.4 Trial

    e3-1225v3

    16GB ECC

    512GB 850 Evo Cache drive

    3x8TB WD Reds

     

    My fstab entry is as follows:

     

    unison /unison  9p trans=virtio,version=9p2000.L,nobootwait,rw,_netdev

     

    Is Virtio 9p just the wrong tool for this job? Is there a faster alternative?

  9. I'm no expert on the matter but surely it can't be a good idea to use SMR drives as parity?

     

    They have two levels of cache (128MB DRAM + 20GB on-disk) managed by a firmware that's optimized for archival (few, large sequential writes). The screenshots suggest Parity workload is the exact opposite.

     

    Any time a data disk is written to' date=' the parity disk needs to be updated as well. Each write to a parity-protected unRAID data disk results in 4 disk operations: a read and write for parity, and a read and write for data. The platter of each disk has to make a full revolution after reading to position the disk head back over the sector being written.[/quote']

     

    That seems like a huge headache waiting to happen once the SMR drives have been populated with data that needs to be overwritten while the cache is full. My ST8000AS0002 dropped to <10 MB/s sequential write speed in those cases.

     

     

  10. That's a pity. The drives are just out of warranty but I don't think WD would do anything about the high LC count.

     

    I've ordered 2x8TB WD Reds. One as parity, one as storage. I'll keep the two "good" WD Reds in the new array and use the older ones as a monthly backup.

  11. The personal documents and pictures are backed up offsite. Most of the important 3TB are backups and diskimages of old computers. I could delete a good amount of it and never worry about it, but keep them around "just in case". Same goes for all my media is from bluray discs catching dust in my cupboard.

     

    I thought about using the Drobo as a backup for the unRAID server but the device is 7 years old and completely proprietary. If the Drobo becomes defective, there's no way to recover the data except for buying another used Drobo and even then it's not sure that i can be restored. :o It would probably make more sense to buy a USB 3.0 docking station and use the drives individually.

     

    Starting with fresh drives has crossed my mind but 8TB disks are still quite expensive at the moment (3x WD80EFZX = 1020€).

     

    Here's the Data from my five 4TB WD Reds. I bought them in two batches.

    For some reason the drives from the first batch have Load Cycle counts over 600k, the newer ones (roughly half as old) only around 4k.

     

    jFmYKUB.png

    5HFVmXG.png

    mLWPO95.png

    btUulva.png

    g3wADoM.png

     

     

  12. Hello,

     

    I'm new to Unraid and plan to move my data from Mac Mini + Drobo (2nd gen, dual parity) with 5x4TB drives to a Dell T20 with unRAID using the same drives but with a single parity drive.

     

    There are ~10TB of storage in use on the Drobo.

    3TB are important files, 7TB are "disposable" media files.

    I'm currently in the process of backing up all 3TB important files + 5TB media files to a 8TB Seagate SMR drive as a cold backup.

    The important files are also backed up across two of my old 2TB drives to be extra safe.

     

    My plan is to:

     

    [*] shut down the Drobo, remove all drives from it, connect them to the T20 (obviously not mounting them) and check their health with SMART (the drives are 3 years old and Drobo doesn't expose SMART data to the user).

    [*]If the SMART data is suspicious, scrap the plan and use it as an excuse to buy 3x 8TB drives.

    [*] If they are O.K, I'll put 3 of them back into the Drobo (which should leave all data accessible but without protection) and pre-clear the other two drives in unraid.

    [*]Add both precleared drives to the array as storage (without parity)

    [*]Copy all important data + the remaining 2TB of not backed up media from the Drobo to unRAID.

    [*]Move the remaining 3 drives from the Drobo to the unRAID array, preclearing them first. 1 as parity, 2 as storage.

    [*]Transfer media from the 8TB Seagate to the array.

    [*]Configure unraid as desired.

     

    Does this seem sensible or is there a better way of doing it?

     

    As for the unRAID array, is there any downside in formatting the storage drives in BTRFS instead of XFS? I feel like BTRFS is stable enough and it has a brighter future than XFS. I'd also like checksumming to protect against bitrot.

    Thanks.

  13. Hello, I'm new to unraid and still in my evaluation/trial phase. So far I'm very humbled by the functionality and ease of use compared to my Mac Mini homeserver running OS X.

     

    One service that I depend on is Unison, a CLI file synchronisation service very similar to rsync but faster and with better conflict management.

     

    On my current (non-unraid) server I use unison with a ssh for secure file syncing. It's fast, full-featured, stable, cross platform and much more dependable than syncthing, Bittorrentsync/Resilio and comparable apps that I've tried.

     

    https://www.cis.upenn.edu/~bcpierce/unison/

     

    I couldn't find anything related to Unison in the Community App program. There's an image on dockerhub but that's for a different purpose and doesn't include SSH.

     

    Where do I begin setting up a personalised Docker container for this?

    The developer is no longer adding features, only occasional maintenance fixes, so updates to unison are rare. That shouldn't make it too hard to maintain it for myself.

    Or alternatively is there a way to pay a developer to create a unison template for unraid?

     

    If all else fails I could make a ubuntu VM for unison but as I understand it docker is a "cleaner" solution with less overhead.

     

    Another question related to Docker: I keep reading that unraid is not meant to face the internet because it wasn't designed with security in mind.

    I understand this. Does this recommendation also affect services running inside docker containers or is the docker abstraction sufficient to make the service secure enough to face the internet?

     

     

     

×
×
  • Create New...