nsainfreek

Members
  • Posts

    31
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

nsainfreek's Achievements

Noob

Noob (1/14)

0

Reputation

  1. If this can't be figured out, can someone show me where can I find a build that is low power and works with sleep? I looked in the build section but there wasn't anything specific. If I can't figure sleep out I won't be able to use unraid and gotta find another backup solution.
  2. On restart, my parity disk has a blue status again and my other 2 disks are green. My array status states "new parity disk installed." So I guess I have to run parity sync again.
  3. Another interesting thing, I tried refreshing the main page and it changed from expecting 875TB to expecting 3.46PB. Then I hit refresh again and it is expected 3.48PB and then 3.67PB and then 3.76PB. It keeps going up... and I think it has to do with how much time has passed. Cause I waited a while and then hit refresh and now it's expected 5.75PB. Also, I chose to shutdown the system via the web gui after this situation. The web gui is no longer accessible after I chose to shutdown (i.e. the system shutdown) but the physical system seems to still be running. Lights and fans are still running. I guess I'm going to have to do a hard shutdown.
  4. Hey Joe, thanks for the reply. I thought I saw the sleep option there on the main page from the first time I installed Unraid but I may be wrong. For that I apologize and thanks for pointing that out to me. My parity sync completed and once again the video didn't work. My parity and 2 disks show they are valid. I stopped the parity and got the same issues. I'm getting an invalid configuration. Parity is showing blue status. Disk 1 is showring red status with a note saying it is the "wrong" drive again. The serial number of the expected drive and the actual drive are the same. As I said before the actual drive is 1.5TB but the expected size is 875TB. If I only had a drive that big =). Anyway, I exported the syslog and attached it. It was too big so I zipped it. Hope that's ok. Any responses would be appreciated. syslog_20120415.txt.zip
  5. Well my thread got moved. I'm not sure how this is user customizations when I'm trying to get the server to sleep and wake correctly and that seems built into the main page of unraid.
  6. Ok, the sync should be done by tomorrow. For my hardware I running a Gigabyte G41M-ES2H v1 motherboard. Never had any sleep issues with that while running Windows 7 and XP. 3Ghz Intel Core 2 Duo. 4GB Corsair Ram 800Mhz.
  7. Can I do that now or do I need to wait until parity sync is complete? I'll list hardware when I get home.
  8. Ok, I've started a few threads on here because I'm starting out with Unraid and am having issues. I try the search feature but I'm not getting answers. Have also read through the FAQ, Manuals and the Best of Forum thread. Please let me know if I need to do a better job finding stuff out because I don't want to be one of those guys on the forum that just asks questions when the answers are easily searchable. Now, I'm having some weird issues with sleep. I wanted to get Unraid to sleep the server after 20 minutes of the drives having spun down. I'm new to linux so I wasn't familiar with scripting but the Simple Features add-on had sleep functionality. I installed that but the server still wouldn't sleep after the scheduled time delay. So while trying to figure that out I just chose to sleep the server from the main Unraid Gui page. The server went to sleep fine but weird things started to happen when I sent a WOL packet to wake it up. The Web Gui still worked but the monitor that is directly attached to the server does not get a signal. It just stays blacked out. Didn't know what was going on so I thought I'd try to stop and start the array again. On the main page all drives were showing green. When I stopped the array the parity drive went to blue and my Disk1 went to red. Disk1 was showing an error that the wrong drive was in that slot even though the serial number of the drive in that slot and the missing drive were exactly the same. However, the capacity of the expected drive was different from the capacity of the actual drive. First time this happened it was looking for a drive that was 1.5PB (assuming this means petabytes). The second time it happened it was looking for an 805GB drive. The actual drive is 1.5TB. I didn't know what to do and since I had access to the webgui, I just chose to restart the server. On restart, my two disk drives showed green but my parity drive showed a blue status. It stated that new parity drive is installed. I just went through 15 hours of a parity check that showed no errors so I know there should be parity data on that drive. Well, I started the array and it is doing another parity check. That's 3 parity checks in 4 days. I'm not sure what's going on but getting pretty tired and fed up with Unraid. I thought it'd be easy to switch over even without linux knowledge but I'm just running into so many problems and reading through hundred pages of threads just to find one small piece of info isn't doing it for me. I attached my current syslog. Not sure if it's any help since I rebooted when I couldn't see the screen on the connected monitor. Any help would be appreciated. Thanks. Also, I tried stopping the parity sync and the parity drive went to yellow. Pretty much said my drives were unprotected. syslog_20120414.txt
  9. If you had a UPS hooked up to the Unraid Server and the power went out you would pretty much need the powerdown add-on installed to shut the server down, right? Otherwise, you would need power available to the router/switch and another PC in order for you to shutdown via web Gui. I guess I better go read up on how to install the powerdown add-on. Thanks for the advice.
  10. I have unmenu installed. Although there's so much stuff about it I'm not sure what to do with it. Managed to get SNAP kind of working. So I need to add a script to get it to shutdown from command line but GUI is always ok? So what happens in the event of a power outage? If parity errors out and has to be re-synced on a power outage that would be really bad because that would be a situation where a drive may likely fail also.
  11. So if I shut down by any other means besides using the webgui and the main console, will this forced parity sync happen?
  12. Not sure what the powerdown script is but I do use the webgui to restart. I'm doing the parity sync right now so in about twelve hours I'm going to shutdown and try it again. Hoping there were just minor glitches from before. So on reboot, the parity drive should still be green right? Thanks for helping and assisting in my issues. I really appreciate it!
  13. Hi, I'm new to Unraid and still testing it out. I have rebooted my 3 drive test array about 3 times now and everytime I reboot my two disk drives are marked with a green circle and my parity drive is marked with blue. My understanding is that blue means the drive is new to the array. When I start the array the system starts doing a parity sync and it says the array won't be valid unless I let the parity sync run it's course. My sync takes about 12-15 hours. Is this supposed to happen? Will I have to parity sync after every reboot? I also tried putting the server to sleep and when I woke it back the system seemed to be completely haywire. It said I had the wrong drive in disk1 slot. The seriel number of the expected drive and the actual drive were the same but the system said the size of the drive should have been 1.5PB rather than 1.5TB. I couldn't figure what to do so I restarted and it started on the parity sync again. Any insight would be helpful. Not sure what's going on. I'm about ready to buy a pro license but need to make sure things are running properly first. Thanks
  14. I set the timer to five minutes and the server is still not going to sleep. On the main page all the drives are shown as spun down (blinking green). Any other ideas?
  15. I have nothing that is keeping the drives spun up because nothing is accessing it. With respect to the delay, is it necessary to shorten it? 20 minutes was a good point for me, in fact I was thinking about setting it at 30. Anything less and the server might go to sleep while I'm trying to do something else.