Drezzden865

Once again thank you to everyone who assisted me on this issue. Thanks to all of you my server is Back you and Healthy finally. I am currently working to rebuild all my Docker apps.

Thank you i will try that.

Ok, is there a way to make docker relink to the app data or should i just reinstall the apps and point them to the same folders

As for formatting Disk1 - I did that and blew it completely to fresh the first time and this issue happened again. Is there anything more i need to do other than go to the Main section and in the bottom select the disk1 and select format? GREAT NEWS I did do the update to 6.12.5 and restarted and Disk2 is backup and running, My Shares are back and Docker path updated the Cache Path and the Docker starts but when i got to Docker it isn't showing any containers. THANK YOU ALL for all the Help

At some point last night the Disk1 just posted Exiting now. Last night will looking at the system i did find a oddity that i had not really noticed before and i just wonder if this could be a issue. The Cache drives both old and new are set to BRTFS format but all the other drives in the system are set to XFS. I'm fine to Format that drive its been done once before. about a month later it did the same thing again and then disk2 did it as well. I just want to make sure i do it correctly to not have this issue again. If i pull the drive and do you think i would be able to attach it to another PC and recover the Information that was on the drive through file explorer. Also is there something i would do other than format the drive.

I went in to the GUI and selected disk 1 and found the Check Filesystem Status section and removed the -n and started the check. this happened right away. its been about four hours now and i have added the results of disk 1 and 2 to my last post.

Any idea how long it will take to Check the Filesystem on a tb drive. I triggered the scan without the -n on disk1 and it instantly told me { Phase1 - Find and verify superblock... Bad Primary Superblock - -Bad macgic number !!! Attempting to find secondary superblock.... } It has been sitting ther stating running for about 4 hours now attached is the result and nothing seems to have changed Disk 1 and 2 Check logs.txt

@JorgeB I will run that tonight and if it works ill do the update. Or should i do the update first? @trurl All the important data is backed up in other places and i have a record of everything on there is just alot of data to replace. What about getting the shares back and access to the data again? What do i do about the Docker not letting me change the path to the new cache drive? Thank you Both for assisting

tower-diagnostics-20231128-1009.zip @JorgeB and @trurl He are the most recent Diagnostics. The rebuild of the Parity drive completed again and the disk1 rebuilt again as well. Both Disks 1 and 2 are still showing the filing system error. My Docker still wont start or update the file path and the shares are still missing i worry that i have just lost all my data.

Yes those where the Diagnostics from before i removed disk one and started the rebuild of the parity and disk one again. I can pull some more tonight and post them.

Support Canceled my appointment 10 mins after it should have stared and i have already paid for it.

tower-diagnostics-20231123-1738.zip I did schedule a support session for Sunday. because i'm not getting anywhere on this.

So Update. I have replaced the PDU with a 1050w unit but in the ordeal i ended up having to replace the motherboard and CPU. Which caused my Lic to fall off and i lost alot of my configs as well and my server name. I was able to reach out to UNRAID and get my License readded. While i was doing this i added another 32g of RAM and a 2tb M.2. I also attempted to swap out the 8tb Parity drive to a 12tb as well as purchased 2 additional 12 tb to change out the drives causing issue. I put in the new M.2 and copied everything over and moved all the shares to the new catche and i was pretty sure Docker. When i changed the PDU i took the old Cache out of the tower and installed one of the 12tb drives to replace the parity with the original still attached. Upon power on, in the software i swapped the parity drive from the current 8th to the new 12 tb and moved the 8tb into the place of disk1 that was not showing at all in the raid anymore. Both rebuilt and it all 8 disks were green. When finished my Docker wouldn't start, when checking my system the docker was still pointing to the old Parity drive. The system wouldn't let me remap it, every time i would go to apply it would just revert back. Disks one and two are still showing Unmountable: Wrong or no file system. Also all of my shares are missing in the software. i took the system down removed the disk one a plugged to old Cache drive in its place. I then turned the tower back on, it is now showing that the old cache drive is back installed and the new M.2 is showing as well. The the old 8 tb Parity drive (that should be the new disk1) is showing up as showing up as the the parity drive and the 12 tb drive is not showing up at all. I attempted to run the script from before and was informed that the file did not exist. my shares are still not showing up and Docker is still not starting. I have turned the tower off and checked all connections. and the 12tb device is still now showing back up, but it turns out not all the sata connectors on the Motherboard work. and i dont have any available ports. When i plug the 12tb in again the system started rebuilding the drives again.

xfs_Repair -v Cleared both drives and they are both showing empty even tho disk 1 is not showing up in the unraid. I lost the data and cant figure out it there is a way to cause it to rebuild manually on disk 2 But im guessing its a moot point as parity ran last night even tho i had it turned off

Ok i used the terminal to navigate to that file and renamed it .bak and restarted the server. I logged back into the server at its new location and went into the Date and time in settings. I was able to adjust the Time Zone and date i had to change manually. I was then able to add my registration key. The docker apps started and are running but not at the right ip so i change the static back to the original. i got the error that the disk was 'unmountable: wrong or no file structure' on disk 1 and 2. I was able to run xfs_repair -v /dev/md2 but the drive came up empty even tho it rebuild yesterday. Is there a way to trigger a rebuild manually? New log file attached tower-diagnostics-20230910-1257.zip