diagnostics attached.

 

I had 2 disks become disabled in my array. I ran an extended smart tests on both disk 1 & 3 and both completed just fine.

 

I bought two extra HDDs of the same size but i decided to reuse disk 3 and install one of the new HDDs for disk 1. I started with a rebuild of disk 3 by stopping  the array, removing disk 3 from array and spinning it back up. Stopped the array again and added back in disk 3 to start a rebuild of the array. After Disk 3 completed. I stopped the array, removed disk 1 (1eg8sh27) and replaced with new HDD (vchwmjgp) Started back up the rebuilt with the new HDD but during this time i noticed Disk 3 was unmountable.

I see the format button, but if im reading this right, this will reformat the disks and start everything over. I don't mind redoing the rebuild but I'm afraid of it reformatting both drives at the same time and then me loosing data in the process. i still have the old Disk 1 on hand, along with a new and precleared 10tb HDD replacement. I would love to know if there is a way to use them to rebuild everything safely or if just formatting and letting unraid rebuild everything is safe enough.

 

also During the replacement i also noticed some of my disks were out of placed physically in my servers so i arranged them to the ordered that is shown in UnRaid GUI. Which i believe is why disk 7 is showing as  not installed. I wanted to know how to fix this.

 

I have also attached the smart tests for the original disk 1 and disk 3 if it helps.

 

 

dlnqnt-diagnostics-20210811-1318.zip dlnqnt-smart-20210808-0159.zip dlnqnt-smart-20210808-0201.zip

For future reference, Diagnostics already includes SMART for all atttached disks so no need to attach separately.

 

Really wish you had asked for advice before doing anything.

1 hour ago, nos0n3 said:

just formatting and letting unraid rebuild everything

Format is a write operation. Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used.

 

Unraid treats that write operation exactly as it does any other, by updating parity. So after formatting a disk in the array, the only thing parity can rebuild on that disk is the empty filesystem you wrote.

 

In other words, DON'T FORMAT unless you don't want that data.

 

1 hour ago, nos0n3 said:

why disk 7 is showing as  not installed

That shows it in the historical list of Unassigned Devices. Your screenshot of the array shows disk7 is installed and mounted.

 

Since you rebooted after rebuilding and reboot resets syslog, there is no information about the rebuild in your diagnostics, so unless you have syslog from the rebuild can't say what happened. Do you remember if there was anything in the Errors column on any disk while rebuilding? Are you sure parity was valid before beginning rebuild?

 

I guess you will have to repair the filesystems and hope for the best.

 

Check filesystems on both disks and be sure to capture the results so you can post them.

 

https://wiki.unraid.net/Manual/Storage_Management#Running_the_Test_using_the_webGui

 

 

i have two previous diagnostics. One from when i first noticed the error, the other I believe is when i first rebuild disk 3 and before moving around the HDDs  in the enclosure.  Seems my memory is off. must been after both disks were rebuilt

dlnqnt-diagnostics-20210810-0944.zip dlnqnt-diagnostics-20210702-0210.zip

Edited August 12, 20214 yr by nos0n3

The diagnostics from back on July 2 (you were still on Unraid 6.8.3) show you were having connection issues on disk1 (SH2Z), disk2 (Z0UN), disk3 (NTAN), disk4 (9WNN). Only disk3 was disabled, and all disks were mountable.

 

So, you had a disabled disk at that time, how did you deal with that problem?

 

08:00.0 SATA controller [0106]: Marvell Technology Group Ltd. Device [1b4b:9215] (rev 11)

Marvell controllers are not recommended.

 

Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected?

The diagnostics from Aug 10 show you were rebuilding disk1, disk3 was not disabled (maybe you had already rebuilt it), and both disk1 and disk3 were unmountable. Looks like it had also corrected a few parity2 sync errors during rebuild.

 

No obvious connection problems had occurred yet.

 

My guess is your Marvell controller is to blame for all of this, and probably the way forward is going to be to eliminate that controller before attempting to fix anything.

 

https://forums.unraid.net/topic/102010-recommended-controllers-for-unraid

Probably the rebuild of disk3 was bad due to controller issues, so it became unmountable, and it may have also made the emulation of disk1 unmountable, then that and/or controller issues resulted in unmountable disk1 rebuild.

 

Maybe if you get that controller eliminated, we could try rebuilding both again to see if anything improves. Rebuilding to different disks would be the best approach, so we don't overwrite the disks already rebuilt. Then we could go from there and see about getting each mountable and see how much can be recovered.

 

Do you have backups of everything important and irreplaceable?

 

Let us know when you have a plan for getting that controller out of the picture and we can get into the details of working to recover data.