ClunkClunk

WeeboTech, thanks for the advice. Did a short test, no major differences. Doing a long test now.

Are you me? Because it sounds like we both have the same exact issue: http://lime-technology.com/forum/index.php?topic=26265.0 Ironically enough, I was also going from 2TB parity to 3TB.

One more thing that might be helpful is that I backed up my super.dat about a week ago. I tried swapping that in, and it found my original 2TB as parity and gave it a green ball, though it gave a red ball on a completely different 500GB disk of mine. I'm hesitant to start the array like this, as I have no idea if it's safe, considering the 2TB parity drive was valid before the 3TB parity was started, so any changes to the array at that point wouldn't be on the 2TB (though to be honest, I don't understand all the finer points of the parity rebuild process).

unRAID 5rc10, since I realized i didn't mention it.

I was upgrading my parity drive today from 2TB to 3TB and encountered a red ball on a completely different drive while it was going. Here's what I did: • Shut down the server • Removed a 640GB that was in the unRAID in my case, put it in an eSATA enclosure • Installed the 3TB (left my original 2TB parity still installed) • Also added a 60GB SSD that I'll later use as cache • Booted back up • Saw unRAID found all the drives I was expecting and started normally (remember I left the 2TB original parity still installed) • I think I restarted but set the array to not auto-start • Assigned the new 3TB as parity • Started the parity rebuild on to the new parity drive About an hour and a half later, my wife mentioned that some of the video shares weren't working, and I saw that Disk 5 was reporting a red ball. Checked the syslog. It was huge - nearly all of it was filled with entries similar to this: Feb 28 17:32:54 Tower kernel: md: disk5 read error Feb 28 17:32:54 Tower kernel: handle_stripe read error: 121995568/5, count: 1 Feb 28 17:32:54 Tower kernel: md: disk6 read error Feb 28 17:32:54 Tower kernel: handle_stripe read error: 121995568/6, count: 1 Attempted to use the clean powerdown, ended up using that, some kill commands and eventually a hard shut off. I double checked and reseated all cabling/connections to Disk 5 and the motherboard SATA port it's on. I'm a bit at a loss of what to do at this point. I still have the 2TB parity, as the 3TB parity didn't complete, but with Disk 5 redballing, I'm not sure how to proceed. Thanks for any advice and help! I've linked to syslogs, since the one is decently large. The small one is the syslog from right before the issue in case that's helpful. https://www.dropbox.com/s/0c50a0jhs7f1dag/syslog-20130228-163140.txt.zip https://www.dropbox.com/s/sae98vllcwvr684/syslog-20130228-175311.txt.zip

I haven't gotten around to doing anything with HandBrake and unRAID 5.0 (my unRAID server went from having one of the fastest CPUs in the house, to one of the slowest over the last few years, so it's not been a priority for me), but I think the install instructions will work to at least install 0.9.6, though it won't be a plugin.

The Sempron line was around for a very long time -- what specific model? SABnzbd will run on just about anything. The only heavy duty requirements are when it needs to rebuild a corrupt/partial file. On a slower machine, it just takes more time.

Enjoy it! My parents are there right now as well, having a blast.

I'm a huge fan of dual band routers with TomatoUSB. I have a Belkin N300 with it, and it's been solid, as was my previous G-only Buffalo WHR54G.

Anyone done a warranty check with a drive outside of its shell and see what Seagate's site reports?

I took a quick glance at it, but the Slackware 12 virtual machine I used to build 0.9.5 wouldn't successfully build 0.9.6 or the snapshots. I have a pretty new baby in the house, so I haven't had much time to dig at it. What did you end up doing, aiden? Did you get it compiled on unRAID 5.0? A Slackware install?

I'm interested, aht! Let's see it.

Attached are two unMENU .conf files for HandBrake. handbrake-unmenu-package.conf is for installing 0.9.5, the most recent release version of HandBrake (same as what was posted a few months back). handbrake-svn-unmenu-package.conf is for installing the most recent SVN build of HandBrake, 3853 (I haven't tested this one, so please give me feedback). If you're not using unMENU, and still want to use HandBrake, here are the URLs for HandBrake for unRAID: http://www.clunkclunk.com/HandBrakeCLI-0.9.5-unraid.tgz http://www.clunkclunk.com/HandBrakeCLI-svn3853-unraid.tgz handbrake-unmenu-package.conf handbrake-svn-unmenu-package.conf

kapperz, I haven't updated it beyond 0.9.5, and that's what the current unmenu .conf is referencing. Since the handbrake unmenu .conf isn't distributed as part of Joe L.'s unmenu, there's no current way to autoupdate. However, if there's a desire for me to compile a newer snapshot, or a newer final version comes out, post in this thread, and I can compile and update the .conf file.

I haven't checked with Joe L. to see if he wants to include it in unMENU, but I don't see why he wouldn't want to.

Joe L., Once again, thanks for your guidance. Attached is an updated unmenu package. handbrake-unmenu-package.conf

I made an unMENU package, and it appears to work, however I can't get the version checking to complete successfully. I'm not sure exactly what's wrong. Perhaps someone can take a look at it and see where I made a mistake. To use it, have unMENU installed, and drop this conf file in to /boot/packages, then use the unMENU package manager to install. (removed the attachment - use the one two posts after this one)

Here's HandBrake 0.9.5: http://www.clunkclunk.com/HandBrakeCLI-0.9.5-unraid.tgz

I just happened to have the same Simpsons DVD already ripped, so I did some experiments, and found a set of settings that works very nicely and targets the 200MB size you wanted (I was within 10MB on about four different episodes): -f mp4 -X 720 --loose-anamorphic --detelecine --decomb -e x264 -S 180 -2 -T -a 1 -E faac -6 dpl2 -R auto -B 128 -D 1.5 -m -x cabac=0:ref=2:me=umh:bframes=0:weightp=0:8x8dct=0:trellis=0:subme=6 -v 1

tola, this isn't really the best place for support with HandBrake (you should probably post on the HandBrake forums), but I think what's happening is two things: • the --size parameter is only the video size, not inclusive of audio. Setting it to 200 means the video will take up 200mb, but audio streams are based on their own settings. • you're including ac3 audio and aac audio, which is resulting in probably ~100mb of audio data, pushing your filesize to that 300 mark. I'd try setting the --size parameter to about 175, then getting rid of the ac3 stream, and maybe even dropping the bitrate of the aac stream to 128kbit.

Here's SVN 3635: http://www.clunkclunk.com/HandBrakeCLI-svn3635-unraid.tgz I haven't tested it much, but it's built using the same methods as previous ones, so it should be okay. Please let me know if there's any issues.

olympia, working on that right now. Should be done in a little bit. Just a few notes to myself so next time I don't have to re-research this again: To configure, then compile HandBrake in CLI only (no more GUI errors): ./configure --launch --disable-gtk

Try the Universal preset, just to make sure it's not the default preset that's causing problems: HandBrakeCLI -Z Universal -i 01.iso -o 01.mp4

Ah, yes, I could see how multiple audio tracks could be difficult to deal with.

I don't normally use mkv, but I think you can generally always use AC3 passthrough to achieve what you want. How about something like this: HandBrakeCLI -t 1 -f mkv -e x264 -q 20 -a 1 -E ac3 -6 auto -R auto -B auto -m -i SOME_DVD -o Some_DVD.mkv Seems to pass the AC3 through without any re-encodes at all.