[FATAL] [mender-convert-package] You can try adjusting the MENDER_STORAGE_TOTAL_SIZE_MB variable to increase available space, or

Thanks Dell, Drew:
I ran
(sspy35_env) ssqr@SS-HealthPOD:~ $ sudo du -h -d 1 /
23M /boot
16K /lost+found
0 /proc
164K /dev
354M /var
4.0K /mnt
3.3G /usr
4.0K /srv
4.0K /media
99M /etc
0 /sys
8.0M /sbin
7.5G /home
8.3M /bin
248M /lib
212M /opt
6.3M /run
44M /root
68K /tmp
12G /

I removed old boot, /var/log/log and gz files files:
sudo rm -rf /boot.bak boot1
sudo rm -rf log.gz
sudo rm -rf log..gz
sudo rm -rf log
rm -rf messages
sudo rm -rf messages
rm *.gz
sudo rm -rf *.gz
rm *.log
sudo rm *.log
history | grep rm

Then here’s the final output of du -h -d 1 /
(sspy35_env) ssqr@SS-HealthPOD:/home/ssqr/SSquare/sspy35_env $ sudo du -h -d 1 /
23M /boot
16K /lost+found
0 /proc
44K /dev
354M /var
4.0K /mnt
3.3G /usr
4.0K /srv
4.0K /media
99M /etc
0 /sys
8.0M /sbin
7.5G /home
8.3M /bin
248M /lib
212M /opt
12M /run
44M /root
68K /tmp
12G /
(sspy35_env) ssqr@SS-HealthPOD:/home/ssqr/SSquare/sspy35_env $

And, the image boots! So I didn’t butcher it to its death.

Is there a utility to do such cleanup to run as part of the mender-convert?

What values should I configure the mender parameters with?

Greatly appreciate your guidance.

Regards,
Raj