Mat1926

I looked at the settings, and I can disable the notification, but is that a good idea? Also, the minimum free space for the disks is set @ 0 KB, is this good bad? Can I adjust this value, or it should be set only once?! Thnx

I did not mean moving existing files, what I meant was when I copy new ones to the system...So what would happen if it reached 100%? Split is set to Automatic Allocation method is set to High-Water

All my disks are at ~85% of usage, except the 1st one it is @ 94% and I am getting notifications every time it goes up by 1%. I am curious, is this how unRaid works? Why it does not copy the data to the other disks since all the remaining disks are below 90%? Also, shall I worry about that, or is unRaid handling everything just fine?.... Thnx

Sorry I was not clear enough. Before using unRaid, I used to have a couple of WD PR4100 raid systems, and the moment you hit the last 5% of the available space, then the system notifies you that you have to free more space since now this limited space hinders the performance of the system. It was raid 5... So I was curious if unRaid suffers from similar restrictions...

If I am down to the last 10% of the available usable space?!

Thnx, it is working now...

I am just testing to see if it is okay to upgrade from 6.3.5 to 6.5.0, and after running the update assistant, it found 1 issue "community.applications.plg () is not known to Community Applications"...

thnx, I did start the daemon, and set the time on battery before shutting down to 60 seconds, shall I make it 30 seconds?...Is this all?!

Thnx, I thought this serial error is related to the UPS. Do I need a plugin for the UPS?!

I did attache the ethernet to USB cable, and after booting the system. I noticed some warnings and errors. Maybe they are not related to the new device, but here are the list Also, what shall I do next? Do I need a plugin for the UPS? The Diagnostics is attached... Mar 15 16:02:05 unRaid kernel: ACPI: Early table checksum verification disabled Mar 15 16:02:05 unRaid kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.SS07] Namespace lookup failure, AE_NOT_FOUND (20160831/dswload-210) Mar 15 16:02:05 unRaid kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20160831/psobject-227) Mar 15 16:02:05 unRaid kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading table (20160831/tbxfload-228) Mar 15 16:02:05 unRaid kernel: ACPI Error: 1 table load failures, 8 successful (20160831/tbxfload-246) Mar 15 16:02:05 unRaid kernel: acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:02:10.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 6: failed to assign [mem size 0x00080000 pref] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:01:00.0: BAR 14: failed to assign [mem size 0x01200000] Mar 15 16:02:05 unRaid kernel: pci 0000:02:08.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:02:09.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:02:10.0: BAR 14: failed to assign [mem size 0x00600000] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:04:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 3: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 1: failed to assign [mem size 0x00004000 64bit] Mar 15 16:02:05 unRaid kernel: pci 0000:05:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit] Mar 15 16:02:05 unRaid kernel: serial 0000:00:16.3: Couldn't register serial port f060, irq 19, type 0, error -28 Mar 15 16:02:05 unRaid kernel: ACPI Error: [GPLD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Mar 15 16:02:05 unRaid kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.XHC.RHUB.HS11._PLD] (Node ffff8804aaf53578), AE_NOT_FOUND (20160831/psparse-543) Mar 15 16:02:05 unRaid kernel: ACPI Error: [GPLD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Mar 15 16:02:05 unRaid kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.XHC.RHUB.HS12._PLD] (Node ffff8804aaf535c8), AE_NOT_FOUND (20160831/psparse-543) Mar 15 16:02:05 unRaid kernel: ACPI Error: [GPLD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Mar 15 16:02:05 unRaid kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.XHC.RHUB.HS13._PLD] (Node ffff8804aaf53618), AE_NOT_FOUND (20160831/psparse-543) Mar 15 16:02:05 unRaid kernel: ACPI Error: [GPLD] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359) Mar 15 16:02:05 unRaid kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.XHC.RHUB.HS14._PLD] (Node ffff8804aaf53668), AE_NOT_FOUND (20160831/psparse-543) Mar 15 16:02:05 unRaid kernel: floppy0: no floppy controllers found Mar 15 16:02:05 unRaid kernel: ipmi_si IPI0001:00: Error clearing flags: cc Mar 15 16:02:06 unRaid rpc.statd[1804]: Failed to read /var/lib/nfs/state: Success Mar 15 16:02:07 unRaid avahi-daemon[1967]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! unraid-diagnostics-20180315-1607.zip

Thnx for the update...

The speed is not my biggest concern here, as long as the integrity of the parity checking process is intact, then I am happy...

Thnx, no writing, just reading at the moment...

Are there any issues at all for both cases with and without corrections? Thnx

So it should be 1000/0.8, i.e. 1250 W minimum? I'm not sure where can I find such UPS...

How long does it last in case of power loss?

Absolutely, my desktop will not be connected to the UPS at all, the purpose of the UPS is to just to give unRaid enough time to power down safely. And browsing the web will be through my tablet...

I am more concerned about unraid to be honest with you. My modem and switch will be connected to the UPS also...so in case of power loss I'll at least be notified and if I am around I can also browse the web until the power is back... Thnx

Thnx, very nice document...

Something like this? https://www.amazon.de/dp/B003IR1CG8/

My estimate was for 24 HDDs, not 16...so it seems I might need something like 700 watts...correct?

What is this 16HD? *edit* for an unknown reason, the HDDs seemed spinned down, this never happened before, do you know what might caused that?! the only thing that I did was to make the array starts automatically...

@jonathanm@Frank1940 I was only able to measure the watts, I do hope that is fine Powering up the system, it peaked @ 180 watts, then idle below 120 watts. Spinning down the HDDs took the power down to 70 watts Spinning up the HDDs it peaked @ 270 watts, then remained below 120 watts Transferring data to the system it peaked @ 140 watts Reading data it was below 120 watts My system is configured with the option reconstruct_write, and I do have 11 disks @ the moment. My chassis supports up to 24, so is it safe to say for 24 HDDs my maximum should be 270 watts x 2 = 540 watts. And in this case I need at least 600 watts Smart UPS? P.S. manually spinning down/up the HDDs, does it affect the system or the data integrity? Thnx

I have a wd m.2 pcie 256 GB in my system. I am not utilizing this one at all. It is available in the unassigned devices list. My system is setup purely as file storage. I don't have any Vms or Dockers, and don't plan to use any at all. I only have the default plugins installed. I also don't want to use a temporary cache drive to hold my files and moved later, I prefer to store everything in the array instantly. Based on all this, shall I just ignore this m.2 entirely, or do you recommend using it? But plz bear in mind what I said earlier about my setup and needs... Thnx 4 the help...

When the parity check is done w/o errors, I will update the disk settings so that the array starts automatically since it will auto check w/o corrections in case of unclean reboot...which I believe is the correct way to do after reading all your comments...