Guzzi

Members
  • Posts

    219
  • Joined

  • Last visited

Everything posted by Guzzi

  1. The powersupply is good for 21 drives - IF (!) you're using green drives (tested myself and can confirm by own experience). I had older drives in another box, requiring twice the current and a combination with bad connections on the splitterplugs gave me bad errors with that combination.
  2. Also we shouldn't forget we're evaluating beta versions - and Tom needs feedback if this features works or not; so at least for the beta it is "mandatory" to have it enabled by default. I am personally not yet sure, if I will use it in the future, will need some more tests. Currently I am dealing with stuttering of mediaportal TV-server via RTSP - while movies from UNraid are fine ;-)
  3. 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?
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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!
  9. Probably not, but that is a good question. in theory, when using FIS-based switching, you should not be affected; not sure, if command based switching includes those requests. Edit: I did a quick test and also had a short freeze on a running HD-stream. Using Sil3132 and Sil3726 PM chips. Yeah probably command based switching will have that problem. Do you know if 3132 is cmd-based or FIS-based? 3132 chipset supports FIS based switching. Those Jmicron chips found on many MoBos support command based switching. Intels latest ICHs also support commandbased switching, but at least in the win drivers usually deactivated due to unresolved bugs afaik. The combination of Sil3132 with 3726 supports FIS-based switching and is a combination that works best when using PMs, although it seems there is also freezes reported.
  10. Probably not, but that is a good question. in theory, when using FIS-based switching, you should not be affected; not sure, if command based switching includes those requests. Edit: I did a quick test and also had a short freeze on a running HD-stream. Using Sil3132 and Sil3726 PM chips.
  11. 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
  12. 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
  13. 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)
  14. I get following response on that command on my sata drives: /dev/sdh: IO_support = 1 (32-bit) HDIO_GET_UNMASKINTR failed: Inappropriate ioctl for device HDIO_GET_DMA failed: Inappropriate ioctl for device HDIO_GET_KEEPSETTINGS failed: Inappropriate ioctl for device readonly = 0 (off) readahead = 256 (on) geometry = 56065/255/63, sectors = 1953525168, start = 0 Does this mean, ioctrl is not properly working on those drives or is this a gap in the command? BTW - there were postings, that with the newer linux kernels the global lock situations should have been improved to avoid just such a behaviour, do we have those improvements already in the UR-kernel?
  15. I have made trials with JMB chipsets in the past - and was NOT happy with it. I finally switched to SIL3132 PCIe adapters - they work flawless for me and fully support portmultipliers (giving 10 ports per PCIe slot) plus smart, spindown and FIS based switching (vs. command based switching with older JMB chipset - not good for raid-5 or Unraid-paritycheck). Although stated, I never got PMs properly up and running with intel ICH chipsets. So Sil-3132 with Sil-3726 PMs is the only combination so far I know to work without flaws. I would be interested if anybody gets those 3726 based PMs properly running with onboard chipsets - fully supported...
  16. To my experience those rates only apply when 2008r2 writes to the RAM cache - I never got those rates continously (with standard HW). If talking about parityprotected arrays, take into consideration differences between raid levels used. Back to topic: I also confirm boost of transfer speed by almost 100% plus working datadrive #19 - very nice and thank you.
  17. 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...
  18. Thank you, I know what the problem is. ok, so is it a general problem or specific to that box? Asking 'cause I have prepared/precleared drive 19, but now hesitating to add it after reading about the probs - with last bug (16+drives) it broke my array and config files ... So some additional info would be appreciated... May we also get an update on AD-integration plans, that is part of this betas? I couldn't get it properly up and running, so I reverted to userlevel security, manually creating all accounts I needed. If you need further testing, let me know, 'cause this can easily be done on my testsystem (that is unfortunately not equipped with 20 drives for the above data-19-drive-test...)
  19. 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?
  20. 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.
  21. Currently unraid ships with four i/o schedulers to chose from: noop, anticipatory, deadline, and cfq. If there were any specific unraid-only reason to only use the noop scheduler, then Limetech would have compiled the kernel with noop only. So you shouldn't worry about that at all. Purko As quoted in the other thread, I am highly interested in solving this "freezing" issue with those parameters; So: Tom, can you please drop a short note/comment from unraid point of view? Thanks!
  22. You folks with S3 suspend issues, and some chipset/driver problems will DEFINITELY like this.... all 4 of my bench systems suspend/resume with unRAID using this kernel. That's good to hear :-) - I was waiting and hoping for those improvements, cause I have read about powermanagement fixes in newer kernels - but since it took long I already exchanged my 2 systems to new hardware properly supporting S3 with beta 6 already :-( ... Is there also improvement in the realtek NIC driver? Can't remember, which kernel should improve this.
  23. Same here - after S3 wakeup no video. Asus board with onboard 690 chipset (IGP)
  24. I'll try, but welcome input from others. Here are the issues as far as I can tell, and you can decide for yourself whether they apply to you. This is of course completely unofficial and subjective, relying too much on my memory. You should also mention the 16+ disk problem - beta intrroduced the usage of 20 drives, but I do not know of any user being able to use it without breaking the whole set - exceeding 16 drives (incl. parity) throws exceptions. btw - lt - welcome back ;-)