talmania

A couple of screen shots... after more research tonight I found a couple of posts referencing that I should be able to start up the array with one drive missing so I unassigned it, rebooted and still can't start the array. Here's what I see...

Thanks for the response--I've reseated every cable in my Norco 2040 and just got back from buying a new EARS, tried it with the exact same result. It recognizes a disabled disk has been replaced but after starting it states "new parity disk installed". I've made zero changes to the drive order other than to try different brand new drives in the same disk 5 slot. I'm attaching a new syslog where I did notice the following: Interesting about the sdj and sdj1. Not entirely sure what it means though. syslog_2.txt

Finished the preclear of the Hitachi and after adding it successfully as disk 5 and then starting the array I again got the message "new parity installed". I'm stuck again.

Here's a link--never done it myself but my thought process was its as simple as reassigning the disk to the drive that you want. http://www.lime-technology.com/wiki/index.php?title=FAQ#What_is_the_safe_way_to_rearrange_disk_numbers.2C_assignments.2C_slots.2C_etc.3F

Anyone? Where's Joe when a guy needs him! I'm approaching this as follows: I've swapped back in the brand new Hitachi and will attempt to preclear it before adding it to the array (just added it directly before) in hopes to avoid the "replace parity" message when trying to start the array. I'm also going to buy a 2TB EARS in the miniscule chance that the issue is that Unraid thinks the unformatted Hitachi is larger than the EARS that's currently the parity drive.

A partial syslog tail when trying to start the array from a ready state. partial_syslog.txt

Ok so I spent last night looking at things and remembered a previous problem I had here: http://lime-technology.com/forum/index.php?topic=11886.0 Similar issue now where I've tried to start the array multiple times (without the disabled drive and with it) and everytime it looks like it's starting to mount then stop. I've looked over the syslog and I don't see a tell-tale entry from the previous issue like: I do see a lock-dev error. Will post an updated syslog soon but I'm stumped on why I'm having these issues. Thanks!

I noticed today that my drive 5 was offline and had the red DISK_DSBL next to it. Took the array down, removed drive 5 from the array, powered off, reseated the drive, powered back on and reassigned the drive to slot five. When trying to start the array it looked like it was going to mount then jumped back to the default screen. So I figured the drive was truly having issues so I removed it, shut down, installed new drive, assigned it to the slot and UNRAID noticed that the disabled drive had been replaced. However when I clicked on the "I'm sure I want to do this" and start the array it then stopped and gave the message that "New Parity disk installed". My parity disk is a 2TB WD EARS and the disk I replaced (also an EARS) was a Hitachi 2TB. Size reported is the same. I'm running 4.7 final and have attached my syslog. Help! Thanks so much! syslog.txt

Jumped in too---2 more 2TB drives. Time to start replacing the few 1.5 7.2k's still in there. Thanks OP!

So quick dumb question for the rebate experts---are rebate forms like this that say limited to two require two separate forms or will they accept one form for two rebates (with both serials etc.)? Just got to thinking about this as I'm waiting on a 60.00+ rebate (can't remember exact amount) from WD that I haven't received yet and it was same thing--limit of "x".

Array rebuilt successfully without problems. Added disk and everythings working as expected. Thanks again all!!

ouch... There is no partition table. The MBR is completely blank. Easiest thing to try. Unplug that drive from the array (or, even easier, un-assign it on the "devices" page), see if the array will start without it. If it does, and you can get to the "re-constructed" files on it, we can try putting the MBR back to is intended form. Did you write zeros to it (or rather, did you knowingly write to its MBR?) did you issue any manual "dd" commands to write to your disks? Success! I removed sdh from the devices page and was able to start the array successfully. I have never issued any manual command to my disks. I've only used screen to preclear them and a couple of times just let unraid handle it as I didn't mind the downtime. Thanks for helping me get back to this point Joe. What's my next step? I was only using about 35% of my array's capacity so there's a chance there's nothing on that drive...but I'm not sure.

Thanks Joe--here's the output of the command given:

Done--thanks for your help! syslog.txt

;D Yeah I figured that out the hard way! As an FYI here's how it currently looks: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & /boot/unmenu/uu cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c I've only commented out the last line and that didn't change the result.

Latest syslog from my reboot etc. syslog-2011-03-23.txt

Put a "#" character at the beginning of any added lines at the bottom of the file. You can edit the config/go file in any editor, even a windows editor. However, what you described is not likely to be the cause of your problem... not unless you used unMENU to install other utilities. I'm certain I used unMenu to install the other required apps. Thanks again! What do you mean by "other required apps"? Poor wording on my part. Specifically for screen there was one or two apps I installed via unmenu. I've commented out the entire go file and nothing seems to work. I can't get my array back online at this point.

Quoted for emphasis and absolute truth! I have this board as well and already purchased a second for my next unraid build. Highly, highly recommended!

Well I just rem'd out the part in my go file about software packages, rebooted and still same result. Wondering at this point if I should try to remove "sds" from the array and assign one of the hitachi's in its place. Trying to get back to square one at this point.

Thanks for the reminder---its the dreaded 1.5TB Seagate Baracuda 7200.11 drive that I'm sure needs a firmware update. I saw that message but completely forgot about it in trying to fix my original problem. Thanks!

Put a "#" character at the beginning of any added lines at the bottom of the file. You can edit the config/go file in any editor, even a windows editor. However, what you described is not likely to be the cause of your problem... not unless you used unMENU to install other utilities. I'm certain I used unMenu to install the other required apps. Thanks again!

Thanks Joe! The only application I've loaded is unmenu and screen per the configuration tutorial here: http://lime-technology.com/wiki/index.php?title=Configuration_Tutorial Not sure how to modify the go script but I'm off to the wiki to find out.

Thanks Peter--just tried that and got same result with the lock_rdev error. Guess I'm stuck at this point.

Thanks Joe--I let the clearing run all night and tried to bring it online this AM with the same failed "looping" result. I then proceeded to remove the two new drives from the array by unassigning those slots. Went back to main page, refreshed and it recognized that there were no new drives so I "started the array" and got the same result. Array would not start but menu looped back to the start array page. syslog attached and it looks like there is a lock_rdev error. What should I do now? syslog-2011-03-23.txt

Hi krackato-- I'd HIGHLY recommend reading every word of a forum member's wiki post here: http://lime-technology.com/wiki/index.php?title=Configuration_Tutorial My apologies to that member for forgetting his name but it's an INCREDIBLY useful document when first starting out--one that set me on the right track and getting things setup! I have just purchased 4 of the Hitachi 5k3000 drives for my array and I've heard nothing but good feedback about them. I wouldn't hesitate using one as a parity drive. Yes you can preclear more than one drive at once---again see the config link above for a helpful reference. Good luck to you--there are plenty of FAR more knowledgable members around here then me that will jump to help. It truly is a GREAT user community!