elcapitan

and get the Mac or PC instructions. This is exactly what I did a few days ago when I had the same issue. Everything booted up perfectly and my settings were intact once I moved my backup of my configs back onto the flash drive.

I'm trying to sync files from one directory on my cache drive to another directory on my cache drive. The code I'm using in the go script is echo "0 * * * * rsync -a /mnt/cache/apps/downloads/transmission/ /mnt/cache/apps/downloads/complete/tv" >> /var/spool/cron/crontabs/root but it doesn't seem to work. From my understanding, this should run at the top of every hour. A short while ago I rebooted the tower 15 minutes before the top of the hour just to make sure the script loaded and nothing happened when the time came. When I try rsync -a /mnt/cache/apps/downloads/transmission/ /mnt/cache/apps/downloads/complete/tv through telnet, it works as expected but I just can't figure out how to make it work in the go script. Here is my entire go script, there's no much in there though. #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & echo "0 * * * * rsync -a /mnt/cache/apps/downloads/transmission/ /mnt/cache/apps/downloads/complete/tv" >> /var/spool/cron/crontabs/root Also, if I want to run this every five minutes, would this be the code? (I started testing with this code just so I could see if it would run without having to wait a whole hour) #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & echo "*/5 * * * * rsync -a /mnt/cache/apps/downloads/transmission/ /mnt/cache/apps/downloads/complete/tv" >> /var/spool/cron/crontabs/root

Joe L, thanks so much for replying. It looks like it is the Supermicro AOC-SASLP-MV8 controller card that is causing the wake problem. I found this thread which confirmed the issues: http://lime-technology.com/forum/index.php?topic=9213.0 Leaving it on won't be much of a problem, that is, until I get quieter fans. The stock norco fans sure are loud.... Thanks again and as promised, here's a picture of a kitty!

I migrated my server to a Norco 4220 case yesterday. As I was doing the move, I added a Supermicro AOC-SASLP-MV8 Controller card and hooked up my 6 hard drives to it. I also upgraded the RAM to 2GB from 1 GB. The server booted up fine and I made sure to run a parity check as well. When I went to test sleep, I was able to put it to sleep through the UI but I'm not able to wake it up. When I try to wake it up, with the power button on the case, the fans spin up but I'm never able to access the web gui. I've tried to telnet into it but it just times out. The only way to get the server running again is to hold the power button down and do a shutdown. Once it restart, everything is fine. At the time I was running RC11 so I decided to upgrade to the current version and see the problem would resolve itself but it did not. So this is where I am at the moment. Prior to moving to the Norco case, sleep and waking from sleep was working fine. I just don't understand how changing the case would cause an issue. The only difference is the new RAM (I've run memtest86 and it passed) and the controller card. Any ideas? P.S. I attached my syslog prior to me putting it to sleep. Once it goes to sleep, I'm unable to access the log so I don't know if there are any errors happening. Thanks P.S. 2 - As I reward, I will gift a cat picture in this thread if a solution is found :-) log.txt

I moved about a month ago too so I'm sure that did not help. Anyway, all is green again

This seems to have fixed it. Something must of come loose since I haven't really touched the server. Anyway, I pressed in all the SATA connections, turned it back on and everything is green again! Thanks dgaschk!

I've been running my unraid server without any issues for a few years now. About 3 months ago, I upgraded to 5.0rc and have been running fine as well. I'm currently on 5.0rc11 and been on it for about 2 months. Last night, I was trying to access my server to copy some files on it and received an error and it was going into read-only. I don't really recall the error since I assumed it was a fluke and I just needed to reconnect to it. Boy was I wrong! I went to the web dashboard to stop the server and start it again hoping that would fix it but when I stopped it, one of my drives went missing. Clicking on the drop down menu showed no available disks so I assumed the disk had gone bad and just needed to be replaced. Luckily, I had a spare sitting around and decided I would just shut it down and install the new drive the following day. The next day, I boot it up just to make sure the drive was still missing but now though two disks are missing!!! So here I am now, freaking out, because I know two disks missing is very bad. I've attached my syslog and hope something can be figured out. If there is something else that is needed, please let me know. syslog.zip