Rastarize

So can I simply run those commands in a terminal window and it will install Handbrake and all required dependencies?

Is there a plugin for Handbrake? How relevant are the install instructions contained within this thread?

No change. I'm going to try my luck at pulling the data off of the bad drive. I must say, I was hoping there was an easier way to troubleshoot that would have been recommended.

I'm starting to wonder if it's a bad motherboard...

Any thoughts? I have to return my bad drive per the RMA, but don't want to until I know for sure I have all of the data.

It doesn't show anything. Seriously, not a thing. Here's a syslog I captured of it hanging earlier. syslogtail.txt

Here's my syslog. Any advice outside of downgrading? syslog-2012-01-28.txt

I'm at about my wits end with this. I replaced a drive that was going bad with a new one. Pre-cleared the drive, all looked good. Assigned the drive, let Unraid begin the rebuild process, and the server hangs - I cannot access it from the terminal nor remotely. It doesn't ping either . This is on Beta 14. So far, here's what I've tried: - disable all plug-ins - replace all sata cables - test powersupply - ran memtest for 50 hours I've tried to capture the syslog, but it doesn't capture anything when it crashes. Previous to this, my Unraid server has been fairly stable. I will hard reset the server, capture the syslog to the flash and attach it, but does anyone have ANY ideas? Could it be that my flash drive is bad? Outside of my motherboard and processor, its about the only thing I haven't checked. Having said that, if I stop the array when the server boots up, or cancel the parity check, the server will stay on just fine. ============================================================ The issue has disappeared after replacing my motherboard. I have filed this under "bad hardware".

I was hoping someone could offer some advice. I have a drive that is failing, and I've gotten a replacement for it already. What I'm trying to do is to remove the old drive, replace it with the new in the same slot and run a preclear on that drive before adding it to the array. My server is powered down right now, so would I simply install the new drive and boot up? Would Unraid go straight into a parity check/correction, or would it boot up without starting the array? I guess if it doesn't go straight into the parity check/correction, that I could initiate the preclear from the terminal and then simply add it through the webgui, format, start the array and let it rebuild? I just wanted to be sure before I did something stupid (not uncommon for me ). Thanks for your help.

I installed this package using the conf file on the first post, but it installed 0.6.7 is it possible the incorrect conf file was posted?

No, that would be logical, and my wife didn't marry me because I'm logical! Will try that and report. That did the trick. Thanks for a slick gui!

Hmmmm, so I downloaded the conf file from the first post, put it into the appropriate unMenu folder and installed the package. Set it up to reinstall automatically, but I'm still getting the default unRAID gui? Any insight?

Upgraded and everything was running perfectly, but overnight two errors appeared: Nov 2 14:11:40 Tower kernel: sh[21343]: segfault at b6af9d53 ip b7675e1c sp bfe6c50c error 4 in libc-2.11.1.so[b7635000+15c000] (Errors) Nov 2 14:11:40 Tower kernel: mdcmd (52): spindown 0 (Routine) Nov 2 14:11:40 Tower kernel: hdparm[21344]: segfault at b7129693 ip b765be1c sp bff35950 error 4 in libc-2.11.1.so[b761b000+15c000] (Errors) Are these errors worth worrying about (I can post up the full syslog if preferred)?

Is it possible to delete the partition on a newly acquired cache drive using unRaid? I got the 250G drive from a friend, and don't own any Windows machines to be able to delete the partition. Is there an unRaid tool I can use?

I think I may have found the culprit, but unsure of how to fix it. I had kept all devices except my main computer from accessing the Server and all was good. After a few days of running without any problems, I thought I would try to watch a movie using my WDLX-TV Live (using brad's firmware upgrade). Well, that only seems to be able to read shares as NFS. So, I setup the NFS shares with *(rw) and then the crashes began again. I'm guessing something from the WDLX-TV Live is writing or "communicating" with the Server and causing these crashes. I tried to setup the shares as read only - I assumed the correct command was *®, but that didn't work, and neither did *(w). So now I'm a bit stumped; the WDLX-TV Live is my main media player and primary reason why I'm using the Unraid server, so I'm looking for any advice anyone may have. For reference, I haven't reconnected my cache drive, and am running no other add-ons.

So figure this one out, completely bare install of Unraid 4.7 that was not connected to the network at all - i.e. no patch cable connected - set the console to pre-clear the cache drive (since SMART came back clean) and it froze/crashed/hung/became totally unresponsive. This HAS to be a hardware issue right!? But WHICH hardware do I start with? I don't have extra RAM or an extra Motherboard lying around. Arrrgghhhh! >

All disks checked out fine. Ran a SMART report on them as well, and they all checked out.

I'll try your suggestion Joe. I'm wondering if the cache drive is just bad. As for hardware: Motherboard: Gigabyte MA790GPT-UD3H (HPA disabled) CPU: AMD Athlon II x4 630 (not overclocked) RAM: G Skill 2GB (don't remember model type...I've run memtest, and it's good though) PSU: Corsair HX750 Case: Norco 4020 Flash: 8GB SanDisk Cruzer Parity: 2TB WD20EADS Drive 1: 2TB WD20EADS Drive 2: 2TB WD20EARS Cache: 300GB Seagate ST332

Sorry, got impatient and went ahead with a clean format on the flash drive. Got the server up and running without any add-ons whatsoever, got my shares setup, and then ran TOP. While I had TOP running, I went through the web gui to manually move the files from my cache drive to my array, and, naturally, crashed. Here's a screenshot of the TOP when I crashed. How is it possible that the Move function can cause me to crash so badly? The files are large (avg of 4GB) but I thought the system would be able to manage. Does this mean I should get rid of the cache drive all together?

So any advice, tips, troubleshoot, or am I doomed to have to continue hard resetting this thing twice a day? EDIT - okay, so I did some searching, should I just try a completely fresh install for a while?

Would adding more RAM remedy my issues, or is there a chance I could still run out of memory?

In the interest of providing as much information as possible, here's a "Fresh Syslog" taken right after I restarted the machine this morning (I canceled parity check). Syslog_Fresh.zip

Re: Addons: UnMenu (invoked by me) Clean Powerdown (UnMenu package) SABNzbd CouchPotato Sickbeard Here's my Go Script: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & # determine if cache drive online, retry upto 7 times for i in 0 1 2 3 4 5 6 7 do if [ ! -d /mnt/cache ] then sleep 15 fi done # If Cache drive is online, start SABnzbd, Sickbeard, and CouchPotato if [ -d /mnt/cache ]; then cd /mnt/cache/.custom installpkg /boot/packages/SABnzbdDependencies-2.1-i486-unRAID.tgz python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d python /mnt/cache/.custom/sickbeard/SickBeard.py --daemon python /mnt/cache/.custom/couchpotato/CouchPotato.py -d fi cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

And yet another crash while we had a movie streaming from the server... This is getting to be quite frustrating. Last weekend I did a fresh install of Unraid on the flash drive, I ran memtest overnight, I checked all the cables (sata, network, etc.), moved off of the switch and onto the router, and still, I'm getting crashes. What gives?!

Okay, so I just had another crash, and this time the logger caught it. Looks like I ran out of memory? My machine has 2 Gb minus 128Mb for the onboard video. When this crash occurred, I had opened a telnet session to move a folder from one location on the cache drive to a second location on the cache drive - it was a video file, so it was on the larger side (if that makes a difference). I've attached the syslog in .zip format. syslog.zip