unburt Posted September 8, 2022 Share Posted September 8, 2022 (edited) Hi, I have been using Unraid for several years. Last night I updated from 6.10.2 to 6.10.3 and all seemed well. This morning I tried to set up a VPN tunnel. I had some issue where the server stopped responding so I powered it off. After power on, I was unable to reach the Web UI. Since I do not have a graphics card in the server, I powered it off again, installed a graphics card and attached a monitor to see the screen output. It was stuck in booting and I googled the last few output lines and found some suggested resolutions to delete vfio-pci.cfg from my USB (I did attempt passing through a GPU in the past and was not successful). I deleted the file and the system now boots and reaches the prompt and allows me to log in. However, I still cannot reach the web UI. Do you have any suggestions on troubleshooting from this point? I have checked the network cable, it is still attached. I unplugged it and rebooted Unraid, after it boots it shows that it has no ip address. After reconnecting the network cable, and rebooting Unraid, it shows its IP address. <edit> I forgot to describe some of the mucking around that I did: 1. Last night, I had made a backup of my USB on version 6.10.2 prior to updating. 2. After I experienced issues, I used a macbook and used dd to create a disk image of my USB (presumably on 6.10.3) 3. I have copied the contents of my 6.10.2 backup onto the flash drive. 4. I have since mounted the dd image on my macbook and copied the contents of the disk image onto the flash drive I am currently in a state where I can log in to the console but I cannot reach the web ui. </edit> Edited September 8, 2022 by unburt Quote Link to comment
unburt Posted September 8, 2022 Author Share Posted September 8, 2022 In another topic I learned about the `diagnostics` command to create the diagnostics zip file. I have attached it here. tower-diagnostics-20220908-1907.zip Quote Link to comment
unburt Posted September 8, 2022 Author Share Posted September 8, 2022 (edited) In the syslog, I've found that there are a large number of errors with `nmbd`, this seems to be related to samba? What might be the problem here or what steps could I take to resolve it? Sep 8 18:25:05 Tower avahi-daemon[2162]: Server startup complete. Host name is Tower.local. Local service cookie is 1101267073. Sep 8 18:25:06 Tower avahi-daemon[2162]: Service "Tower" (/services/ssh.service) successfully established. Sep 8 18:25:06 Tower avahi-daemon[2162]: Service "Tower" (/services/smb.service) successfully established. Sep 8 18:25:06 Tower avahi-daemon[2162]: Service "Tower" (/services/sftp-ssh.service) successfully established. Sep 8 18:25:27 Tower nmbd[2132]: [2022/09/08 18:25:27.246828, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Sep 8 18:25:27 Tower nmbd[2132]: ***** Sep 8 18:25:27 Tower nmbd[2132]: Sep 8 18:25:27 Tower nmbd[2132]: Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.152 Sep 8 18:25:27 Tower nmbd[2132]: Sep 8 18:25:27 Tower nmbd[2132]: ***** Sep 8 18:25:27 Tower nmbd[2132]: [2022/09/08 18:25:27.462024, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:25:27 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:25:27 Tower nmbd[2132]: [2022/09/08 18:25:27.462096, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:25:27 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:25:27 Tower nmbd[2132]: [2022/09/08 18:25:27.462161, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:25:27 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:25:27 Tower nmbd[2132]: [2022/09/08 18:25:27.462181, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:25:27 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:25:46 Tower login: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0) Sep 8 18:25:46 Tower login: ROOT LOGIN ON tty1 Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710253, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:27:37 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710313, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:27:37 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710371, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:27:37 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710388, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:27:37 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710432, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:27:37 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710449, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:27:37 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710486, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:27:37 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Sep 8 18:27:37 Tower nmbd[2132]: [2022/09/08 18:27:37.710501, 0] ../../source3/nmbd/nmbd_packets.c:1027(reply_netbios_packet) Sep 8 18:27:37 Tower nmbd[2132]: reply_netbios_packet: send_packet to IP 192.168.1.52 port 137 failed Sep 8 18:30:28 Tower nmbd[2132]: [2022/09/08 18:30:28.907945, 0] ../../source3/libsmb/nmblib.c:923(send_udp) Sep 8 18:30:28 Tower nmbd[2132]: Packet send failed to 192.168.1.52(137) ERRNO=Destination address required Edited September 8, 2022 by unburt Quote Link to comment
unburt Posted September 9, 2022 Author Share Posted September 9, 2022 If it is relevant, I believe a parity check may have been in progress. Quote Link to comment
unburt Posted September 9, 2022 Author Share Posted September 9, 2022 I have resolved my issue by following the Restore From Backup article from the manual with the backup I created prior to updating to 6.10.3. I used the USB Creator on OSX with my backup zip file. https://wiki.unraid.net/Manual/Changing_The_Flash_Device I did still have to remove vfio-pci.cfg from the restored files though. And I had to run the make bootable batch file but otherwise I seem to be back up and running. it is frustrating not really knowing what actually went wrong but I guess that is the beauty of having a backup. it doesn't really matter. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.