My unRAID server's shares don't appear in the network. Not even the server appears in the network tab of my Windows computers that used to have connected network drives that are now offline. I can, however, access the server's root directory via its IP; here, no shares are being shown and manually going into a share via its path of `\\IP\PATH` does not work.

 

This behavior follows a restart of the server after having solved a different issue a couple of days ago. As far as I am aware, no settings beyond removing the cache SSD from accidentally being passed through to a VM were changed.

 

I have checked from multiple Windows and one Android device. The server is not visible in the network via SMB. SSH and any other applications (running lots of Docker containers) are working though. Only SMB seems to be faulty.

 

Thanks.

tower-diagnostics-20240510-1251.zip

Edited May 10, 20242 yr by DesertCookie
added smb and shares settiings pictures

Check in the settings of the various shares that exporting them is enabled.

In addition to what @Kilrah said, check this:

 

Then go to each share (under the SHARES tab) that you want to access, and click on that share.  Then look for this section:

 

Note that I have both NFS and SMB enabled.  On this share, I am exporting the share using only SMB and not NFS. 

 

 

 

Edited May 10, 20242 yr by Frank1940

1 hour ago, Kilrah said:

Check in the settings of the various shares that exporting them is enabled.

19 minutes ago, Frank1940 said:

In addition to what @Kilrah said, check this:

 

Thanks, forgot to add that I made sure my configurations were still as they were beforehand. I added some pictures to the OG post.

I have also attempted to create a new share that's fully public, in case the existing share's configuration was somehow borked. That share too was inaccessible via the network.

Edited May 10, 20242 yr by DesertCookie

I looked at your syslog and found this:

May  9 16:00:09 Tower kernel: pcieport 0000:00:1c.4: AER: Multiple Corrected error message received from 0000:05:00.0
May  9 16:00:09 Tower kernel: atlantic 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May  9 16:00:09 Tower kernel: atlantic 0000:05:00.0:   device [1d6a:d107] error status/mask=00000041/0000a000
May  9 16:00:09 Tower kernel: atlantic 0000:05:00.0:    [ 0] RxErr                 
May  9 16:00:09 Tower kernel: atlantic 0000:05:00.0:    [ 6] BadTLP                
May  9 18:50:26 Tower kernel: ------------[ cut here ]------------
May  9 18:50:26 Tower kernel: WARNING: CPU: 1 PID: 11584 at net/netfilter/nf_conntrack_core.c:1210 __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
May  9 18:50:26 Tower kernel: Modules linked in: xt_mark xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_net tun vhost vhost_iotlb tap macvlan xt_nat xt_tcpudp veth xt_conntrack nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype br_netfilter xfs xt_MASQUERADE ip6table_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs af_packet 8021q garp mrp bridge stp llc bonding tls i915 intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iosf_mbi drm_buddy i2c_algo_bit ttm drm_display_helper drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryptd btusb mei_hdcp mei_pxp intel_cstate btrtl btbcm btintel intel_gtt mei_me i2c_i801 nvme agpgart i2c_smbus
May  9 18:50:26 Tower kernel: gigabyte_wmi intel_wmi_thunderbolt wmi_bmof bluetooth intel_uncore atlantic i2c_core ahci mei nvme_core cdc_acm ecdh_generic libahci syscopyarea ecc sysfillrect sysimgblt fb_sys_fops thermal fan video tpm_crb tpm_tis tpm_tis_core wmi tpm backlight intel_pmc_core acpi_pad acpi_tad button unix
May  9 18:50:26 Tower kernel: CPU: 1 PID: 11584 Comm: kworker/u24:11 Tainted: P           O       6.1.79-Unraid #1
May  9 18:50:26 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z590 AORUS MASTER/Z590 AORUS MASTER, BIOS F8a 01/24/2022
May  9 18:50:26 Tower kernel: Workqueue: events_unbound macvlan_process_broadcast [macvlan]
May  9 18:50:26 Tower kernel: RIP: 0010:__nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
May  9 18:50:26 Tower kernel: Code: 44 24 10 e8 e2 e1 ff ff 8b 7c 24 04 89 ea 89 c6 89 04 24 e8 7e e6 ff ff 84 c0 75 a2 48 89 df e8 9b e2 ff ff 85 c0 89 c5 74 18 <0f> 0b 8b 34 24 8b 7c 24 04 e8 18 dd ff ff e8 93 e3 ff ff e9 72 01
May  9 18:50:26 Tower kernel: RSP: 0018:ffffc9000007cd98 EFLAGS: 00010202
May  9 18:50:26 Tower kernel: RAX: 0000000000000001 RBX: ffff88813751d600 RCX: 56e1aa9c88d044be
May  9 18:50:26 Tower kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff88813751d600
May  9 18:50:26 Tower kernel: RBP: 0000000000000001 R08: 5231d8afbbe07d96 R09: 1112f27a472757eb
May  9 18:50:26 Tower kernel: R10: 300dbacebc2f7fa6 R11: ffffc9000007cd60 R12: ffffffff82a16f40
May  9 18:50:26 Tower kernel: R13: 000000000001ca78 R14: ffff88814ff0c500 R15: 0000000000000000
May  9 18:50:26 Tower kernel: FS:  0000000000000000(0000) GS:ffff8888a0240000(0000) knlGS:0000000000000000
May  9 18:50:26 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May  9 18:50:26 Tower kernel: CR2: 00000c44a409d000 CR3: 0000000645d34001 CR4: 0000000000772ee0
May  9 18:50:26 Tower kernel: PKRU: 55555554
May  9 18:50:26 Tower kernel: Call Trace:
May  9 18:50:26 Tower kernel: <IRQ>
May  9 18:50:26 Tower kernel: ? __warn+0xab/0x122
May  9 18:50:26 Tower kernel: ? report_bug+0x109/0x17e
May  9 18:50:26 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
May  9 18:50:26 Tower kernel: ? handle_bug+0x41/0x6f
May  9 18:50:26 Tower kernel: ? exc_invalid_op+0x13/0x60
May  9 18:50:26 Tower kernel: ? asm_exc_invalid_op+0x16/0x20
May  9 18:50:26 Tower kernel: ? __nf_conntrack_confirm+0xa4/0x2b0 [nf_conntrack]
May  9 18:50:26 Tower kernel: ? __nf_conntrack_confirm+0x9e/0x2b0 [nf_conntrack]
May  9 18:50:26 Tower kernel: ? nf_nat_inet_fn+0x123/0x1a8 [nf_nat]
May  9 18:50:26 Tower kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack]
May  9 18:50:26 Tower kernel: nf_hook_slow+0x3a/0x96
May  9 18:50:26 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164
May  9 18:50:26 Tower kernel: NF_HOOK.constprop.0+0x79/0xd9
May  9 18:50:26 Tower kernel: ? ip_protocol_deliver_rcu+0x164/0x164
May  9 18:50:26 Tower kernel: __netif_receive_skb_one_core+0x77/0x9c
May  9 18:50:26 Tower kernel: process_backlog+0x8c/0x116
May  9 18:50:26 Tower kernel: __napi_poll.constprop.0+0x28/0x124
May  9 18:50:26 Tower kernel: net_rx_action+0x159/0x24f
May  9 18:50:26 Tower kernel: __do_softirq+0x126/0x288
May  9 18:50:26 Tower kernel: do_softirq+0x7f/0xab
May  9 18:50:26 Tower kernel: </IRQ>
May  9 18:50:26 Tower kernel: <TASK>
May  9 18:50:26 Tower kernel: __local_bh_enable_ip+0x4c/0x6b
May  9 18:50:26 Tower kernel: netif_rx+0x52/0x5a
May  9 18:50:26 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
May  9 18:50:26 Tower kernel: ? _raw_spin_unlock+0x14/0x29
May  9 18:50:26 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]
May  9 18:50:26 Tower kernel: process_one_work+0x1a8/0x295
May  9 18:50:26 Tower kernel: worker_thread+0x18b/0x244
May  9 18:50:26 Tower kernel: ? rescuer_thread+0x281/0x281
May  9 18:50:26 Tower kernel: kthread+0xe4/0xef
May  9 18:50:26 Tower kernel: ? kthread_complete_and_exit+0x1b/0x1b
May  9 18:50:26 Tower kernel: ret_from_fork+0x1f/0x30
May  9 18:50:26 Tower kernel: </TASK>
May  9 18:50:26 Tower kernel: ---[ end trace 0000000000000000 ]---
May  9 20:19:15 Tower kernel: pcieport 0000:00:1c.4: AER: Multiple Corrected error message received from 0000:05:00.0
May  9 20:19:15 Tower kernel: atlantic 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May  9 20:19:15 Tower kernel: atlantic 0000:05:00.0:   device [1d6a:d107] error status/mask=00000041/0000a000
May  9 20:19:15 Tower kernel: atlantic 0000:05:00.0:    [ 0] RxErr                 
May  9 20:19:15 Tower kernel: atlantic 0000:05:00.0:    [ 6] BadTLP                
May  9 20:41:35 Tower kernel: TCP: request_sock_TCP: Possible SYN flooding on port 9001. Sending cookies.  Check SNMP counters.
May  9 23:33:10 Tower kernel: pcieport 0000:00:1c.4: AER: Corrected error message received from 0000:05:00.0
May  9 23:33:10 Tower kernel: atlantic 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May  9 23:33:10 Tower kernel: atlantic 0000:05:00.0:   device [1d6a:d107] error status/mask=00000001/0000a000
May  9 23:33:10 Tower kernel: atlantic 0000:05:00.0:    [ 0] RxErr                 
May 10 01:12:25 Tower kernel: pcieport 0000:00:1c.4: AER: Corrected error message received from 0000:05:00.0
May 10 01:12:25 Tower kernel: atlantic 0000:05:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
May 10 01:12:25 Tower kernel: atlantic 0000:05:00.0:   device [1d6a:d107] error status/mask=00000001/0000a000
May 10 01:12:25 Tower kernel: atlantic 0000:05:00.0:    [ 0] RxErr       

 

Not normal.  I am going to ping @JorgeB and hopefully he can provide some insight. 

For the macvlan call traces change to ipvlan and reboot, for the PCIe errors see if this helps:

https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009

 

But not of these should help with the shares issue.

9 minutes ago, JorgeB said:

For the macvlan call traces change to ipvlan and reboot, for the PCIe errors see if this helps: [...]

 

Did both of these. Had enabled macvlan after some issues with Docker containers being unable to see each other; that seemed to fix it back then.

tower-diagnostics-20240510-1851.zip