karateo

+100000000000000 I spent hours trying to understand whats needed. Different hardware, different unraid versions, different drivers, different plugins. Some posts in this forum, some posts in reddit, some issue discussions in github! Documentation 3 months ago when I was trying to understand how to set up Ultra 7 265k was incomplete. Those are the results for SR-IOV today. Only changelogs. https://docs.unraid.net/

I also own an ultra 2 cpu and i was waiting for this beta. Unfortunately there is a bug of unmountable disk so i will wait for beta2 to test. I really need to start using my igpu using the virtual gpus feature.

I think that solved it! I didn't know that /mnt/user/Photos appears the same folder as /mnt/some-cache-drive/Photos Thank you for your help. It drove me crazy as there was nothing accessing the cache pool directly! No spin ups since yesterday afternoon that I did what you suggested. Thank you all!

I created a new share with only new cache pool named Photosimage and run mv /mnt/photoscopy/Photos /mnt/photoscopy/Photosimage/Photos I don't know why the cache only Photosimage has a green cycle thinking thats in the array!

I will try what Kilrah suggests and if I can't solve it, I will run in safe mode. I need Homeassistant to run my house so this is the worst case scenario!!!

1) Creating a new cache pool using two drives as single with a different name (/mnt/photoscopy) than any other share is not a problem right? 2) How can this command appear as a copy? It's not linked in any way with the old share (/mnt/user/Photos). rsync -avh --info=progress2 --stats /mnt/user/Photos/ /mnt/photoscopy/Photos/ The new mount point should be "incognito" !!! I will try to create a new share using Unraid GUI and select only the new cache pool and I will run mv /mnt/photoscopy /mnt/new-share-name right?

I have not created any share! I only created a new cache pool using two drives as single and I used their mount point /mnt/photoscopy to rsync my share /mnt/Photos It drives my crazy! I uninstalled most of my plugins, checked all mount point in running dockers (VM are shut down) and checked all settings in Unraid for any scheduled job but I didn't find anything!

I still cant figure what causes the disks to spin up. I uninstalled some plugins but it didn't fix it. Any idea what to look for? tower-diagnostics-20260105-1007.zip

Happy new year! Wishing everyone a New Year filled with good health! I am using latest Unraid. I created a single btrfs cache pool with two disks. I set spin down in 15 minutes. I don't use them anywhere in unraid. Dockers/VMs... I want only to use them to rsync a share /mnt/Photos once per week. For some reason they spin up as it appears in specific intervals. I run File monitor and it didn't catch anything as expected so there must be either unraid or a pluging. I have attached diagnostics. I will uninstall some plugins as a first step. (I was trying to make use of the igpu of the intel ultra 2 but I think I need to wait for the v7.3 with new kernel). Any suggestions what/where to look? tower-diagnostics-20260101-0945.zip

I just built a new server with intel ultra 265k and I want to create virtual igpus. After a lot of reading I think i need to wait for the new kernel. Right? There is no easy way to do it now.

Everything was working fine (changed one cable 10 days ago) and today I got new errors! I need a confirmation that it's the cable of parity 2 (sdf) and I think my usb disk needs to be replaced (sdb) tower-diagnostics-20251008-0842.zip

I noticed today some errors. Any idea if it's something important or should I ignore them?

Thank you very much for your help! The error reporting system should be a little more foolproof!

I had disk2 failing so I bought 2x 8TB disks to replace parity and disk2. Parity was 4TB so I had to add a second parity (8TB) and then remove the old one (4TB) to be able to replace the disk2 with the 8TB) new disk. Parity sync completed without errors. But disk2 rebuilt finished with errors. My problem is that I don't know what kind of error happened. Is any file corrupted so I need to restore it from backups? This part in syslog shows the error. I have also attached diagnostics. Thank you! tower-diagnostics-20250926-0905.zip

Last time I had an error during parity-check was in 2021 (for a 24/7/365 4-5 discs array) and then it was a failing disc. For me (having a Xeon with ECC - don't know if that matters) it's not necessary. If it happens I just need to know which files are affected to restore from a backup. To be fair I hadn't realize that with parity check I am also checking for file integrity (assuming two bit rots in two discs at the same position is realistically impossible!). Just to note that all the above applies only in the case of a filesystem with check summing to identify (through scrub) the altered file. Unraid can not identify which disc had the out of sync bit.