Namecaps

It works now but I stopped it after one hour. Why are you copying empty space in the image, it doesn’t make sense. I have 4GB of data there and 1TB of empty space and you’re copying it all. I can’t imagine doing it everyday day over full array and this is just one VM…

almost same error 2026-03-21 01:08:55] Backup session finished - Duration: 21s [ERROR] Skipping HA due to incompatible mount types [ERROR] USER can only back up to USER or EXEMPT (remotes/addons). USER0 can go to USER0, DISK, or EXEMPT. DISK can go to DISK or EXEMPT. [ERROR] Vdisk /mnt/cache/domains/HA/vdisk1.img is on mount type (DISK) and backup destination (USER0) — incompatible combination Stopped HA Started backup for HA VM(s) to be backed up - HA [2026-03-21 01:08:32] Backup session started - Plugin version: 2026.03.20.01

Unfortunately it’s the same [ERROR] Skipping HA due to incompatible mount types [ERROR] They must be on the same mount type i.e both fields using user or both user0 or none using either user or user0 [ERROR] Vdisk /mnt/cache/domains/HA/vdisk1.img is using mount type (USER) and backup destination (USER0) [DRY-RUN] mkdir -p /mnt/user0/Backup-4/VMBackupRestore/HA Started backup for HA

Thanks. I learned something new today. This means I have to fix few other apps I'm using for backup as well then 😂 My backup share contains two disks actually in case one is full data will be copied to the next one. So how this will work in case of vm backup and restore? Same?

Yeah snapshots are a must. I’m also using above mentioned plugin - just keep in mind restoring (this plugin does not restore and there is none that does) is major PITA as you have to use shell scripts from another person. I had major issues with them and took me hours to restore. Ok but I just chose the VM from the picker…So I should choose my destination as disk not share? If so will it end up on an array?

I’m getting: HA's vdisk /mnt/cache/domains/HA/vdisk1.img uses mount type (OTHER) but backup destination uses (USER). Both must use the same mount type. I’m trying to backup from cache to array. Why you are not allowing it? My VM is on cache because I have 2 fast SSDs in RAID1 and backup is of course on array. On another note I came here because I couldn’t find a way to choose destination. Folder picker really should be done differently ;)

I know but there are 4 in total. One of them doesn't seem to be visible

Sadly this doesn't work. Ollama still doesn't see the gpu.

no idea but Ollama:rocm doesn’t work with my 780m. It works for transcodding but ollama doesn’t see the device.

also reviving. any way to disable heartbeat blinking when disks are spun down? I have 6 of them and LEDs in my new NAS are very bright. I would like to have them completely off when disks are spun down.

how are you have 3 array fans when there are two? unless this is the one in the bottom of the case? that one in bios reports 0rpm to me but it’s working… weird

yeah same :( It seems it’s not maintained anymore. 50* Nvidia are like one year old already.

I’m trying to run it with different frontends but everytime I’m getting this error in logs. Can you advise how to fix it? /config/03-invokeai/env/lib/python3.11/site-packages/torch/cuda/__init__.py:287: UserWarning: NVIDIA GeForce RTX 5060 Ti with CUDA capability sm_120 is not compatible with the current PyTorch installation. The current PyTorch install supports CUDA capabilities sm_50 sm_60 sm_70 sm_75 sm_80 sm_86 sm_90. If you want to use the NVIDIA GeForce RTX 5060 Ti GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/ warnings.warn( /config/03-invokeai/env/lib/python3.11/site-packages/torch/cuda/__init__.py:287: UserWarning: NVIDIA GeForce RTX 5060 Ti with CUDA capability sm_120 is not compatible with the current PyTorch installation. The current PyTorch install supports CUDA capabilities sm_50 sm_60 sm_70 sm_75 sm_80 sm_86 sm_90. If you want to use the NVIDIA GeForce RTX 5060 Ti GPU with PyTorch, please check the instructions at https://pytorch.org/ge

Cheers man, I’m getting WTR MAX tomorrow and getting ready to move from my intel machine. If you find any other nice tips and tricks for unraid on this machine please do not hesitate to share!

But those chips in same board run for a week now in Ubuntu with no reboots.

CPU is also new... As I have two of the same devices now (they let me kept the old one) I'm running it on plain linux and stressing the memory and no issues. There most be something wrong elsewhere. I changed 2x RAM, Board, Controller, CPU, PSU - nothing else left to change and unraid itself is the only thing left.

Ok but why it started after 8 months and it's happening also on new board? No bios updates were done.

Ok so I would like to come with the update. Unfortunately rebooting problem is not solved, but I start to believe it's software problem. After replies I should check the RAM I indeed removed one of two 32GB chips and lo and behold - server was working fine for a week without an Issue (mind I had 50% chance chip I removed is the faulty one). I decided to get a ram replacement. When It arrived I put it in - reboot after 1 hour. I thought - OK I was wrong got the wrong chip replaced. Got another Replacement for the first chip and same story, reboot after few hours. I started to test RAM chips extensively in the same hardware - 0 errors in memtest after running it for 48h so chips I replaced were actually good it seems and new ones are good too. In the meantime I replaced the whole NAS due to UDMA errors - got replacement of same NAS, Same Hardware. And the story continues. No UDMA CRC Errors anymore but it keeps rebooting with 64GB (2x32GB). Now I'm running unraid for 3 days no issue with 1x32GB and 1x8GB chip I found somewhere. So why the server is rebooting without anything in the logs when I work with 2x32GB? Mind that this setup worked fine for almost a year and reboots started out of nowhere. How do I narrow the real problem since hardware is OK? People are running same hardware with 96GB no issues and I had no issue running it for almost a year with 64GB.

I did not use powertop, ASPM disabled earlier, no dice. Unfortuanetly no way to update bios as manufacturer doesn’t release anything new yet (latest is from Aug 2024). Well, will try to play with settings further, but for now I need to get the system stable like it was for past 200 days so let’s start with the RAM. By the way NAS is Terramaster F6-424 MAX so someone can find this thread if they’re looking. Will update if I find something that helps.

Yeah this is what I suspect but how to address it now? Same disks were working fine under TOS (linux that NAS came with). Is there anything I could look up in bios?

All Disks. It started as soon as I installed Unraid and created and started array (for 2 weeks I was using original os without any issues) All 6 Disks, all new. It happens on a a disk which is currently in use. EDIT: Forgot to add I found a reddit user with exactly the same problem on same hardware with same disks (Ironwolf pro) and also only with Unraid…

Thanks this is basically what I'm doing now. Will see. I still would like to do something with udma errors but don't know how can I solve it. I have this problem only in unraid so I suspect it doesn't like the controller. There are no cables or way to reseat anything and it happens on all 6 drives so definately something with contriller but on the original system (also linux) this NAS came with no issues whatsoever. Maybe something to disable in BIOS? [ 3240.647354] ata1.00: sense data available but port frozen [ 3240.647363] ata1.00: exception Emask 0x11 SAct 0x80 SErr 0x0 action 0x6 frozen [ 3240.647365] ata1.00: irq_stat 0x48000008, interface fatal error [ 3240.647367] ata1.00: failed command: READ FPDMA QUEUED [ 3240.647368] ata1.00: cmd 60/80:38:78:6e:e9/01:00:ee:00:00/40 tag 7 ncq dma 196608 in res 43/84:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3240.647373] ata1.00: status: { DRDY SENSE ERR } [ 3240.647374] ata1.00: error: { ICRC ABRT } [ 3240.647377] ata1: hard resetting link [ 3240.952430] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3241.057220] ata1.00: configured for UDMA/133 [ 3241.057259] ata1: EH complete [ 3241.103343] ata1.00: sense data available but port frozen [ 3241.103348] ata1.00: exception Emask 0x11 SAct 0x100000 SErr 0x0 action 0x6 frozen [ 3241.103350] ata1.00: irq_stat 0x48000008, interface fatal error [ 3241.103353] ata1.00: failed command: READ FPDMA QUEUED [ 3241.103354] ata1.00: cmd 60/00:a0:f0:ee:08/02:00:7c:00:00/40 tag 20 ncq dma 262144 in res 43/84:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3241.103358] ata1.00: status: { DRDY SENSE ERR } [ 3241.103359] ata1.00: error: { ICRC ABRT } [ 3241.103362] ata1: hard resetting link [ 3241.410345] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3241.507577] ata1.00: configured for UDMA/133 [ 3241.507595] ata1: EH complete [ 3241.543370] ata1.00: sense data available but port frozen [ 3241.543375] ata1.00: exception Emask 0x11 SAct 0x8 SErr 0x0 action 0x6 frozen [ 3241.543378] ata1.00: irq_stat 0x48000008, interface fatal error [ 3241.543379] ata1.00: failed command: READ FPDMA QUEUED [ 3241.543380] ata1.00: cmd 60/00:18:f0:ee:08/02:00:7c:00:00/40 tag 3 ncq dma 262144 in res 43/84:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3241.543384] ata1.00: status: { DRDY SENSE ERR } [ 3241.543386] ata1.00: error: { ICRC ABRT } [ 3241.543389] ata1: hard resetting link [ 3241.849924] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3241.949575] ata1.00: configured for UDMA/133 [ 3241.949591] ata1: EH complete [ 3242.040303] ata1.00: sense data available but port frozen [ 3242.040310] ata1: limiting SATA link speed to 3.0 Gbps [ 3242.040311] ata1.00: exception Emask 0x11 SAct 0x20000 SErr 0x0 action 0x6 frozen [ 3242.040314] ata1.00: irq_stat 0x48000008, interface fatal error [ 3242.040316] ata1.00: failed command: READ FPDMA QUEUED [ 3242.040317] ata1.00: cmd 60/00:88:f0:f0:08/02:00:7c:00:00/40 tag 17 ncq dma 262144 in res 43/84:00:00:00:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error) [ 3242.040321] ata1.00: status: { DRDY SENSE ERR } [ 3242.040323] ata1.00: error: { ICRC ABRT } [ 3242.040325] ata1: hard resetting link [ 3242.344742] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 3242.449260] ata1.00: configured for UDMA/133 [ 3242.449276] ata1: EH complete

up

Unraid died again with automatic reboot. Unfortunately there is nothing interesting in the remote log :/ Last ones are these Sep 8 10:29:41 Tower sshd-session[3167839]: Accepted keyboard-interactive/pam for root from 192.168.1.189 port 55222 ssh2 Sep 8 10:29:41 Tower sshd-session[3167839]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0) Sep 8 10:29:41 Tower sshd-session[3167839]: User child is on pid 3167844 Sep 8 10:29:41 Tower sshd-session[3167844]: Starting session: shell on pts/1 for root from 192.168.1.189 port 55222 id 0 Sep 8 10:29:41 Tower sshd-session[3167844]: Starting session: command for root from 192.168.1.189 port 55222 id 1 Sep 8 10:29:41 Tower sshd-session[3167844]: Close session: user root from 192.168.1.189 port 55222 id 1 Sep 8 10:29:41 Tower sshd-session[3167844]: Starting session: command for root from 192.168.1.189 port 55222 id 2 Sep 8 10:29:41 Tower sshd-session[3167844]: Close session: user root from 192.168.1.189 port 55222 id 2 Sep 8 10:50:22 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update Sep 8 11:17:26 Tower emhttpd: read SMART /dev/sdf Sep 8 11:28:57 Tower autofan: Highest disk temp is 36C, adjusting fan speed from: OFF (0% @ 0rpm) to: 181 (70% @ 1377rpm) Sep 8 11:29:04 Tower autofan: Highest disk temp is 36C, adjusting fan speed from: OFF (0% @ 0rpm) to: 181 (70% @ 1386rpm) EDIT: Wait, this time is different. After reboot one of my disk dissapeared from Array. I rebooted manually and it showed again… This wasn’t the case in last 2 reboots. I’ll investigate futher but disk seems fine now… I have no clue what’s causing these reboots.

Yeah I suppose but it's less than a year and was working great till yesterday. Anyways let's wait and see