Junsas

Ok thanks for the quick reply! I thought raid 1 would mirror also with more than 2 drives. Regarding my 2nd question: I only want the two new drives in the pool. Can I just remove the original one and the pool will be OK with the 2 remaining drives? Or is it more complicated than that? EDIT: Ok, this sounds like it will be possible:

I recently tried to add two new SSD to my cache pool and are experiencing an unexpected behavior. The cache pool had one 500GB SSD (SATA) with BTRFS RAID1. I assumed I can add my two new drives (also 500GB, but NVME) to the pool, so that the original SSD will be mirrored to the two new ones. However, now I see a pool size of 750GB instead of 500GB. In addition, it displays 381GB in use and 228 as free, which are just over 600GB. So now I am a bit confused about what's going on. All I could find is, that if disk size is the same, it should be possible to just add the new drives and it should mirror to the new drives. Can somebody explain or point me in the right direction? Thanks! If any info is missing, please let me know! I am now on v6.12.8. However, when I added the two new drives, I was still on 6.9.2. Just updated today, after I had problems a while ago and had to roll back and forgot to try again. Just in case this could be relevant. --- Another question: Once this is cleared up and the cache pool works as intended with 500GB pool size - can I just remove the original drive from the pool and only leave the two new ones? Or will that cause problems?

Small update from my site. I have installed a new 16TB drive and precleared it for testing. Now the parity is being copied from my old 12TB to the 16TB drive. Let's see how it goes :)

Yes, all disks are mounted. I was/am just not sure if all data on disk 3 is uncorrupted after the rebuild? When the rebuild finished with errors, I just assumed there must be some corrupted files somewhere? Or was the result "just" the corrupted filesystem and I got lucky that this could be repaired without any files landing in lost+found? Array is shut down and will stay shut down until a new drive arrives. What would be the safest way? Parity is currently 12tb, but the sweet spot for a new drive would be 16b. Can I manage it risk free with a 16tb and parity swap? Or would it be much safer to buy another 12tb drive and just replace disk 2?

thanks so much for taking the time @trurl! Yes, I know I should have just shutdown the array and posted here, when the first problems occurred. Sometime you (I) think the situation is manageable and then you're suddenly in over your head! I know it is a mess and I made the situation worse. Thanks for taking the time to help me! Already had some serious lessons learned from this experience. A scheduled parity check is once a month. I am pretty sure that the unclean shutdown parity check started on August 19th in the late evening and I stopped it at around 1/2am on August 20th after I saw the many errors during the check and the read errors on disk 2. Why are you still running 6.8.3? I updated a few month back to current version, but had a problem with VM startup, which I couldn't solve. I was planning to install the new hardware anyway and thought I will wait until that is done. No SMART errors except disk2 (pending sectors and multi zone errors). Disk 3 has UDMA CRC error count = 79, but that was probably due to the marvel controller acting up. The Marvel controller was removed from the server after disk 3 failed. During rebuild of disk 3 and later the disk was connected to the MB sata. Marvel card is gone and won't be used anymore. But it never gave me problems before I switched CPU/MB/RAM. I read, that there seems to be a connection between virtualization features being active and marvel controller problems. My old I5 probably didnt support those and that is why I had no problems with the old build? Disk 1 and 3 had the corrupted filesystem after rebuild of disk 3. I read the parity swap procedure. Main question now is, if the rebuild of disk 3 resulted in usable data, even though I had the read errors on disk 2 during the rebuild? And as you write, if disk 2 can be emulated and mounted.

Hi everybody, I think I fucked up... Short version: Last successful parity check was on August 3rd Changed MP, CPU, RAM on August 5th, no parity check afterwards Unraid crashed during reboot (August 19th) automated parity check after crash resulted in lots of errors, due to read errors on disk 2 (which had a pending sector for a while, but never acted up before) replaced cabeling, restarted parity check, then disk 3 (marvel controller card) was marked as failed Removed marvel card, rebuild disk 3 from parity, but had lots of read errors from disk 2 again (August 20), runraid showed health as "green" After restart filesystem of disk 1 and 3 was corrupted. Repared both. Disk 2 doesn't complete a extended smart check due to read errors parity check shows now 27729 errors (finished last night, August 22nd) Don't know what to do now, as I have to replace disk 2, but probably parity information is fucked up as far as I understand... Please help Diagnostic files are attached. Pictures, documents etc. are all backup up offsite, so no problem. Media files are expandable and can be re-ripped from BDs. Details: My last successful parity check was on August 3rd. On August 5th I replaced the MB, CPU and RAM of the server to a supermicro x10 with Xeon E3-1275 v3 and 32GB ECC RAM. Before, I was running an old Asrock with I5 and 8GB non-ECC RAM. Initially I also wanted to replace my old Marvel sata card with two ports with a Dell H310 card. I didn't have enough time, so I thought lets do this in the next days, because the Marvel worked perfectly so far (still had to flesh the IT Bios of the H310 card). Unfortunately after the replacement it never occurred to me to do a non-correcting parity of the new build. The server was running fine until Thursday, August 19th, when during a manual reboot the array would not stop (took forever) and then unraid froze completely. I waited a few hours, but no response, so I did a hard reset. When the server was back up, all Docker where gone. Apparently the docker image was corrupted and reset. No biggie, installed everything and all worked fine. After the system was back up, an automatic parity check was started (with correcting errors) and showed quite many errors (633) after ~ 2h30 at which point I also saw that disk 2 had read errors. So I stopped the parity check and read up on the forum. Then I understood, that automatic parity checks with correcting errors is not such a good idea, because of the risk if you have a broken disk. In a few threads it was suggested that read errors could be cable problems, so I replaced the cable of this drive and started another parity check (non-correcting). Then disk 3 which was connected to the Marvel card started to act up and was marked as failed by unraid. I removed the marvel controller and attached disk 3 to the MB controller. At this moment I still had hope, that problems on disk 2 were due to a bad cable and rebuild disk 3 from parity (big mistake I guess). Rebuild completed with lots of errors (1405) on Friday evening, August 20. Disk 2 still had read errors Disk 2 smart extended test does not complete due to read errors Parity check shows now 27729 errors (finished last night, August 22nd) Don't know what to do now, as I have to replace disk 2, but probably parity information is fucked up as far as I understand... Parity drive is 12TB, I plan to buy one or two new 16TB. Can I relplace disk 2 with the 16TB and have only 12TB usable? Please help Diagnostic files are attached. Pictures, documents etc. are all backup up offsite, so no problem. Media files are expandable and can be re-ripped from BDs. PS: I hope all is clear and all info is included in the diagnostic files. If not, please tell me. bigfoot-diagnostics-20210819-2216.zip bigfoot-diagnostics-20210822-1257.zip bigfoot-diagnostics-20210820-1821.zip