Bill A

Well I installed SAS Spindown, waited over 15 minutes (set as global and on each disk) and no disks spun down, I manually spun all disks down and they spun down. I stopped and restarted the array, waited over 15 minutes and the drives didn't spin down Rebooted the server, waited over 15 minutes and the drives are spun down! Thank you Decto for the solution!

Didn't know there was such an app 🙂 I will try and report back in a bit.

I have had many different hardware build of my unraid server over the years (I think my fist server was an old desktop over 10 years ago), I am not a Linux user so the backend (non-gui) of unraid is 100% not something I am familiar or comfortable digging into with out some direction. For my latest server build I decided to start from scratch (I will transfer appdata and configs for plex and a couple other dockers to the new server once I have data transfered) My old server was a desktop with 1 ssd for the cache, and mainly shucked WD 5400rpm drives for data My new server is HPE dl380 gen9 (12 bay 3.5" drive setup) Dual e5-2690v4 128gb ecc ddr4 2400 ram 2 @ 12tb used 7200 sas drives for a dual parity drive setup, these are in and Precleared but will not be added to the array until all data is copied) 5 OR 6 (Still debating on 5 or 6 data drives) used 7200 sas drives, I current have 5 installed and 6th is Precleared and out of the server. 1 @ 500gb sata ssd unassigned but holding OS for torrent box outside of the array 1 @ 8tb used 7200 sas drive for torrent data plex transcoding files etc, again unassigned but mounted so not hitting the parity 1 @ 4tb sata ssd cache drive for disk writes (copying files to shares) 1@ 1tb sata ssd cache for all appdata/dockers etc The drives are all installed in hot swap cages connected to the 12 drive backplane The backplane is connected to a HPE sas multiplier The multiplier is connected to an HPE p840 sas controller HP Ethernet 1Gb 4-port 331i Adapter - NIC (appears to be Broadcom) HP Ethernet 10Gb 2-port 557SFP+ will be connected to my UI Dream Machine Se on next reboot LSI Corp 2308 SAS Controller this was going to connect to external jbod enclosure that I am not current going to use Currently I have the following apps/plugins/dockers installed Unassigned devices Unassigned devices plus (addon) Unassigned devices preclear Openfiles, this was installed to see if there were files keeping the drives spinning Community applications Appdata cleanup, not being used yet Appdata backup/restore v3, this isn't being used yet but will be used to transfer appdata from the old server I have a global disk setting telling disks to spin down after 15 minutes I have set a 15 minute spin down of all data drives (8tb sas drives) I have stopped and started the array multiple times I have rebooted the server multiple times The issue I am having is that the 5 data drives are spinning 100% of the time, if I click on the disk icon the little pop up message says "normal operation, disk is in use, click to spin down drive" but nothing happens. I am able to "spin down" the ssd cache (for disk writes) and I see "feb 18 16:26:18 bob-new emhttpd: spinning down /dev/sdd" in the system log but the drives status changes back to green and the system log shows "Feb 18 16:26:22 bob-new emhttpd: read SMART /dev/sdd" If I attempt to spin down the data drives by clicking on the green dot nothing happens and there is nothing entered into the system log (maybe there is a better log to look at?) The drives are enterprise class drives so im not terribly worried that they are spinning all the time but I would really like to have them spin down when not in use. Any ideas, or help troubleshooting would be greatly appreciated.

i can successfully create a diagnostics with the same usb stick in the same port if I boot into standard mode, so I don't believe this is an issue with 2 seperate usb sticks that have been tried in multiple usb ports ... it only fails if booting into GUi mode. The server is running again so I'm going to leave it alone for now. if we go down the path of unraid I will fight with it then.

in GUi mode I get approximately 100 lines of errors saying there is no space on the device and no IP address is assigned. if I boot to normal non GUi mode then it boots correctly and I get an ip address. this is an older sff of that is being used as a proof of concept to make sure my parents will and can use Channels DVR... once they prove they can and will use the software then we will either replace this hardware with a rpi4 raid setup, or I will rebuid this with more ram new drives etc. just to answer questions asked, yes I can copy files to the usb stick, both were formatted fat32 under win10, full format not quick format, usb sticks don't show as read only. when I attempt to boot into GUi mode I do get a logon, Id of root brings we to the command prompt. when I attempt to run diagnostics I get over a screen full of warning: file_put_contents(): only 0 of xx bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamic/scripts/diagnostics on line XXX to me it seems, being that the server boots successfully, and gets an IP address in standard non GUi mode it isn't likely to be a hardware issue, due to the error about space it seems much more likely this is drivers etc are not being loaded.

got it working, for some reason this system doesn't like booting into GUi mode, booting into standard mode works fine.

that would be great if the system was even booting, but how do I pull logs if the machine isn't even booting? maybe im missing something? the machine will not boot into this mode, so I can't get to tools > diagnostics, and the machine is not getting IP address so I can't access it via the browser. I receive the message listed above on every boot, I have tried a cheap 4gb usb stick from microcenter and a brand new Sandisk 16gb stick (this is the usb that was working perfect previously). I tried to use the usb creation tool on both usb sticks and both hang at "syncing the file system" I found this online and it looks semi common,I then downloaded the zip, extracted it to the usb (fresh fat32 format), and ran the make bootable file as admin. all have the same result of what appears to be about 100 lines of the error listed above with no IP address assigned.

I am setting up an unraid for my parents to run Channels DVR, I was lax and didnt get the trial server to them in time for them to fully test the DVR functionality... I attempted to recreate the USB drive and on first boot I am seeing a bunch of messages saying /etc/rc.d/rc/samba: line 110: echo: write error: no space left on device The server does not receive an IP address. Is there a fix for this? I need to "reset " the server so I can give mom and dad at least a couple weeks with a trial before spending the money on a server license, we might not go with unraid as a final solution, but proving Unraid as a viable solution goes a long way toward me "selling" them on unraid vs a Linux R-pi4 solution that can't run Unraid.