1 Rookie
•
20 Posts
0
114
April 1st, 2025 17:59
Dell Storage Manager 2020 R1.20 won't start due to root partition full
Discovered that the root partition of the DSM virtual appliance is full and after rebooting it, the Data Collector will not start and I'm unable to log into the GUI.
We receive an email alert saying this
Alert Message: Exception Starting Data Collector Service: java.lang.NullPointerException
If I log into the console I can see that it does briefly mention a storage issue and Aria Operations is notifying me of this too, however, I am unable to do anything to it. Logging in via SSH or the virtual console gives me a menu system and not access to a bash prompt.
I don't want to need to redeploy the VA so how can I clean up the file system so it can come back up? Is there some backdoor method of dropping to the command line when in the console? I couldn't find anything that indicated so in the manual.
Origin3k
4 Operator
•
2.3K Posts
1
April 1st, 2025 18:23
You can try to boot from a Live ISO and see of you can mount the file system and than delete logs/core dumps.
The Appliance was never for "production".
Regards,
Joerg
MarcLaflamme
1 Rookie
•
20 Posts
0
April 1st, 2025 18:01
I failed to mention, when viewing the console I can see this appear in the output logging
Java HotSpot(TM) 64-Bit Server VM warning: Insufficient space for shared memory file:
MarcLaflamme
1 Rookie
•
20 Posts
0
April 1st, 2025 18:24
@Origin3k I never thought about a Live ISO, good idea. I tried single user mode but it still redirected to the menu system.
What do you mean by "The Appliance was never for "production"."?
Origin3k
4 Operator
•
2.3K Posts
0
April 1st, 2025 18:28
IIRC there is a statement when you install the product. Because iam a certifed Installer and Partner i have in mind that the appliance never was for production. I only can say that our Windows based Enterprise Manager installations runs way better.... but for sure the majority of my customers used the Appliance onces.
Compared VSI against DSM DC the later one wins.
Regards
Joerg
MarcLaflamme
1 Rookie
•
20 Posts
0
April 1st, 2025 18:34
@Origin3k Ah I clearly must have missed that when installing. It's a good thing this is a small setup and nothing is really dependent on this install. I would also have thought that a dedicated VA without all the extra overhead would be far superior than running it on Windows. Good to know though.
I'm going to try the live iso route and if that fails, I'll probably redeploy although I don't really want to. Thanks!
MarcLaflamme
1 Rookie
•
20 Posts
0
April 2nd, 2025 12:57
@Origin3k Got it back up! I extended the VMDK in vCenter and then using a live iso was able to resize the logical volume so root had enough space. Unfortunately I wasn't able to explore the root volume due to an old version of LVM being used on the VA (or something like that? I wasn't too clear on why). But at least I got some more life out of it. I might move it over to a Windows box eventually however it'll do for now. Thanks for your help.
Oh the only thing I saw mentioned about Not for Production Use was regarding the embedded database (which is inherently what the VA uses)... So.. I probably didn't put 2 and 2 together.
(edited)
Origin3k
4 Operator
•
2.3K Posts
0
April 2nd, 2025 17:39
Yes.... it was the statement about the embedded (My)SQL Db. But who use a VA with external DB? Iam pretty sure there is none.