brambo23

I recently upgraded my unraid server to 6.12.8 from 6.9.2 due to other issues. After the upgrade it seemed the docker settings slightly changed (i also accidentally upgraded to the latest version when I was on 22.2.2, but updated the tag to the version i'm currently running.) The port switched back to 443 (default port). I had changed it back to the previous setting port 4445 (noted in the config file below). I did run a new permissions as i found an issue with my plex server and upgrading past 6.10. Since the upgrade my nextcloud is now returning a 404 error on any page I visit. I'm struggling to find any additional clues on where to look to find the problem. The docker logs show: but then later i went to look at it and saw this repeatedly The port on the docker container matches the config file The access logs show regardless of where i go (nextcloud/log/ngix/access.log) Any tips on where I can find the source of the problem here?

Happy to report that the data is back and the parity is rebuilding with no issues. Appreciate all the help!

On the physical disks yes, I did not do anything with the emulated disks (that I know of) I repaired, mounted, and looked in the drive itself again, found no folder or entity titled "lost+found"

What I meant by is, I started the array and it immediately began the rebuild process. Out of fear I cancelled the process, and the drives were not mountable until I did a file system check. It repaired the issue again then I was able the mount the drives again. It would appear the corruption is already logged in the parity There's nothing terribly lost, mostly just time. I don't store important personal data on this array for that reason. If it were to die, all I would of lost was time. My goal is to save myself time if at all possible. I built this server many years ago but when it comes to the details of how everything works, I will admit I am not the most knowledgeable (if that isn't already apparent). So having said that, it seems if i want to keep the data and the fixed drives, the best move is to reset the array configuration?

So they will remain unmountable until the rebuild finishes?

Judging by all the information I'm reading, it sounds like resetting the array configuration is the only way to make sure the data on the two drives remain intact

I do not see any lost+found folders on the physical disks in question i tried re adding the drives and "rebuilding" the array, but when i started the array, the disk 8 and 9 were still listed as unmountable

You are correct, you didn't post a direct link, but it was in the contents of the one page you did link https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

so the second problem with that is i realized the emulated data is missing the data that's on those physical disks what happens if i rebuild the array with that status? will it rebuild the array as emulated then the data from the physical disks gets added? or the physical disks look more like the emulated disks and i lose that data anyway?

So I looked at the link you sent about rebuilding data onto itself. The emulated data is missing the data that is on those drives. Should I copy the data off those drives in order to properly rebuild the array? I assume if I add those drives back, since the emulated data is missing the data on those drives, it will blank out the data

I can see data on the disks. Do I have to reassign them? Can i just add them back to the disk they were originally assigned to?

I ran it again (didn't change any flags) now it says no data corruption detected

So after this test, I mounted and unmounted the drives (unassigned) and it was able to read the amount of data on the drive, I ran the file system check on both drives and now both of them say no file system corruption detected. Also I did buy and install a new card based on the recommendation of @trurl should I be ok to mount these drives back in the array and try to start the array again?

So i upgraded, installed For drive in SDC (252MG) : For drive in sdb (RD0B)

well, i'll give it a shot then