disco

Awesome, thank you so much. Parity sync is running now.

Ergh, guess I'm gonna go to bed and deal with this tomorrow. Is there a way I can use initconfig to fix my issues? Should I use the 2 week old super.dat (or a blank one) when doing this? Alternatively, can I mount the individual drives somehow and get the data off of them somehow?

Yup, so the super.dat file on my flash drive is a 0 byte file. My backup is from Jun 3rd, but unfortunately I've upgraded/replaced a couple drives since then. I loaded up the old super.dat and it's showing "Too many missing/replaced drives". Not going to start the array like this as I'm guessing I'll lose data, but not really sure what to do. Is there a way to re-initialize the array by picking my parity drive and data drives? none of the data on them should have changed...

Oh, maybe it's this: Jun 18 22:01:35 Tower kernel: md: could not read superblock from /boot/config/super.dat Going to try a check disk on the flash.

I actually don't see flash.cfg in my backup.....strange?

Shit just noticed this: Jun 18 22:01:35 Tower emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Is my flash drive dying?

Starting to freak out. Just upgraded from -rc15 to -rc15a on my second unRAID server. Copied over bzroot/bzimage/syslinux.cfg as required. Started the array up and I'm seeing this: Did a config file get screwed up somehow or something? I have a backup of the flash drive but I think I've replaced a disk or two since the last backup Just want to make sure I don't somehow wipe my data... Syslog here: http://pastebin.com/X2BeCcz2

i think this is standard behavior, the webui will become responsive again once the data begins rebuilding.

looks good here on my microserver

Works for me. Can you post the system log? Nevermind, it works, it just took like ~10 minutes to connect to the share for some reason.

Is AFP broken in -rc15? I had to restart it to get it functioning correctly in -rc13...but I can't connect at all using my Mac via AFP with -rc15...

Maybe this has already been reported, but I had to manually stop and then start AFP to be able to connect to the shares via my Mac after upgrading to -rc13. I haven't restarted unRAID since upgrading, so not sure if this is a requirement upon each reboot.

I installed -rc13 earlier this week on my HP Microserver. No issues so far. I actually pre-cleared a new 4TB drive and then replaced my 3TB parity with it. Rebuilt at ~110MB/sec with no issues. I've also stopped and restarted the array several times during this process without the crashing that others are reporting. Looks good to me.

any suggested additional burn-ins i should run on this thing? i feel like most drives die within the first few months of heavy use, so hoping to make sure this is a solid drive before the warranty ends.

Maybe this has been discussed in the past, but what's up with the new warranty system from WD/Seagate? I have a large (well, i guess probably small compared to most of you) 8x2tb system (+ cache/parity) that has been stable for a 3+ years (no drive deaths after a bunch initially when buying drives), but recently had my parity drive go out. Unfortunately, out of warranty, so I figured I'd pick up a 3tb as they're only $30 or so more than the 2tb variety these days. Picked up one of these without checking warranty: http://www.amazon.com/Seagate-Barracuda-3-5-Inch-Internal-ST3000DM001/dp/B005T3GRLY/ref=sr_1_1?s=electronics&ie=UTF8&qid=1360998171&sr=1-1&keywords=3tb+seagate Now, reading, I find it only has a 1 year warranty??? I could swear, the standard used to be 3 years for standard drives, 5 years for pricier drives. 1 year seems like a total joke given how often I've had drives fail in the past. Guess I'll have to preclear the crap out of this thing before adding to my system.