wheel

Post-rebuild syslog attached; last time, the 66,423,368 errors were directly associated with the dead disk #16, but this time, parity check results still list 66,423,368 errors (post-rebuild) with no individual disks listed as bearing the errors (unlike last time with the dead #16). Is this normal after a rebuild? syslog.zip

Sorry, wrong syslog - believe it or not, I'm juggling two towers simultaneously (one 4.7, one r8168-test), and both are giving me headaches at the moment (see General Support for the other thread). Here's the r8168-test syslog: syslog.txt

UPDATE: I left everything as-is last night (with the webgui hanging and all), slept 7 hours, and woke up this morning to find the webgui loading fine. Syslog attached.

UPDATE: Parity check performed at solid speeds (50-80mb/s), and came back with 0 errors. I decided to try preclearing a couple of drives that may have gone bad in my other tower, and performed a proper power down on the r8168-test tower. Inserted the two "dead" drives in the r-8168 tower, powered up, and unraid booted normally... until I tried accessing the webgui. Timeout. Telnet's still alive; syslog attached. syslog.txt

...and yet, parity is valid. Does anyone have any clue what could have caused that insanely large amount of errors without a syslog? Away from my system right now (sending this by mobile), but slightly freaked out; syslog coming within the hour... Edit: 4.7 box, Raj's 20-drive beast tower Edit 2: this appeared immediately following a drive rebuild - but the rebuilt drive was #14 (no errors) and the error-ridden drive was #16... Edit 3: Made it home, syslog attached and rebuilding #16 now... syslog.txt

"lsof /mnt" gives me nothing - just bumps me back to the command line, no spaces or anything... What's weird is when I go back to "fuser -mvk" after the "lsof /mnt", it still shows the "busy" process, but when I type "kill [PID]," it comes back with "No such process". EDIT: Hard rebooted, running a non-modification parity check now; if anything turns out strange, I'll let everyone know.

I'd given that a shot already, but received "drive is busy" errors, so figured hard power was my only option - is there a way to manually override whatever process is causing the "busy" message? Or are the "drive is busy" errors indicative of something even more serious? EDIT: Should probably mention I've received the errors after "fuser -mvk" & "kill PID" attempts, in case anyone was going to suggest I try those steps.

Nice. Do you think a hard power down would be a mistake right now, or is that pretty much my only option anyways?

I'd actually been running two preclears earlier in the day, but both finished (successfully) late last night... Does it look like the preclear caused the webgui hang?

Build: exact replica of Raj's Greenleaf-Technology.com's 20-drive budget tower: 2xAOC-SASLP-MV8, Realtek 8111DL Up on r8168-test for well over a week with no troubles (except the drive swap issue mentioned earlier, which may or may not be a r8168-related issue), until last night - I've been transferring files almost non-stop since the system went live, parity speeds are normal, and I hadn't hit any of the reported errors until I tried transferring another block of 500gb or so and the transfer hung ("Windows cannot access file [on r8168-machine side, not transferring side]"), at which point I closed the error windows and checked the webgui. Webgui seemed to lock, but finally refreshed after about 8 minutes. I decided to wait until morning to mess with the system, and just tried stopping the array about 30 minutes ago; webgui is still locked in a loading pattern. Unless I see a recommendation otherwise, I'm going for a hard shutdown at the 90-minute wait mark, and I'll provide a log as soon as I have everything up and running again. EDIT: Syslog attached via Telnet - that's still responsive... syslog.zip

Bizarre - I think I solved my own problem, but I'm going to leave my post up for posterity unless and until someone indicates this had nothing to do with RC5: (1) Power down, move "ghost drive" to a new slot (2) Start back up, get the "BIOS Bump" (boot order changed) (3) Rather than switching BIOS, I powered back down and moved the "ghost drive" back to its trouble slot (4) Powered back up, launched web interface... and there it is. Formatting now. I'm guessing this was just some sort of a hardware hiccup, but just in case it's something bigger - I hope this information helps the development process!

OK, I may have something: Got RC6-R8168 up and running on a virgin box (exact replica of Raj's Greenleaf-Technology.com's 20-drive budget tower: 2x AOC-SASLP-MV8, Realtek 8111DL) last Wednesday, and I've been copying files to it almost nonstop since. This morning, I finished preclear on 3 new drives. I powered down the system and moved them from their preclearing slots (I'd spread them out to test my SAS cards, but wanted them "permanently" housed on the top row). When I restarted, I realized that I'd forgotten to check serial numbers, and wanted to make sure I was loading them into "unRAID drives" using the same order that they were physically stacked in the tower, so I pulled each one out (hotswap bays), checked the serial, then plugged them back in to the exact same slots they were in during the boot process. Rather than restarting (hotswap and all), I went straight back to the web interface and tried to add one of the drives as Disk 4. The web interface accepted my selection, and promptly... did nothing (still "unassigned"). Disk 4 is still blank, but now the drive I'd tried to add as Disk 4 no longer appears in my list of available devices. So, being the impatient running-late-for-work guy that I am, I go ahead and try a full power down and start up - and that disk I'd tried to use as disk 4 is STILL missing from the list. However, the other two drives are still listed, and I just added both to the array without any trouble. Does anyone have any clue whether I'm experiencing a new 5.0 bug, or if this is the sort of thing that happens all the time? And if it's the latter, does anyone have any idea how to get that "ghost drive" to re-appear in the web interface for inclusion in the array? Thanks!

This is REALLY not my day... Discount from rebate: http://www.newegg.com/Product/Product.aspx?Item=N82E16817151087

OK, everyone - it's like a car wash, now that I've spent over a thousand dollars rounding up a few of these at local stores over the last two weeks, Fry's puts them on sale for $50 off. I'm (frustratingly enough) set (literally just started my preclears on the last drives this morning), but hopefully this helps someone else: http://www.frys.com/product/7057131?site=sr:SEARCH:MAIN_RSLT_PG

OK, PSU has been RMA'd and hit the mail (just in time for a 4th delay...) With a little luck, I'll have my replacement in time for the weekend, and I can give it a shot. Thank you for the help, everyone!

It definitely appears to be connected - I've just unplugged and reconnected to test, and I'm getting the same results... Also worth noting: I've tried the "screwdriver on motherboard pins connected to front panel" trick, and while it seems to run SLIGHTLY longer (maybe 7 seconds) using that method, it still kills itself mid-boot now... I would think that a PSU would be good or bad out of the box - has anyone ever heard of a PSU "degrading" over the first couple days of operation?

Well, this is bizarre - I checked my CPU and its fan, everything seemed fine (gel present, heatsink flush), but I re-seated it just to be safe (checked the pins, too - everything looks perfect). Unplugged and replugged the PSU connector from the motherboard for good measure. Now, the system still powers on, but it turns itself off ALMOST IMMEDIATELY after it spins everything up (talking 5 seconds or less). Also worth noting: last night, after shutting itself off, the only trick to turning it back on via front panel was a PSU power toggle off-on... Now that it's shutting itself down super-fast, that trick doesn't work. The power toggle is a 50-50 shot, with odds increased by more time between toggles. Any ideas? I'm leaning more towards PSU than CPU now, but the progression (20 hours fine, less than an hour fine, less than a minute fine) without any software elements outside of unraid on a stick and a preclear script has me completely confounded. PSU = CORSAIR Enthusiast Series TX650 V2 650W

I've had a few friends tell me of "phantom power-offs" that eventually seemed tied to CPU activity (like a preclear), saying they were most likely the result of poor seating or other damage CPU-wise (absent other signs)... is that way outside the majority? (EDIT: I just realized, I'd probably written my original post poorly - I don't have any problem turning the system on (even if it shuts itself down, as long as I toggle the PSU off, then on again) or maintaining power without real activity... my problems stem from the system completely shutting itself down after brief periods of preclearing activity (a few minutes on rc5-8168, consistently 11:15 minutes on b14) but otherwise staying up and running "idle" unraid just fine. Hope that clears my situation up a bit!)

Hardware: Raj's new 20-drive Tower Budget build (http://greenleaf-technology.com/blogs/prototypes/index.php?id=2601838967498401788) Server built on Sunday, started preclearing 4 drives (2x4TB, 2x3TB) simultaneously Sunday morning. I checked on them this morning, and everything seemed fine at 20 hours' progress. An hour later, I check the system remotely, and it's unavailable. I get home tonight, and the power is completely off. I press the power button - no response. I flip the PSU toggle off, then back on after a few minutes and try again - the system boots. I tried running a few preclears again. No dice - this time the system powers down as I'm running the fourth preclear. Restarting it on a different power outlet, I tried running two preclears. Again, system powerdown, but this time after a few minutes or so. Following this thread (http://lime-technology.com/forum/index.php?topic=21099.0), I picked up on the b14 trick, and gave it a shot. The last two tries have been with one preclear at the eleven minute mark, and both runs ran almost immediately after 11:15 in both instances before the power died. I'm leaning towards thinking this is a CPU issue in some way (planning on trying an RMA, though I was careful as could be when installing), but figured I'd post in here on the off chance that it isn't. I'll post back the impact when I get a new chip in there, but if anyone has seen or heard anything like this before, I'd definitely appreciate any guidance at all. Last syslog attached syslog7212.txt

I may be experiencing a similar problem with RC5-R8168 (hard to tell remotely - left my house an hour ago with four preclear screens running at the 20-hour mark, everything seemed fine, but just checked and Telnet was killed / unable to reconnect...) Full details as soon as I'm home and can reboot the system, but stats preview for the next few hours: brand new box, see Raj's most recent 20-drive budget tower build, but only one SASLP-MV8 card right now (just in case I need to scrap the SAS and pick up some LSI cards instead...)

Thanks for the heads up - I'll be starting on Tower #2 in about 24 hours, and immediately preclearing my new 3TBs for at least two cycles. Not sure how Amazon will treat me on RMA's, but Newegg shouldn't be too bad... What's frustrating is that I'd fully intended to start Tower #2 as an all-4TB monster, but the dearth of 4TB drives on the market killed that idea pretty quickly. Plus, at current rates, a single drive failure could seriously impact my savings account. $150 a pop isn't fun, but it's doable, so I'll be snatching up any 3TB by any manufacturer at that price for awhile now... Crazily enough, it seems like the only "green"-ish 3TBs out there are this one and the WD (which I've also heard complaints about), so there may just be a bunch of preclearing and failures in my immediate future. Really wishing I'd have started down my 4TB path back before the floods...

Looks like Newegg is matching with a promo: $20 off (of $169.99) w/ promo code EMCNDHJ33, ends 6/27

http://www.amazon.com/Seagate-Barracuda-3-5-Inch-Internal-ST3000DM001/dp/B005T3GRLY/ref=lh_ni_t

I'm sorry if I'm completely off-base - I was just thrown by this exchange: "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?" Response: Supported, but not working to full speeds/ability. I read that to mean there was a problem with the AOC-SASLP-MV8 based on the "now neither of these are supported" part... I really wasn't following much of the NIC discussion up to that point, but being so close to trigger-pulling on my new build, I'm hyper-sensitive to the shifting 5.0 landscape. Hope this clears things up!

Vexhold, is that Antec case still available by any chance, or did it already make its way to Canada? (Shipping to California)