Rich Minear

That was what I thought might need to happen, but wasn't sure. First time running across this. And it worked like a charm. Since I had a Dual Parity system, I was able to swap out one of the parity drives and it ran for about 24 hours. Then I was able to take the old parity drive and use it as the new data drive. Thanks for the excellent help!!! rm

/dev/sdc = new drive /dev/sdf = 1st parity drive /dev/sdg = 2nd parity drive root@swissarmy:~# fdisk -l /dev/sdc Disk /dev/sdc: 10.92 TiB, 12001339219968 bytes, 23440115664 sectors Disk model: ST12000NM0127 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes root@swissarmy:~# root@swissarmy:~# root@swissarmy:~# fdisk -l /dev/sdf Disk /dev/sdf: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors Disk model: ST12000NM0127 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: CACBBE2B-BBCA-4E51-B450-06A31CE2595A Device Start End Sectors Size Type /dev/sdf1 64 23437770718 23437770655 10.9T Linux filesystem root@swissarmy:~# fdisk -l /dev/sdg Disk /dev/sdg: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors Disk model: ST12000NM0127 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: BA5F0623-3045-41C4-B5F7-820D1431CB13 Device Start End Sectors Size Type /dev/sdg1 64 23437770718 23437770655 10.9T Linux filesystem root@swissarmy:~#

I have a two-parity drive system that contains Western Digital ST12000NM0127 Drives (12 TB). I have a failed drive that is a Toshiba 3TB drive. I'm replacing it with another Western Digital ST12000NM0127 Drive (12TB). I shut down the array, turned of the server. Replaced the drive, and started it back up. When I go to replace Disk1 (which is missing now), I see the new drive. But I get the error: "Disk in Parity slot is not the biggest". Not sure where to go next..... swissarmy-diagnostics-20240722-1312.zip

That appears to have worked! Thanks for the tip.

Good morning! I have an older version of memos running under docker on my server, and I see that there is an update. I had used the docker cli to install in. Any idea how to update that with yours in the community app repository? I'm hoping not to lose my existing posts/memos. Thanks

I had the most recent Plex docker, and I was getting corruption of my DB with 6.7. Rolling back to 6.6.7 stabilized everything. I've been reading through the forums here and people have stated that the config files should be on the cache drive...but I do not have one. They also stated that you should put the config files on a single disk rather than on the "array". But I went for over a year with zero problems the way mine was configured (no cache, and on the array)....it only started to corrupt with 6.7. So I'm waiting a while before I upgrade...and "studying" some more.