Error nbjm(pid=5256) NBU status: 800, EMM status: The robotic library is not defined in EMM resource
Difficult to say too much with the details you have provided ...
However ... - the vast majority of the causes of this error are config related. I appreciate you have readded the device, and that is where I would have started.
You have two libraries, if you removed both, have they gone back with the same robot number as before. If tld(0) is now tld(1) you will potentially have issues.
On simple set-ups (that is not too many drives/ libraries etc ...) I usually delete devices using nbemmcmd -deletealldevices -allrecords. The advatage of this is it completely clears the tables in NBDB that hold the config. The downside is that is removes ALL robots and drives from everything.
I would be temped to do the above, and put the libraries/ drives back being very careful that what was library tld(0) goins back as tld(0), and what was tld(1) goes back as tld(1). To do this, simply add just one library first in device wizard (this should then be tld(0)) and then go back and add the other, this should be tld(1).
Also, be sure that the density type remains the same as it was before, eg drives show as hcart2 in your outputs, have they always been hcart2, or did this get changed when you re-added.
The reason these config changes described above can affect things, is because the storage units are related to the robot number and density.
Eg. A typical STU name may look like this
nbmaster2-hcart3-robot-tld-0
As you can see, the density and robot number are 'embedded' in the STU. So if the denisty of roobot number changes, but the STUs are not recreated, you can see the mis-match.
Another option, could be to just delete the STU and recreate them, though you would have to update the policies after.
If you do delete things again, recrate as the used to be, and cancel the wizrd just before it would normally create the STUs. If the config is set up the same, the original STUs should match.
- You seem to physically have 2 robots (TLD 0 and 1) with 2 drives each but you have storage units configured for 4 robots - 0, 1, 2 and 3.
Any jobs going to STUs for robots 2 and 3 will fail with above error.
Delete storage units for TLD 2 and 3 and ensure policies have only STUs selected for TLD 0 or 1.
If you have STU group(s) configured, remove non-existing STUs. The issue resolve finally
I found I didn't delete storage units completely. I deleted storage unit in Device Manager, that is nor clear storage unit at all.
I go to storage unit categlory and delete two deveices again, then I reconfig storage device, everything works.
