AWMTech-AllynJ

02:02.0 is the new add-in card, and I cannot get it to work for God Love or Money... 02:06.0 is the onboard NIC which works just fine. Running unRAID Server Basic version: 5.0 Found this is some of the sys log stuff --- Nov 10 19:59:30 Unraid ntpd[1007]: new interface(s) found: waking up resolver Nov 10 20:16:44 Unraid kernel: skge 0000:02:02.0: cannot map device registers Nov 10 20:16:44 Unraid kernel: skge: probe of 0000:02:02.0 failed with error -12 Assistance is requested! Thanks!! 02:02.0 Ethernet controller: D-Link System Inc Unknown device 4302 (rev 10) Subsystem: D-Link System Inc Unknown device 4302 Flags: 66MHz, medium devsel, IRQ 22 I/O ports at de00 Memory at fddff000 (32-bit, non-prefetchable) [virtual] Expansion ROM at fdf00000 [disabled] Capabilities: [dc] Power Management version 2 Kernel modules: skge 02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) Subsystem: Micro-Star International Co., Ltd. Unknown device 297c Flags: bus master, medium devsel, latency 64, IRQ 21 I/O ports at dc00 Memory at fddfe000 (32-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Kernel driver in use: 8139too Kernel modules: 8139too

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!

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!

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