Nomad32

Got it! Thank you!

Thank you for that!!!! I really do appreciate it. My knowledge of linux is just enough for me to be able to google what I want to do, but I don't have any real knowledge of what's happening in the background. Thank you again!

Final update - Magic. I deleted the 2 config files after re-reading your first solution. I was then able to go in and adjust the settings and set things back up. Thank you!

Update - I'm looking at the file system within Plex's docker container - it shows a lowercase "videos" under /mnt/user/

Thank you - I did the clean-up thing and it said it removed 2 shares. I am looking at /boot/config/shares and I only see Videos.cfg (not an additional videos.cfg) - same thing for the other share (Software.cfg). Is it OK to delete that config file? It won't remove the data will it? I'll look through the settings on the docker images.

Sorry about that. tower-diagnostics-20260205-1455.zip

This is a machine that has been up and running for several years now. I've recently updated my server and now I've lost access to a couple of my shares. The share details looks really off, when compared to the other shares that have been up and running for the same length of time. The only thing that jumps out at me is that the 2 affected User Shares are using Cache for storage now (instead of Cache to Array, or most likely I had just set those affected to Array directly). Any thoughts on how to sort getting access to these shares? TIA

Understood. And, it copied directly from my other parity drive. I apologize - but, essentially believed (when I typed that), that I was rebuilding parity, by copying it to the new parity drive?

I ended up buying 2, new, 14TB drives. I started by removing the dead 12TB parity drive, and replacing it with the 14TB drive. Unraid automagically started to rebuild parity on the new parity disk. Once that completed - I followed the steps on the parity swap procedures page:: https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/ For anyone curious - That process basically works through adding a new drive that is larger than your current parity drive. You remove the data drive you're replacing, change the current parity drive to be the data drive, and then assign the new disk as parity. After rebuilding parity, the system will start up the array and rebuild the new data disk (old parity drive converted to data).

OK - thank you. Disk 4 has shown errors for a while now - but, never an issue bad enough to crap out on me. I think I'll pick up a couple of larger drives to replace the parity drives, and then use the good parity drive to replace disk 4. Oh well - thank you so much for letting me know.

Sorry - attached is the SMART report and the diagnostics report. tower-smart-20240131-1218.zip tower-diagnostics-20240131-1220.zip

I don't check the dashboard everyday - but, I checked a couple of weeks ago and found that one of my parity drives had an error and was disabled. I started an extended self-test and these are the results. I'm looking for advice here on if I should ignore the error - or, try to see if the drive is covered under warranty for replacement? Thanks in advance:: ATA Error Count: 11733 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 11733 occurred at disk power-on lifetime: 18079 hours (753 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 50 ff ff ff ef 00 19d+15:20:45.234 READ DMA EXT 25 00 08 ff ff ff ef 00 19d+15:20:45.234 READ DMA EXT 35 00 88 ff ff ff ef 00 19d+15:20:45.231 WRITE DMA EXT 35 00 30 ff ff ff ef 00 19d+15:20:45.229 WRITE DMA EXT 35 00 40 ff ff ff ef 00 19d+15:20:45.227 WRITE DMA EXT Error 11732 occurred at disk power-on lifetime: 18079 hours (753 days + 7 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 c8 ff ff ff ef 00 19d+15:18:55.847 READ DMA EXT 35 00 18 ff ff ff ef 00 19d+15:18:55.841 WRITE DMA EXT 35 00 40 ff ff ff ef 00 19d+15:18:55.837 WRITE DMA EXT 35 00 40 ff ff ff ef 00 19d+15:18:55.833 WRITE DMA EXT 35 00 40 ff ff ff ef 00 19d+15:18:55.829 WRITE DMA EXT Error 11731 occurred at disk power-on lifetime: 18059 hours (752 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 f8 ff ff ff ef 00 18d+19:49:36.163 READ DMA EXT 25 00 88 ff ff ff ef 00 18d+19:49:36.161 READ DMA EXT 25 00 40 ff ff ff ef 00 18d+19:49:36.158 READ DMA EXT 25 00 40 ff ff ff ef 00 18d+19:49:36.140 READ DMA EXT 25 00 80 ff ff ff ef 00 18d+19:49:36.139 READ DMA EXT Error 11730 occurred at disk power-on lifetime: 18059 hours (752 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 18d+19:48:32.973 READ DMA EXT 25 00 40 ff ff ff ef 00 18d+19:48:32.970 READ DMA EXT 25 00 40 ff ff ff ef 00 18d+19:48:32.940 READ DMA EXT 35 00 b0 ff ff ff ef 00 18d+19:48:32.939 WRITE DMA EXT ea 00 00 00 00 00 a0 00 18d+19:48:32.873 FLUSH CACHE EXT Error 11729 occurred at disk power-on lifetime: 18059 hours (752 days + 11 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 ff ff ff ef 00 18d+19:47:56.650 READ DMA EXT ea 00 00 00 00 00 a0 00 18d+19:47:56.636 FLUSH CACHE EXT 35 00 08 ff ff ff ef 00 18d+19:47:56.636 WRITE DMA EXT 25 00 40 ff ff ff ef 00 18d+19:47:56.615 READ DMA EXT 25 00 08 ff ff ff ef 00 18d+19:47:56.614 READ DMA EXT

Thank you! When I searched for the installed apps (via community apps) - it would show a different prompt for items already installed. I clicked reinstall and everything fired up. Plex was a bit of a pita - but, I started over with a new plex install.

I should have mentioned that I've had all of these docker containers installed for months (if not a year). No changes to settings (once I got it installed).

OK - if I move to install again, will it automatically pick up the settings from the installed image?