Nodiaque

If you can see it in the list and can't connect, there's something wrong with your network. Specially if it never reach the server. Either port not open properly, routing problem... I can't really say more, it's not an issue with the docker itself.

What does the log say? Is your server really up? Do you see it in the list (although I know the game browser is shitty)? Do you see it in the server list when you go into steam and search on lan (not in the game, in steam)

What you just did is delete the game each time you start. Which mean you redownload each time. It's not normal, nobody else have this problem. There's something wrong with either your permission or your configuration. Are you using it with Unraid? Cause you don't need to do any of those thing under unraid with the community app. You can also set validate true in the template which will force a valide of the steam apps and game, just like with real steam. There's no magic here, proton have it's own quirk but here, it's just linux steam running and downloading game. We don't have any control, to see why it doesn't update, you need to check the log and see what error it does when it try to update at the beginning.

Might be a permission issue. The way the docker work is it start Steam and Steam download everything. If it's not updating, there's a permission or file corruption issue. Maybe turn verify on and check start logging.

Happened again. server was up less then 24 hours. I did a clean shutdown yesterday. Looking at what's printed on the monitor, it seems once I press shutdown on the gui, it wait only 90 sec before declaring a diagnostic. This is nuts since I have a lot of docker and it take way more time then that to shutdown. Again, I had to ssh into the server to send halt -f -p, wait for all drive dismount and do ctrl+alt+delete to have a complete reboot. diagnostic file that's suppose to be created isn't there. edit: just found the 90 sec is a parameter I can set. I though it was a setting for each docker. I'm changing it now for 5 minutes, should help.

ok. Since I can mount it after an array stop, I'll copy the content into the array and format it. Whatever corrupted file there is isn't a big problem. It's a security camera disk and currently, there's nothing of value in it

Ok. since it's single drive, should I out it on xfs? I put btrfs cause I though maybe adding another drive in the future to that pool, but it won't be needed to have these in mirror or raid.

Oh I don't really mind losing the data. I tried all recovery and what's weird is that when it get back up, it's working. It just failed again today, was fine since monday. I also changed the sata cable and port just in case. I guess it's format and restart?

Ok, but this drop the drive. It stays up but can't read or write anymore. My vm that use it says drive offline and the share show empty drive. I have to stop and start the array. Happened twice in 24h

Oh, I see. Well it's not something urgent. I just saw this today and I'm using unbalanced right now to balance things out. This would maybe be a split level 1.5 or something, but I do get it's not easy to do. I guess something else I could do is put the metadata in the cache drive instead since Emby does offer that.

what other option?

What I describe poorly is a bit different. In my exemple, all files under tv\showA\asdf.txt will be written, like you said, per allocation method. What I would like is to be fixed on one drive. so tv\showA\asdf.txt is the first file written on this share, it follow allocation method. The next files, tv\showA\qwerty.txt to be on the same drive as asdf.txt and not follow allocation (like if it was inside a level 3 folder). But I still want new folder created on that leaf to be created following allocation method. Like tv\showA\FolderA on drive 1, tv\showA\folderB on drive 2 following allocation method.

ok, how do i fix this? Cause the disk cannot be used until I stop the array and start it back, I tried scrub, btrfs repair and it solved it for maybe 3 hours. I did a short and long smart without error.

Hello, I found out looking at my log that one of my drive is making an error, but the error make no sense. oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 1 wanted 1 found 0 Oct 12 16:12:21 ServRaid kernel: BTRFS error (device sdj1 state EA): level verify failed on logical 3598354939904 mirror 2 wanted 1 found 0 It talk about mirror, but it's a single drive pool Last time that happened, I just stopped my array and restarted. Is my drive failing? Should I use xfs instead of btrfs for a single pool drive (I do plan on having more disk in the futur for that pool but not in mirror). thank you servraid-diagnostics-20251012-1615.zip

Hello, I was wondering if something like this could be possible in the futur. I have a 2 level split folder which allow me to have shows where each series is possibily split on different disk like season 1 on disk 1, season 2 on disk 2, etc. But, I found out that I also had small file on the root of that folder scattered accross multiple disk. What I would love is something that split the folders but not the file, unsure if that make sense. For exemple. tv\ - split level 1 (split everything) tv\showA - disk 1 (split level 2, split folders but not files) tv\showA\filea.txt - disk1 tv\showA\fileb.txt - disk 1 tv\showA\season1 - disk 1 tv\showA\season2 - disk 2 What I found out on my installation is since I'm using high water and that I have some stuff working after everything is created, I had some file on the root drive present on a totally different drive then anything that's on the show. Likle a filex.txt on disk 3 in that exemple. Which made that drive spin when someone access that show for no reason. Right now, I'm running unbalance and gathering each show one by one on a drive to fix that but I know it will come back due to high water and split level 2. I did right now switched to split level 1 but that mean a serie could stop getting files if it's on a full drive. So that's why having something that would say I split the leaf folder but not the leaf file of that level would be a nice to have. It has a specific use case, I do agree with it. It is for small stuff like metadata and images for shows and such. Thank you

well, it happened again, I closed all vm and docker before shutdown and had the same crash. I SSH on the server and ran shutdown -n -h -P -f now which closed everything but on my monitor, I still was seing only the crash. I press ctrl+alt+del and it started a reboot (it printed rebooting server on the display). So there's something but nobody can tell me :(

Can we know why it didn't shutdown? It's happen randomly but quite often. I even had a thread about it (or it was this one). Because my issue is it doesn't shutdown. That's my problem. It's also the title of the thread

https://forums.unraid.net/topic/144501-unraid-server-locked-up-shutdown-gets-stuck-at-starting-diagnostics-collection/#findComment-1580373

I posted that myself and never had answer. I have syslog enabled and I posted the relevant portion from the shutdown even received and to the hang up. Also posted the diagnostic ran.

Wow a timeout.... Unraid does have a hard time closing some docker from the webgui. Something I've saw many post on the forum with no fixe. You send the docker stop in terminal and the docker stop in 2 seconds but through webgui, it timeout. Still, nothing should prevent a shutdown except a kernel panic. My server already take over 5 minutes to boot and about the same time to close without diagnostic. I feel ill see where the diagnostic command is and render it none working. So it will launch it but do nothing.

I think my next step will be to find the reboot/shutdown script and remove diagnostic from it. I really don't care about a diagnostic on shutdown that prevent a shutdown. I will get a warning about dirty shutdown anyway on next boot. Right now, it's way worst to have a hard shutdown be Aude of battery failure or hard reset cause it's frozen.

It's random. I rebooted maybe 4 days before without any issue. But randomly, it happen and I never can find anything in log saying with suddently, it need it. Honestly, even on unclean shutdown, it need a failsafe to say if it hang trying to get it, stop and close the server. We are closing it, I need it close not hanging eating battery. Maybe an option to remove diagnostic on shutdown and if it's needed, we activate it for something. But even there, we have the diagnostic and it seems it doesn't tell you why it's an unclean shutdown, meaning it useless

That's what I did. The question is why do I need it. This time if you look at log, it doesn't even to have stuck at the unneeded diagnostic. That server was restarted like 4 days before without any problem. I was restarting this time because of nvidia driver update. And that happen. This make the solution very unreliable in case of emergency shutdown because of UPS (happened more then once that the server died because UPS battery was dead waiting for the server to close more then 30 minutes). Something is needed to prevent this issue. I never saw an issue on shutdown on any unix system. I've uploaded the logs I could give, if something else is needed I'll give it. edit: unsure if you check the syslog. But everything stopped promptly. All service stopped, all docker, vm, network connection, all disk where unmounted. But then Sep 24 21:14:31 #### root: Capture diagnostics to /boot/logs Sep 24 21:14:31 #### publish: curl to diagnostics failed Sep 24 21:14:31 #### publish: curl to diagnostics failed Sep 24 21:14:31 #### publish: curl to diagnostics failed (repeating infinitly) Sep 24 21:14:32 #### kernel: XFS (nvme2n1p1): Unmounting Filesystem 0dc5511c-9b2f-46cc-bfa6-de412b4769e0 Sep 24 21:14:31 #### publish: curl to diagnostics failed (repeating infinitly)Why a diagnostic, everything shutdown properly. And then, it try to kill nginx and crash Sep 24 21:14:36 #### rc.nginx: Stopping Nginx server daemon forcibly... Sep 24 21:14:36 #### rc.nginx: Nginx server daemon... Already stopped. Sep 24 21:14:39 #### kernel: BUG: unable to handle page fault for address: ffffffffa7466458 Sep 24 21:14:39 #### kernel: #PF: supervisor read access in kernel mode Sep 24 21:14:39 #### kernel: #PF: error_code(0x0000) - not-present page Sep 24 21:14:39 #### kernel: PGD 541a067 P4D 541a067 PUD 541b063 PMD 10a506067 PTE 0 Sep 24 21:14:39 #### kernel: Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI Sep 24 21:14:39 #### kernel: CPU: 0 UID: 0 PID: 1445014 Comm: btrfs Tainted: P O 6.12.24-Unraid #1 Sep 24 21:14:39 #### kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE Sep 24 21:14:39 #### kernel: Hardware name: Dell Inc. Precision 5820 Tower/06JWJY, BIOS 2.11.0 09/30/2021 Sep 24 21:14:39 #### kernel: RIP: 0010:bdev_open+0x8e/0x300 Sep 24 21:14:39 #### kernel: Code: 00 48 89 c7 48 89 44 24 08 e8 ae d3 59 00 49 8b 46 40 48 83 b8 80 04 00 00 00 75 0a b8 fa ff ff ff e9 35 02 00 00 49 8b 46 48 <48> 8b 78 78 e8 09 bd b7 ff 84 c0 41 89 c7 74 e2 80 3d 23 35 fb 00 Sep 24 21:14:39 #### kernel: RSP: 0018:ffffc90001f23c38 EFLAGS: 00010282 Sep 24 21:14:39 #### kernel: RAX: ffffffffa74663e0 RBX: ffff888107518c80 RCX: 0000000000000000 Sep 24 21:14:39 #### kernel: RDX: ffff88844828dd00 RSI: 0000000000000009 RDI: ffff88810a6929f8 Sep 24 21:14:39 #### kernel: RBP: 0000000000000009 R08: ffff88826b30ca80 R09: 0000000000000009 Sep 24 21:14:39 #### kernel: R10: 0000000000000f01 R11: fefefefefefefe01 R12: ffff88826b30ca80 Sep 24 21:14:39 #### kernel: R13: 0000000000000000 R14: ffff88810a692800 R15: 0000000000000000 Sep 24 21:14:39 #### kernel: FS: 0000152b0e43f900(0000) GS:ffff88a01fa00000(0000) knlGS:0000000000000000 Sep 24 21:14:39 #### kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 24 21:14:39 #### kernel: CR2: ffffffffa7466458 CR3: 0000000139e32002 CR4: 00000000003706f0 Sep 24 21:14:39 #### kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 24 21:14:39 #### kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Sep 24 21:14:39 #### kernel: Call Trace: Sep 24 21:14:39 #### kernel: <TASK> Sep 24 21:14:39 #### kernel: ? iput+0x64/0x1a0 Sep 24 21:14:39 #### kernel: ? __pfx_blkdev_open+0x10/0x10 Sep 24 21:14:39 #### kernel: blkdev_open+0x96/0xc0 Sep 24 21:14:39 #### kernel: do_dentry_open+0x1ae/0x330 Sep 24 21:14:39 #### kernel: vfs_open+0x27/0x50 Sep 24 21:14:39 #### kernel: path_openat+0x8e8/0x9f0 Sep 24 21:14:39 #### kernel: ? terminate_walk+0x1d/0x70 Sep 24 21:14:39 #### kernel: do_filp_open+0xa4/0x110 Sep 24 21:14:39 #### kernel: ? __pfx_kfree_link+0x10/0x10 Sep 24 21:14:39 #### kernel: ? kmem_cache_debug_flags+0xc/0x20 Sep 24 21:14:39 #### kernel: ? rawspin_unlock+0x14/0x30 Sep 24 21:14:39 #### kernel: do_sys_openat2+0x6d/0xc0 Sep 24 21:14:39 #### kernel: do_sys_open+0x3a/0x60 Sep 24 21:14:39 #### kernel: do_syscall_64+0x68/0xe0 Sep 24 21:14:39 #### kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e Sep 24 21:14:39 #### kernel: RIP: 0033:0x152b0e4d95c7 Sep 24 21:14:39 #### kernel: Code: 46 b8 04 00 00 00 48 8b 15 1e 78 16 00 64 89 02 48 c7 c2 ff ff ff ff 5b 48 89 d0 c3 0f 1f 80 00 00 00 00 48 8b 44 24 10 0f 05 <48> 63 d0 3d 00 f0 ff ff 77 0f 48 89 d0 5b c3 66 2e 0f 1f 84 00 00 Sep 24 21:14:39 #### kernel: RSP: 002b:00007ffefba98510 EFLAGS: 00000202 ORIG_RAX: 0000000000000101 Sep 24 21:14:39 #### kernel: RAX: ffffffffffffffda RBX: 0000152b0e43f900 RCX: 0000152b0e4d95c7 Sep 24 21:14:39 #### kernel: RDX: 0000000000080800 RSI: 0000000000521ec0 RDI: ffffffffffffff9c Sep 24 21:14:39 #### kernel: RBP: 0000000000520430 R08: 0000000000000000 R09: 0000000000000000 Sep 24 21:14:39 #### kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000068d4977f Sep 24 21:14:39 #### kernel: R13: 0000000068d4976c R14: 0000152b0e82aa9c R15: 0000000000000013 Sep 24 21:14:39 #### kernel: </TASK> Sep 24 21:14:39 #### kernel: Modules linked in: nft_compat tls cmac cifs cifs_arc4 nls_ucs2_utils cifs_md4 dns_resolver af_packet bluetooth rfkill xt_CHECKSUM ipt_REJECT nf_reject_ipv4 ip6table_mangle iptable_mangle vhost_iotlb nft_m asq nft_chain_nat nvidia_uvm(PO) veth nf_conntrack_netlink xt_nat xt_conntrack bridge xfrm_user xt_addrtype xt_MASQUERADE xt_tcpudp xt_mark tun nf_tables nfnetlink ip6table_nat iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv 4 ntfs3 tcp_diag inet_diag zfs(PO) spl(O) ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs macvtap macvlan tap 8021q garp mrp stp llc ixgbe xfrm_algo mdio e1000e nvidia_drm(PO) nvidia_modeset(PO) intel_rapl_common io sf_mbi nvidia(PO) x86_pkg_temp_thermal intel_powerclamp coretemp drm_ttm_helper ttm video drm_kms_helper drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel crypto_simd cryp td rapl i2c_i801 backlight intel_cstate input_leds intel_wmi_thunderbolt wmi_bmof dell_smm_hwmon Sep 24 21:14:39 #### kernel: intel_uncore led_class tpm_crb mpt3sas nvme agpgart i2c_smbus mei_me raid_class nvme_core scsi_transport_sas i2c_core ahci mei vmd tpm_tis libahci tpm_tis_core wmi tpm libaescfb ecdh_generic ecc acpi_tad button [last unloaded: md_mod] Sep 24 21:14:39 #### kernel: CR2: ffffffffa7466458 Sep 24 21:14:39 #### kernel: ---[ end trace 0000000000000000 ]--- Sep 24 21:14:39 #### kernel: pstore: backend (erst) writing error (-28) Sep 24 21:14:39 #### kernel: RIP: 0010:bdev_open+0x8e/0x300 Sep 24 21:14:39 #### kernel: Code: 00 48 89 c7 48 89 44 24 08 e8 ae d3 59 00 49 8b 46 40 48 83 b8 80 04 00 00 00 75 0a b8 fa ff ff ff e9 35 02 00 00 49 8b 46 48 <48> 8b 78 78 e8 09 bd b7 ff 84 c0 41 89 c7 74 e2 80 3d 23 35 fb 00 Sep 24 21:14:39 #### kernel: RSP: 0018:ffffc90001f23c38 EFLAGS: 00010282 Sep 24 21:14:39 #### kernel: RAX: ffffffffa74663e0 RBX: ffff888107518c80 RCX: 0000000000000000 Sep 24 21:14:39 #### kernel: RDX: ffff88844828dd00 RSI: 0000000000000009 RDI: ffff88810a6929f8 Sep 24 21:14:39 #### kernel: RBP: 0000000000000009 R08: ffff88826b30ca80 R09: 0000000000000009 Sep 24 21:14:39 #### kernel: R10: 0000000000000f01 R11: fefefefefefefe01 R12: ffff88826b30ca80 Sep 24 21:14:39 #### kernel: R13: 0000000000000000 R14: ffff88810a692800 R15: 0000000000000000 Sep 24 21:14:39 #### kernel: FS: 0000152b0e43f900(0000) GS:ffff88a01fa00000(0000) knlGS:0000000000000000 Sep 24 21:14:39 #### kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 24 21:14:39 #### kernel: CR2: ffffffffa7466458 CR3: 0000000139e32002 CR4: 00000000003706f0 Sep 24 21:14:39 #### kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Sep 24 21:14:39 #### kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Sep 24 21:14:39 #### kernel: note: btrfs[1445014] exited with irqs disabledAnd then that curl error about diagnostics again and... it start nginx back????? Sep 24 21:14:39 #### publish: curl to diagnostics failed Sep 24 21:14:39 #### publish: curl to diagnostics failed Sep 24 21:14:39 #### publish: curl to diagnostics failed Sep 24 21:14:41 #### rc.nginx: Starting Nginx server daemon... Sep 24 21:14:42 #### rc.nginx: Nginx server daemon... Started.It's not normal. Honestly, that diagnostic on shutdown is good for nothing, specially in case of emergency reboot. Someone needing to shutdown because of battery low could have a server crash just because it decided to ran a diagnostic nobody will check.

So I just did a manual reboot from GUI. Right before, I ran a diagnostic just to be sure that diagnostic would finish. Well guess what, it's stuck. I can SSH in it no problem. syslog show it did a diagnostic, failed and tried to start nginx back (Why?) and then it's stuck syslog.txt edit: I tried calling a shutdown -r now, I lost my ssh session and cannot open a new one. 10 minutes have passed, I can still ping but that's it. I had to force shutdown. It's not normal. All docker where shutdown and vm also (I've checked with ssh and syslog shows it). I can't realy on something that cannot be shutdown when UPS is running, it's absurd servraid-diagnostics-20250924-2145.zip

Dam, it's brand new. I hate flash drive.... Thanks