agw

Nice wiring luca.

No argument from me about the dollars and sense of an inexpensive gigabit switch. Just want to weigh in on the DIR-655: I upgraded to that same router from an older Netgear g-router, and it was worth every penny. The range and the reliability of the wireless connection are outstanding in contrast to the Netgear router that it replaced. Where I was re-booting the Netgear on a regular basis, the DIR-655 has been up for probably six months and I haven't had to touch it yet. And, of course I use as a gigabit switch for the unRaid box and desktop without any problems. agw

A quick google search of 'Nvidia 8800 sleep' nets a lot of posts about similar problems under Vista. I realize the OSs are completely unrelated, but I would consider the video card to be low-hanging fruit anyway and see if swapping it out solves the problem. No problem getting to the unRaid web interface or telneting-in from a networked computer after it wakes up? agw

I put my notes on getting sleep and wake on lan working in the wiki under the 'How-Tos' section. This way the smart people can go in and make edits and hopefully make it more useful. Link: http://lime-technology.com/wiki/index.php/Setup_Sleep_%28S3%29_and_Wake_on_Lan_%28WOL%29 In the notes, I reference my batch file for sending the magic packet and also my s3.sh file that is called from the 'go' script. Copies of those files are attached to this post. Hope there's something useful in there for someone. AGW

From memory, I'm going to say 8-10 seconds or so? I definitely remember it being faster than a fresh boot. But again, I'm only running two drives, so not sure how the numbers might change for some of the large arrays that many are running. Of course, after several days of glorious S3 / WOL use - I dug back into this to write-up my FB,BB (For Beginners, By Beginners) Guide to S3 / WOL . . . and I somehow got things all goofed up. So, this weekend I get to wrestle with two things: 1. Server is no longer responding to magic packet. I'm hoping I just made a bad BIOS tweak - I don't remember doing that but I was in the BIOS the other day and it's plausible. 2. When it is sleeping and waking properly, I noticed that the server no longer negotiates a gigabit connection upon wake-up. It's 1000Mb/s off of cold-boot, but if I check it after wake from sleep, it seems to be coming back at 100Mb/s. It's onboard Realtek 8168b NIC, so I suspect a driver issue - which means I probably won't be able to do much about it other than hope a driver update in next unRAID release cleans it up. Or buy a NIC, but I'm inclined not to go that route if I can help it. AGW

Well, my box currently only has two drives in it - so for me 'all drives spinning up' just means that both spin up. Although I'm fairly certain that all of them would spin up regardless of how many were installed. Mine spends most of its time idle, and when it is online I have the drives set to spin for a minimum of one hour of no activity before they spin down - which seems like a reasonable compromise of energy saving vs drive wear. I'm using an 80+ power supply, integrated video and a 45W processor, and my machine still pulls about 70W idle with both drives spun down, so I really wanted the machine to sleep when it's not in use. BTW flambot - I haven't forgot about you, I'm still putting together my S3 / WOL step-by-step - but I've not had much time to piece it all together. I realize you may not even be that interested anymore, but I think it may still be good reference for others. I'm pretty green at all of this, so I'm even learning quite a bit as I re-visit everything.

This is something I would like to be able to achieve. Is it possible you could detail exactly how you achieved this? When I get home this evening, I will try to put something together. To automate the sleep process, I essentially copied OMV's script (see beginning of this thread) verbatim and then made a couple of very minor edits. Do all the drives spin up when you wake it up? Yes. Can a magic packet be sent by an xbox (Original using xbmc)?? No idea. I'm far from an expert (and I don't own an xbox). Perhaps someone else will chime in. Ideally I'd like the machine to wake up whenever someone tries to browse to it or access it, but I'm not sure that's currently possible. May even be a motherboard restriction, not sure.

OK - it's been a long and frustrating effort, but I've finally got unRaid sending me email alerts if the system goes offline. AND . . . it's reliably sleeping after spindown and waking up via magic packet! I consider these two functions to be key to any respectable home server system so I really wanted to get both working. After it was working, the next challenge was making the WOL function a little more wife friendly. She couldn't be expected to jump through many hoops to wake the server up if she needed to access her files from her laptop. I found a windows command line tool called wolcmd that works great from a .bat file to send the magic packet. http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx Instructions for use are on the site. Basically the .bat file is a two-liner (could be a one-liner probably), first change to the directory where wolcmd.exe is stored, then call it along with your server mac address, ip address, and subnet mask. Pretty straighforward. Now I have an icon on the wife's laptop called "Wake Server" that she can just double-click if the server is not online. I hope this might help someone. I'll see if I can add a link to the wiki for the wolcmd tool. agw

Review on Missing Remote.com. They've geared it toward WHS, but I thought it might be of interest to some in this community as well. A bit pricey compared to the typical home-build, but - generally speaking - I like the way things are progressing in the home server market. http://www.missingremote.com/index.php?option=com_content&task=view&id=3979&Itemid=236

That does help a bit. Essentially you are using the 'echo' command to "apply" a value of 3 to /proc/acpi/sleep . . . I guess. What I've done so far is taken OMV's updated bash script that is designed to suspend the machine after a preset period of spindown time, and created a file called s3.sh, using wordpad, that contains OMV's script. Then I try to call that file from the go script using nohup, but it doesn't work. I get: "No such file or directory". I suspect that I'm missing something very basic in the process of creating a useable script file.

Is that the actual command you typed? I've tried all sorts of commands that looked similar, but that exact one doesn't look familiar. Which build of unRAID did you use that with, and do you have and mods to it? Yes, if I telnet into the tower and type: echo 3 > /proc/acpi/sleep my machine goes to sleep. Works very well, actually. I gleaned this command from this thread. I'm not sure WHY it works, of course - which is what makes everything so frustrating. I do try to understand things as I try to implement them, so that I am learning as opposed to just typing. But I haven't even been able to decipher the first part of this: 'echo 3' ! Anyway, using unRAID 4.4 on a Foxconn A7GM-S motherboard.

OK - I'm able to put my server to sleep using the: echo 3 > /proc/acpi/sleep command. Wakes up via magic packet. So far, so good. I've fiddled around with my go script and tried to implement OMV's script to force sleep after a set period of drives being spun down. This exercise just served to reinforce how little I really know about linux, scripts, etc. Anybody that has this working successfully willing to share what exactly is in their go script and, if there is a separate script for OMVs routine (or similar), how that is generated, where it is stored, etc? Many (many) thanks in advance!

Jru I'm using the same board with just two drives (SATA) currently hooked up. I can boot fine and server 'seems' to run normally under 4.4 - but in reviewing the syslog I (and others using the SB700 chipset) get the following messages: ata 1: soft reset failed (device not ready) ata 1: failed due to HW bug, retry pmp=0 Whether the messages are important or not hasn't really been determined, but I'm curious if you could review your syslog and see if you have the same messages present? Just for curiosity's sake. Thread discussion here: http://lime-technology.com/forum/index.php?topic=2826.15 AGW

Thanks for the syslog feedback RobJ! I'm not sure what this means: "I see a *lot* of core changes in the syslog. Perhaps some are only cosmetic, but they are substantial and involve core modules" . . . but it certainly sounds ominous so I think I will go back to 4.3.3 and wait things out for a while. AGW

I recently upgraded from 4.3.3 to 4.4 also and get similar errors in the syslog using a SB700 / 780G based motherboard (Foxconn A7GM-S). I also got a couple of other new errors that were not present in 4.3.3. However, my system boots through them and actually seems to be less concerned about the error messages than I am. I've sent a few GBs back and forth and even completed a parity check and no complaints in the syslog. I will post a 4.3.3 and a 4.4 syslog later tonight for your guys' comments. ------- Syslog from 4.3.3 and 4.4 attached. Before I saved 4.4 syslog, I made a few more tweaks in the BIOS and managed to eliminate two errors that were unique to 4.4: 1. ACPI Warning (tbutils-0217): Incorrect checksum in table . . . . 2. Tower kernel: spurious 8259A interrupt: IRQ7 However, you will still see the following in 4.4 syslog that are not present in 4.3.3: 3. ata 1: soft reset failed (device not ready) 4. ata 1: failed due to HW bug, retry pmp=0 5. ata 2: soft reset failed (device not ready) 6. ata2: failed due to HW bug, retry pmp=0 Again, other than the above, the system boots fine and seems to be operating correctly. Also, this is the latest BIOS from Foxconn. Note that in 4.3.3 I had to append the 'noapic' statement to syslinux . . . otherwise everything else remains unchanged b/w the two. The burning questions I have: 1. Do the Linux / Unraid gurus think the above errors in 4.4 are important enough to revert back to 4.3.3? It doesn't really bother me to do so . . . just that the spin down of my Samsung 1TB parity works better in 4.4. There is a new "Error attaching device data" in my 4.3.3 syslog that I do not believe I have seen before - likely a result of my BIOS fiddling under 4.4. I suspect I can make that disappear though. 2. Kind of unrelated, but can someone smart please tell me what the following means: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01113, max UDMA7 ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32) ata1.00: configured for UDMA/133 Am I getting my full SATA 3.0 speeds? Is UDMA/133 the same as SATA 3.0? What am I not understanding? I have tried to figure this out on my own - but honestly I think I've been to the end of the internet and I never ran across a good explanation of how to interpret. In case you can't tell, I'm Linux-challenged. Please be gentle.

Seems to be working great. Been up for about a month under the free Unraid license, using 4.3.3. Initially was getting some APIC CPU errors in the syslog (esp during a parity check), but appending the 'noapic' statement into syslinux.cfg has resolved that. BTW - kudos to Joe L for unMenu (along with the other help he and others provide via the forum). Sure makes keeping an eye on the syslog very simple! Currently using A7GM-S, BE-2400 45W CPU, 4GB ram and Antec 300 case. Very inexpensive start . . .

Loooong time lurker (soon to be unraider). I suspect most of you are on the Newegg email distribution, but for those that are not the above seem to be pretty good deals. I know the CM590 gets a lot of play here on the forums - $20 discount essentially negates the shipping cost. Power supply is free shipping though. Promo code for PC Pwr & Cooling Silencer 500, $64.99 w/ free shipping: EMCAKDAAB Promo code for Coolermaster 590, $39.99 no free shipping: EMCAKDAAC