Adrian

Ok, I swapped out the 128GB drive with a matching 256GB drive, added the missing drive to the pool and started it up. Looks like everything is good now, but please confirm. Thank you, Adrian mediaserver-diagnostics-20230629-1249.zip

Ok, so if I wanted to just fix everything and get this setup correctly, could I simply stop docker, then copy all the contents from /root/media/cache, that's where I see the appdata, docker, and some other folders that are on the SSD to a backup folder. Then replace the 128GB drive with another 256GB drive and just recreate the raid1 cache and copy the folders back?

It's been years since I set this up, but I've uploaded the latest logs where everything is working. If you need to know any of configuration setting values, let me know which ones specifically and I'll reply back with them. It looks like I have 2 physical SSDs in my server. Not really sure what I was trying to do. I see one listed under Pool Devices and the other under Unassigned Devices. I think I was trying to have one for cache and one for docker. Please note, there's a high possibility that I might not have had all this configured in a typical way. mediaserver-diagnostics-20230628-1139.zip

While the cache pool not mounting is a problem, the real problem is 6.12 which obviously has some changes that somehow is breaking it. I may have jumped the gun too fast and I'm not really ready to deal with working through the issues. I'll try it again when I have some more time so I can provide more info to help sort this out, but for now I've reverted back to 6.11.5 and everything is working again. I'll try to read up on the changes and post in the release forum. Maybe there is something I can change in preparation to upgrading to 6.12.

Yes I saw that, but it's been years since I set all this up and I don't know how to fix it. Do you do this under unassigned devices in the "Change Disk Mount Point" dialog that pops up when I click the drive? When I tried to change that to "cache" I get an error saying, "Jun 28 08:39:45 MEDIASERVER unassigned.devices: Error: Device '/dev/sdc1' mount point 'cache' - name is reserved, used in the array or a pool, or by an unassigned device." It sounds like 6.12 introduced some breaking changes. I can name it something else and mount it, but now I see it as /mnt/disks/ssd so looks like "disks" got added to the mount path. This should let me fix the Docker vDisk location, but not the Default appdata storage location which I had on the SSD also. It's only listing the user shares on the array, so I can't set it to /mnt/disks/ssd/appdata. Looks like other users are having issues after the upgrade. I reading up now to see if what solutions are already out there.

I recently updated to 6.12 and found my docker down. When I access the Docker tab I see the following message, Docker Service failed to start. I noticed there was an update to 6.12.1 and upgraded thinking maybe it had a fix for this issue. Same error message. It's been forever since I set all this up, so not even sure where to start to troubleshoot. I do see the drive listed under unassigned devices and if I mount it I can browse the contents and I see everything is there, including the docker image. Thanks in advance, Adrian mediaserver-diagnostics-20230627-2051.zip

Worked perfectly, thank you again!

Great, thanks again. Parity2 building now.

Current system has 2 Parity and 17 disks. I want to physically re-arrange the disks and want to confirm the steps. Stop Array New Config -> Preserve Current assignments = None? Configure Parity and Disk 1 - 17 in Array Devices When do I state that Parity #1 is valid? When do I set Parity 2 so that it rebuilds only the 2nd parity? Thank you, Adrian

Disregard everything I said about the folders and names being difference. I was looking in the wrong place, my fault. It's all good. Thank you trurl and everyone else for your help and guidance, I really appreciate it!

The old repairs that I ran were the ones previously instructed to run. I was told that was only on the emulated disks. Recently I just put the drive in the available slot and mounted it as an unassigned drive. I used the Web UI to browse the contents.

Yea that part I understood. It's just 2-3 other folders in their normal location that were not named correctly. The folders had some videos and were named with the event (concert) name, but I renamed them to include the date and city/state as the concerts are part of a tour. It's the date and city/state of the folder name that was missing.

haha yea true

Former disk 14. Disk 15 was always unassigned, it's where I would preclear from. At some point I want to rearrange the disks so I don't have a disk id being skipped, adds to the confusion.

Well this is odd, the original drive looks same. I recall the repair saying something about logs being discarded. May the folder renames were in the logs that were discarded? Any recommended tools\scripts to run to compare the drives?