Im running a 5.0 guest on an ESXi server.

 

I've precleared a 3TB WD RED drive with no errors.  After I stop the array and add the drive, nothing happens when I try to restart.  At the bottom it just says (I think): 'Spinning up all drives...starting SMB"  then it refreshes back to the stopped server screen.

 

When I unassign the drive I am able to start fine.

 

I've attached my syslog.  Any help would be appreciated.

syslog.txt

Haven't read your syslog, so I'm just shooting in the dark, but are you by any chance running a non-stock gui? If so, remove it and try again.

Update to the latest version. Updates are free.

Haven't read your syslog, so I'm just shooting in the dark, but are you by any chance running a non-stock gui? If so, remove it and try again.

 

I was running the updated wegui that looks like SimpleFeatures so I rolled it back (using your sig actually) and the problem persists.

 

Update to the latest version. Updates are free.

 

I plan to when I get home, but I don't expect an update from 5.0 to 5.0.4 to be fruitful.  I'll be completely arsed if that is the solution tho. 

 

The problem is should here:

Jan 17 10:58:40 Apollo emhttp: writing GPT on disk (sdh), with partition 1 offset 64, erased: 0
Jan 17 10:58:40 Apollo emhttp: shcmd (30): sgdisk -Z /dev/sdh &> /dev/null
Jan 17 10:58:40 Apollo emhttp: _shcmd: shcmd (30): exit status: 1
Jan 17 10:58:40 Apollo emhttp: shcmd (31): sgdisk -o -a 64 -n 1:64:0 /dev/sdh |& logger
Jan 17 10:58:40 Apollo logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk)
Jan 17 10:58:40 Apollo emhttp: shcmd (32): udevadm settle
Jan 17 10:58:40 Apollo emhttp: new disk(s) are not cleared

 

This is usually caused be an incompatible add-on. A system update may fix it. It does not appear as if the disk was pre-cleared successfully.

The problem is should here:

Jan 17 10:58:40 Apollo emhttp: writing GPT on disk (sdh), with partition 1 offset 64, erased: 0
Jan 17 10:58:40 Apollo emhttp: shcmd (30): sgdisk -Z /dev/sdh &> /dev/null
Jan 17 10:58:40 Apollo emhttp: _shcmd: shcmd (30): exit status: 1
Jan 17 10:58:40 Apollo emhttp: shcmd (31): sgdisk -o -a 64 -n 1:64:0 /dev/sdh |& logger
Jan 17 10:58:40 Apollo logger: sgdisk: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by sgdisk)
Jan 17 10:58:40 Apollo emhttp: shcmd (32): udevadm settle
Jan 17 10:58:40 Apollo emhttp: new disk(s) are not cleared

 

This is usually caused be an incompatible add-on. A system update may fix it. It does not appear as if the disk was pre-cleared successfully.

It appears as if an add-on has loaded a library that is incompatible with the one normally supplied with unRAID BREAKING the sgdisk utility that is used t partition disks > 2.2TB.

 

Since your disk cannot be partitioned (because you loaded an incompatible shared library via an add-on) , it cannot be added by unRAID.

 

This has nothing to do with the preclear process, although at this point if you had pre-cleared the disk it is likely no longer has a valid pre-clear signature once unRAID attempted t partition it.

 

 

Very strange since the only add-on I use is the webgui.  Everything else I migrated onto their own vms.

 

So what can I do about this??  Update unraid and run another cycle on the disk?

I had the same issue and resolved it this way:

 

#1 - Remove Simple Features (which I had installed) from flash drive

#2 - Update to latest unraid

#3 - Reboot

#4 - Under Settings update the GUI

 

Now adding the drive works

...what kin0kin said.  

---

If you had SF before, you might check out 'DYNAMIX'.

Its a branch of SF and works great.  It also has nice plugin management.

I never had SimpleFeatures, but I'll do the rest of the steps when this preclear is done.

Very strange since the only add-on I use is the webgui.  Everything else I migrated onto their own vms.

Apparently, prior to being migrated to their own "vm", one of them installed an incompatible shared library.

Does not matter that they are no longer being used.

 

Joe L.

Format the flash and reinstall the OS.

Apparently, prior to being migrated to their own "vm", one of them installed an incompatible shared library.

Does not matter that they are no longer being used.

 

Joe L.

 

I use the term migrate loosely (all terms probably).  After I moved all plugins off unRAID, I started from scratch.  But I'll try formatting the flash again.

 

Unfortunately I'm away for the remainder of the weekend so this will have to wait until Monday.  Just as good, since I decided to run an addition preclear cycle on the drive, for good measure, which won't be complete until tomorrow. 

 

Thanks for the help guys...  It's funny that it's almost detrimental to get everything running the way you want it, because you then become hands off and almost forget the things you learned when you started.

Ok, so I reformatted the USB (but copied over config stuff after), upgraded to 5.0.4, and ran another pre-clear cycle for good measure.  Same result.  When I try to start the array after adding the new drive, nothing...it just stays stopped.

 

I will attach the syslog when I get home.

Prepare a new install but do not restore the old config.

Could it possibly have been the UnRAID-Web package?