2TC

Alright, this explains it. The AWS part seems hardcoded, and the linode expects "AKIA"-prefix of the Key ID and Access Key. From the payload I can read provider: s3 provider_config[access_key] provider_config[secret_key] So unless I make a change to the actual config or it is being added as an alternative in the base, it will most likely fail.

When I try to add linodes object storage (equal to aws) as the cloud sync configuration I am getting an error "GET /api/shared/notification?type=error&message=An%20error%20occurred%3A%20Unprocessable%20Content HTTP/1.1" 200 OK Anyone know what could be the cause of it?

I figured it out after reading how to delete a pool.. I did not realize I could click the pool name and then remove the pool.. That really feels like a very rookie mistake. I did the following * Deleted both pools * Created a new pool * Assigned the new drive and started the array. * formatted the newly assigned drive.

Alright. That is great! yes, they both were completely empty and all the data was moved over to the array before I tried working on the cache drives. I created a new pool. But the old pool os still there. Indicating missing devices. I will not be able to start the array unless they are assigned. Now I have 2 pools giving me the same error. I would like to delete both pools, add one new pool and put the new 2TB nvme drive into it.

btrfs fi show The response is empty. The array is not started (if that is required). I am still worried about the part where "All existing data on this device will be OVERWRITTEN when array is Started". If I can start it without it triggering a new parity sync or if I can rebuild the config without having to triggering it. Essentially afraid I will lose the content on the data drives.

@JorgeB It was/is using BTRFS

Issue: Replacing Cache Drive (1TB SSD → 2TB NVMe) I’m trying to upgrade my 1TB SSD cache drive to a 2TB NVMe. Here’s what I did: Followed forum guides: moved data off, stopped the array, set the cache slot to "no device". Attempted to start the array in maintenance mode, but I got an error: "cache - too many wrong or missing devices" Tried adding the new NVMe temporarily to then remove it (as per official docs), but no success. I also tried: Reducing cache slots from 2 to 1 — unRAID wouldn’t allow it. Is that normal? Ran wipefs -af /dev/sdX on both drives, rebooted — but they still show up as "missing" in the cache pool. Renamed super.dat to super.dat.bak in /boot/config to trigger a rebuild — this unassigned my data and parity drives, but NOT the cache drives... So I had to reassign them manually. Now I’m getting this error for the parity drive: "All existing data on this device will be OVERWRITTEN when array is Started" I triple-checked serial numbers — they match exactly. My question: Can I safely start the array? Or will this force a parity rebuild? Should I be creating a new configuration instead? Even after all that, the cache pool is still not functional. I’m kind of stuck. Any ideas on how to fix this?I

I switched from emilated to host passthrough and now it all works as intended. Thank you very much for the help!

No, not really. I could do either or. I am just used to running it as emulated. And to be frank, I cant say that I have the biggest clue about the pros and cons of the different alternatives.

Thank you for replying, nothing changed in the XML, only changed the version of machine as stated before. When I create a new machine and use the vdisk it works as intended. This VM does not start and throws an error This VM works

Bump

I have a Debian 11 VM that I have had some issues with, so I tried to stop the VM and upgrade the "Machine" from Q35-4.2 to Q35-7.1, thinking this migh solve some issues. When I stopped the VM and changed the value and tried to start it again, I keep getting the following error "Execution error the CPU is incompatible with host CPU: Host CPU does not provide required features: svm" As I understand, svm is related to virtualization for AMD CPUS, I am using an INTEL CPU and the Intel VT-X is enabled in BIOS. I have not update my BIOS or anything. I had not rebooted the computer for over 4 months and after last reboot it all worked as intended. Right now, I updated to the latest version of unraid, 6.12.6 and thought that might solve the problem, it did not. Does anyone have an idea of where to start with this issue? Also, if you want any logs, let me know and I will pull them.

Ah, I assume that is what I mean. When I click the icon on the disk which ways "disk log information". If that is tied to syslog, then yes. Surely syslog gets cleared every reboot, but if it was a read error I would assume it should come up again if there was an issue with the disk.

That is true, I should see them more as statistics overtime than anything else. The error in the disk log is also gone, but I assume that correlate to the error counter changing from 0 to another number. I am currently doing a parity check to see if there will be any errors during that, once it is done and all is good I will redo the smart test to see if that can see anything.

When I boot up my server I get the following error in the output of the screen mv: cannot stat '/usr/local/bin/mover': No such file or directory it is not really an issue, I searched the web and I found this post talking about this and the addon "move tuning plugin", which I assume is "CA Mover Tuning". The post talks about deleting the plugin. Now I do not have an issue with the server not starting, just that the entry is there. I looked at the '/usr/loval/bin/mover' which is a shell script #!/bin/bash PPPID=`ps h -o ppid= $PPID 2>/dev/null` P_COMMAND=`ps h -o %c $PPPID 2>/dev/null` /usr/local/emhttp/plugins/ca.mover.tuning/mover.php $P_COMMAND $1 I looked at the file mentioned, and the mover.php file is where it is supposed to be, seems everything is working as intended, except that I get the error when booting it, surely I could just ignore it. But I rather fix it than leave it there.