bubbaQ
Moderators
-
Joined
-
Last visited
Everything posted by bubbaQ
-
I don't know what the reason is... I just know it has worked in some instances in the past. My P5B-Deluxe was that way. You always need to run ethtool to check the WOL setting. Set it to "g" and that's all. If you use the others, like any directed packet, it will wake up on it's own in a few seconds when any other system checks on it.
-
In some cases, you have to use Windows to force the registers on the NIC. Boot Windows, and then go to driver options for the NIC, and select all the options there. Also go to power management in the NIC, and make sure that "allow this device to bring the computer out of standby" is enabled, and disable "allow the computer to turn off this device to save power." I know that should make a bit of difference, but some NIC drivers in Linux have some bugs when it comes to setting registers for things like WOL.... but it you do them first in Windows they will stick. Also, go to the latest unRAID beta... the .29 kernel has a number of s3 suspend improvements. My bench machine does not suspend with unRAID 4.4.2 but does splendidly with 4.5-Beta6.
-
You can put a ping command in the script, and ping each HTPC to see if it is running.
-
A few years old, bit this was hot when I first found it.... it was the case I was going to get at the time... http://www.xxera.com/SS-480.html
-
Thank you. Will there be any indication the unrecoverable error was experienced?
-
Which brings me back to my question from several weeks ago, of what does unRAID do when it encounters an uncorrectable read error when operating in degraded mode (i.e. with a failed data drive)? It needs to continue, and not mark the drive as bad.
-
They failed statistics 101.... like the other article. The gist is that 12 TB = 1x10^12 bits. If the unrecoverable read error rate for each drive is 1 in 1x10^12 bits, they think you will get one error during the rebuild of a 12TB array. But having 12 drives that each has a 1x10^12 bit error rate is NOT the same as 1 drive with a 1x10^12 bit error rate.
-
Try deleting the share from the Windoze box before unraid reboots.