jit-010101
Members
-
Joined
-
Last visited
-
have you looked up standby power consumption for those? It's 5x spinning rust + 7x ssd so 12 physical devices. There is a limit to what kind of power consumption you can save from standby and spindown. however what you are describing sounds like something is constantly writing to your array. do you have apps on a separate nvme/ssd only pool? If not there's your answer as to why the hdds constantly spin up.
-
I'm for one glad I decided to move away from Unraid for my Backup Server to a pure Debian System with ZOL. Otherwise I would have never noticed that the mover script didn't really move a lot of data of my restic repository over from the Ssd-Pool which could have led to catastrophic loss of all/most data in my repository and hassle full recovery from Offsite. In the end I think the Mover Script itself should undergo fundamental refactoring in how it works. For example making it carry a two way Sync option, Excludes, Includes. Better Locks, better checking and delay/debounce for Moves. There is a lot that could be improved. Verification and Transparency in the UI most importantly! Not just running silently as a background service. There is a lot to take from this Plugin here and make it much more stable that doesn't require Money patching with a Plugin and much better integrated. I only see this because I have migrated and am recreating my own now (which naturally makes that much more transparent for myself) . Be careful if what you are looking at is beyond a simple script you might be fooled into a false sense of security is what I'm saying.
-
While setting up some backup schedules with crond and checking the log I just noticed on both of my servers that there are at lot of log spams like these: atd[1260378]: Userid 0 not found - aborting job 6 (a0000601b9b9fa) While there are reports here to be found related to samba I did a lot of trying to bug fix this (the usual stuff including giving world access permissions too). So naturally I moved to my backup server, because that has almost nothing installed - let alone customized naturally given the job of trying to find the cullprint. I disabled Samba, checked permissions on all files, most importantly related users and user-resolution, disabled, restarted - cleared all jobs. Checked if the ids for the root users are correct and so on ... Last but not least I installed strace from Slackware 15 repos and did an strace with a test-job like this: pkill atd strace -f -e trace=all -s 10000 atd -d > /root/atd_strace_detailed.log 2>&1 & echo "echo 'Test job' > /root/test_job_output.txt" | at now + 1 minute Attached is the atd_strace_detailed.log too just in case you are wondering ... After further steps up and down I tough about checking the version via at -V: # at -V at version 3.2.5 Please report bugs to the Debian bug tracking system (http://bugs.debian.org/) or contact the maintainers ([email protected]). Weird, why does that mention Debian? Lets check /etc/slackware-version ... # cat /etc/slackware-version Slackware 15.0+ Lets check the official repo ... oh it appears like the last one is 3.2.4 there for Slackware 15 at least ... hm. https://slackware.pkgs.org/15.0/slackware-x86_64/at-3.2.4-x86_64-1.txz.html Lets install it over the current one ... wget https://slackware.uk/slackware/slackware64-15.0/slackware64/ap/at-3.2.4-x86_64-1.txz upgradepkg --reinstall at-3.2.4-x86_64-1.txz Suprise Surprise - Its back to working now. I have NO clue if any kind of Plugin did that to me, if anything I would suspect NerdTools (yada, yada I know its not supported in Unraid 7 - I didnt use it anyhow but neither uninstalled it or the previous extra packages to not change anything yet) or if it was an Extra package OR if its a broken at at-scheduler base package from Unraid 7.0.0 but I figured I should maybe report this just in case its an official issue - because then all kind of scheduling using at would be broken at this point, e.g. using Unassigned Devices. Sorry if its a local issue for my two Servers - but I really barely touched the Backup-Server in terms of configuration over the time I last installed it. So I figured I better give it a go with an detailed write-up. atd_strace_detailed.log
-
Had a quick glance into the code base. Honestly not sure if I want to do it - C++ or Qt aint my strongest contenders and they come with a lot of uglyness in that specific code base (many external dependencies, originally based on Qt5 which is Out-of-Support already). Specifically speaking from a low-level the customization features are also tailored for the Raspi-Bootloader - should be U-Boot as most SBCs as far as I remember. But then again this topic interests me quite a bit (in terms of learning) so I decided to create something from scratch in Rust (yesh): https://github.com/thiscantbeserious/usb-creator-rs Upside is I charge 0,00 - if you want to help with the planning and design feel free to contribute by feature requests. If it turns out useful / works as intended then I'll gladly rebrand / customize it for Unraid too. But no promises - I was initially planning to keep quite about it but here we are ... no pressure!
-
yes absolutely, did a quick search but didn't find the topic for the requirements
-
Is this already being worked on?
-
> assuming open to internet Unraid was and is never ment to be used being exposed to the Internet directly. You should always honor such design decisions - and work with that. Say run Unraid in a VM like on Proxmox in such cases. If you need internet exposure you can use a pull solution like Syncthing - if you want to expose services you have much better solutions based on Kubernetes/Portainer on hardened Server OSes with LTS Kernels which can run in a seperate VM and just use the NAS-Storage as a mount. Docker containers are still updatable, as it is too ... so the individual containers are never staying behind. It all sounds a lot more like that you want to use it in edge cases the easy way - that's not going to work out too well. Can't you simply downgrade to the last known stable and call it a day. Like outlined above: Unraid was never be designed to be exposed to the internet directly. There are shit ton of equipments with far older Kernels hidden behind propitary firmware with much bigger holes than that.
-
I'm honestly not sure - maybe someone from the team can tell but if you're using pools and not the array it might not even use shfs. 🤔 I personally never encountered such issues myself - I'm "just" using it to host Paperless, Nextcloud (58k pictures/video), Homeassistant, Node-Red, Calibre and stuff like that ... and never had an issue. But this is all on an classic Array with BTRFS individual drives (ssd's only) of different sizes ... I've yet to use any form of Media-Streaming use cases myself ...
-
Eh well, that explains it - server hardware and maybe an not so power efficient PSU all combined with 12 drives probably none of them in spin-down ... there is a LOT of potential to save energy here hehe (just not for FreeNAS). I remember that there was an issue related to *arr with shfs (the underlying technology used as a basr for Unraid merged folders) so I'd highly recommend you to test the trial to the fullest to be able to face any issues and get yourself an idea what you might need to do.
-
Right now on mobile but my second backup server is running on Unraid too and is 100% ZFS on Spinning Rust. But I'm not using RaidZ - but invidiual ZFS drives in the array with a parity drive. That gives me the ability to do snapshots and enables the drives to spin down - especially when combined with the Folder Caching Plugin (which reduces Reads from the HDDs by caching recently/often used folders into RAM). ZFS single drive array has the downside of no automated bitrot protection on the fly and I wish RaidZ support would be already there especially with multiple Arrays that would be even more powerfull - as I understand it that's planned for later. Right now ZFS does have some downsides, like if you are manually creating folders within your shares via commandline - this is not handled automatically and can lead to weird problems / dataloss (yet). All that in mind: What the heck is wasting away those 200W? Both my servers use less then 60W together ...
-
I had two Plus Licenses - just Upgraded one to Pro. I can totally understand the change to the licensing model and will still purchase additional licenses as needed - with subscription fees and will still recommend it to anyone looking for a server/NAS/media OS. There needs to be a steady income flow for you guys, to continue founding and development - otherwise there will be no more versions at a point in time. I'm 100% sold and satisfied that Unraid is a much better general use home server system then any of the other options I've so far seen and used - for my use case (like, for example DSM - or heck much more complex setups like with Proxmox/k8s/or any of the countless server distros I've been trough in my years).
-
You'll have to turn off Turbo too (as mentioned in the powertop readme), and probably also have to limit PL1/PL2 power states - keeping PL1 within 32 seconds. The exact values you'll have to try yourself (i think mine are set to 5000 and 8000). If it doesn't reach C8 then it might be related to your nvme-drive ... have you tried removing that yet?
-
That consumption levels seem to be quite fine - 20W for 4x HDD and 2x SSD is quite good. I do reach 15.8W with a lot of tuning an C8 on a N5105 board with the same amount of drives I'd say the difference is that you use 3x RAM-Sticks and maybe C6 vs C8 - and obviously the drives themselves. if you remove everything but one RAM-Stick you might be able to see lower consumption - have you also enabled GEAR2 for the memory ... that could give you a little bit more power savings too ...
-
@scy01d @Marshsr Here you go ... no guide or no disclaimer for now how to reach C8 (I've started from scratch 6 times now and always reach it again). I did add a quick readme.txt to the root directory of the USB-Stick. You should unpack this to a clean FAT32 formated USB-Stick and simply reboot and it should flash everything ... Be sure to READ THE README first! Edit: ffs, tons of misspellings in the readme ... not going to fix that Edit #2: If you're scared of the contents and/or have your own EFI-Boot-Files ready all you need is basically the /EFI/R208_Mod.bin file jit-010101_20231122_bkhd_nas_5105_bios_mod.zip Edit #3: Here's my current build and consumption with this:
-
Backup-Server: Fractal Node 304 Case - Fans replaced for 2x Noctua NF-B9 Redux 92mm/3-Pin @ Front and 1x Noctua NF-A14 140mm/4-Pin/PWM at back connected to PWM-Pin on Mainboard Mini-ITX BKHD-N5105-NAS Board with 6 Sata Ports On-Board (ASM1166) with Modded BIOS 32GB (2x16GB) Crucial RAM -Kit CT2K16G4SFD8266 - DDR4 2666MHz CL19 200W Inter-Tech 88882190 PicoPSU + 12V/120W Power-Supply (No-Name) Drive Temps are down to <25 °C accross everything now after the NF-B9 upgrade - the NF-B9 Redux are working lovely in this case ... Array - Spin-Down 15 Minutes, Mover enabled each 8h + Mover Tuning Plugin to Move files > 2 days old: 2x18TB Seagate X20/18TB - ST18000NM003D 1x10TB WD White-Label @ 5400RPM - WDC_WD100EZAZ 1x8TB >SMR-Hell< Seagate Archive - ST8000DM004 ZFS-Mirror - Cache + System (Docker+VM): 1x500GB NVMe - Samsung_SSD_970_EVO_500GB_S466NX0M914394B 1x512GB SATA SSD - Crucial_CT512MX100SSD1_14300CB78BC7 ~15.8-16.8W currently in spin down over the day, semi-idle - goes up to single disk non-spin-down (18TB) ~20W and at average ~45-48W at load multiple disks, with very short peaks to about 60W ... (there is also staggered spin up if you enable the sata options and set spin down to just one drive on but I didn't verify that lately, might be interesting for PicoPSU users ...) Hourly backups are stored via Restic to the SSD-Cache - running restic-rest-server Keep in mind thats only possible with a modded bios that unlocks all options to enable GEAR2, enable ASPM,... and properly makes it go to C8 Apparently there's also an ECC-Support option to enable (which is seemingly enabled by default, maybe I accidently did that) - that makes no sense but I also do not have an UDIMM SO-DIMM ECC-RAM myself so I really didn't try if it works ... I doubt it does. Write/Read speed averages at around ~200MB/s I'll share the BIOS later on in a seperate thread going onto the specific settings ... so that others might be able to reproduce it Edit - BIOS shared here for the time being:
