Tibbar

Well... Looks like I'm slowly answering my questions. I'm able to access the dockers in question by changing the "Network Type" to br0 and assigning an unused ip address. Still don't know why bridge mode is not working when it did before.

This is from Syslog. Can someone please explain whats all this entering blocking, forwarding, disabled state is : " Sep 26 21:03:32 Tower kernel: device vethbb043b0 entered promiscuous mode Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:32 Tower kernel: docker0: port 2(vethbb043b0) entered disabled state Sep 26 21:03:33 Tower kernel: eth0: renamed from vethf963646 Sep 26 21:03:33 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbb043b0: link becomes ready Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered blocking state Sep 26 21:03:33 Tower kernel: docker0: port 2(vethbb043b0) entered forwarding state Sep 26 21:03:35 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface vethbb043b0.IPv6 with address fe80::c884:cbff:fe8f:fdb5. Sep 26 21:03:35 Tower avahi-daemon[4528]: New relevant interface vethbb043b0.IPv6 for mDNS. Sep 26 21:03:35 Tower avahi-daemon[4528]: Registering new address record for fe80::c884:cbff:fe8f:fdb5 on vethbb043b0.*. Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:24 Tower kernel: device veth929c61e entered promiscuous mode Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:24 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:25 Tower kernel: eth0: renamed from veth192b2ad Sep 26 21:07:25 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth929c61e: link becomes ready Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered blocking state Sep 26 21:07:25 Tower kernel: docker0: port 7(veth929c61e) entered forwarding state Sep 26 21:07:26 Tower avahi-daemon[4528]: Joining mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower avahi-daemon[4528]: New relevant interface veth929c61e.IPv6 for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Registering new address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.*. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: veth192b2ad: renamed from eth0 Sep 26 21:07:26 Tower avahi-daemon[4528]: Interface veth929c61e.IPv6 no longer relevant for mDNS. Sep 26 21:07:26 Tower avahi-daemon[4528]: Leaving mDNS multicast group on interface veth929c61e.IPv6 with address fe80::fc1d:29ff:fea6:1f94. Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower kernel: device veth929c61e left promiscuous mode Sep 26 21:07:26 Tower kernel: docker0: port 7(veth929c61e) entered disabled state Sep 26 21:07:26 Tower avahi-daemon[4528]: Withdrawing address record for fe80::fc1d:29ff:fea6:1f94 on veth929c61e.

Just tried unplugging and plugging back network cable rebooting my two network switches. That didn't do anything. btw pfsense runs on 4 port network switch that is passed through to VM. tower-diagnostics-20210926-1155.zip tower-syslog-20210926-1554.zip

Hello. Need help. Yesterday I was redoing some network cabling (disconnecting cable, restarting server etc) and today I can not access any of my dockers that run in bridge mode. I can access Plex and HomeAssistent that run in "Host" mode. I didnt do any changes to Unraid until it all stoped working at that point I upgraded Unraid from 6.8.2 to 6.9.2. Same effect, still can not access Rutorrent and Krusader. RuTorrent : 172.17.0.2:51413/TCP192.168.1.122:51413 172.17.0.2:6881/UDP192.168.1.122:6881 172.17.0.2:9090/TCP192.168.1.122:9090 Krusader: 172.17.0.5:6080/TCP192.168.1.122:6080 Both docker are running but I can not access WebUI. btw. I'm running pfsense as my router in "VM"

Big THANK YOU to @JorgeB. It worked like a charm.Was able to retrieve all the data. Linux 4.19.98-Unraid. Last login: Tue Apr 20 19:19:53 -0400 2021 on /dev/pts/0. root@Tower:~# ddrescue -f /dev/nvme0n1 /dev/sdo /boot/ddrescue.log GNU ddrescue 1.23 Press Ctrl-C to interrupt ipos: 500107 MB, non-trimmed: 0 B, current rate: 1099 MB/s opos: 500107 MB, non-scraped: 0 B, average rate: 113 MB/s non-tried: 0 B, bad-sector: 0 B, error rate: 0 B/s rescued: 500107 MB, bad areas: 0, run time: 1h 13m 19s pct rescued: 100.00%, read errors: 0, remaining time: n/a time since last successful read: n/a Finished root@Tower:~# Still don't know if that drive is completely dead or not. Again Thank You.

Shit. Thanks though.

Response I get is : mount: /root/Samsung: mount(2) system call failed: No data available.

Thanks for reply. How do I mount it in read-only mode? It is Unassigned drive that was hosting my VM's. Thanks.

hello. This morning we had couple power fails and for some reason my UPS didnt protect the server. After work I check the system and non of my vms are working. They were all located on Unassigned drive (Ultra M.2). Can not mount the drive and drive log says: Apr 19 17:45:06 Tower unassigned.devices: Adding disk '/dev/nvme0n1p1'... Apr 19 17:45:06 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/nvme0n1p1' '/mnt/disks/Samsung_SSD_970' Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): Mounting V5 Filesystem Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 488502266 Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 488504266 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): xfs_do_force_shutdown(0x1) called from line 1270 of file fs/xfs/xfs_buf.c. Return address = 0000000089f929dd Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): I/O Error Detected. Shutting down filesystem Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): Please umount the filesystem and rectify the problem(s) Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): metadata I/O error in "xlog_bwrite" at daddr 0x1d1df3ba len 8192 error 61 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): failed to locate log tail Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): log mount/recovery failed: error -61 Apr 19 17:45:06 Tower kernel: XFS (nvme0n1p1): log mount failed Apr 19 17:45:06 Tower kernel: print_req_error: critical medium error, dev nvme0n1, sector 0 Apr 19 17:45:06 Tower unassigned.devices: Mount of '/dev/nvme0n1p1' failed: 'mount: /mnt/disks/Samsung_SSD_970: mount(2) system call failed: No data available. ' Is that drive fried and data lost ar anything could be done? Any help very appreciated. Thanks tower-diagnostics-20210419-1735.zip

Can anyone help me with this?

Anyone knows how to update Mono in this docker?

Ok. Thanks, that clarifies thinks a bit of who to ask for help.

Hello, anyone?

Hello. I,ve been running NodeLink docker on my server for quite a while. Recently it updated itself to new version and stopped working. Apparently it has to do with outdated mono version on unraid. Nodlink reports Mono version: 4.2.1 (Debian 4.2.1.102+dfsg2-7ubuntu4) and Mono version: Recommend moving to >= 4.6. Is there anyone here that could help me with that? Thanks. I'm on Unraid 6.6.3. Apparently Mono needs to be updated in a docker- Anyone?

Hi. Just tried installing nodelink on unraid ver 6.3.5. Looks like it installed OK but I can not get to webui. How do I set it up. Thanks P.S here is its log file Log for_ NodeLink.html