Lerxst

Hi Brandon, at last someone who's finally decided on running ESXi on an AMD platform I've been waiting ages for someone to try this as everyone else seems to have gone the Intel Xeon/Sumpermicro route. Post some pics of your setup when you get back

It sounds like a lot of people are getting a bit upset over things development wise with unRaid. I take it that most of the issues are related to the beta version of 5.0. I'm still running 4.7 final and only have 4 drives and decided to give version 5 a wide berth because of the fact that it was a beta version and that there was a clear warning about using it on a production system! As far as regular updates goes if Joe's moved across the country then I'd expect that things are going to have to take a back seat while "Real Life" takes precedence. unRaid isn't the first product of a one man company where the owner has gone AWOL see http://gizmodo.com/5884684/why-ill-never-trust-a-human-with-my-data-again for what happened to a one man web hosting company and the panic that it caused among its customers. I'm sure Tom's working on things so I'm cool with that and if not then I'll just start looking at the alternatives instead.

And now the thrilling conclusion to this episode This has been bugging me for days now, it's a good job I lost my hair years ago else I'd be bald now I started wondering if I had a faulty board so I decided to fit an Intel Pro 100 NIC and disable the onboard one and try testing again. I noticed that a new MAC address was being picked up during the boot phase and made a note of it and tried testing the WOL function again. The result was still the same... nothing... While reading about WOL and how it works I found a nice Windows based magic packet sender from http://magicpacket.free.fr/. While using the program I suddenly noticed something that I should have spotted earlier... you know the kind of problem where the answer is staring you in the face and you go off in every other direction because it couldn't possibly be that simple... Well the old saying "fool me once... shame on you... fool me twice... shame on me!" came true. The problem was due to the subnet mask! The value 255.255.255.255 is a broadcast to all networks (like the internet!) which would take who nows how long before getting to my internal network. As soon as I changed the subnet mask to 255.255.255.0 (which is right for a 196.168.0.0 IP address) the server sprang to life. I've tested it several times from my PC which is linked through another switch and it's woken up every time like a champ! For future reference the "correct" format of a Wake On Lan command should be: wolcmd.exe {Server MAC Address} {Server IP Address} {Server Subnet Mask} eg: wolcmd.exe 485B39622053 192.168.1.100 255.255.255.0 Well at least it looks like this mystery is now solved. Thanks to everyone who helped! It proves that even IT Admins can get it wrong

Hi there, well my unRaid box has a static IP and I tried running the wakeup script from my HTPC which is on the same switch as the unRaid box with no change. It looks like the server is going into a deep sleep and powering off the onboard NIC. I'm going to try and dig a little deeper into the driver issue as I am sure there must be some subtle differences between the 8169 and 8111 drivers. To be continued...

Hi Guys, to follow on from my last post I've tried out a couple of things, according to one of the threads on this forum relating to s3 and WOL there was some mention of running Windows and making some changes to the device's power management settings, I tried using a Hiren's boot disc and running Mini XP and tried altering the power management settings for the onboard NIC which strangely was being detected as a Realtek 8168/8111. Tried rebooting unRaid and got the same results. Here's the contents of my wakeup batch file: cd c:\wolcmd wolcmd.exe 485B39622053 192.168.1.100 255.255.255.255 I've tried both sets of 255's with no change. My network is wired, I have a 10/100 switch and a gigabit switch I've tried running the script from my HTPC with the same effect. Now this might be of interest. In the syslog the onboard NIC is detected as an r8168 but it loads the 8169 driver... Sep 7 21:30:14 TARDIS kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded Sep 7 21:30:14 TARDIS kernel: r8169 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Sep 7 21:30:14 TARDIS kernel: r8169 0000:02:00.0: setting latency timer to 64 Sep 7 21:30:14 TARDIS kernel: r8169 0000:02:00.0: irq 26 for MSI/MSI-X Sep 7 21:30:14 TARDIS kernel: eth0: RTL8168d/8111d at 0xf8276000, 48:5b:39:62:20:53, XID 083000c0 IRQ 26 Now according to this site http://louwrentius.blogspot.com/2009/12/problem-with-wake-on-lan-wol-and-r8168.html there's an issue with WOL not working due to the driver and the proposed solution was to backlist the 'r8169' driver in the blacklist.conf file. Unfortunately I've not been able to get the change to be saved back to the flash drive to run on the next boot. There's one more weird thing... if I open a telnet session and login as root, if I enter the command "echo 3>/proc/acpi/sleep" the server doesn't go to sleep but runs a parity check syslog-2010-09-07.zip

I've replicated your settings and so far the server won't wake up, I've looked at the status lights on the NIC and they're both out which is strange...

Yes I have the M4A78L-M motherboard with the 0705 BIOS version. Thanks in advance

Hi everyone, I recently build a budget unRaid box using the Asus motherboard and while everything else if working fine I'm having some issues in getting the server to resume from S3 sleep. I've been trying to use the S3 script that is elsewhere on this forum but removed it to try and isolate the problem. I've updated the BIOS to the latest one and enabled S3 only, PME - Enabled, ACPI - Enabled and APIC - Enabled. Now here come the strange part, if I put the server to sleep via the user scripts page I can wake it up by sending a magic packet within a few seconds of the drives spinning down, but wait anymore than that e.g. 30 minutes and sending the magic packet does nothing at all. The only way I can wake up the server is by manually pressing the power button. So has anyone had any success in getting this working, and if so what settings did you set in the BIOS in case I've missed something.