Guzzi

I have 2 GB RAM in the box: (from /usr/bin/top -b -n1) top - 01:15:04 up 1:13, 0 users, load average: 3.94, 4.00, 3.73 Tasks: 73 total, 2 running, 71 sleeping, 0 stopped, 0 zombie Cpu(s): 7.8%us, 60.5%sy, 0.0%ni, 22.3%id, 5.0%wa, 0.6%hi, 3.7%si, 0.0%st Mem: 1943344k total, 1617648k used, 325696k free, 39868k buffers Swap: 0k total, 0k used, 0k free, 1481180k cached (Did a reboot after I saw those kernel things in syslog - never had that before, just during this specific preclear) Addons: I have disabled cachedirs to keep memory free while moving data to the box. Here is the goscript: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c # Unraid_Notify (E-Mail Notification) #installpkg /boot/packages/socat-1.7.0.0-i486-2bj.tgz #installpkg /boot/packages/unraid_notify-2.30-noarch-unRAID.tgz installpkg /boot/packages/acpitool-0.4.7-i486-1goa.tgz #unraid_notify start sleep 30 # enable wakeup /usr/sbin/ethtool -s eth0 wol g # Start UnMenu /boot/unmenu/uu I have to say that I was moving constantly data to the box while clearing the disk - maybe the problems with the disk has blocked the copy process? Do I need to upgrade the RAM to 4 GB?

This is a new one to me... According to a "google" search on "Power-Off_Retract_Count", I got the following [pre] # Power-Off_Retract_Count = No of times drive was powered off in an emergency, called Emergency Unload. # Load_Cycle_Count = This number is highly affected by your power management policies. For e.g. a too aggressive power management might put hard disk to sleep too often. This number is indicative of when your hard disk parks, unparks , spins up, spins down. [/pre] So. reading between the lines... unless you powered down the disk while it was being cleared, it *thought* it had lost power, or it really did lose power. It retracted the disk heads in an emergency-unload, thinking it had lost power, then loaded them again once it thought power had been restored. I'd check the system log for any other errors while the drive was being cleared. I'd also check any power connectors or "Y" splitters. They can be intermittent. Joe L. Hi Joe, checking the powerconnectors is no problem - I can do that. I cheked the syslog several times during preclear and except in the very first minutes (some drive not ready) there was nothing special. But it seems, that in the post read there happened a lot - which I do not understand; could you have a look in the log? It's the complete preclear-process from beginning to the end!? Thanks, Guzzi

Hi, I have succesfully precleared a disk, but got smartdifferences as below. Is this something I have to worry about or can I use this disk? I realized some interface errors in the log in the very beginning, but no errors in the script. Thanks, Guzzi ============================================================================ == == Disk /dev/sdq has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 62,63c62,63 < 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31 < 193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 25344 --- > 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 > 193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 25345 ============================================================================

Tnx Joe for the quick answer - will give it a try...

Hi, I modified the script to check if there is any htpc left running and this works fine. I inserted commands in the go script - this blocks my console. So: How do I "background" it ("launch as separate script in background"?) to keep my console free? Sorry for the silly question, but I am completely unexperienced with shell scripts... tnx, Guzzi

No. s2ram has custom parameters for hundreds of mobos built into it, as well as additional command line parameters for special handling of ACPI and video quirks of a mobo. ok, understand - so this could help reinitializing the videocard for display. So I will wait if someone can compile a package for unraid - as I understood this is currently not available. @cricker: No, but google for it, can be found quickly (that's the way I did it)

Sometimes there is a bios option to re-initialize the video bios after returning from sleep. You can check your bios and toggle the option to see if this helps. No, there is no such option - checked this before posting here...

Didn't find an installable s2ram - bit I found and installed acpitool - usind acpitool -s (found that somewhere else here in the forum). Is this the same as s2ram? Package installed: acpitool-0.4.7-i486-1goa The behaviour doesn't change, same like using the echo command Thanks, Guzzi

Thanks for the hint; could you kindly send me an example for a script, that I could integrate in the script of omv to check ip in addition of drive spin? I am not good at all in scripting.... @all: I now bought a new motherboard, that properly supports wol - especially the wakeup via magicpacket. Did a testinstalltion and works fine so far, but before migrating my unraidbox I have one issue left: After the box went to S3 and waking up via magoc packet, I do not get the screen back; this means: the box is alive, I can telnet to it, but the physical monitor does not show the console anymore. Any hints how to solve this? thanks and regards, Guzzi

My German is way too rusty to follow that page...care to summarizes the key bits? Actually, it's just giving several hints and some descriptions, where known problems can be found and how to solve them. There is also a linux specific part. I think you find the same info by searching the weg on other pages too. The most important for me from the article I have already written above - tried those with my boards as good as I ca, but since I am not so erperienced in Linux, I don't know where exactely I find certain things in the unraid distribution. And e.g. changing the Realtek-driver is way too hard for me also... I hope that we will get some improvement with next kernel release. for the time now, I will order another mainboard - cause I tried WOL with my htpc and this worked fine even with unraid. Will order today the same board for my unraid server ....

I have EXACTLY the same behavior on my test box -- a K8NE running unRAID. Did some more reading and found some interesting infos: h++p://www.vdr-wiki.de/wiki/index.php/WAKE_ON_LAN Did not check this stuff yet. Further I have read, that with the latest kernel release there should be some improvements with regard to powermanagement - so with a little luck we might get improvement as soon as Tom integrates latest Kernel in the unraid distribution ... Anyhow, I am still happy for help...

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. Great Tips. I'll try the new beta first, then see if the windows tricks do any good. With the new beta, does one still have to do all tweaks to turn it on and set the card? Hi BubbaQ, I did some more Tests - funny, as you said, on exactly the same machine, it's working perfect under windows, but NOT under Linux/Unraid. Windows goes to standby (S3) and wakes up by MagicPacket. Unraid goes to standby (S3), but does NOT wake up. I used the latest beta6 for the tests. It seems there is some problems with the NIC driver for the realtek onboard chip - found somewhere on the web that there "might be issues" with WOL & r8169 and the recommendation to use r8168 driver instead - too hard for me, no idea how to do that... I used ethtool to set the NIC, works fine: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes I also tried "modprobe r8169 enable_wol=1" All didn't help - going to S3 works fine, but no wakeup via WOL. Any further hints how to troubleshoot the problem? Will try 2 other mainboards later if I find the time ...

Hi Neil, did you find a solution for your problem? Asking, because I am facing the same problem - although enabled in the BIOS and setting driver to wake on magic packet, NIC link goes down thus not being able to wake the machine .... regards, Guzzi

Hi all, unfortunately, I am not very good in programming or scripting - thus a question to you people: Is there any possibility to create some sort of script in the windows client ("keepalive") that prevents S3 sleep whenever the htpc is running but still allows the unraid box to fall to S3 if all htpcs are switched off? It sould also include the sending of the magic packet to wakre unraid box if htpc comes from S3 - via scheduler? There is something similar for the windows home server (which I do not have/use) called "lightsOut". As a result, Unraid machine would only be running, if a minimum of one htpc is running, otherwise S3. Thanks, Guzzi