Truenas 12 No Longer Accessible

[Vike]

Hi all and a Happy New Year to you. I'm currently running TrueNAS-12.0-U8.1. I use it to run Plex Mediaserver but mainly for backing up my Windows 11 pc. Up until I was on Freenas everything was working fine. Then I upgraded to Truenas and still everything was fine in that my backups were all writing to my Truenas pool and I could play my videos through Plex mediaserver on my TV and through the pc. I could access the pool disks through the original Freenas shortcut that I'd set up when I was on Freenas. The only thing that changed after the initial upgrade to TrueNAS was that when trying to access the data through the windows network shortcut, FREENAS had changed to TRUENAS but was no longer accessible with the error Windows cannot access \\TRUENAS.

Then we went away for Christmas and when we returned I discovered that the last backup to succeed was on Christmas Day. After that they were all failing. Error: Failed to create directory. Now Plex mediaserver is no longer accessible. The Freenas shortcut no longer works with the same error as the network shortcut: The network path was not found.

If I go to my Truenas Server through my browser using the ip address the interface is all there but I discovered that SMB shares are not on and neither can I start them. "SMB service failed to start"

Any advice greatly appreciated as I'm concerned that I can no longer backup my pc.

 

[Vike]

Does anyone have any suggestions/advice, please?

 

[Redcoat]

Have you tried (re)starting the SMB service? Services>SMB?

Can you run the following and post the output here in code tags?

zpool status zfs list testparm

 

[Vike]

Thanks Redcoat, this is one of the first thing I checked. SMB service was stopped but when I tried to start it I just got this:

I ran what you asked and these are screenshots of the results. I hope this is what you meant.

Does this help?

 

[Redcoat]

You clipped the top of the datapool status display - can you try

zpool status -v

 

[Vike]

the -v switch didn't seem to make a difference but I scrolled up to take this:

 

[anodos]

what is output of smbd -d 5 -i?

 

[Vike]

I don't know if these critical alerts help. The lower one about space usage I can understand. But the top one about Failed to check for alert HasUpdate is beyond me.

 

[anodos]

But the top one about Failed to check for alert HasUpdate is beyond me.

That means that either your boot disk is probably 100% full, which might also explain why Samba is failing to start.

What is output of zpool list and df -Th /var/db/system?

 

[Vike]

Hi anodos

what is output of smbd -d 5 -i?

I can get the screen shots of the entire output, do you need all of it as its goes on for pages?

That means that either your boot disk is probably 100% full, which might also explain why Samba is failing to start.

What is output of zpool list and df -Th /var/db/system?

I'm using a 32GiB (29.82 GiB) USB drive. Which I know is not a good idea. I was using this since creating the FreeNAS server. After upgrading to TrueNAS am I correct in thinking that the upgrade writes to the boot drive, filled it and that is what has caused my problems? If this is the case how can I proceed?

 

[Vike]

df -Th /var/db/system AND
zpool list:

 

[Whattteva]

Hi anodos


I can get the screen shots of the entire output, do you need all of it as its goes on for pages?

I'm using a 32GiB (29.82 GiB) USB drive. Which I know is not a good idea. I was using this since creating the FreeNAS server. After upgrading to TrueNAS am I correct in thinking that the upgrade writes to the boot drive, filled it and that is what has caused my problems? If this is the case how can I proceed?

You could still use a USB drive for the boot device, but use an SSD-based one instead of those thumb drives.

 

[anodos]

Yup. Your system dataset is on your data pool and has zero free space available. You'll need to free up space otherwise SMB won't work.

 

[Vike]

Yup. Your system dataset is on your data pool and has zero free space available. You'll need to free up space otherwise SMB won't work

OK, so how do I free up space on my datapool if I can't access the pool to delete the oldest data. Would I need to clear the lot and start again?

 

[Vike]

I'm back in! I moved the location of the dataset to the boot drive, under System>System Dataset, restarted the SMB service which now started instantly. and I'm now even able to reach the Server from the Network shortcut on my pc. I'm now able to clear some old backups before moving the system dataset back to my main data pool on the HDDs.

Anything else I should do/be aware of, going forward so I don't end up in the same situation again. Thank you all for your help.

 

[anodos]

I'm back in! I moved the location of the dataset to the boot drive, under System>System Dataset, restarted the SMB service which now started instantly. and I'm now even able to reach the Server from the Network shortcut on my pc. I'm now able to clear some old backups before moving the system dataset back to my main data pool on the HDDs.

Anything else I should do/be aware of, going forward so I don't end up in the same situation again. Thank all for your help.

We should be generating alerts as you start to get above certain thresholds of used space. Configure alerts so that you're getting them though email or some other means, and take action ahead of time to maintain free space.