Andiroo2

My understanding is that you have to stop the array, move the 2TB drive into slot 1 in the pool config (remove from slot 2 and select in slot 1) and then select ‘None’ for slot 2, then start the array. It would be good to someone to validate this though, I’ve only done this once recently. EDIT: Forgot the step of starting the array with NO cache drives present…see @JorgeB’s post.

Do you really need to partition the cache for this? You could create a 4TB mirrored cache and put your appdata and system (docker) shares on it and they will happily exist together. You won’t notice any performance hit by having these on the same mirrored NVMe cache drives. Are you worried that the “other” shares will take over all the space on the cache, and looking for a quota-like system perhaps?

I’m wondering if the crashes on 13th and 14th gen CPUs would show somehow in the Unraid log as a kernel panic or other error. I’ve been troubleshooting panic-type errors for months on my new 13th gen CPU and wondering if my CPU could be experiencing the issues. Anyone have experience here?

If I replace and resilver larger drives into a ZFS pool, will the pool eventually show the higher capacity once the smallest drive is removed?

Is it possible to get a temporary license upgrade (plus to pro) to facilitate a hard drive upgrade? I am actually looking to decrease the number of drives in my system, but to do so I will need to attach the new, larger drives and migrate data before removing the old ones. This will put me over 12 drives temporarily. thanks, Andrew

Same thing happened to me just now. I deleted my pool and wanted to start fresh. I couldn't get it to format. I had to delete the /mnt/cache mount point (rm -r /mnt/cache) and then it formatted and came online.

Check this similar post for some initial steps to take. Patience now, this part sucks but it’s how you find the problem!

This same thing happened to me, BTW. Went from a Z490 board with this same QNAP card, 4x 2TB NVMes loaded to a Z690 board and now i have nothing but problems with it. It's seemingly hit and miss on whether the drives show up or not (depending on different combinations of drive population and onboard slot usage).

Same issue happening to me, 3 years later, FYI Hard reboot due to a lock up, no SHIM network. Need another graceful reboot to restore it

I have been testing/judging NVMe speed based on network transfers in my Windows VM to Unraid shares. Is there a better way to just test this within Unraid core? The disk speed docker doesn’t work for pooled cache drives…what else could I try here? Can I run rsync with some stats?

ARC size didn’t help. Saw the same speeds afterwards. That being said, my speeds jumped to around 800MB/s when I switched to exclusive shares.

This is where it gets weird. htop doesn’t show any cores at 100%. I see it only in the Unraid Dashboard and in my Grafana panel (fed by telegram with out of the box CPU reporting).

Sounds like your Docker folder/image could have been moved to the array. Can you confirm they are on SSD/NVMe storage?

I’m getting 100% CPU usage on CPU Core0 when I use Unbalanced. Everything is working correctly, but just wondering if this is normal.

Yes, many reboots. Maybe I should remove isolation on the GUI and in syslinux and start again.

I see text there but I don’t know if it was manually added. Does the pinning GUI add this, or could I have added it years ago?

I have some cores pinned and isolated…seemingly no issues there. Every time I visit the cpu-pinning page though, I get the “CPU Isolation: a reboot is required to apply changes” banner along the top of my GUI. Should I be concerned that the pinning changes aren’t working, or is this a GUI bug? Thanks!

Ram Memtest overnight and had errors this AM. Pulled one stick of memory and started up again without issues in the log. Ordered a new set to arrive later today and will re-test.

I’ve uninstalled a few plugins and stopped my VM…things have stabilized for now. I will see if I can get this through the night and if so, will look at the VM config. I wonder if there is some VFIO call or conflict that is causing issues. More to come…

Latest Unraid version installed, moved from a stable system on 10th get Intel to a new 13th gen Intel. New CPU/MB/RAM, Memtest86 passed without issues. Having issues keeping the system online for more than a few hours. Everything works when it's up, but then it just dies. I have syslog server activated with logs attached, and diagnostics as well. Looking for where to start...thanks!192.168.1.10 syslog.txt tower-diagnostics-20240414-1119.zip

Love my R5. AMA.

OK I increased my ARC to 1/4 of RAM instead of the default 1/8. Will see what happens.

Sitting at 88% right this minute:

Background: I have 5x 2TB NVMe SSDs in a RaidZ1 pool (non encrypted, some datasets have compression and some do not), used as my cache. I'm sitting between 80% and 90% utilization at any given time (8TB usable, ~1TB free). Moving large files within the pool is very slow compared to when I was running the same drives in a BTRFS Raid1 pool (5TB usable). Moving a 5GB file from folder A to folder B within the cache gives me consistently less than 500MB/s transfer speed (usually much less), while I was seeing around 1.5GB/s on BTRFS. Not sure what I can check here. Could this be due to the higher pool utilization? I have a 10th gen i7 and 48GB of RAM, and the system isn't taxed. The PCIe bus is 3.0 and all NVMe's have DRAM. Thanks for your suggestions!

Odd issue today...trying to move files off my ZFS cache and...nothing is happening. I've had Mover Tuning for years without issue. I have tried changing a LOT of these settings to see if anything changes and nothing has worked so far. I haven't tried disabling Mover Tuning yet because I don't want to clear the cache pool out at this point. My Mover Tuning settings: My share overview is attached as well. If I run the dedicated "move all from this share" in a shares settings, Mover works. When I run mover via Move Now (or via the schedule), the log shows this: Nov 22 06:43:37 Tower emhttpd: shcmd (206793): /usr/local/sbin/mover |& logger -t move & Nov 22 06:43:37 Tower root: Starting Mover Nov 22 06:43:37 Tower root: Forcing turbo write on Nov 22 06:43:37 Tower root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 45 5 0 "/mnt/user/system/Mover_Exclude.txt" "ini" '' '' no 100 '' '' 95 Nov 22 06:43:37 Tower kernel: mdcmd (46): set md_write_method 1 I don't get the ****staring mover*** line in the log. When I run mover manually from a share's settings page, I get a much nicer looking set of logs: mvlogger: Log Level: 1 mvlogger: *********************************MOVER -SHARE- START******************************* mvlogger: Wed Nov 22 05:52:42 EST 2023 mvlogger: Share supplied CommunityApplicationsAppdataBackup mvlogger: Cache Pool Name: cache mvlogger: Share Path: /mnt/cache/CommunityApplicationsAppdataBackup mvlogger: Complete Mover Command: find "/mnt/cache/CommunityApplicationsAppdataBackup" -depth | /usr/local/sbin/move -d 1 file: /mnt/cache/CommunityApplicationsAppdataBackup/ab_20231120_020002-failed/my-telegraf.xml file: /mnt/cache/CommunityApplicationsAppdataBackup/ab_20231120_020002-failed/my-homebridge.xml ... Running a find command shows plenty of files older than the specified age that should be caught by the mover: root@Tower:~# find /mnt/cache/Movies -mtime +45 /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023).eng - 1080p.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023).eng -.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023) - 1080p.fr.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023).eng.HI -.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023) - 1080p.es.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023) - 1080p.en.srt /mnt/cache/Movies/Movies/BlackBerry (2023)/BlackBerry (2023) - 1080p.mp4 /mnt/cache/Movies/Movies/80 for Brady (2023) /mnt/cache/Movies/Movies/80 for Brady (2023)/80 for Brady (2023) WEBDL-2160p.es.srt /mnt/cache/Movies/Movies/Toy Story 4 (2019)/Toy Story 4 (2019).mkv /mnt/cache/Movies/Movies/Toy Story 4 (2019)/Toy Story 4 (2019).en.srt /mnt/cache/Movies/Movies/Toy Story 4 (2019)/Toy Story 4 (2019).en.forced.srt /mnt/cache/Movies/Movies/Toy Story 4 (2019)/Toy Story 4 (2019).es.srt /mnt/cache/Movies/Movies/Toy Story 4 (2019)/Toy Story 4 (2019).fr.srt Diagnostics attached in case it helps. Thanks! tower-diagnostics-20231122-0656.zip