Trying to add new disks to my unraid array (for the first time since initially setting it up) and when i try to add either of the new disks (or both at the same time), the messages:

Stopped. Found 1 new erased disk(s).

 

pops up at the bottom (it changes to 2 new erased disks if i try both at the same time).  When i added the first three disks, it just worked.  When i added the parity disk it didn't give me any issues either.  No idea why i can't add more data disks.  Licensed for pro, did a pre-clear on all drives.  Any idea what this error actually means?

What makes you think that is an error? As far as I remember from adding additional disks the last weeks, it's plain informational. Just start the array, unRAID will tell you that the new disks are unformatted. Check the box and click the button to format all unformatted disks, and once unRAID is done with that they will be available as regular data shares.

I assumed it was an error because it won't actually start the array.  I hit the check box to enable the start button, hit the start button, and it just reloads the page.  The only thing to indicate an error is the Stopped line.

 

If i remove the new disks from membership, check the box, hit start, the array comes up fine.  i did manage to get the array to give me a clear option on one of the disks (a smaller 1.5tb one i had lying around), but even after it finishes clearing, nothing changes, still cant start the array with the disks in them.  plus, these disks were pre-cleared, so it should just be an online/format thing, no?

I assumed it was an error because it won't actually start the array.  I hit the check box to enable the start button, hit the start button, and it just reloads the page.  The only thing to indicate an error is the Stopped line.

 

If i remove the new disks from membership, check the box, hit start, the array comes up fine.  i did manage to get the array to give me a clear option on one of the disks (a smaller 1.5tb one i had lying around), but even after it finishes clearing, nothing changes, still cant start the array with the disks in them.  plus, these disks were pre-cleared, so it should just be an online/format thing, no?

 

It should be online with no extra space until you hit format. I'm not really sure what advice to give, but, I'm posting this so that you don't do something thinking it's meant to be like this.

I assumed it was an error because it won't actually start the array.  I hit the check box to enable the start button, hit the start button, and it just reloads the page.  The only thing to indicate an error is the Stopped line.

 

If i remove the new disks from membership, check the box, hit start, the array comes up fine.  i did manage to get the array to give me a clear option on one of the disks (a smaller 1.5tb one i had lying around), but even after it finishes clearing, nothing changes, still cant start the array with the disks in them.  plus, these disks were pre-cleared, so it should just be an online/format thing, no?

 

It should be online with no extra space until you hit format. I'm not really sure what advice to give, but, I'm posting this so that you don't do something thinking it's meant to be like this.

Same advice as usual, post a screen shot and attach a syslog.  That way we'll know exactly what is happening.

I assumed it was an error because it won't actually start the array.  I hit the check box to enable the start button, hit the start button, and it just reloads the page.  The only thing to indicate an error is the Stopped line.

 

If i remove the new disks from membership, check the box, hit start, the array comes up fine.  i did manage to get the array to give me a clear option on one of the disks (a smaller 1.5tb one i had lying around), but even after it finishes clearing, nothing changes, still cant start the array with the disks in them.  plus, these disks were pre-cleared, so it should just be an online/format thing, no?

 

It should be online with no extra space until you hit format. I'm not really sure what advice to give, but, I'm posting this so that you don't do something thinking it's meant to be like this.

Same advice as usual, post a screen shot and attach a syslog.  That way we'll know exactly what is happening.

 

I wouldn't call that advice, I'd call that more a "Help us so we can help you" statement.

Run checkdisk on the flash in a PC or Mac.

Finally had a chance to take the cluster down today and try to add the disk again.  Attached is the syslog.  I only attempted to add a single disk this time around, and it actually does ask if i want to record the new info and add to the array but it is stuck at that step (reloads the page with the same question, no matter how many times i say "yes, do it").

 

I also attached pictures, though i'm not sure they'll be a huge help.  Everything looks like it should work, so i don't doubt i have something oddball in my specific implementation.  I'm running the latest version (5.0-rc11) because i couldn't get the 3TB drives to show up in the previous version.

 

Thanks for the help and advice.  I am new to the product but so far, I really am impressed with it. 

 

unraid_syslog.txt

Did you check the checkbox to enable the "Start": button and then press "Start" to start the array?

 

Here is your issue:

Mar  3 00:07:03 DataStore logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk)

 

Did you by chance load any add-on or plugin packages that might have put into place a different version of the libstdc library?  If so, disable your plugins, (they are breaking the unRAID system commands) and reboot, and then add your disk. 

 

Then, you can go back to the authors of the plugin(s) involved to let them know their add-on is breaking the sgdisk command (and probably other things too) in your versions of unRAID.

 

Joe L.

Did you check the checkbox to enable the "Start": button and then press "Start" to start the array?

 

Here is your issue:

Mar  3 00:07:03 DataStore logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk)

 

Did you by chance load any add-on or plugin packages that might have put into place a different version of the libstdc library?  If so, disable your plugins, (they are breaking the unRAID system commands) and reboot, and then add your disk. 

 

Then, you can go back to the authors of the plugin(s) involved to let them know their add-on is breaking the sgdisk command (and probably other things too) in your versions of unRAID.

 

Joe L.

 

Yup, it was an addon.  One I hadn't even realized i had loaded (called "unRAID-Web").  I pulled all of my addon's off one-by one, found that one (literally) at the bottom of the list, and after it came off (and rebooted) i could add disks again.  Never used it, so i won't miss it.

 

Thanks for the help!