-
[Support] ich777 - Gameserver Dockers
--disregard-- my server is running. my UDM was not saving ports correctly issue on my end. thanks again
-
System fails to mount array, kernel panic on boot after update
What causes this? It seemed nominal before I triggered the update. Any way to monitor this / be more prepared in the future?
-
System fails to mount array, kernel panic on boot after update
Update. Was able to start the array after mounting the cache in read only disable auto start of array reboot mount cache read only: zpool import -o readonly=on cache start the array seems fine? would the path here be to backup all the cache and reformat? thanks
-
-
System fails to mount array, kernel panic on boot after update
updated earlier tonight and now my system fails to mount. Tried rolling back, disabling docker, removing a stick of ram, etc... not sure how to proceed. diag attached. showing weird drive data in the dashboard too: Intel 14th gen failure? here is the panic when starting the array: Sep 15 19:48:02 GhostNAS emhttpd: shcmd (432): udevadm settle Sep 15 19:48:02 GhostNAS emhttpd: Opening encrypted volumes... Sep 15 19:48:02 GhostNAS emhttpd: shcmd (433): touch /boot/config/forcesync Sep 15 19:48:02 GhostNAS emhttpd: Mounting disks... Sep 15 19:48:02 GhostNAS emhttpd: mounting /mnt/disk1 Sep 15 19:48:02 GhostNAS emhttpd: shcmd (434): mkdir -p /mnt/disk1 Sep 15 19:48:02 GhostNAS emhttpd: shcmd (435): mount -t xfs -o noatime,nouuid /dev/md1p1 /mnt/disk1 Sep 15 19:48:02 GhostNAS kernel: SGI XFS with ACLs, security attributes, no debug enabled Sep 15 19:48:02 GhostNAS kernel: XFS (md1p1): Mounting V5 Filesystem Sep 15 19:48:03 GhostNAS kernel: XFS (md1p1): Starting recovery (logdev: internal) Sep 15 19:48:03 GhostNAS emhttpd: shcmd (436): xfs_growfs /mnt/disk1 Sep 15 19:48:03 GhostNAS kernel: XFS (md1p1): Ending recovery (logdev: internal) Sep 15 19:48:03 GhostNAS root: meta-data=/dev/md1p1 isize=512 agcount=13, agsize=268435455 blks Sep 15 19:48:03 GhostNAS root: = sectsz=512 attr=2, projid32bit=1 Sep 15 19:48:03 GhostNAS root: = crc=1 finobt=1, sparse=1, rmapbt=0 Sep 15 19:48:03 GhostNAS root: = reflink=1 bigtime=1 inobtcount=1 nrext64=0 Sep 15 19:48:03 GhostNAS root: data = bsize=4096 blocks=3418095603, imaxpct=5 Sep 15 19:48:03 GhostNAS root: = sunit=0 swidth=0 blks Sep 15 19:48:03 GhostNAS root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Sep 15 19:48:03 GhostNAS root: log =internal log bsize=4096 blocks=521728, version=2 Sep 15 19:48:03 GhostNAS root: = sectsz=512 sunit=0 blks, lazy-count=1 Sep 15 19:48:03 GhostNAS root: realtime =none extsz=4096 blocks=0, rtextents=0 Sep 15 19:48:03 GhostNAS emhttpd: mounting /mnt/disk3 Sep 15 19:48:03 GhostNAS emhttpd: shcmd (437): mkdir -p /mnt/disk3 Sep 15 19:48:03 GhostNAS emhttpd: shcmd (438): mount -t xfs -o noatime,nouuid /dev/md3p1 /mnt/disk3 Sep 15 19:48:03 GhostNAS kernel: XFS (md3p1): Mounting V5 Filesystem Sep 15 19:48:03 GhostNAS kernel: XFS (md3p1): Starting recovery (logdev: internal) Sep 15 19:48:03 GhostNAS emhttpd: shcmd (439): xfs_growfs /mnt/disk3 Sep 15 19:48:03 GhostNAS kernel: XFS (md3p1): Ending recovery (logdev: internal) Sep 15 19:48:03 GhostNAS root: meta-data=/dev/md3p1 isize=512 agcount=8, agsize=268435455 blks Sep 15 19:48:03 GhostNAS root: = sectsz=512 attr=2, projid32bit=1 Sep 15 19:48:03 GhostNAS root: = crc=1 finobt=1, sparse=1, rmapbt=0 Sep 15 19:48:03 GhostNAS root: = reflink=1 bigtime=1 inobtcount=1 nrext64=0 Sep 15 19:48:03 GhostNAS root: data = bsize=4096 blocks=1953506633, imaxpct=5 Sep 15 19:48:03 GhostNAS root: = sunit=0 swidth=0 blks Sep 15 19:48:03 GhostNAS root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Sep 15 19:48:03 GhostNAS root: log =internal log bsize=4096 blocks=521728, version=2 Sep 15 19:48:03 GhostNAS root: = sectsz=512 sunit=0 blks, lazy-count=1 Sep 15 19:48:03 GhostNAS root: realtime =none extsz=4096 blocks=0, rtextents=0 Sep 15 19:48:03 GhostNAS emhttpd: mounting /mnt/disk4 Sep 15 19:48:03 GhostNAS emhttpd: shcmd (440): mkdir -p /mnt/disk4 Sep 15 19:48:03 GhostNAS emhttpd: shcmd (441): mount -t xfs -o noatime,nouuid /dev/md4p1 /mnt/disk4 Sep 15 19:48:03 GhostNAS kernel: XFS (md4p1): Mounting V5 Filesystem Sep 15 19:48:04 GhostNAS kernel: XFS (md4p1): Starting recovery (logdev: internal) Sep 15 19:48:04 GhostNAS emhttpd: shcmd (442): xfs_growfs /mnt/disk4 Sep 15 19:48:04 GhostNAS kernel: XFS (md4p1): Ending recovery (logdev: internal) Sep 15 19:48:04 GhostNAS root: meta-data=/dev/md4p1 isize=512 agcount=8, agsize=268435455 blks Sep 15 19:48:04 GhostNAS root: = sectsz=512 attr=2, projid32bit=1 Sep 15 19:48:04 GhostNAS root: = crc=1 finobt=1, sparse=1, rmapbt=0 Sep 15 19:48:04 GhostNAS root: = reflink=1 bigtime=1 inobtcount=1 nrext64=0 Sep 15 19:48:04 GhostNAS root: data = bsize=4096 blocks=1953506633, imaxpct=5 Sep 15 19:48:04 GhostNAS root: = sunit=0 swidth=0 blks Sep 15 19:48:04 GhostNAS root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Sep 15 19:48:04 GhostNAS root: log =internal log bsize=4096 blocks=521728, version=2 Sep 15 19:48:04 GhostNAS root: = sectsz=512 sunit=0 blks, lazy-count=1 Sep 15 19:48:04 GhostNAS root: realtime =none extsz=4096 blocks=0, rtextents=0 Sep 15 19:48:04 GhostNAS emhttpd: mounting /mnt/cache Sep 15 19:48:04 GhostNAS emhttpd: shcmd (443): mkdir -p /mnt/cache Sep 15 19:48:04 GhostNAS emhttpd: shcmd (444): /usr/sbin/zpool import -f -N -o autoexpand=on -d /dev/nvme0n1p1 -d /dev/nvme1n1p1 811097023252368398 cache Sep 15 19:48:10 GhostNAS kernel: VERIFY3(size <= rt->rt_space) failed (281442900340736 <= 16139841536) Sep 15 19:48:10 GhostNAS kernel: PANIC at range_tree.c:436:range_tree_remove_impl() Sep 15 19:48:10 GhostNAS kernel: Showing stack for process 19845 Sep 15 19:48:10 GhostNAS kernel: CPU: 8 PID: 19845 Comm: z_wr_iss Tainted: P O 6.1.79-Unraid #1 Sep 15 19:48:10 GhostNAS kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D29/MEG Z690I UNIFY (MS-7D29), BIOS 1.I0 07/26/2024 Sep 15 19:48:10 GhostNAS kernel: Call Trace: Sep 15 19:48:10 GhostNAS kernel: <TASK> Sep 15 19:48:10 GhostNAS kernel: dump_stack_lvl+0x44/0x5c Sep 15 19:48:10 GhostNAS kernel: spl_panic+0xd0/0xe8 [spl] Sep 15 19:48:10 GhostNAS kernel: ? bt_grow_leaf+0xc3/0xd6 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? zfs_btree_find_in_buf+0x4c/0x94 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? zfs_btree_find+0x16d/0x1b0 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? rs_get_start+0xc/0x1d [zfs] Sep 15 19:48:10 GhostNAS kernel: range_tree_remove_impl+0x77/0x406 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? zio_wait+0x1ee/0x1fd [zfs] Sep 15 19:48:10 GhostNAS kernel: space_map_load_callback+0x70/0x79 [zfs] Sep 15 19:48:10 GhostNAS kernel: space_map_iterate+0x2d3/0x324 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? spa_stats_destroy+0x16c/0x16c [zfs] Sep 15 19:48:10 GhostNAS kernel: space_map_load_length+0x93/0xcb [zfs] Sep 15 19:48:10 GhostNAS kernel: metaslab_load+0x33b/0x6e3 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? slab_post_alloc_hook+0x4d/0x15e Sep 15 19:48:10 GhostNAS kernel: ? rs_get_start+0xc/0x1d [zfs] Sep 15 19:48:10 GhostNAS kernel: ? spl_kmem_alloc_impl+0xc1/0xf2 [spl] Sep 15 19:48:10 GhostNAS kernel: ? __kmem_cache_alloc_node+0x118/0x147 Sep 15 19:48:10 GhostNAS kernel: metaslab_activate+0x36/0x1f1 [zfs] Sep 15 19:48:10 GhostNAS kernel: metaslab_alloc_dva+0x8bc/0xfce [zfs] Sep 15 19:48:10 GhostNAS kernel: ? preempt_latency_start+0x2b/0x46 Sep 15 19:48:10 GhostNAS kernel: metaslab_alloc+0x107/0x1fd [zfs] Sep 15 19:48:10 GhostNAS kernel: zio_dva_allocate+0xee/0x73f [zfs] Sep 15 19:48:10 GhostNAS kernel: ? kmem_cache_free+0xc9/0x154 Sep 15 19:48:10 GhostNAS kernel: ? spl_kmem_cache_free+0x3a/0x1a5 [spl] Sep 15 19:48:10 GhostNAS kernel: ? preempt_latency_start+0x2b/0x46 Sep 15 19:48:10 GhostNAS kernel: ? _raw_spin_lock+0x13/0x1c Sep 15 19:48:10 GhostNAS kernel: ? _raw_spin_unlock+0x14/0x29 Sep 15 19:48:10 GhostNAS kernel: ? tsd_hash_search+0x70/0x7d [spl] Sep 15 19:48:10 GhostNAS kernel: zio_execute+0xb1/0xdf [zfs] Sep 15 19:48:10 GhostNAS kernel: taskq_thread+0x266/0x38a [spl] Sep 15 19:48:10 GhostNAS kernel: ? wake_up_q+0x44/0x44 Sep 15 19:48:10 GhostNAS kernel: ? zio_subblock+0x22/0x22 [zfs] Sep 15 19:48:10 GhostNAS kernel: ? taskq_dispatch_delay+0x106/0x106 [spl] Sep 15 19:48:10 GhostNAS kernel: kthread+0xe4/0xef Sep 15 19:48:10 GhostNAS kernel: ? kthread_complete_and_exit+0x1b/0x1b Sep 15 19:48:10 GhostNAS kernel: ret_from_fork+0x1f/0x30 Sep 15 19:48:10 GhostNAS kernel: </TASK> ghostnas-diagnostics-20240915-2140.zip
-
Can't reliably get 10Gbit(1GB/s) speeds
Yes. Degraded state & after reboot are attached Obviously something with retries, I just can't seem to figure out what.
-
Can't reliably get 10Gbit(1GB/s) speeds
I have to systems, Unraid & a PC, both equipped with their own 10gig nics. I am using a UDM PRO from Ubiquiti and a separate 10gig switch to link the two. Both devices (PC and Unraid) are communicating just fine... however sometimes my read and write speeds drop to around 300MB/s. This can be mitigated by rebooting the Unraid server. Not the switch, or the PC. The only solution is a reboot of Unraid. Obviously this is not ideal. To reiterate, I CAN transfer at 1GB/s however after an undetermined amount of time it will degrade to around 300MB/s. I've done the usual, set direct transfer to ON, isolated a share to be CACHE ONLY, and set the MTU on both devices to their maximum respectively (9000). I can't seem to figure this one out. I've also set both ports on the switch manually from AUTO to 10Gbit speeds. It very clearly seems Unraid related at this point. Diag attached. diag-20240705-0121.zip
-
[Support] Membarr Docker Template
Tested disabling two-factor, still cant seem to connect now
-
[Support] ich777 - Gameserver Dockers
Interesting issue with Palworld. When restarting the server you are prompted to re-create a character. I don't think its an issue with the container, but the game itself.
-
10G NIC not detected by Unraid
Yep. Riser card was dead. Card is working properly now.
-
10G NIC not detected by Unraid
Recently got setup with Unraid, been great so far. However I can't get my NIC to show up under interfaces. it was quite involved to find drivers for my windows system, but I was able to. I'm not even seeing it under System Devices. Could that be a bad riser cable? This is the NIC. https://www.amazon.com/NICGIGA-Network-Controller-Ethernet-Windows10/dp/B0BG2FDCSN/ref=sr_1_4?keywords=10gb%2Bnic&sr=8-4&th=1 which is an intel x520-da1 controller I believe. Any advice? Diagnostics attached. ghostnas-diagnostics-20230514-1931.zip
sens_dep
Members
-
Joined
-
Last visited