ViperSuicide

Members
  • Posts

    27
  • Joined

  • Last visited

Everything posted by ViperSuicide

  1. 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
  2. Can you post the link to the official thread so I can follow?
  3. Upgrade complete. I’ll leave this video here in case it helps anyone else regarding the upgrade process
  4. 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.
  5. Do you know if there is a fix for this yet? Im still getting this error with VM backup installed on v6.9.1
  6. Thanks. Any tips on finding out why it won’t unmount so I can avoid having to pull the power?
  7. 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
  8. 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
  9. 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?
  10. 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.
  11. 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
  12. 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)
  13. 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.
  14. Thank you Jorge. I found that one too but I don’t have any Windows VMs. Only 2x Ubuntu VMs. shouldnt setting the cache on a folder to “Yes” move all the data to the array and leave only sym links on the cache? Either mover is not working or my understanding of how it works is incorrect. Probably the later but I need some help so I can move the VMs and dockers back to the cache and stop the warnings.
  15. I got a warning saying cache was almost full so i changed some of the shares to "Yes" so mover could tidy up. I'd rather not have the VMs running on the array and should have the space on the ssd if they are only using 51G. But it carried on filling up. Now i have moved all the shares to "yes" as im almost out of space but mover is doing nothing. Just says its finished a few seconds later but the folders/files are all still there on /mnt/cache/ Also du -sh shows only 72gb when GUI says 113Gb (out of 120gb) Some other posts mentioned Windows VMs taking more space than the vdisk size shows but i think my problem is just that mover is not actually moving anything so the drive just fills up. root@Tower:~# du -sh /mnt/cache/ 72G /mnt/cache/ root@Tower:~# du -sh /mnt/cache/vms/ 51G /mnt/cache/vms/ root@Tower:~# du -sh /mnt/cache/vms/ispconfig.qcow2 41G /mnt/cache/vms/ispconfig.qcow2 root@Tower:~# du -sh /mnt/cache/vms/scudvpn.qcow2 9.9G /mnt/cache/vms/scudvpn.qcow2 The first VM is 100Gb but the actual size is only 41G ispconfig started 4 8192M 1 / 100G VNC:5901 ON DISK DEVICES BUS CAPACITY ALLOCATION /mnt/user/vms/ispconfig.qcow2 VirtIO 100G 41G scudvpn started 4 2048M 1 / 10G VNC:5900 ON DISK DEVICES BUS CAPACITY ALLOCATION /mnt/user/vms/scudvpn.qcow2 VirtIO 10G 10G Version: 6.8.3 Server Description Registration UptimeTower • 192.168.0.18 Media server Unraid OS Basic 25 days, 21 hours, 38 minutes NAME COMMENT SMB NFS AFP CACHE SIZE FREE VIEW amy Private - - No Compute... 556 GB Browse /mnt/user/amy appdata application data - - - Yes Compute... 564 GB Browse /mnt/user/appdata domains saved VM instances - - - No Compute... 564 GB Browse /mnt/user/domains isos ISO images Public - - Yes Compute... 556 GB Browse /mnt/user/isos Media Public - - No Compute... 556 GB Browse /mnt/user/Media share Private - - No Compute... 556 GB Browse /mnt/user/share system system data - - - Yes Compute... 564 GB Browse /mnt/user/system timemachine Mac Backup Public - - No Compute... 556 GB Browse /mnt/user/timemachine vms Private - - Yes Compute... 564 GB Is it safe to set all the folders to "No". Manually rm -rf /mnt/cache/ and then set the VM and appdata back to "Prefer"? I have backups of all VMs and appdata dockers just in case. Thank you in advance.
  16. Ah I see. Thanks. I’ll give it a try. I’ve set two of the folders that were Prefer to Yes and pressed the Move button. hopefully that will do the trick.
  17. hi Johnny, thanks for the post. I want do move data “off” the cache. Changing the folders to “yes” would move data “on” to the cache. the point of changing the folder not to use the cache was that when I do a mv on the cli the mover doesn’t undo my work and put it back on. also this doesn’t explain why the cache is showing as nearly full when the cli shows it’s only half full.
  18. My cache drive space is reporting high usage so I tried to change some of the folders to not use cache and deleted some unneeded files but the usage is still high. if I log into the cli and run du -sh on /mnt/cache the value shows 20gb difference. is there a way to refresh or force it to recheck or do I need to reboot? im on unraid version 6.8.3 and have two 120gb SSDs as the cache. anonymised diags attached tower-diagnostics-20200606-1834.zip
  19. What’s the use of anonymising the data when I’m posting as Rik Bignell.
  20. “Ifyou let me know which other parts of the diagnostic zip you want to see i'll post them? Posting the whole zip would expose a large amount of secure info.”
  21. Just tried the backup again and its frozen again. Nothing in the syslog other than a timeout when i try and load the unassigned devices page root@Tower:~# tail -f /var/log/syslog May 23 09:46:32 Tower nginx: 2020/05/23 09:46:32 [error] 6881#6881: *2034262 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.23, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.18", referrer: "http://192.168.0.18/Main" And via ssh the /mnt/disks ls hangs root@Tower:~# ls -la /mnt/disks/ ---HANGS--- As soon as i unplug the usb drive it all returns to normal. May 23 10:02:46 Tower kernel: usb 3-2.1: USB disconnect, device number 5
  22. These are the errors im getting in syslog. If you let me know which other parts of the diagnostic zip you want to see i'll post them? Posting the whole zip would expose a large amount of secure info. May 16 19:32:35 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=446 count=1 if=/dev/sdk 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 5s! May 16 19:33:16 Tower kernel: mdcmd (39): set md_num_stripes 1280 May 16 19:33:16 Tower kernel: mdcmd (40): set md_queue_limit 80 May 16 19:33:16 Tower kernel: mdcmd (41): set md_sync_limit 5 May 16 19:33:16 Tower kernel: mdcmd (42): set md_write_method May 16 19:33:16 Tower kernel: mdcmd (43): set spinup_group 0 0 May 16 19:33:16 Tower kernel: mdcmd (44): set spinup_group 1 0 May 16 19:33:16 Tower kernel: mdcmd (45): set spinup_group 2 0 May 16 19:33:37 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=449 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:40 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=450 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:42 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=451 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 16 19:33:50 Tower unassigned.devices: Error: shell_exec(/usr/bin/dd bs=1 count=1 skip=460 if=/dev/sde 2>/dev/null | /bin/sum | /bin/awk '{print }') took longer than 2s! May 19 21:28:26 Tower ntfs-3g[12391]: Version 2017.3.23 integrated FUSE 27 May 20 19:30:04 Tower ntfs-3g[4890]: Version 2017.3.23 integrated FUSE 27 May 21 23:39:23 Tower nginx: 2020/05/21 23:39:23 [error] 6881#6881: *1760428 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.23, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.0.18", referrer: "http://192.168.0.18/Main" May 21 23:45:24 Tower kernel: traps: lsof[13685] general protection ip:148d174bbb8e sp:80f7be55bc258d0f error:0 in libc-2.30.so[148d1749c000+16b000]
  23. Hi, I have an issue which other seem to have reported too where unassigned devices section becomes unresponsive and smb shares to usb devices hang. Usually when copying a large amount of data to an smb share of a usb disk. Other shares on the main array are fine when this happens. it means I currently can’t backup my PC as there is not enough space on the array to complete the backup so needs to go direct to the usb share. When it hangs the fix is to unplug the usb and remount. When it stops the wave symbol on the whole unassigned devices section just shows loading forever and the smb shares do not respond but via ssh the usbs are still mounted and accessible. please help.