chuckbucket
Members
-
Joined
-
Last visited
-
Issue is resolved. I had the br0 network disabled. I could not find how to enable it so I created a custom network which overlapped br0 once it was enabled. Solution: I removed the custom network. disabled Docker. disabled IPv4 custom network. saved. enabled IPv4 custom network. saved. Enabled Docker. saved, Here are the settings that worked: Thank you for the help Opawesome.
-
yes. they all look the same. I had the br0 disabled on the docker settings page, but have since enabled it. I have shut down the array multiple times toggled bridging mode several times.
-
Thank you. I am thinking the issue is with br0 interface. Even though it is now enabled, I cannot select br0. Unraid Docker Settings: Pihole Docker settings:
-
I am having issues assigning a static IP to my PiHole docker container. I have tried following several different PiHole guides. Either something is wrong with my network settings or all PiHole guides are out of date. The custom IP is on the left, my unraid server IP is on the right. if I understand correctly 192.168.2.1 should be on both sides. I cannot connect to it with any of the ip addresses/port below. Another note is that br0 is not available as a custom network option. I turned bridging off and on, that did not bring it back, so I created a new custom network. Thank you. mcp-diagnostics-20240223-1017.zip
-
I am unable to mount my ZFS pool, starting the array in Maintenance mode work. Running in safemode sometimes work. My system has been less stable since upgrading to 6.12.x, but has improved since I changed docker to use ipvlan. Things were running well until yesterday, the system took a hard crash and have been unable to mount the ZFS shares since. The diagnostic tool did not grab my entire log file, so I manually added it to the zip. Jul 7 02:07:24 MCP emhttpd: mounting /mnt/cache Jul 7 02:07:24 MCP emhttpd: shcmd (176): mkdir -p /mnt/cache Jul 7 02:07:24 MCP emhttpd: shcmd (177): /usr/sbin/zpool import -N -o autoexpand=on -d /dev/nvme0n1p1 -d /dev/nvme1n1p1 -d /dev/sdf1 12239425747297594656 cache Jul 7 02:07:32 MCP kernel: PANIC: zfs: removing nonexistent segment from range tree (offset=9901bf8881000 size=5008000) Jul 7 02:07:32 MCP kernel: Showing stack for process 3781 Jul 7 02:07:32 MCP kernel: CPU: 5 PID: 3781 Comm: metaslab_group_ Tainted: P O 6.1.36-Unraid #1 Jul 7 02:07:32 MCP kernel: Hardware name: Gigabyte Technology Co., Ltd. H470M DS3H/H470M DS3H, BIOS F22 11/23/2021 Jul 7 02:07:32 MCP kernel: Call Trace: Jul 7 02:07:32 MCP kernel: <TASK> Jul 7 02:07:32 MCP kernel: dump_stack_lvl+0x44/0x5c Jul 7 02:07:32 MCP kernel: vcmn_err+0x86/0xc3 [spl] Jul 7 02:07:32 MCP kernel: ? put_cpu_partial+0x6e/0x9f Jul 7 02:07:32 MCP kernel: ? bt_grow_leaf+0xc3/0xd6 [zfs] Jul 7 02:07:32 MCP kernel: ? bt_grow_leaf+0xc3/0xd6 [zfs] Jul 7 02:07:32 MCP kernel: ? zfs_btree_find_in_buf+0x4c/0x94 [zfs] Jul 7 02:07:32 MCP kernel: ? zfs_btree_find_in_buf+0x4c/0x94 [zfs] Jul 7 02:07:32 MCP kernel: zfs_panic_recover+0x6b/0x86 [zfs] Jul 7 02:07:32 MCP kernel: range_tree_remove_impl+0xc3/0x406 [zfs] Jul 7 02:07:32 MCP kernel: ? zio_wait+0x1ee/0x1fd [zfs] Jul 7 02:07:32 MCP kernel: space_map_load_callback+0x70/0x79 [zfs] Jul 7 02:07:32 MCP kernel: space_map_iterate+0x2d3/0x324 [zfs] Jul 7 02:07:32 MCP kernel: ? spa_stats_destroy+0x16c/0x16c [zfs] Jul 7 02:07:32 MCP kernel: space_map_load_length+0x93/0xcb [zfs] Jul 7 02:07:32 MCP kernel: metaslab_load+0x33b/0x6e3 [zfs] Jul 7 02:07:32 MCP kernel: ? _raw_spin_unlock_irqrestore+0x24/0x3a Jul 7 02:07:32 MCP kernel: ? __wake_up_common_lock+0x88/0xbb Jul 7 02:07:32 MCP kernel: metaslab_preload+0x4c/0x97 [zfs] Jul 7 02:07:32 MCP kernel: taskq_thread+0x266/0x38a [spl] Jul 7 02:07:32 MCP kernel: ? wake_up_q+0x44/0x44 Jul 7 02:07:32 MCP kernel: ? taskq_dispatch_delay+0x106/0x106 [spl] Jul 7 02:07:32 MCP kernel: kthread+0xe4/0xef Jul 7 02:07:32 MCP kernel: ? kthread_complete_and_exit+0x1b/0x1b Jul 7 02:07:32 MCP kernel: ret_from_fork+0x1f/0x30 Jul 7 02:07:32 MCP kernel: </TASK> mcp-diagnostics-20230707-1414.zip
