error efault insuffcient space - fixed via a re-install on a larger capacity drive

[ADB1979]

I have gotten this error when in TrueNAS 13 stable (brand new install) on a 120G SSD when I go to System > Update > Apply Pending Updates.

"Error: [EFAULT] Insuffcient space to install update".

The top DuckDuckGo hit is on these very forums and the guy simply said that he fixed it, with no explanation of how, and no further comments in the last two years, this is as you can imagine rather unhelpful.

Can we please find a resolution for this, identify the cause of the problem and then label the post and it's contents well enough that others can find this post and and use the following content to resolve their problem with ease.

Many Thanks.

 

[ADB1979]

This is what I see when I attempt the updates (after a few attempts, the final one being where I took the pictures), on the second image the update percentage goes straight from 0.0% to the error as seen in the third image.

I have plenty of other things to be doing elsewhere, until this is fixed the server will remain offline.

 

[Ericloewe]

Is the boot device actually full? That's important info that shouldn't be omitted.

Also, snipping tool (or whatever screenshot tool your favorite environment uses) is your friend and ours. Looking at photographs of a monitor is obnoxious.

 

[ADB1979]

Is the boot device actually full? That's important info that shouldn't be omitted.

I do not know, I am using TrueNAS as a novice. Whilst the UI on TrueNAS for a NAS is phenomenal compared to everything else, there is still a lot that that is not obvious to a novice (just as there are in other Operating Systems). It is not obvious how to find this out.

I have used the command prompt (shell) before in Ubuntu, and I assume that this is the same, or largely the same to setup a ZFS RAIDZ array following information online, I kept on running into problems, didn't (still don't) have the time to learn how to do all of this from the command prompt and setup TrueNAS as the solution, that was on another machine that was entirely clean, problem solved, no issues (so far).

I am now on a secondary machine and having tested on the first machine that I can "import" a ZFS array made in Ubuntu, and it works perfectly in TrueNAS, that was great, but I had a drive that was faulty, which then died as I was fixing the array using a spare drive (it was successful), I then tried to update it.

The only information in the GUI about the boot drive is useless, it simply says "Space 88.68 G".!

I assume that I need to now use the "shell", which I was truly hoping to avoid, especially considering the great UI in TrueNAS is one of the two prime reasons why it is so popular.

 

[ADB1979]

Also, snipping tool (or whatever screenshot tool your favourite environment uses) is your friend and ours. Looking at photographs of a monitor is obnoxious.

When I have the ability to replace those obnoxious pictures I will, I have just taken new pictures, don't know why I didn't take screenshots

 

[Ericloewe]

I do not know

You can find this info under System / Boot / Actions button around the top right / Stats/Settings

 

[ADB1979]

You can find this info under System / Boot / Actions button around the top right / Stats/Settings

Excellent, we are getting somewhere I also have enough space to install an update, surely.!

 

[Ericloewe]

Enough space, maybe, it might not be enough (depending on what exactly is being reported there, what support logic is doing, etc.)... But there is no scenario where you should have 80+ GB on your boot pool, so something is very wrong there.

This is a weird one and you'll have to get over your fear of the CLI, because we need the output of zfs list -o space bootpool, where bootpool is whatever the GUI reports as the name of the boot pool (used to be freenas-boot, but not anymore on newer installs). Alternatively, zpool list will, to no surprise, list all imported pools.

 

[danb35]

It seems to me that system -> boot would be relevant, in that it would show the boot environments and how much space they're using:

 

[ADB1979]

But there is no scenario where you should have 80+ GB on your boot pool, so something is very wrong there.

Sure sounds that way to me, even Windows doesn't abuse that much data (on a brand new install at least).

This is a weird one and you'll have to get over your fear of the CLI, because we need the output of zfs list -o space bootpool, where bootpool is whatever the GUI reports as the name of the boot pool (used to be freenas-boot, but not anymore on newer installs). Alternatively, zpool list will, to no surprise, list all imported pools.

Will do.

Offo on Tangent/Rant (perspective): I best note that I do not have an aversion to CLI (assuming this is another term for the "command prompt", or Shell), I am a long way from understanding the commands, and copying+pasting commands even from trusted sources is not learning, I was learning sometime back, but life intervened and had other ideas, now I am in copy and paste mode again, with the exception to this befuddling issue that has seemingly never been "publicly" resolved, and now I am determined to, with your help of course, find a solution and make this a simple pain-free fix for the next guy who bumps into this problem.

It seems to me that system -> boot

Yes, there was this weird (as a lifelong Windows user, and dabbler in Linux) partition in the Megabytes. I will update this in a while with screenshots.

There were only two items listed, One under the "active" column said Now/Reboot, the other was blank as are yours, and aligns accurately with when I installed it (3-days ago).

 

[danb35]

Just a random thought--are you using the FTP service, by any chance?

 

[ADB1979]

Just a random thought--are you using the FTP service, by any chance?

Interesting question, to which I have no answer (answer added via above image, no i am not using FTP). I literally installed it, double checked everything (I missed the region, and "time" is important) so rebooted, I had a look around and was happy with what I saw.

I am only bullet pointing this (currently) as I (seemingly) have a love for brackets Guilty as charged.

I had a look around the OS generally, trying to spot anything that was "wrong" (like I did with the timezone), and specifically at the "Storage" section.
I imported the existing ZFS Array, all was well.
Drive died, I (without looking anything up on da-intawebz) managed to fix this by using an unused drive, it "re-synched" with the only hole tensioning being that the old drive died 1-hour into it.!
I setup a share [(not realising that some (messed up because I didn't know what I was doing in Ubuntu/Linux) existing shares were already there)], and proceeded to bump into issue moving data around (I still have those, but they are a minor insignificance, and the literature of fixing them is massive (and singularly specific).
Once the ZFS RAIDZ was "resynched", I rebooted the machine and tried to update it, and bumped into this issue. I decided to create an account and post here are there is no actual answer to this that anyone can fix by searching for it (DDG in my example), and here we are.

Latest pictures to come shortly, now that I have earned my "Edit badge" (first "Edit" of "Edit badge") >

 

[danb35]

Interesting question, to which I have no answer

...then you almost certainly aren't using the FTP service. You'd have to have enabled it manually, just like most of the other services on the system. I asked because, at least at one point, that was a fairly common cause of the boot device filling--the default storage path was on the boot device, so anything you'd upload via FTP went there. But if you haven't turned on that service (and it doesn't sound like you have; I'd expect you to remember if you had), it wouldn't be that.

there is no actual answer to this that anyone can fix

I do think that at least part of the issue is that there are multiple causes for this error message. The obvious one is that the boot device is full, but the real question is what caused that--and I doubt there's a single answer to that question.

 

[ADB1979]

The obvious one is that the boot device is full, but the real question is what caused that--and I doubt there's a single answer to that question.

I have other drives.!

I used this one as it was on-hand, I can sure find another one. FYI, when I was fed-up with messing around with Ubuntu, I wiped the drive by booting into a "LiveCD" of Linux Mint and deleted all partitions, then quick formatted the whole drive to NTFS as I knew that TrueNAS would rightly destroy that garbage FS, and in the manner that it chooses, I simply accepted, could this be part of the issue.?

 

[ADB1979]

An update, and a fix via a re-install on larger capacity drive(s).

I cloned the 120G drive to a 480G drive and as expected there was no change as the drive was a straight clone, so the usable space for the OS did not change as the excess 360G was unused.

I looked at the relevant things in TrueNAS that I had setup, and used a pair of 480G drives as a mirrored pair during a fresh install, I setup things as they were previously and then ran the update with no issues at all. Everything is working exactly as it should be with the exception of TrueNAS not supporting my RTL8125.

I am not going to investigate this problem any further, and as far as I am concerned the problem has been fixed by a re-install, not ideal, but for me it was not a major issue, I just had to prematurely take a pair of 480G SSD's from another system as that is what is available to me right now.