Tophicles

Ok, round two of our saga.... Ran the good part ofthe day with no errors, everything fine. Checked a few minutes ago, now disk THREE is disabled instead of disk FOUR. Stopped array, ran SMART on disk THREE and it came up clean. BIOS SMART shows disk three as clean. Removed, reassigned, data-rebuild now on drive three.... Which will be next? I'm taking bets here, gentlemen!! (purchases small firearm, loads rounds, cocks hammer, place barrel in mouth and watches unRAID screen - waiting... waiting ...)

Second parity check completed, parity is valid and all drives are green and good to go... VERY weird. I just don't understand, maybe it was a glitch in a single write attempt? No other tests gave warnings or errors on that drive... Oh well, as long as it's back up and running, I'm a happy camper

Data rebuild is finished, the drive has a green ball and it says "Parity is valid". Should I assume it's good to go, or run another parity check? Km.

Ok, data-rebuild is in progress, will report in 10 hours

Is that safe? I'm assuming it'll attempt the rebuild but error out if it can't? The array is unusable during the rebuild, right? I'll rebuild tonight after movie night

Ok, so now I have a question about this "failed" disk. 1) I can see it from the disk share in \\tower\disk4 2) I can run a SMART test which returns no errors. 3) I can run a speed test which shows it at the same speeds as my other drives. 4) BIOS reports the drive as present and SMART capable and fine... Is this drive really failed, or has unraid goofed up? Thoughts? unRAID version is 4.7 I'll attached my syslogs (multiple logs, since I am not sure where/when the error occured). Thanks! Km logs.zip

Ok, so here's my story Last night I ran a parity check on my unraid server and it passed, however, when it rebooted my disk 4 was disabled. Ok, so I am thinking maybe there was a wire loose somewhere, so I powerdown (via powerdown script) the unraid box and double check all cables, everything fine. "No problem, bad drive", I solemnly think to myself, "I'll just boot it up and replace it later". So the box boots, but I cannot access it from my internal network No ping, no telnet, no emhttp, no unMenu, nothing... except the samba shares? I check syslog, "link beat" is up, eth0 is up, so I go and logon locally to the unraid box. I ping my router, every other box on my network and the intertubes from the unraid commandline successfully. Yet, my other machines cannot get to the unraid box, except for the samba shares. I've run out of ideas... anyone got a brainstorm? Everything was running flawlessly until this morning. My system is running unRAID 4.7. Syslog is attached... -----------------------------------------------SOLVED-------------------------------------------------- Ok, stupid error (though I don't know why). It was not taking the static IP I had setup in my router, it was taking another IP so I set it to static in network.cfg Very weird, but all is working now (apart from my failed drive ) syslog.zip

Gig-E cards I have, but my current mobo has no onboard SATA, so I'm running all my 5 drives on two SiS PCI adapters. I haven't got a lot of dough to blow on gear right now, so that's why the six onboard SATA connectors appealed to me. This board is like $30 brand new right now, $78 with a CPU. So I figured I could just toss in a PCI Gig-E card for now...

Any problems with unRAID and these boards? Here are the specs: Processor Socket: AMD Processor Interface: Socket AM2+ Additional Technologies: RoHS Compliant Northbridge: AMD 740G Southbridge: SB700 Memory Type: DDR2 Video Chipset: Integrated LAN Type: 10/100 Mbps Serial ATA 3.0Gb/s Headers: 6 Anyone have any issues with this chipset?

I am in agreement there and didn't purchase it after all. Thanks for the heads up!

I think the HPA is disable-able (ha!) in the BIOS, and the CPU is an X2 5800+.

Any thoughts on using/not-using this for unRAID? I can get the mobo/cpu for $100! Thanks.