January 27, 201412 yr Unraid 4.7 ? 5.0.5 upgrade – spinup issues I've recently upgraded my server from 4.7 to 5.0.5, and I ran into three main issues: [*]At least some of the hardware health detection stuff doesn't work (specifically – the fan speed device node doesn't exist anymore). [*]A disk attached to my SATA card does not spin down, ever. (it does spin down but immediately spins back up again). [*]Disks are spun up inappropriately (i.e outside of a share access / spinup group) Issues 1 and 2 were solved by avoidance – replacing the fan and removing the SATA card. The spinup problem is a pain though. There were two main examples that made me think there was a problem. I have 4 disks, parity, and disks 1-3. All disks have separate spinup groups. Right after startup, clicking spindown worked just fine, as it did after doing a parity check. I have a share that spans disk 2 and 3. I try to access said share, and the parity, disk1 and disk2 spin up. Disk 3 does not, but it does if I access a file that is stored on it. Another example – disk 1 did not spin down after the half hour timeout I set. I manually clicked the spin down button, but parity and disk 2 were spun up. I clicked it again and disk 3 was then spun up. There are more examples of disks being spun up inappropriately on this machine, but I didn't think to log them. I have since reverted to unraid 4.7, which spins up disks correctly. I can carry on using version 4.7 for a while, but it limits the expandability of the server as I'd have liked to install larger disks. –----------------------------------------------------- Hardware details: Motherboard: Gigabyte GA-425-TUD (Atom, NM10), 2GB memory, 4 SATA ports Hard disks: Parity: 2 GB WD EARS Disk 1: 1.5 GB WD EADS Disk 2: 1.5 GB WD EARS Disk 3: 2 GB WD EARX
January 27, 201412 yr Author I didn't - I always run pure vanilla unraid (with the exception of adding the fan control script and a cronjob in unraid 4.7, I don't have this is unraid 5). I like my fileserver to be as simple as possible!
January 31, 201412 yr Author A hopefully exhaustive analysis: 1. I set up an unraid array with 3 disks to test this out, I started off on my desktop computer. 3 shares, A on disk 1, B on disk 2, C on disks 1 and 2. Spinups went as expected (except one time when it spun up an extra disk, but on the whole it seems to do the right thing and not spin up disks unrelated to the share). I found that setting the disks that a share is not allowed to be on as well as the disks that it is may have helped. 2. I tried to use this knowledge on my server. It didn't help, and in fact it was spinning up all the disks for a share that was restricted to one disk. Turning on / off spinup groups etc didn't help. 3. I moved the 3 disk set and USB stick from step 1 and put it on the server. No matter how many times I clicked spin down, the first disk and parity would not spin down. Conclusion: The GA-425-TUD motherboard works with unraid 4.7 but not unraid 5.0.5. Followup: NM10 chipsets may not work properly in unraid 5, at least with respect to spinup issues. Guess this means I need to buy a new Mini-ITX board. I only want to use the server for storing files, so any recommendations are welcome. I would prefer integrated CPUs to keep the cost / heat down, so I was looking at a Zacate board from Gigabyte for £45.
January 31, 201412 yr Guess this means I need to buy a new Mini-ITX board. I only want to use the server for storing files, so any recommendations are welcome. I would prefer integrated CPUs to keep the cost / heat down, so I was looking at a Zacate board from Gigabyte for £45. There was a recent thread about an integrated board with an AMD chip... ~$60US. Check the end of the following thread for some discussion about the AMD-6400 chip's throughput, transcoding speed, etc. http://lime-technology.com/forum/index.php?topic=31282.msg282591#msg282591
February 6, 201412 yr Unraid 4.7 ? 5.0.5 upgrade – spinup issues I've recently upgraded my server from 4.7 to 5.0.5, and I ran into three main issues: At least some of the hardware health detection stuff doesn't work (specifically – the fan speed device node doesn't exist anymore). How were you using this in 4.7? A disk attached to my SATA card does not spin down, ever. (it does spin down but immediately spins back up again). Disks are spun up inappropriately (i.e outside of a share access / spinup group) Please do a reboot, make this happen again, and then post your system log. I would also like to see your 'config/disk.cfg' file. Probably this has nothing to do with the motherboard. Once the server is up, do you have any external applications running that could possibly be accessing shares on the server?
February 6, 201412 yr Author I'll get back to you with the logs - I need to put the card back in, resync and then do the upgrade, which will probably take a few hours. In my old setup, I had the CPU fan controller (as it's the only one that you can control the speed of) connected to the fan on the front of my case (A Lian Li Q25B), and I used a fan control script to control the speed of this fan based upon the temperature of the hottest hard disk, with a cron job rechecking and updating the speed every couple of minutes. I've since just connected the fan to a 12V supply (which is less ideal but seems to work okay). I did the checks using a laptop + crossover cable, so there is no possibility of anything using the share. (this was after doing the same checks on the network as a whole).
February 7, 201412 yr Author Okay, upgrade to unraid 5 complete, 5th disk and card installed. Reboot, start array on reboot set, reboot, click spin down 3 times, results enclosed. The summary: The disk didn't spin down, and on the third time, all the disks spun up. Syslog and disk.cfg enclosed. syslog.txt disk.cfg
Archived
This topic is now archived and is closed to further replies.