January 27, 201214 yr I'm at about my wits end with this. I replaced a drive that was going bad with a new one. Pre-cleared the drive, all looked good. Assigned the drive, let Unraid begin the rebuild process, and the server hangs - I cannot access it from the terminal nor remotely. It doesn't ping either . This is on Beta 14. So far, here's what I've tried: - disable all plug-ins - replace all sata cables - test powersupply - ran memtest for 50 hours I've tried to capture the syslog, but it doesn't capture anything when it crashes. Previous to this, my Unraid server has been fairly stable. I will hard reset the server, capture the syslog to the flash and attach it, but does anyone have ANY ideas? Could it be that my flash drive is bad? Outside of my motherboard and processor, its about the only thing I haven't checked. Having said that, if I stop the array when the server boots up, or cancel the parity check, the server will stay on just fine. ============================================================ The issue has disappeared after replacing my motherboard. I have filed this under "bad hardware".
January 28, 201214 yr I would say move back to 4.7 and do the rebuild of the array (note: don't let anything write to the array while it does the rebuild). Or try Beta 12a (what I believe most others are using for a "stable" beta).
January 29, 201214 yr Author Here's my syslog. Any advice outside of downgrading? syslog-2012-01-28.txt
January 29, 201214 yr Collect a syslog when it hangs using telnet: http://lime-technology.com/forum/index.php?topic=9880.0
January 29, 201214 yr Author It doesn't show anything. Seriously, not a thing. Here's a syslog I captured of it hanging earlier. syslogtail.txt
January 29, 201214 yr Author Any thoughts? I have to return my bad drive per the RMA, but don't want to until I know for sure I have all of the data.
January 30, 201214 yr One of the drives may be bad. I keep a spare pre-cleared drive so I can rebuild ASAP. Then I can test and RMA a failed drive at my leisure.
January 30, 201214 yr Try moving disks to different SATA ports and cables for testing. This may be tough to isolate.
January 31, 201214 yr Author Try moving disks to different SATA ports and cables for testing. This may be tough to isolate. No change. I'm going to try my luck at pulling the data off of the bad drive. I must say, I was hoping there was an easier way to troubleshoot that would have been recommended.
Archived
This topic is now archived and is closed to further replies.