Guzzi

A lot will depend on how many files & folders you have... basically, you are now doing a "find" on twice as many. It might even be worse, as the entries from the disk shares you want to stay in the cache, to keep them from spinning down, might be displaced by the extra ones read by scanning the user share's twin copies. so this is the result after running the box overnight: All disks are spun down and memoryusage is as follows: root@TOWER:/# free total used free shared buffers cached Mem: 4017452 3866908 150544 0 247984 2939772 -/+ buffers/cache: 679152 3338300 Swap: 0 0 0 I ususally access the server for files via the [TOWER-Root] - path = /mnt/user entry in smb-extra.conf to get all usershares on one drive; this access (from windows SMB1) is fast and no disks spin up. Can you comment on how to read the output of free-command? I check the same without -u parameter to compare later... THanks, Guzzi

Thanks for explanation - I currently have it installed and checked with htop - so CPU usage seems pretty high, but can't say if it was the same before without -u. Will just let it run some days and see "how it feels". rgds, Guzzi

Hi Joe L., I have another question: What is the usecase for the "-u" parameter? I understand it reads and caches the usershare - but I thought, this is already working, if the disk dirs are cached? If -u is enabled - would the excludes still work? (Because I have mapped dirs in the usershare, that I do not want to cache) Thanks, Guzzi

I don't know exact details about WHS, but assume it run's NTFS - it is MUCH EASIER to recover files from NTFS partition with corresponding tools, ReiserFS has very bad support for this (I did it an both filesystems myself, got all files including names/directories recovered on NTFS, while lost filenames on RFS and most files recovered were corrupt).

THe only way is to test several improvements like BIOS settings, HW, etc. to find a working config. Might be possible, that your hardware does not support S3 properly and thus there is no working solution/workaround - then it would be the only solution to change HW - that's the way I did in the past ...

When I upgraded the bios I did a "load optimized settings" I did not overvolt my CPU, was not necessary - but I removed the undervolting because I experienced instabilities similar to yours. Overvolting (minimal!!!) nevertheless might help to stabilize the rig in some cases - that's why I mentioned it. So loading the default usually should be fine - you might want to load "optimized", although this is usually using "tighter" settings, it might better for the rig - unfortunately there is lots of bad BIOS implementations everywhere :-( - I assume this is the reason why Tom officially is not willing to support S3. As a solution it would help to add a testsection for S3 and point working setups - I would have been very happy, if this would have been available - avoiding all those "try and errors" by myself ... btw - PSU should be fine. I have no experience with your adaptercard. There is always hope to get implovement with newer kernel - the last update made quite some improvements to powermanagement. To make it even more complicated: Even n older BIOS might work better ... I know this sounds bad, cause means lot's of testing, but unfortunately I have no better hints at the moment ...

not easy to answer this ... I have NOT have this experienced ever (so far) in my environment, using S3 regulary. I assume, you have no entries in the syslog, so the freeze is before any reinitialization happened!? Possible reasons (fixes) could be: - Powersupply too weak (voltages drop when WOL happens and MB/CPU hangs) - check with no drives attached or check with "sifficient" powersupply - MB HW incompatibility - change MB (I did so in the beginning, 'cause I wastn't able to get S3 properly running with my former MB) - ACPI/BIOS incompatibility - check if newer/fixed BIOS is available or try using addons circumstancing that (you already did some stuff like boot parameters, e.g. I have to use S2RAM to properly reinitialize graphics after WOL. There is lot's of stuff in the linux kernel to handle bad BIOS/MB/ACPI behavior, so also a newer linux kernel might fix it/help. - instability by configuration: If you are undervolting, this could lead to freezes in such situations - use standard config or even try a little (!) overvolting to stabilize the set (I used undervolting in the past to save cureent, running on standard now plus S3 as better solution and avoiding freezes or other problems. You could also try resetting to defualts in BIOS to get other settings back to normal and see if it helps. Difficult to solves such issues - as stated above, I had quite some problems in the past and ended up changing the mobo - my final solution was to order some mobos and test them - I kept the one working best and sent back the others. Because I am a linux noob, other people can help you more on linux specific things happy new year and "happy testing", Guzzi

... maybe your drives do not spin down because they're not in the array? You might want to check this - as far as I remember the script only sends the server to S3 if all disks are spun down.

I'm running the same versions. I only cache three levels deep. I only have 512 meg of RAM in my server and under 5000 files in my Movies and Music folders. You have lots more files you are attempting to cache, but far more memory too. Yes, it is normal to see two processes. part of the script is run in a sub-shell. (The while loop is run as a sub-shell) Hi Joe, I also have lots of files and directories on my server and experience a lot of reading on the disks. I upgraded memory to make sure, it is sufficient to hold all dir-infos. Nevertheless my disks DO spindown (all), but often reread all contents. Might be caused, when I write to the array so the buffers are reused for writing? So my question (I am Linux noob....): Is there a way/tools to check/monitor what's happening? currently I used "free" to check memory usage and the mgmt page to see read operations on the drives. So I can see how many reads I had for first run of cache_dirs - and after some days of operation I see 10 or 20 times the amount, although there was no "real" read on the disks. Thanks, Guzzi Edit: I use S3 and wake the server via WOL - does cache_dirs a reread after S3? Does UnRaid flush the buffers after S3-wake? Hmmm, that would explain it - how can I verify this and is there a way to avoid it? Here is my "free" output: total used free shared buffers cached Mem: 4017452 2313480 1703972 0 248792 1391780 -/+ buffers/cache: 672908 3344544 Swap: 0 0 0 Do I read right, that mem extension from 2 to 4 GB wastn't necessary?

Anyone have a clue why this may be? Most likely it's due to a bug/feature in the MB BIOS implementation of S3. Seems to be. After flipping ACPI bios settings willy nilly, it is now working....mostly. It doesn't re-post video on resume, but I don't care. It's a headless system now that its running anyhow. I had the same problem and solved it by using S2RAM.

100% agree with agw! forget about all the scripts and check, if your machine supports S3 properly (by far not all HW/BIOS combinations do!). Entering S3 from commandline: echo 3 > /proc/acpi/sleep pressing powerbutton should then wake up your machine - check syslog if everything is fine. If yes, at least S3 mode entering worked fine and reinitializing too. Second check, if waking up the server via magic packet (instead of power button) works by sending a magic packet to your NICs MAC address if all this is fine, you can try integrate those scripts - otherwise you won't be able to use them anyway with your setup. and btw: S3 is not officially supported by Tom/limetec - probably because of the problems with so many HW/BIOS environments I assume - I had to change my MoBo to get it working ;-)

No idea for that, because I have no PS3. You might try searching the keywords "PS3" and "WakeOnLAN"/MagicPacket. If the PS3 is not capable of sending a Magicpacket and you have another machine running 24/7, you might run a monitoring script there to check is PS3 started and send Magicpacket to Unraid server in that case. Could also be running e.g. on your DSL-router - I know that AVM boxes are running minilinux on them and are capable to send WoL-Packets. Good luck!

Thanks Joe, that worked perfect!

One question to get "GreenIT" running - I tried to get the S3-Syslogmessages Colored: I tried to add match_case||"s3sleep"||green to syslog_match.conf But my syslogentries are still in "black"... Dec 3 11:05:35 XMS-GMI-01 AutoS3sleep[21258]: Switching power state to S3 now Dec 3 21:44:25 XMS-GMI-01 AutoS3sleep[22504]: Returning from Power State S3 now Any hint what is wrong?

I use it with -f -p - but it depends on your MB and if and in what manner it is supported Options: sonne@erde:~> s2ram -h Usage: s2ram [-nhi] [-fspmra] Options: -h, --help: this text. -n, --test: test if the machine is in the database. returns 0 if known and supported -i, --identify: prints a string that identifies the machine. --nofbsuspend do not suspend the framebuffer (debugging only!). -f, --force: force suspending, even on unknown machines. the following options are only available with --force: -s, --vbe_save: save VBE state before suspending and restore after resume. -p, --vbe_post: VBE POST the graphics card after resume -m, --vbe_mode: get VBE mode before suspend and set it after resume -r, --radeontool: turn off the backlight on radeons before suspending. -a, --acpi_sleep: set the acpi_sleep parameter before suspend 1=s3_bios, 2=s3_mode, 3=both -v, --pci_save: save the PCI config space for the VGA card. Google is your friend, e.g. http://de.opensuse.org/S2ram

Manual Test from command line works fine - just inserted it in the Sleepscript and will check after next sleep state (currently not possible due to usage of family ;-) Syslog shows: Nov 24 23:28:15 XMS-GMI-02 AutoS3sleep[11578]: Switching power state to S3 now

Thanks for the hint - one more question: Do I need to follow a "sleep" to give it some time to finish? Well, I can just give it a try and see what happens - will post results... Guzzi

http://lime-technology.com/forum/index.php?topic=4405.30 Did that not work for you? uups, didn't see that - will give it a try, thanks! Hi, this is to confirm s2ram is working fine on my setup. I get the videoscreen back and Eth-link set to 1000 also by the script. Mobo is GA-MA78GM-S2H. Now after looking in the syslog it seems, all messages - also the stuff being done for shutdown - are being written AFTER wakeup and all with same timestamp. Question to the professionals here: Is there the possiblility to write a line within this script to get at least one entry in syslog when machine is sent to suspend (including the timestamp WHEN the script triggered it)? Thanks, Guzzi

http://lime-technology.com/forum/index.php?topic=4405.30 Did that not work for you? uups, didn't see that - will give it a try, thanks!

Kapperz, do you get proper videosignal on the monitor after WOL from S3? I have the precedor of this board (GA-MA780G) and suffer from that problem. No other functional issues beside this. There were hints using S2RAM, but I couldn't find a working slackwarepackage. Thanks, Guzzi

No and you won't.... ACPI doesn't provide for it. Even for drives with power management that will power up in spin-down mode, it won't work. ...so the script you have posted somewhere else for WD drives to get staggered spinup also doesn't work for it? So the reinitialization process includes a command to the disk that ALWAYS spins up the drive? I am not experienced nor do I know enough about the ata protocol and that stuff, just want to make sure i properly understand that and why it's working or not working. Thanks, Guzzi

When I wake my server from S3, it always spins up all drives and does some reinitialization on the ports. I have two questions: 1.) Do others get those errormessages on inizialization also? Is it something to be worried about or is it harmless? 2.) Did anybody find a solution to AVOID the spinup of the drives after WOL? So that just the drives being accessed spin up as in normal operations? I would be interested in a solution or hints into the right direction. Thanks, Guzzi Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.05: SATA link up 1.5 Gbps (SStatus 113 SControl 320) Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x11) Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.00: revalidation failed (errno=-5) Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.15: hard resetting link Nov 17 22:37:04 XMS-GMI-02 kernel: ata2: controller in dubious state, performing PORT_RST Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.00: failed to IDENTIFY (I/O error, err_mask=0x11) Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.00: revalidation failed (errno=-5) Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.15: hard resetting link Nov 17 22:37:04 XMS-GMI-02 kernel: ata1: controller in dubious state, performing PORT_RST Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.15: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Nov 17 22:37:04 XMS-GMI-02 kernel: ata2.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 17 22:37:04 XMS-GMI-02 kernel: ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Been running the s3 script for several days and these new changes look great. What would make this perfect for me was if, as its final check, it pinged a list of IPs and if it couldn't reach any of them, then it would go to sleep. I don't know enough to do it myself and am looking for a bit of help on this. I believe someone else mentioned this earlier in the thread, but I don't think it got fleshed out far enough. It's just adding another section after the check of the timeframe. But I better do not post it - I can only do "if-then-else" - those guys here knowing better can easily set a vaiable containing the IP-adresses and have them processed. It should be very easy. So long you can do something like ping 1.2.3.4 -c 1 | grep -q "ttl=" if [ $? -eq 0 ] then ... so you can set a variable that prohibits (or allows) the machine to fall asleep...

Sorry. You guys are far... far ahead of me when it comes to Linux, which is to say that I don't know enough about Linux to write a competent script on my own. Rereading Guzzi's post and looking at the S3.SH script that I am using from awg's wiki, I now understand that Guzzi is refering to modifications he made on his script to check whether his HTPCs were on, and not to the basic script I am using. So Guzzi, if you would be kind enough to share your code I would like to give it a try. [edit]If all the added code does is ping the client for a response, I don't think it will help with the WDTV, because the WDTV does not power off completely. It only "soft-offs" so the network controller remains on. You can even telnet and FTP to it while it's in the "off" state.[/edit] And, WeeboTech, if you could illustrate how to incorporate your idea into the script I would also appreciate it. Though, please note, I am using NFS shares not smb, so maybe it wouldn't help in my case. My apologies for being at the beginning of the learning curve on this stuff and relatively useless at helping myself. Any help would be appreciated. ok, in fact my script is useless for you, if your networkdevice keeps TCP up while "switched off" - it works fine for devices that enter e.g. S3 mode - so, the networkadapter is active and responds on MAC address, but TCP-stack is not running, so it's NOT responding to a ping. For sure I am not good in scriptingstuff, so my script is not elegant, but it does what I need... here is what I added as "check": ping "DNSNameOfDevice or IP-Address" -c 1 | grep -q "ttl=" if [ $? -eq 0 ] then echo HTPC is active else echo HTPC is not active fi One more question from my side - I read somewhere, that it is possible not to spin up the harddrives when waking up the unraid machine from S3 - has anybody successfully done this? To my understanding at least the devices need some reinitialization that usually causes the drives to spin up. Or is this depending on the mobo/BIOS?

The S3 script already checks, if all disks are spun down. I have added checks if the HTPC-machines are up and available (powered on) - so Unraid doesn't go to sleep as long as the HTPCs are running - even if the disks are spun down. Can be done easily e.g. with ping and works fine. Disadvantage: Unraid will never go to S3 if HTPC is running, even if HTPC is not using it.