August 2, 201015 yr It is? Where's the web interface button or what is the shell command to enter S3 sleep? Written about ad infinitum in the forum And why doesn't S3 sleep work on my box (it did when it was a Windows machine) Grin If you don't know the command to invoke it, how do you know it doesn't work? If it's been written about ad infinitum why isn't it a feature? I know the command. It doesn't work. It'll S3 sleep, but won't WOL -- useless for me, as I may as well switch it off completely if I have to hit the power button to get it going again. I know the board supports WOL, because I've WOL'd it when it was a Windows box, but unRAID won't do it. Very frustrating.
August 2, 201015 yr It is? Where's the web interface button or what is the shell command to enter S3 sleep? Written about ad infinitum in the forum And why doesn't S3 sleep work on my box (it did when it was a Windows machine) Grin If you don't know the command to invoke it, how do you know it doesn't work? If it's been written about ad infinitum why isn't it a feature? I know the command. It doesn't work. It'll S3 sleep, but won't WOL -- useless for me, as I may as well switch it off completely if I have to hit the power button to get it going again. I know the board supports WOL, because I've WOL'd it when it was a Windows box, but unRAID won't do it. Very frustrating. But what you may be running into is a NIC driver issue or BIOS or a few other things. WOL is one of those things that can take a little bit of playing around with to get just right... for your setup. While it would be nice to see it have a GUI section in unRAID i think we would see many more people saying "I enables suspend in the GUI, why does it not work?" As you said yourself, your board suspends fine but wont come back from a WOL packet. Do some google searching and see if others running Linux have got it working and go from there.
August 2, 201015 yr If it's been written about ad infinitum why isn't it a feature? Because it depends on your hardware, your BIOS, and your system. If it was a "feature" half the people would be bitching that it doesn't work, because S3 doesn't work on half the machines out there and there is no way for unRAID to know of yours works or not. Does you NIC support WOL? What types of WOL does it support? Which WOL trigger to you want to use? Do you need to save/restore the frame buffer on you system? Is s3 mode enabled in your BIOS? Is s1 mode enabled in your BIOS? Does your system have a buggy ACPI implementation? Everything unRAID can do to support S3 has been done. The rest is up to you.
August 2, 201015 yr I realise there are setups where S3 and WOL doesn't work, but to have it work on a Windows machine, then to put unRAID on that same machine and have it not work is frustrating. I've tried several times to get it to work, I've read all the threads, I've posted in the threads, I' pumbg'd or whatever the command is. It doesn't work. It's not the end of the world, but it's annoying. Oh, and my motherboard is basically the unRAID reference board.
August 2, 201015 yr Oh, and my motherboard is basically the unRAID reference board. That doesn't mean anything. The unRAID reference board was not picked for it's Suspend/S3 capabilities. It was picked for overall stability. Suspend/S3 is not a feature. It does not come into consideration on official unRAID systems.
August 2, 201015 yr Oh, and my motherboard is basically the unRAID reference board. That doesn't mean anything. The unRAID reference board was not picked for it's Suspend/S3 capabilities. It was picked for overall stability. Suspend/S3 is not a feature. It does not come into consideration on official unRAID systems. That's one problem with 99.99% of support for unRAID coming from users -- there's no-one to actually commit to an official line.
August 2, 201015 yr In your situation, you also need to make sure in addition to your CPU, Motherboard, and BIOS settings support S3/Suspend that all your add-in SATA cards properly support it too.
August 2, 201015 yr S3 suspend is dangerous. You can corrupt drives and lose your whole array messing around with it. I don't know how I can explain it differently ... S3 is not something that even can be "built-into" unRAID. It depends on way too many other variables, such as your BIOS, your PSU, your chipset, etc. The only thing unRAID can do, is include the S3 module. If it was not there, you could not do S3. unRAID has the s3 module. That's all that can be done from unRAID's perspective. Your frustration that you can't wake up your box from S3 is YOUR HARDWARE'S FAULT. Your hardware either has crappy Linux drivers, or implements the standards improperly, or any of 100 different bugs related to ACPI on Linux and S3 suspend mode. Did you try an Intel NIC, and disable the Realtek on the mobo? That's the first thing I would try.
August 2, 201015 yr Did you try an Intel NIC, and disable the Realtek on the mobo? That's the first thing I would try. I also have a newly built server with the SuperMicro C2SEE motherboard. I've tried to put the server to sleep after enabling S3 mode in the bios. It goes to sleep perfectly. However, the lights on the NIC connector go dark. There is absolutely no way to wake it with a WOL packet if it is not listening. Now, it might be the OS's fault, but I'm guessing a faulty BIOS implementation. (We're talking hardware now, since when asleep, no OS is in effect) Yes, I can wake it by pressing the "power" button, but it comes alive without the NIC and without video. As mentioned, the board was not picked for its S3 capabilities. I'm very happy with having a fast, stable reliable server. Most of my media players would not be able to wake it anyway, since they do not have the capability to send a WOL packet. If I find an inexpensive Intel NIC, I'll give it a try... Who knows.... might just work. Joe L.
August 2, 201015 yr Yes, I can wake it by pressing the "power" button, but it comes alive without the NIC and without video. This is very common. You have to save the video registers and restore them. The s2ram package will do this nicely.
August 3, 201015 yr If I find an inexpensive Intel NIC, I'll give it a try... Who knows.... might just work. Joe L. Dude.. Maybe you could glue together some cool gawk & sed scripts to press the button? LOL!!! That's a compliment, not a put down, you've done some really cool things with very basic unix tools, I figure you can do this one too!
August 3, 201015 yr Yes, I can wake it by pressing the "power" button, but it comes alive without the NIC and without video. This is very common. You have to save the video registers and restore them. The s2ram package will do this nicely. Very true, but somehow I doubt it will illuminate the LED on the RJ-45 connector when the server goes to sleep showing it is listening. (and powered up, waiting/listening for the WOL packet) I was not worried about the S3 sleep, as in my house the server is used at all hours of day and night. It would not get much sleep. If I find a good deal on an Intel Gigabyte LAN card, I'll give it a try, but I don't have it as a priority. The new C2SEE based server is currently sitting on the corner of the kitchen table as it gets burned in. My original server is still feeding most of the media servers in the house.
August 3, 201015 yr S3 suspend is dangerous. You can corrupt drives and lose your whole array messing around with it. Your frustration that you can't wake up your box from S3 is YOUR HARDWARE'S FAULT. Your hardware either has crappy Linux drivers, or implements the standards improperly, or any of 100 different bugs related to ACPI on Linux and S3 suspend mode. Did you try an Intel NIC, and disable the Realtek on the mobo? That's the first thing I would try. The corruption did occur to me, which is why I didn't spend any extra time futzing with it. Wow, my hardware's fault? At the time, I had essentially the same hardware as the (previous) reference build plus two 1430SA adapters (also in the reference build) and it's crap? Ignoring that, I'm sort of surprised that no-one has piped up and said they have the same hardware and it does/doesn't work? Like I said, it's not the end of the world, but it is a feature I'd appreciate, which is why I posted the feature request in this thread -- not exactly expecting to get shouted down. I'm fairly sure it's not the "fault" of the hardware as it works in Windows. By all means blame Linux, if you will. If it turns out that adding the 1430SA adapters screws with S3 standby, then that's a good enough explanation for me. I'll keep the 1430SAs and forget about S3. It's also not worth me buying another NIC, I can work around not having S3.
August 3, 201015 yr Wow, my hardware's fault? At the time, I had essentially the same hardware as the (previous) reference build plus two 1430SA adapters (also in the reference build) and it's crap? * * * I'm fairly sure it's not the "fault" of the hardware as it works in Windows. By all means blame Linux, if you will. Actually, it is very likely the hardware. You would be AMAZED at what shortcuts HW manufacturers pull that makes their HW non-compliant with official standards (which Linux expects) and then they "fix" it in their Windows drivers.... never bothering to "fix" it in the Linux drivers. Particularly with something as low-profile as WOL. Yes, NIC and chipset manufacturers, I'm talking about you. So, if you want to blame Linux for expecting HW manufacturers to comply with standards, then that's up to you. I blame the asshat hardware manufacturers. Put a REAL Intel NIC in the system and you will likely not have a problem.
August 3, 201015 yr FYI, I have been using S3 ( WOL) since I set up my server , and it's works flawless
August 27, 201015 yr Trying to get this topic going again... What we need is to nail down the event and plugin structure. This alone will be fundamental in allowing unRAID to progress further with community development. Below is a list of items which I think a NAS appliance should have, if not built in there should be options for addons, plugins, or upgrades to provide the functionality. Some of this was taken from looking at existing NAS Appliances' featuresets. Simple Web-based Configuration Secure Management (https, ssh, policy-based ip blocking) Simple Web-based file manager Support for Win OS, MAC OS X, NFS Clients Pseudo-Realtime Notification of events - email, pager, sms Proactive Monitoring of HDD SMART UPS Support Network Recycle Bin Backup Server for client machines FTP Server Print Server Active Directory Integration UPnP / DLNA Media Server / Media Streaming for popular devices Supports remote Syslog Servers Torrent Client Usenet Client iSCSI Target Service Community Software Package Platform (Plugins and Addons)
August 27, 201015 yr Looks good. Personally i dont think a print server should be there but thats personal opinion. I would add: more/all fs support folder mirroring i.e. multiple copies of same critical data timestamped cosmetics and artwork. for the unraid target market it needs to look professional and contiguous. online version updates and rollbacks anti spinup countermeasures overheating countermeasures USB storage device actions i.e. backup to NAS, rip iso, mount as share etc
August 30, 201015 yr I think support for Win OS, MAC OS X, NFS Clients is a basic NAS feature, and the UnRAID 5 series should support this. Also iSCSI Target Service is important.
Archived
This topic is now archived and is closed to further replies.