Array won't start with new hard drive

[gulo]

Hello

 

I added new hard drive to my unraid server but the array won't start.

 

Here is what it looks like when I stop the server:

 

 

Then I check "yes i want to do this" and hit start

 

 

On the bottom it says Spinning up all drives...Restart SMB... and it goes right back to the first screen.

 

If I remove Disk 4 and hit start it comes up just fine.

 

What could be the problem ?

 

thanks

 

 

Here is the log

 

http://pastebin.com/S3DcjBg4

[dgaschk]

What happens if you check the box?

[gulo]

I did check the box..otherwise I can't hit run. I just took the screenshot before hitting it

[gulo]

Here is the screenshot after I hit start:

 

 

Then it goes back to the same screen as if nothing happened

[JonathanM]

What version of unraid are you running? The syslog you linked is incomplete, so I can't tell.

[dgaschk]

Need the entire log. See my sig.

[gulo]

Hi

 

I am running 5.0-rc10

 

Here is the full log:

log.zip

[JonathanM]

Update to the latest release. Some of the RC versions had a bug that wouldn't allow adding a drive unless it was precleared first with Joe L's script. It wouldn't be a bad idea to preclear the drive before adding it anyway, to make sure the drive is ok, and keep the array available instead of having it offline for hours while the drive is cleared.

[gulo]

OK I upgraded to RC16 - same results. The only difference is that now it also says Restart NFS, after RESTART SMB. but still not working

 

here is the new log:

log.zip

[JonathanM]

OK I upgraded to RC16 - same results

We are past RC's, you need to use the latest release.

[gulo]

OK I upgraded to RC16 - same results

We are past RC's, you need to use the latest release.

 

wow, apparently I missed the full release !

 

Alas even with 5.0 I am getting same results, someone please help I have no idea what to do

 

New log attached

log.zip

[JonathanM]

someone please help I have no idea what to do

I would recommend preclearing the drive, using screen over telnet, or at the physical console.

 

There is obviously an issue here, as what you describe was supposed to be fixed, but instead of beating your head against it, I'd just preclear the drive.

 

What EXACTLY did you do to upgrade? Did you remove any and all addons? I suspect if you disable all third party stuff it will start working.

[garycase]

I suspect if you disable all third party stuff it will start working.

 

Agree.  Boot again with a console attached, and select Safe mode ... then try adding the new drive.

 

[gulo]

someone please help I have no idea what to do

I would recommend preclearing the drive, using screen over telnet, or at the physical console.

 

There is obviously an issue here, as what you describe was supposed to be fixed, but instead of beating your head against it, I'd just preclear the drive.

 

What EXACTLY did you do to upgrade? Did you remove any and all addons? I suspect if you disable all third party stuff it will start working.

 

I just replaced bzroot, bzimage and syslinux.cfg and then rebooted

[garycase]

someone please help I have no idea what to do

I would recommend preclearing the drive, using screen over telnet, or at the physical console.

 

There is obviously an issue here, as what you describe was supposed to be fixed, but instead of beating your head against it, I'd just preclear the drive.

 

What EXACTLY did you do to upgrade? Did you remove any and all addons? I suspect if you disable all third party stuff it will start working.

 

I just replaced bzroot, bzimage and syslinux.cfg and then rebooted

 

Seems very likely this is due to a plugin.    That issue (not adding a drive that wasn't pre-cleared)  was resolved for v5.0.    But you've upgrade a pretty big jump from RC10, so it's likely you have a plugin that was part of the issue that's still in place.    Upgrade to v5.0, then do a "Safe Mode" reboot and then add the drive.

 

 

 

[gulo]

OK, it probably had something to do with the plugins. I wiped off the whole flash drive and started with a clean install.

 

This time instead of "Start" the button said "Clear", and sure enough it cleared the new drive and everything is up and runnig now.

[garycase]

Glad it's sorted out.    It's always best to (a) use the latest stable version; and (b) try running without plugins if you're having issues, to confirm whether or not it's an issue with UnRAID or one of the plugins [that's the primary reason Tom added a "Safe Mode" boot option].