wheel

Raj, I was about to start my new build when I saw this thread RE: AOC-SASLP-MV8 performance on 5.0rc4 (and based on limetech comments, 5.0final) - http://lime-technology.com/forum/index.php?topic=20633.15 If I can't track down the IBM and want to maintain peak speeds, do you recommend a "third option"? Thanks in advance!

Raj, thank you again for all of your hard work - I couldn't have built my first box without your help! Secondly, I'm still combing through threads to wrap my head around the LSI issue, but figured I might ask here for my own (and hopefully others') benefit: is your 20-drive budget tower currently 100% unRaid v5.0 RC3-compliant? I'm seriously thinking of starting the part-ordering procedure tonight and tomorrow, but would hate to realize I'd misread a post and ordered the wrong SAS card or motherboard... Thank you in advance!

Fully reconstructed. I'm reminded of the Popeye's Chicken scene from "Little Nicky"... unRAID is f*'n awesome! Thank you again, Joe.

Thank you so much for the help, Joe! As soon as I checked the smart status, my fears were confirmed: SMART overall-health self-assessment test result: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. So here is my plan, based on what I've read across multiple posts (unless someone tells me I'm doing this wrong - I'll probably hold off until tonight just in case a "STOP BEFORE YOU SCREW SOMETHING UP!" post comes through...) (1) Stop Array (2) Remove dying drive (3) Insert new drive (hot-swap cage) (4) Telnet to tower, run preclear x2 (normally x3, but I hate to leave the disabled disk status for 3 days...) (5) Start array (which automatically starts data rebuild, right?) (6) Nightmare resolved

OK, I've checked cables, running (what seems to be a neverending) "short" SMART test via unmenu, and I'm about ready to run by Best Buy and overpay for a replacement... Can anyone advise any other "last ditch steps" before I start preclearing the new drive? Should I stop the array, remove "bad" disk 9, put "new" disk 9 in its place, preclear it a couple of times, then restart the array so it automatically rebuilds - or is there a different set of steps I should take? Thanks for your patience and help!

4.7, Rajahal's 20-drive beast tower build (incl. cache drive), and no problems for a good while now - but as of this post-outage restart, it took forever for most of my drives to mount, and one disk (#9) is now red-dotted (but still totally accessible, as the complete array is now spun up in spite of the warning)... My gut tells me it's time to replace that (barely six-month-old, 3x-precleared) drive, but I figured I'd check with the experts here before shelling out ~$130 on another 2TB just to tread water (was just about to start working towards a 5.x 3TB-grade box...) Syslog attached, and any guidance would be greatly appreciated. Thanks in advance! *Clarification - red dot next to Disk #9, orange dot next to "started" (which based on research suggests the disk has failed and needs replacement... so why can I still access it through raw //tower/disk9?)

This is either an unusual question / situation, or I'm not searching properly (unless my key concern was already addressed through a different question in Reply #165)... CAVEATS: Linux Newcomer; UnRAID 4.7 CURRENTLY: 20-Drive Tower (1 Parity, 1 Cache, 18 Data - 4x5-in-3 cages) BECOMING: 21-Drive Tower (1 Parity, 19 Data - 4x5-in-3 cages) (1 Cache 2.5" mounted internally) PACKAGES: 08/20/11 prostuff1 attachments from this thread & Sickbeard thread Let the (most likely stupid) questioning begin... Since I'm totally dropping my 3.5" cache drive from the array and replacing it with a virgin 2.5" cache drive, how (if at all) will unRAID perceive this migration? Are there any "uninstall" steps I should take to disassociate the initial SABnzbd install with //tower before I make a "clean install" on my virgin 2.5"? Do I need to remove SABnzbd's package from unMENU and start the package process from scratch? If there are no "uninstall" steps and unRAID would just automatically pick up the new SABnzbd install on the new cache drive, is there any way to associate my new cache drive's SABnzbd / Sickbeard installs with a different port than the one //tower uses right now (currently :8081 SAB / :8080 Sick)? (Background on this last question: tried to set up SAB/Sick simultaneously back in August; SAB was fine, Sick tried to associate with :8080 because I didn't think to avoid a conflict with unMenu; didn't sweat it much, just ran Sickbeard on another system - now that I'm switching out my cache drives, though, it'd be nice to harmonize both services on the same system if it's less-migrainey than I'd imagine...) Any advice is enormously appreciated - thank you in advance!