schwabelbauch

Along some other dockers i use pihole as my local dns/dhcp/... and OpenVPN. Some month ago i had the problem, that i was unable to access my pihole dns if i remotely connect via openvpn into my local network. The problem was, that i give pihole a different ip than my unraid tower. I found a solution in this forum with installing a second nic, some little configurations and everything worked. Had a new entry in the container Network Type-selectbox to select the "second nic". Sadly i had to fully reinstall unraid this weekend (was my own stupid fault) and now i'm unable to find this good solution again. Can somebody help me finding this solution or give me some advise how to use a second nic with docker

Everything works good except accessing dockers which have an custom IP. I use e.g. pihole docker as my DNS server with a custom IP via network type custom: br0. Any clue what i have change/add on my default OpenVPN config to access dockers with custom ip? Edit: I fixed my issue with this post by adding a second network card:

Happy Birthday

Sadly i did some reboots after rebuild. So the diagnostics are lost? Next time i will create much more logs and diags. But i have successfully restored all my missing data from my backups. For me, this case is closed.

Thank you for your help! It worked, but almost al of my data on this disk is missing Don't know yet if data from other drives a missing too

Somebody any idea? Is this disk and all its data lost?

Okay... strange... The old disk lie on my right side. It was the only 2TB disk inside my tower. I removed this disk and put the new 3TB disk on the exact same place (same SATA port). I executed the sudo blkid command and got the following result: /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs" /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" TYPE="vfat" /dev/sdb1: UUID="83108b31-affc-4898-8734-4b45d1684720" TYPE="xfs" PARTUUID="85bdf95a-9ac2-42b4-ae2c-cb3bc8940e91" /dev/sdc1: UUID="f8a788eb-e4b8-4f8b-8a7d-5bd1da90c7db" TYPE="xfs" PARTUUID="0b3f26b0-6319-4ab5-8c5c-0df05922ded7" /dev/sdd1: UUID="83108b31-affc-4898-8734-4b45d1684720" TYPE="xfs" PARTUUID="5d099f93-d623-4023-b765-08b6219520bb" /dev/sde1: UUID="81e134b3-14cd-4b14-9aca-4b78d0192fef" UUID_SUB="7e186c91-33bc-4262-a982-701bd45f1d9c" TYPE="btrfs" /dev/sdg1: UUID="f8a788eb-e4b8-4f8b-8a7d-5bd1da90c7db" TYPE="xfs" PARTUUID="1a106826-f4b9-4ba1-aeb9-fca623d197d6" /dev/md1: UUID="f8a788eb-e4b8-4f8b-8a7d-5bd1da90c7db" TYPE="xfs" /dev/md2: UUID="83108b31-affc-4898-8734-4b45d1684720" TYPE="xfs" /dev/md3: UUID="83108b31-affc-4898-8734-4b45d1684720" TYPE="xfs" /dev/sdf1: PARTUUID="41578220-ea80-4b75-935d-136577bd933d" If i read the result correctly, my new disk has the exact same UUID like my disk2. But disk2 was never faulty and runs without any errors. Something is really strange. Can i change the UUID of the new disk3? Will it fix my problem? Or did unRaid restored the wrong disk data to my new disk3?

I tried xfs_repair via webinterface without any parameter and did a reboot after it was finished. Still the same error. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 0 - agno = 2 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done

unRaid Version: 6.7.2 Two days ago my unRaid told me "Unmountable: No file system" for disk3. Because this disk was an really old 2TB one (8y) i thought its broken. So i replaced it with a new 3TB disk like it was described on this page https://wiki.unraid.net/Replacing_a_Data_Drive. After 12Hours of restoring the disk, i got the same error for the brand new disk3: "Unmountable: No file system" I tried a restart, but still them same error. xfs_repair -n produce this output: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 2 - agno = 0 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Can somebody help me? tower-syslog-20190710-1530.zip tower-diagnostics-20190710-1546.zip

I have given this docker in my unRaid (6.6.7) a different IP (Networktype: custom br0). But for now, it is ignoring the option 'WEB Port for GUI'. How can i set a custom IP and WebUI port (80)?