Hi guys,

 

Due to a problem with my onboard LAN, I had to buy a PCI Network Adapter to connect my array to the network. However, it seems to me like the PCI network adapter goes to sleep together with the rest of the array when it goes to S3.

 

I've tried reverting back to my onboard LAN and I can wake it up from S3, but not so for my PCI Network Adapter.

 

When the array goes into S3, there are no lights on the PCI Network Adapter.

 

When using the PCI Network Adapter, ethtool eth0 shows that Wake on Lan is g, meaning it should be able to be woken up, but it doesn't.

 

Please advise.

 

Thanks so much!

Ervine

Hi guys,

 

Due to a problem with my onboard LAN, I had to buy a PCI Network Adapter to connect my array to the network. However, it seems to me like the PCI network adapter goes to sleep together with the rest of the array when it goes to S3.

 

I've tried reverting back to my onboard LAN and I can wake it up from S3, but not so for my PCI Network Adapter.

 

When the array goes into S3, there are no lights on the PCI Network Adapter.

 

When using the PCI Network Adapter, ethtool eth0 shows that Wake on Lan is g, meaning it should be able to be woken up, but it doesn't.

 

Please advise.

 

Thanks so much!

Ervine

some PCI network cards will have an extra jumper cable that needs to be added to the motherboard to supply power when asleep for exactly that reason.

It will look a lot like this: http://www.directron.com/wol.html  (Your motherboard may not have the corresponding connector if it has a built in network-interface, but you might check the manual to see if it does.)

 

Joe L.

Thanks for the prompt reply Joe.

 

I forgot to mention this earlier but I read about that, but I don't see any place for a jumper to can be attached to my card (it's a TP-Link TG-3269).

 

From what I understand it SHOULD be able to get power from the PCI slot directly, but somehow it doesn't.

 

Any thoughts on this?

Oh man... I think my PCI card might not support WOL... I read "Remote Boot" on the box and I assumed it was WOL...

 

http://www.tp-link.com/products/productDetails.asp?class=anm&content=fea&pmodel=TG-3269

Have you got an on board NIC which supports WOL or something along those lines? I'm assuming you're using a addon PCI NIC because youre after a 1Gbps NIC? In the past I had installed an addon PCI NIC just to have a 1Gbps speed as the on board NIC was only 100Mbps, but thr addon card didn't support WOL, so I connected both thr on board and addon NICs to my switch, enabled WOL in BIOs for the addon card and was able to get WOL working using the old inboard NIC and have the OS disable the on board at start up only using the 1Gbps NIC only.

thanks! i didn't know you could fire both up simultaneously.

 

the on board does indeed support WOL. I've tested it and it works.

 

can i know how you disabled it via the unraid OS?

My suggestion was done on a Windows-based machine though I'm possible it can be done under unraid too. To do it you might have to try one of the following:

 

From memory I'm certain that you can set the unraid os to use a specific NIC as well, it might have something to do with the network.cfg file under /boot/config folder, specifying which ETHx to use, whether it be eth0 or eth1 (not sure on this as I'm on leave and can't access my unraid server to test this)

 

Or you might want to try this, if you run a 'ifconfig eth0 disable' assuming that eth0 is the on board NIC that you want disabled. You'll have to place this line into your 'go' file (located under /boot/config folder), which will disable your on board NIC upon start up and the eth1 being your addon card should get a IP if using DHCP and you should be able to use this as your primary NIC for the unraid OS.

 

Finally their might be another command or configuration all together to perimanantly disable the unwanted NIC all together, but I'm uncertain how to do this.

Ah.. okay I'll give it a go. If not then I'll just have to get a seperate NIC that can support WOL.

Thanks guys, I've got the array to go to sleep and I've been able to wake it up via WOL after popping in another NIC I had from another computer. Now to just get the s3.sh script to work!

 

Also just to add, the Asus NX1101 NIC is NOT COMPATIBLE with unRAID. Just in case someone wants to know..