Walter S

My log file shows "Dec 13 12:24:52 Server crond[1661]: time disparity of 722 minutes detected". I'm wondering if this is something I should be concerned with. My time & date is set to auto update. Could this be the difference between the bios date/time and unraid before it auto corrects?

I have a question with the S3 Sleep plugin. The issue I have is when I set it to “Wait for array inactivity” “Yes, exclude cache” It still refuses to go to the sleep mode. I noticed, on the main page with all drives spun down a Temp for one or more of the drives stays and doesn’t turn to *. Could this be why the system thinks it still up and not inactive? Preventing it from going to sleep. Any thoughts would be helpful.

This ability would be useful for many users. Settings/Schedules already has a Parity Check section, we just need the ability to wake the system if needed, preform a parity check and when finished go into S3 sleep if no activity.

No that's not the case, all the HTPC are shutdown and none are set to automatically update its library. I've rechecked everything including the bios, and no the bios RTC settings are all off. This is pretty strange..

Geez, I hear you, but my system has in the past woke-up at 0030 hours on the first day of the month and started a parity check. (?) I would find it running hours later. its always been set to sleep in 30 min. with no activity. All on its own.. How the hell could this be then? The beginning of each month I would look for this to complete. I not imagining it. Over the last X months I've noticed it not happening anymore. Now i'm really stumped.

I seem to be having a problem with the Scheduler app in settings. I adjust the appropriate settings in scheduler to wake the system and preform a Parity Check once per month on the 2nd day at 00:30 hours. Later in the morning when I wake I've noticed the system is still in sleep mode.(?) This has worked in the past and I have not changed anything in the bios. WOL works from HTPC’s on the same lan. This should be a simple task but no-go? I just did a test to see if a parity check would start on its own from wake state and it did. So it seems to be a wake-up issue here from a "sleep state". Any suggestions would be appreciated

This is the same problem I'm having. I've tried MS Edge (browser) with the same results..

I have a Tripp-lite UPS connected to my desktop computer and my Unraid server along with my cable modem. My question is, I keep my Unraid server in sleep mode most of the time. I have experienced several power outages lately and I have noticed the Unraid server wants to do a parity check due to an unclean shutdown. Just to be clear my Tripp-Lite is connected to the server via USB and all should be good. I'm thinking the UPS doesn't talk to the Unraid server (to safely shut-down) when its sleeping. Is this correct? anybody's input would be appreciated.

This App looks useful, Would you please add turn on /off services such as Unraid docker apps. I use Plex in my docker but I don't always leave it on (It prevents some drives from sleeping). It would be useful to be able to turn theses apps on or off.

I rebuilt my Server. What a great case. Antec11-129-100June7June2816mw55.pdf

ahh leme look..Duh. =You learn something new every day. sorry for wasting your time..

Just noticed the RC-1 is released. Updated v6.0beta15. I've just noticed my system upon start up the Array is in the Off (?) position and I have to press the "Start Array button" to bring everything to normal. I can't understand why this is. My configuration is valid, parity is valid. Powerdown Package (2.14) updated. my Go file has the following at the end echo "/sbin/powerdown" | at 01:00 This has worked in the past. I'll include a copy of the syslog before I bring the array on line.. any suggestions would be helpful also I have no scripts in my flash\config\plugins\powerdown\rc.unRAID.d folder so there's nothing to adjust there. syslog.zip

For what its worth I'm using a WD Enterprise 3TB for parity. I think there supposed to be as bullet proof as you can get for a server.. its been good for me..

I found it, You need to download the Powerdown plugin package. The next thing is put the below line in the "go file". echo "/sbin/powerdown" | at 02:00 I found the plugin file here=https://github.com/dlandon/unraid-snap/raw/master/powerdown-x86_64.plg Thanks dlandon

I'm using V6beta15 I installed the Powerdown package v6 on the plugin tab all went fine. The question I have now is can I put a line in my Go file ie: "powerdown | at 02:00" ? this works on my Version 5 system with unmenu just testing v6b15 to see if I want to jump to it now.

Trurl could you write a and example to try, and where I should put it. thanks

Gee, I have been reading about plugins/templeats/dockers all day looking for anything where I might be able to properly "Power Down" my system at a certain time like for example 02:00am. I would like to move to version 6 (which has a lot of great additions) but I like having my system automatically power-down at 2:00am. Please somebody point me in the right directions that a advanced novice can understand.. thanks

I have ver. 6.0beta15 working. Is there a shutdown script to automatically and safely powerdown the system at say 02:00 am. attached is a copy of my "Go" file that worked under v5.0 (when I had UnMenu running) thanks go.zip

Well, parity check with corrections has completed. I safely shut system down. backed up (copied) usb key (V5.0). copied all config, shares files to the spare usb we'll call it V6.0b15, except of course the usb key license file. Restarted my system and everything is perfect now. Now, to get familiar with the new GUI Thanks all for the tips..

I'm Sorry for the confusion, what I mean is a correcting parity check. I looked at the super.dat file from the v6.0 usb key and it is from early 2014, and the super.dat file on my v5.0 usb key has a date from yesterday 5/5/2015, could this be where the disk1 confusion comes from? \I’m doing a correcting parity check now, when that’s done I’ll reformat my spare usb key put v6.0beta15 on it and make sure I have only up-to date files on it. I’ll also look at the memory allocation in the bios. I’m sure the system has 4 GB of memory. Thanks for the tips.

Here’s an idea, I routinely don’t over-write my parity drive, I just check it for errors, if there are no errors I just let it go. I’m not sure this is the right way to do things in UnRaid. (?) I have been thinking about this issue all day. And this could be the problem. My parity drive (data) is the one I used when I replaced this latest drive “disk1”. What I’ll try is first do a complete parity rewrite. Than redo my spare usb key with a new formatted usb with UnRaid 6 beta15. Any thoughts from you folks?

Oww, that's above my head. I just went back to my original usb key (v5.03). and all is fine now with all drives and data. SNAP plug-in = i don't know what that is at this point.

No, I thought of that. I properly shut down my system, backed-up the usb key, re-created (reformatted) my spare usb key with UnRaid 6.0. copied over the necessary folders/files (License key) to the proper location and restarted. I did this procedure twice, thinking I mussed something. but no same thing happened. version 6beta doesn't recognize the "disk1", which is formatted and contains data, strange,. I put back my main usb key (ver 5.0) and restarted the system. All is fine now, all drives and data are present. Maybe I should't tempt fate and stop screwing around, you know if it ain't broke don't fix it kind of thing. I thought it might be helpful for others.

I have a second spare usb key and thought i would try Unraid 6.0 beta15. I backed up the usb key, reformated it as per instructions listed in Upgrading_to_UnRAID_v6. copied the key file over and all the other steps. Shut down my system copied the shares, config folders from the main usb key. All loaded fine, all shares are there, license key was read ok. the only problem is one data disk "disk1" fails to load. I replaced this disk last month with a WD Red 3TB, at this point it see's the original disk (which I replaced). UnRaid 6.0 console suggests (wants to) Rebuild data and than bring array on line. When I switch back to the main usb key (Unraid v5.) its all fine all drives are present. Anybody see this kind of problem thanks Syslog is attached syslog.txt

I'm relatively new at this so bear with me. I have 3 2TB WD green drives (1 3TB Enterprise class Parity Drive). In the Unmenu tab Main it says one of the HDD is at 76%. Can anybody tell me when this HDD has reached its limit as in full? Will unRaid report a full drive, than wright to the others? I have 3 2TB drives dedicated to movies, one is at 76%, 71% and the last one is at 51% I know I have room and will be switching to 3TB WD Reds when needed.