August 22, 201312 yr So I just started experimenting with unRAID. Yay me! I have the RC, because I figured might as well play with the latest and greatest. So odd behavior. My parity drive, and one of my two drives in the array spinup / spindown as needed without *ANY* issues. However, the one mentioned in the subect line, will only spin up, if I force it to spin up. I configured a High water share, and started writing. I even changed the split level to 1, just in case that was my problem, but this thing WOULD NOT spin up the drive above, and start writing. Once i manually woke the drive up. It started writing to the drive without issue. It does spin down (confirmed this morning when the entire server was silent save the fans... Ideas, troubleshooting steps? I am also fully new to linux, so this is my crash course in learning linux. I am a several year IT guy, so I am not a total noob, but pretty much noob to linux. Any help or suggestions appreciated. Thanks! Allyn
August 22, 201312 yr The high-water allocation won't write across all disks. It starts filling one until it reaches half full then starts filling another disk and so on. There's a good explanation on the wiki here. I'm assuming you were writing to an User Share. If you're concerned about spin up not working try sharing the individual disks, wait for it to spin down, then write to that specific WD drive. It should definitely spin up and write in that situation.
August 22, 201312 yr Author I will test what you said, but I only have 3 drives. Parity, and 2 array drives. It ran the first drive down to 0, and never spun up and wrote to the second... So, yes I will test direct writing to each drive to confirm spin up, and let you know how it goes. Thanks in advance!
August 22, 201312 yr Author Testing confirms individual spinups work... so, have no clue what caused the abnormal behavior before... But good to know that the spinup/down is working correctly. Thanks!
Archived
This topic is now archived and is closed to further replies.