RoninTech

Just an update for people form the future. I re-arranged my drives so that the 2 new 3TB drives were on the MB (6 ports) rather than the SASLP card (8 ports), along with parity and my only non-full drive. I keep > 20GB free on all my drives. Re-booted and re-assigned disks based on original device list screenshot, and array came up fine. Ran the ReiserFS tests on all the drives and only 1 of the 9 needed a fix and it fixed no problem (no lost+found). Finally re-ran preclear on both 3TB drives with 1.13 version of script and unraid 4.7 and they both finished with no issues. Looks like my SASLP might have some issues on 4.7 when stressed. And all just in time to switch to 5.0 if this rc9 (edit: make that rc9a, lol!) looks ok! Thanks

P.S. It looks like the preclear did quite a bit before failing. Does it only access > 2.2TB after step10?

Yeah, I figured the SASLP being so popular would be OK. What about my idea of re-arranging the drives so the 3TB one's are on the MB? Is that doable or is preclearing 3TB drives on 4.7 just plain risky? Thanks!

I thought I'd seen this somewhere on here: yes. Just make sure you use the latest version of the preclear script (1.13 is the newest at this time) Joe L. This is exactly what I'd like to do.

Thanks Joe. For some reason I was under the impression that the preclear script could be used on 3TB drives in 4.7 but you couldn't add them to the array, until upgrading to 5.

The web OI eventually responded although all the SAS drives show as 0 deg C temp. Sure enough I can samba the non-SAS drive files. So it looks like I had a fatal SAS error during the pre-clear. Can I move existing full drives onto the SAS card and do the pre-clears via motherboard SATA ports in the hopes that will have a better chance of working and all SAS errors will go away with 5.0?

Hi All, I've been running 4.7 for a long time. In anticipation of migrating to latest 5.0 rc release (plus forum samba fix) I picked up a couple of WD 3TB drives. I did a /boot/preclear_disk.sh -A sdc under screen for the first 3TB drive. They are both hanging off my AOC-SASLP-MV8 (latest .21 FW). All seemed to be going well until the preclear script stalled at this stage (it hasn't moved in a couple of hours): ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 90% complete. ( 2,702,827,008,000 of 3,000,592,982,016 bytes read ) 75.3 MB/s Disk Temperature: 26C, Elapsed Time: 30:03:35 I can still access the machine via telnet, but Web OI is non-responsive and trying to read any files on the raid drives via samba usually fails. Some files failed half an hour ago but now are readable?? No zombies and nothing unusual under top other than most of the 4GB RAM is used and nothing related to the pre-clear is hogging anything as I'd expect (with a working system). Bootup after successful parity check: http://pastebin.ca/2299213 First error shortly after preclear had started: http://pastebin.ca/2299215 SAS error spewage every 10s a few hours later: http://pastebin.ca/2299216 Throw in some reiserfs unhappiness for good measure: http://pastebin.ca/2299218 I can still telnet into the machine. The web interface is inaccessible. What should I do? Other than "Don't Panic" 1) Kill the pre-clear that was "nearly" finished? 2) Do a reiserfs check? 3) If 2 is ok, try pre-clearing again? If I try another pre-clear I'll not use the box for anything other than running screen while it does it's thing. I did some reading and writing during the pre-clear this time. Since it wasn't to the drive being cleared I figured it'd be OK, just maybe slower than usual. Thanks for any help! P.S. Full 25MB syslog is attached as a .7z file to squeak under the forum max size. Renamed to .zip in case .7z was disallowed. syslog.zip

Nevermind, found one. r8168.zip

Cool! Now I just need the AOC-SASLP-MV8 issues sorted and I can try 5. In the meantime, anyone know if there's a 8168 driver available for 4.7?

Any chance you could make this available? Here's what 4.7 says I have and I get regular kernel panics that require a reboot:

Doh! I was starting to get excited after the beta's appeared to work with this r8169 driver (which cause my 4.7 box to occasionally kernel panic under heavy network load) and also support my AOC-SASLP-MV8. Am I reading the various threads correctly in that now neither of these are supported (i.e. working without issues) in the current RC?

Don't you just love this forum! Thanks adammerkley. Donovan, You might want to mock up where you sit the template in the tray with a drive before drilling to make sure that the stock Antec 1200 fans will fit.

Sorry mate I've looked and looked but can't find it.

If you do a search you'll see how I fit 5 drives in each bay for peanuts. The great airflow hasn't let my WD Green drives exhibit any serious issues. Knock on wood.... :-)

Greta deal for a fantastic unraid case!

I had a drive (WDC_WD20EADS) drop out with the red ball. SMART queries reported that this drive and the parity drive didn't support SMART. The parity drive also showed millions of errors. I shutdown the array, rebooted and now the drives show up as being SMART friendly and no errors on the parity drive. A few short SMART tests on the drive in question all passed although the raw_read_error_rate and calibration_retry_count look mildly suspicious: I also noticed this in the syslog after reboot: Running "reiserfsck --check /dev/md1" resulted in it telling me to run it again with "--rebuild-tree". I'm about half way through that (estimated 10 hours to finish). When that is done, how do I put the drive back in the array (assuming its still useable)? Do I just make it trusted? The make trusted FAQ page mentions only to do it if no writes have been done and I'm not sure what --rebuild-tree" does with respect to this. Thanks! EDIT: Syslog from after reboot attached, previous syslog was full of these repeated every 10s: syslog-2011-10-01_1.txt

I couldn't access my NFS shares until I went into the unraid shares screen and hit apply on each of them before doing a sudo mount -a on the clients.

Just upgraded to this MB after my last one was taken out by a power failure surge. It has 6 x 6 Gbps SATA ports on board and 2 PCIe x16/4 (x16 graphics, x4 everything else). Had a problem with slow parity check until I noticed BIOS wasn't using AHCI. Set drives to AHCI and now parity check speeds are back to normal. See my related post here for system details.

Just a note that the card is performing very well in the video card slot of my Asus MB. I switched the drives around so the full ones (so mostly just reading) are hanging off this card and the emptier ones (need more writing to) are off the 6 ports on the MB.

The cable above is for going directly to 4 SATA drives. So you'd need 2 of the other type to go to your Norco case's connectors.

For $102 US: http://www.provantage.com/supermicro-aoc-saslp-mv8~7SUP918N.htm They also have the forward breakout cables for card to drive setups for $16 US: http://www.provantage.com/3ware-cbl-sff8087ocf-05m~73WAR02N.htm Can't wait for them to show up

The nerve of me!

Damn, out of stock and price is up to $111.

Hi Terrastrife, How do you tell its a forward cable? I don't see it mentioned anywhere in the ebay item.

I'll be connecting directly from the card to the drives with nothing in between. From reading other threads/posts I'd need a forward breakout cable to do that. Not sure if you need forward or reverse for your scenario but I'm sure one of the experts will pipe up.