thekiltedwonder

I think we are talking past each other. I understand what you are saying. I did not move or delete anything on the emulated drive. Further, all files are still available and none have been deleted from teh array. Because I did not move anything, I am trying to understand why certain files were on the original physical drive, but on a different physical drive after the drive was rebuilt.

To be clear, it is still on the array, but not on this particular drive. That is what has me confused. As soon as the issue happened, I did my best to ensure that nothing changed so I didn't accidentally overwrite anything. To that end, I made no changes after the drive wouldn't mount properly and had not added or removed anything from the drive in the prior couple of days.

tower-diagnostics-20260810-1923.zip For some reason my text was deleted when I hit submit. It's working properly, but one thing happened that I did not understand. There are several files on the removed drive that are not on the rebuilt drive, but are on the server. Is that normal? Other than that strangeness, it's working fine.

Thanks. There shouldn't be any writes after the issue popped up, I'm going the careful route anyway.

I've used that in the past and totally forgot. Perfect. Thanks! Everything looks good. I'm going to go ahead and swap in a new disk and rebuild to that. Unless something stupid happens, I think this is solved. I'll come back and officially mark it solved once the rebuild and update are done.

Is there an easy way to check that disk specifically? My Shares are not assigned to any specific disks and all disks are near full. My first thought is to just pull the drive and check it on my desktop, but if there is a better way, I can do that. Also, how should I handle updating? Assuming everything looks good emulated, should I rebuild this first, then update and potentially need another rebuild? Or should I update first and then rebuild afterwards? Also, I have two new disks to go in. Would I be best off to rebuild to that and keep this one as is until I verify that everything is kosher with the rebuild? Also, thanks a million.

I rebooted and started the array. Here is the diag file from immediately after doing that. tower-diagnostics-20260809-1441.zip

I did nothing else. I've never used Docker, but was thinking of installing Pi Hole in Docker. So I wanted to be fully up to date before doing anything. I hit upgrade, rebooted when it said to, and the issue was there immediately. For the diags, I rebooted and started in Maintenance mode. Is that what you wanted or did you want me to start it in normal mode? tower-diagnostics-20260809-1047.zip

I finally upgraded to 7.x from 6.9.2 and one of my drives no longer mounts. I then downgraded back to 6.9.2 and the problem persists. xfs_status shows: Not available Trying Check anyway does not appear to even attempt to fix anything, when run without flags. Running xfs_repair -v /dev/md6p1 yields : /dev/md6p1: No such file or directory /dev/md6p1: No such file or directory fatal error -- couldn't initialize XFS library To ensure I'm running that correctly, this is Disk 6, so md6p1 should be correct, right? Unraid was running fine prior to the upgrade. Every test I've run on the drive shows good. I can run any specific tests you want. My last parity check was about a month ago and I have not had a single error since I upgraded my drives ~4 years ago. Any help is greatly appreciated. tower-diagnostics-20260808-1909.zip