oliver

im not sure you understand how video playback works. transcoding is absolutely necessary to account for the capabilities of the client. simply increasing bandwidth doesn't mean it's going to be able to magically decode the video.

im so torn on going with this approach vs just waiting for arrow lake support, then i don't even need the ARC card anymore, the CPU will take care of it

at the glacial rate the unraid team updates the kernel, i imagine it will be quite a while before it's supported.

will arrow lake require unraid 7 for support? specifically looking at using the igpu for av1 encoding

this is a really poorly designed image for being official, doesn't work very well. it can't even be connected to from outside the container the documentation is awful.

all these years later the bug is still there. how is it the price of this software goes up but the quality remains so poor?

So im having some very odd behavior. I have two NICs - one on my motherboard (Qualcomm Atheros QCA8171 Gigabit Ethernet) and a USB adaptor (8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN). Both of these are listed under system devices. Only one of them shows up in my network settings - the USB one. See attached screenshot. However, it doesn't work. When plugging into it, I get no connectivity. Oddly enough, the onboard ethernet doesn't show up anywhere in 'network' - but that one works. I can plug it in and everything is accessible. I'm completely at a loss as to how a NIC that isn't even showing up is working, while a NIC that DOES show up isn't working. Attached diagnostics. nasbackup-diagnostics-20240717-2050.zip

nas-diagnostics-20240510-1844.zip I've attached some older diagnostics when I was troubleshooting the crashes earlier. Logs just appear to show the array starting as normal. In this bootup, all docker containers are set for autostart:off but you can see some starting normally.

Unfortunately not, even with a clean shutdown, the auto-start settings are no longer honored for some of the containers.

For now im manually moving it off the array, I just wanted to get an initial backup created manually.

I had several kernel panics and unclean shutdowns, after recovery, some of my docker containers aren't respecting the auto-start flag. I have everything turned off but some of them still start with array start. I tried flipping the flags, editing the containers to generate a new one but they keep starting with the array when they shouldn't. How is this flag controlled (docker.img?) and how can I view/edit it?

When updating to 6.12.10, usually within 30 minutes I get a kernel panic related to what appears to be the Realtek 8152 driver. Reverting back to 6.12.8 everything works fine. I know unraid included new drivers - do they work in conjunction with this? Should I uninstall this before upgrading? I have a USB 8156 USB NIC. Panic logs: ? tun_do_read+0x4f4/0x51f [tun] ? sock_sendmsg_nosec+0x2b/0x40 sock_sendmsg_nosec+0x2b/0x40 sys_sendto+0x2/0x111 ? timespec64_add_safe+0x36/0x83 ? fpregs_assert_state_consistent+0x20/0x44 x64_sys_sendto+0x20/0x2? do_syscall_64+0x68/0x81 entry_SYSCALL_64_after_hwframe+0x64/0xce RIP: 0033:0x14d83dd2781a Code: d8 64 89 02 48 c7 c0 ff ff ff ff 0f 1f 44 00 00 41 54 48 83 ec b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 15 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 7e ca RSP: 002b:00007ffd66e229f8 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000014d83dd2781a RDX: 0000000000000546 RSI: 0000556b7384f3d4 RDI: 00007ffd66e23558 RBP: 00007ffd66e22a90 R08: 0000000000000003 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffd66e22bc0 R13: 0000000000000000 R14: 0000556673808660 R15: 0000000000000002 </TASK> Modules linked in: xt_CHECKSUM ipt_REJECT nf_reject_ipv4 iptable_mangle iptable_nat iptable_mangle host_net tun vhost vhost_iotlb tap veth xt_nat xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype br_netfilter xfs dm_crypt dm_mod nd_mod zfs(PO) zunicode(PO) zzstd(PO) zlua(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(PO) tcp_diag inet_diag ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc bonding tls e1000e r8152(PO) igb intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel i915 kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 iosf_mbi sha256_ssse3 drm_buddy sha1_ssse3 ttm aesni_intel crypto_simd drm_display_helper cryptd btusb drm_kms_helper rapl btrtl btqca btintel intel_cstate mei_hdcp mei_pxp drm nvme i2c_i801 intel_gtt bluetooth intel_uncore mptsas i2c_algo_bit agpgart i2c_smbus mei_me sr_mod syscopyarea input_leds ahci nvme_core sysfillrect i2c_core mei libahci ecdh_generic raid_class cdrom sysimgblt joydev ecc scsi_transport_sas fb_sys_fops fan -[ end trace 0000000000000000 ]- thermal video wmi backlight intel_pmc_core button acpi_pad unix [last unloaded: e1000e] RIP: 0010:netdev_tx_sent_queue+0x8/0x51 [r8152] Code: 74 04 48 8d 42 ff c3 cc cc cc cc 0f 1f 44 00 00 8a 87 e1 0e 00 00 f6 d8 19 c0 83 e0 f0 c3 cc cc cc cc 81 fe ff ff ff ff 0f 76 02 <0f> 0b 89 b7 c8 00 00 00 01 b7 c0 00 00 00 8b 97 c4 00 00 00 86 87 RSP: 0018:ffffc9000028c5b0 EFLAGS: 00010292 RAX: 0000000080000702 RBX: ffff8881069a5000 RCX: 0000000000000000 RDX: 0000000000000703 RSI: ffff88810294c800 RDI: 0000000000000570 RBP: ffff8881b16b4f00 R08: 0000000016b4b000 R09: 0000000000000001 R10: 86815736d9a21d85 R11: ffffc9000028c5f8 R12: ffff8881b16b4f00 R13: 0000000000000000 R14: ffffffffa077b1a0 R15: 0000000000000000 FS: 000014d83e4637c0(0000) GS:ffff88841edc0000(0000) knIGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000001366b210034 CR3: 00000001cbf9a004 CR4: 00000000003726e0 Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: disabled ---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---

thanks this fixed it

hi im trying to make a manual backup with default settings and get an error the destination is not writeable. I am trying to write to a folder inside of appdata: debug id is 9860c8a1-b3cd-4349-b3a1-0178ca1ef98b EDIT: fixed by manually creating the folder as described here: there's something wrong with the scripts ability to create the folder properly itself.

same issues today too. it would be nice if at least unraids core functionality, file sharing would work without bugs...

my passphrase ends with a %, can that cause any issues?

bumping this thread as im facing the same issue but looks like i shouldn't expect any solutions.

Hi, im trying to get it working via fetching the passphrase remotely but it doesn't seem to recognize the passphrase. I've validated it is downloading the file and the file contents contain the passphrase and nothing else but it doesn't recognize it. My go file: #!/bin/bash # Start the Management Utility wget pizero.lan.local/key.html -O /root/keyfile /usr/local/sbin/emhttp & I get this error, full logs attached: I also noticed the GUI looks different after a failed log, it only allows me to work with keyfiles. My understanding is that passphrase/keyfiles work the same but that appears to not be the case. autounlock.txt

there is something terribly wrong with unraid. containers with autostart marked as 'off' are starting anyways. stop/start commands don't do what they shoud. i can't even kill the containers when this happens, i get: Error response from daemon: cannot stop container: <container-id>: tried to kill container, but did not receive an exit event what would you say is the best way to start from scratch here without losing my appdata? i do have backups. and on a secondary note, why is an errant docker container enough to completely halt the system? im re-thinking using docker containers on unraid because they shouldn't be able to completely lock up the array in this way. EDIT: just downgraded to 6.12.8. even though i had been running 6.12.10 for a few days, i immediately noticed two things: docker is far more responsive the glitch with containers not respecting autostart is fixed too soon to tell if it's permanently fixed.

yeah, thanks it's running stable now although im very carefully managing containers. the symptoms seem somewhat similar to this it's very odd. the unraid GUI seems to not by in sync with what docker ps shows as up and running in certain scenarios. im gonna try rebuilding all of the containers like OP there is doing.

Hi, I did have that enabled at that time via a remote syslog server, attached logs.txt

Hi, suddenly today out of nowhere my unraid system is unresponsive, usually within minutes of starting the array. This started completely out of the blue, with no hardware or software changes for a while. Running 6.12.10 I've attached diagnostics but here are some observations/behaviors. WEBUI is not responsive. Docker containers are not responsive. Shares are not responsive. VM's ARE responsive and appear to function normally. SSH is responsive During all of this, syslog continues writing, but there are no errors. When I try to run `ls /mnt`, the terminal freezes - I am never able to view the mount directory. Throughout all of this, syslog continues to write but I don't see any errors or anything pop up. Everything just....freezes. This either seems to be hardware failure or something docker related. I'm leaning towards a docker container being the problem. I noticed random port allocation/execution errors pop up once I enable docker. Not sure which container it could be as I didn't make any changes recently. Is it possible to disable autostart so I can go one by one? EDIT: After doing more testing, im increasingly convinced this is some docker issue, particularly networking related. I get random errors across all containers, that stop and go in between service restarts. I'm using ipvlan. I've attached unraid logs, which should include previous logs, as I had that enabled copy to flash drive on shutdown. nas-diagnostics-20240510-1844.zip

i don't use unraid for time machine, couldn't say.

all i have to say is wow....i made these changes to sonoma 14.4.1 /unraid 6.12.10 and the mac experience is far better. i have a large array and directory listings are almost instant.

if i have multiple shares, some native windows, do you see any conflicts with the unraid specific ones and those? specifically from the changes to the mac nsmb.conf file?