i have a truenas running EE and it is using nearly 60 gigs of space int he boot pool…it is booting from a 256 gig ssd but i am curious what is using all of that space and can i make it smaller?
Possibly old boot environments.
@hescominsoon You never specified what version of TrueNAS you are running, that is important. Also, when was this boot drive last completely imaged, and on what version of TrueNAS. You can find that in the GUI below.
If using SCALE, go into the GUI, System → Boot → look to see if you are using that much space here, add up the boot environments to get a rough estimate. If not, then post how you determined 60GB is being used. Do not assume we know how you did it.
When an update occurs, TrueNAS will decompress the file inside the boot-pool, that was just what it looks like to me due to having not enough space will cause an upgrade failure indicating it needs more storage.
To be honest, 60GB sounds like a lot of space, I didn’t know TrueNAS would create such a large partition, but iXsystems sneaks these things in where I either don’t pay attention or it was under the radar.
1 Like
He did; he said he was running EE.
Boot environments certainly could be part of it, but are unlikely to be all of it. You have something going on on your system that’s saving data to the boot device, most likely either in /root or /home/admin. Looking in those directories will likely find what’s that data is, and then you can move it to your pool.
I don’t think this is so much the case any more, but in the past, the most common culprit I’d see was FTP–one of its defaults was storing data in /root. You may want to check that out.
2 Likes
It is too early Christmas morning I guess.
1 Like
Goto SYSTEM > BOOT, and delete some old unnecessary boot environments. I boot off a 32GB DOM so I need to clean out the old environments periodically.
the active boot environment is the one using up so much space…and it is the only one present there are no other BE’s present.
Did you look at the directories @dan mentioned above?
i looked around…got tired of wasting time…i finally made a config backup…nuked the disk…reinstalled…and then restored the config…that made the usage something sane…
But since you never figured out what happened to fill up the space, chances are it will happen again.
oh i found it after i removed the data from the boot pool via ftp…i amde a slight finger error in one webserver target and it dumped onto the boot pool instead of the data pool…oopsie on my part…