WCA

For the Fractal Arc Midi R2, in the same style as the unraid ones

I was expecting that notes would be synced across devices since I self host the application, but that doesn't seem to be the case. Is this normal behavior? Or am I not getting the purpose of this app?

I get that, but I think it's safe to say it's a better idea to go back to stable than to keep messing around on a release that potentially corrupts my data right? I regret having updated to a beta release already, I'm not doing that again. Hoping it will be fixed by the final release. I won't be able to provide diagnostics, so I hope that someone else will be able to provide them. I'm sorry, but I just don't want to lose any data. If a Limetech employee would confirm that these errors are not destroying any data, I'd be willing to upgrade temporarily to provide the diagnostics though.

Can I post diagnostics.zip from 6.7.2? I'm hesistant to upgrade to RC4 again in fear of data loss

I went straight from 6.7.2 to RC2 or RC3 i think I downgraded back to 6.7.2, issues are gone now.

Since (atleast) 6.8rc2 I've been getting read errors on multiple disks in my array (across controllers, both on my HBA (Dell H200) and my integrated controller (Intel), I spin down my disks after 4 hours, and the problem seems to only occur when disks are spun down. It's the same problem this user on reddit seems to have: https://www.reddit.com/r/unRAID/comments/dmxcr5/am_i_playing_with_fire/ My Specs are: Storage consists of the following: And for what it's worth, here is the entire hardware map: I will attach logs for the last few hours: Oct 24 23:46:52 PLEXSCH kernel: blk_update_request: critical medium error, dev sdh, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569296 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569304 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569312 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569320 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569328 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569336 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569344 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569352 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569360 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569368 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569376 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569384 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569392 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569400 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569408 Oct 24 23:46:52 PLEXSCH kernel: md: disk5 read error, sector=4026569416 Oct 24 23:47:04 PLEXSCH kernel: blk_update_request: critical medium error, dev sdj, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569296 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569304 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569312 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569320 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569328 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569336 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569344 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569352 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569360 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569368 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569376 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569384 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569392 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569400 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569408 Oct 24 23:47:04 PLEXSCH kernel: md: disk0 read error, sector=4026569416 Oct 24 23:47:05 PLEXSCH kernel: blk_update_request: critical medium error, dev sdk, sector 4026569360 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569296 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569304 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569312 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569320 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569328 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569336 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569344 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569352 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569360 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569368 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569376 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569384 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569392 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569400 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569408 Oct 24 23:47:05 PLEXSCH kernel: md: disk29 read error, sector=4026569416