ViperSuicide

Sorry for the new post as i realise there are some other similar posts on this but i have followed the other instructions with no luck. I had to rebuild my docker.img due to corruption which meant reinstalling the containers. Everything went fine up to the point i reinstalled openvpn. Im using the same settings as before and even have another unraid server using the same setup so i know the method works. I have the openvpn container on br0 with a set ip then have set the other containers to network None and the extra params to --net=container:openvpn I add the port say 9117 for the container in the openvpn xml and save. Now i cannot connect to those containers. Just says connection timed out in the browser like its not listening on that port. I cannot see anything in the logs on the containers or in the system log that could suggest why its not working. The vpn is logged in and i can ping out so the openvpn container has connectivity. One thing i noticed is that before im sure it used to show something similar to this in the port mapping column: :9117/TCP:9117 now thats empty. How can i troubleshoot it? What do people think is wrong? Any tips? tower-diagnostics-20240130-1743.zip

Can you post the link to the official thread so I can follow?

Upgrade complete. I’ll leave this video here in case it helps anyone else regarding the upgrade process

Is this the right place for an unbalance feature request? Can future versions be built as a plug-in that is available natively via the unraid gui rather that a web plugin that only works on another port? as the cert doesn’t work I have to use safari as chrome won’t let me load the page with a cert warning. it would be so handy just to have this available via the unraid gui. I know this would prob be a lot of work so just an idea.

Do you know if there is a fix for this yet? Im still getting this error with VM backup installed on v6.9.1

Thanks. Any tips on finding out why it won’t unmount so I can avoid having to pull the power?

Here you go. Usb wouldn’t unmount so I pulled the power. Then when I plugged it back in Unraid couldn’t mount it again showing errors in syslog that it was already mounted. tower-diagnostics-20210319-0904.zip

Diagnostics are in the link. Appreciate your help.

I have a usb disk that won’t always unmount. If I pull the power on the usb drive I have issues mounting again and have to reboot the server. the usb works fine in other pcs and macs and unmounts clean from those. I only use the usb for backups and then usually unmount and disconnect. I posted about it here but didn’t really get much of a suggestion to a fix

Stopped the VM and rebooted and all seems ok now. I have the unraid upgrade to do next. 6.8.3 to 6.9.1. Is there anything i need to be aware of before doing the upgrade? I have a backup of the usb. Is it quick and simple like the plugin upgrades just with a reboot? Then if there is an issue, is the rollback just copy the backup usb files over the top of the new and reboot again?

What is the safest way to reboot? Manually stop Vms and dockers first or just use the reboot option in the gui without manually stopping anything? I dont reboot very often unless i have to.

Hi, I use a usb drive to backup my share once a week. Its a usb i use for other machines to take backups. The usb drive has been fine up to now and still works in the other machines but in the last few days it wont mount on unraid saying in the log its already mounted. I think i must have disconnected it previously without a clean unmount. Is there a way of fixing this without rebooting the server? Ive tested my other usb drive which is the same usb model and that one mounts fine on unraid. Im still on 6.8.3 at the moment on my HPZ620. Diags attached. Mar 18 16:42:40 Tower kernel: usb 3-2.1: new high-speed USB device number 10 using xhci_hcd Mar 18 16:42:40 Tower kernel: usb-storage 3-2.1:1.0: USB Mass Storage device detected Mar 18 16:42:40 Tower kernel: scsi host0: usb-storage 3-2.1:1.0 Mar 18 16:42:41 Tower kernel: scsi 0:0:0:0: Direct-Access Seagate Expansion Desk 0915 PQ: 0 ANSI: 6 Mar 18 16:42:41 Tower kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0 Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] 11721045167 512-byte logical blocks: (6.00 TB/5.46 TiB) Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08 Mar 18 16:42:53 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 18 16:42:54 Tower kernel: sda: sda1 sda2 Mar 18 16:42:54 Tower kernel: sd 0:0:0:0: [sda] Attached SCSI disk Mar 18 16:42:54 Tower rc.diskinfo[8929]: SIGHUP received, forcing refresh of disks info. Mar 18 16:42:54 Tower unassigned.devices: Adding disk '/dev/sda1'... Mar 18 16:42:54 Tower unassigned.devices: No filesystem detected on '/dev/sda1'. Mar 18 16:42:54 Tower unassigned.devices: Partition 'ST6000DM003-2CY186_ZF302PAK-part1' cannot be mounted. Mar 18 16:42:54 Tower unassigned.devices: Adding disk '/dev/sda2'... Mar 18 16:42:54 Tower unassigned.devices: Drive '/dev/sda2' already mounted. Mar 18 16:47:45 Tower kernel: usb 3-2.1: USB disconnect, device number 10 Mar 18 16:47:45 Tower kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Mar 18 16:47:45 Tower kernel: sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00 Mar 18 16:47:45 Tower rc.diskinfo[8929]: SIGHUP received, forcing refresh of disks info. tower-diagnostics-20210319-0904.zip

This is happening to me too on v6.8.3 i followed the guy above who got the process id from top, killed it and typed wsdd to restart. The process had been running for a while. It seems to have cleared the issue for now but I guess the only perm fix is to disable WSD in the samba settings (need to stop the array to change it)

That did the trick. Thanks.

Ah that’s prob why then. Let me try mover again with all the VMs and Dockers turned off and see what happens. Thanks, I’ll report back later.