SMB service failed to start 11.3-U4/U5

[toasteroven]

I was suddenly unable to connect to my SMB share from my windows 10 machine and also from my iPad. Decided to try restarting the SMB service and I am now unable to start it again. The system was running just fine for a couple month now. Happened on 11.3-U4 and i then updated to U5.

When running smbd -i -d 3 i get:

smbd version 4.10.18 started.
Copyright Andrew Tridgell and the Samba Team 1992-2019
uid=0 gid=0 euid=0 egid=0
lp_load_ex: refreshing parameters
Initialising global parameters
Processing section "[global]"
messaging_dgm_init: bind failed: Unknown error:122
messaging_dgm_ref failed: Unknown error:122

 

[Samuel Tai]

Sounds like smbd crashed, but didn't let go of the interface. Try rebooting.

 

[anodos]

messaging_dgm_init: bind failed: Unknown error:122
IIRC errno 122 indicates a ZFS error (ECKSUM). Possibly corruption of samba files in system dataset. What's output of zpool status?

 

[anodos]

This type of error can often happen if system dataset is moved to a boot device that has limited write endurance.

 

[toasteroven]

Sounds like smbd crashed, but didn't let go of the interface. Try rebooting.

I rebooted a couple of times already. That did not solve the issue.

 

[toasteroven]

messaging_dgm_init: bind failed: Unknown error:122
IIRC errno 122 indicates a ZFS error (ECKSUM). Possibly corruption of samba files in system dataset. What's output of zpool status?

root@freenas:~ # zpool status
pool: USB-Drives
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 0 in 0 days 00:02:14 with 36 errors on Sun Jan 17 00:02:15 2021
config:

NAME STATE READ WRITE CKSUM
USB-Drives ONLINE 0 0 0
gptid/83232901-01b1-11eb-aabf-7085c27d433d ONLINE 0 0 0
gptid/87b2c77c-01b1-11eb-aabf-7085c27d433d ONLINE 0 0 0

errors: 1 data errors, use '-v' for a list

pool: Vault
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
scan: scrub repaired 0 in 0 days 01:04:33 with 0 errors on Sun Jan 24 01:04:45 2021
config:

NAME STATE READ WRITE CKSUM
Vault ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/d6900c21-eb30-11e6-a68b-7085c226ae10 ONLINE 0 0 0
gptid/d75b9525-eb30-11e6-a68b-7085c226ae10 ONLINE 0 0 0
gptid/d81112d8-eb30-11e6-a68b-7085c226ae10 ONLINE 0 0 0

errors: No known data errors

pool: freenas-boot
state: DEGRADED
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 512 in 0 days 00:00:12 with 69 errors on Thu Feb 4 03:45:12 2021
config:

NAME STATE READ WRITE CKSUM
freenas-boot DEGRADED 0 0 361
ada2p2 DEGRADED 0 0 883 too many errors

errors: 64 data errors, use '-v' for a list

I moved my system dataset from a USB drive to a new SSD couple month ago.

 

[anodos]

I moved my system dataset from a USB drive to a new SSD couple month ago.

May want to double-check that midclt call systemdataset.config. Regardless, you'll need to replace your boot device. Looks like it's toast.

 

[anodos]

You can run zpool status -v to perhaps see a list of corrupted files. You _might_ be able to start SMB service if you see one ending in ".tdb" and delete it (most of these will just be re-created as needed).

 

[toasteroven]

May want to double-check that midclt call systemdataset.config. Regardless, you'll need to replace your boot device. Looks like it's toast.

It is calling the boot device. And there isn’t any .tdb file. Didn’t think that the cheap SSD would last super long but it failing so fast is a bummer. Will try replacing it. Thanks for the help!