SMB Server does not work

[dellorianes]

Some days ago I found the array with all my disks unlocked.

 

After rebooting the server all seems to be ok, but since then (I do not know if the problem existed before), I can not access my server via SMB from any device at home (Home Assistant OS, Android Mobile, Windows 11..)

 

I tryed to stop the smb server, reestart the server and activate again but nothing changed.

 

I have also tryed to make a share folder public but it cotinued not having access.

 

Find attached my diagnostic file.

 

Thank you very much

 

nasdiego-diagnostics-20230511-1208.zip

[JorgeB]

Give the name of a share you are trying to access, I checked a couple and they were not being exported.

[dellorianes]

The following shares are, between other, setup a smb shared:

Andrea, Casa

 

Regarding System Logs it a shows:

In several periods of time

Thank you again

[JorgeB]

This is a problem, Samba is failing to start because of that secrest.tdb error, try deleting /boot/config/smbpasswd and reboot, note that I believe deleting that file will lose user stored passwords.

 

[dellorianes]

I proceed to delete smbpasswd and Reestart (I have to force the shootdown) the system.

Once reestarted, smb continous not working.

I checked that smbpasswd whas reseted (as you said without other users different than root).

There are logs I am getting and the diagnostics file:

 

 

nasdiego-diagnostics-20230511-1534.zip

[JorgeB]

@dlandonany idea what could cause the secrets.tdb fail to load?

[OneMeanRabbit]

Having this issue (smb all of a sudden not working) as well as constant hard locks, since upgrading to 12rc5, rolling back - even after restoring from backup before everything...will post my own thread once I power cycle and turn on syslog server 

[dlandon]

At a command line, what is the output of these commands:

ls -la /var/lib/

and

ls -la /var/lib/samba/

 

[dellorianes]

2 hours ago, dlandon said:

At a command line, what is the output of these commands:

ls -la /var/lib/

and

ls -la /var/lib/samba/

 

root@NASDiego:~# ls -la /var/lib/
total 16
drwxr-xr-x 14 root       root   280 Nov 20 22:27 ./
drwxr-xr-x 15 root       root   360 Dec 31  2019 ../
drwxr-xr-x  2 root       root    40 Oct  6  2022 arpd/
drwxr-xr-x  2 messagebus root    60 May 11 15:24 dbus/
drwxr-x---  2 root       root    40 Aug 28  2022 dhcpcd/
drwx--x---  1 root       root   254 May 11 16:18 docker/
drwxr-xr-x 10 root       root   220 Nov 20 22:26 libvirt/
drwxr-xr-x  6 rpc        rpc    220 May 11 16:18 nfs/
drwx------  7 root       root   140 May 11 15:25 nginx/
drwxrwxr-x  2 ntp        ntp     60 May 11 21:24 ntp/
drwxrwx---  2 root       apache 100 May 11 21:45 php/
drwxr-xr-x  6 root       root   160 Nov 20 22:26 pkgtools/
drwxr-xr-x  4 root       root    80 Nov 15 21:10 samba/
drwxr-xr-x  2 root       root    40 May  1  2022 swtpm-localca/
root@NASDiego:~# ls -la /var/lib/samba/
total 0
drwxr-xr-x  4 root root  80 Nov 15 21:10 ./
drwxr-xr-x 14 root root 280 Nov 20 22:27 ../
drwxrwx---  2 root root  40 Nov 15 21:10 bind-dns/
drwx------  3 root root 100 May 11 16:18 private/

 

Thank you again

[dlandon]

Someone please provide 6.12.rc5 diagnostics.  6.12 diagnostics include additional information that can help troubleshooting SMB issues.

[dellorianes]

Up

[JorgeB]

Like mentioned above upgrade to v6.12-rc5 and post new diags.

[dellorianes]

1 hour ago, JorgeB said:

Like mentioned above upgrade to v6.12-rc5 and post new diags.

Sorry, my English is not as well as I want but I undertooth in @dlandon post that someone (I didn't get alluded to due to I am not in v6.12-rc5) that posts 6.12-rc5 diagnostics to evaluate.

I also understand that the problems of @OneMeanRabbit started when he upgraded to 6.12-rc5.

 

So, being me in 6.11.5, are you recommending me to upgrade to 6.12-rc5?

 

Thank you

Edited May 15, 2023 by dellorianes

[JorgeB]

18 minutes ago, dellorianes said:

So, being me in 6.11.5, are you recommending me to upgrade to 6.12-rc5?

Yes, but if you didn't yet that try booting in safe mode first, if the same error is there upgrade.

[dellorianes]

8 hours ago, JorgeB said:

Yes, but if you didn't yet that try booting in safe mode first, if the same error is there upgrade.

Tryed safe mode and continued the same.

 

Upgraded to 6.12-rc5 and the same again. Find diagnostics attached.

 

May 15 22:47:17 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
May 15 22:47:17 NASDiego kernel: ACPI: Early table checksum verification disabled
May 15 22:47:17 NASDiego kernel: floppy0: no floppy controllers found
May 15 22:47:17 NASDiego kernel: Bluetooth: hci0: FW download error recovery failed (-19)
May 15 22:47:17 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP
May 15 22:47:26 NASDiego mcelog: failed to prefill DIMM database from DMI data
May 15 22:47:27 NASDiego smbd[1563]:   tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record
May 15 22:47:27 NASDiego smbd[1563]:   Failed to open /var/lib/samba/private/secrets.tdb
May 15 22:47:27 NASDiego smbd[1564]:   tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record
May 15 22:47:27 NASDiego smbd[1564]:   Failed to open /var/lib/samba/private/secrets.tdb
May 15 22:47:27 NASDiego smbd[1564]:   exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13
May 15 22:47:27 NASDiego winbindd[1577]:   tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record
May 15 22:47:27 NASDiego winbindd[1577]:   Failed to open /var/lib/samba/private/secrets.tdb
May 15 22:47:59 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204)

 

nasdiego-diagnostics-20230515-2252.zip

[dlandon]

Start by removing the smb-extra.conf entries:

 path = /mnt/disks/gDrive
      comment =
      browseable = yes
      # Public
      public = yes
      writeable = yes
      vfs objects =

That's a UD disk and UD can do the sharing for you.

[dellorianes]

9 hours ago, dlandon said:

Start by removing the smb-extra.conf entries:

 path = /mnt/disks/gDrive
      comment =
      browseable = yes
      # Public
      public = yes
      writeable = yes
      vfs objects =

That's a UD disk and UD can do the sharing for you.

 

After removing that, SMB server started to work again.

 

Fix common problems also warned me to change macvlan to ipvlan in Docker settings.

 

Thank you very much.

 

Now, I also have this warning after reset. Should I do something with them?

 

May 16 07:26:52 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
May 16 07:26:52 NASDiego kernel: ACPI: Early table checksum verification disabled
May 16 07:26:52 NASDiego kernel: floppy0: no floppy controllers found
May 16 07:26:52 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP
May 16 07:26:57 NASDiego mcelog: failed to prefill DIMM database from DMI data
May 16 07:27:28 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204)
May 16 07:27:55 NASDiego rpc.statd[10765]: Failed to read /var/lib/nfs/state: Success
May 16 07:28:05 NASDiego kernel: BTRFS info (device sdi1): using crc32c (crc32c-intel) checksum algorithm
May 16 07:28:35 NASDiego kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
May 16 07:28:40 NASDiego kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm

 

Edited May 16, 2023 by dellorianes

[JorgeB]

You can ignore those.