Help - Read-Check will take 176 Days to complete.

[trurl]

That screenshot showing SMART healthy was useful, saves me from having to look at all those other disks.

 

It was complaining about the filesystem on disk9 when you started the array but I think it may have fixed that since I don't see that later on like I do for disks 1 and 5.

 

As mentioned, connection problems with disk1 and 9, but no connection problem with disk5.

 

Do you have a spare disk you can use to rebuild disk1? You could rebuild onto that same disk since it looks OK, but rebuilding to a spare gives more options in case of problems during rebuild.

 

 

 

[StewLoft]

I can pull one from another computer. What are the steps to rebuild?

[trurl]

3 minutes ago, StewLoft said:

I can pull one from another computer. What are the steps to rebuild?

How large is the spare? It needs to be at least as large as disk1 but no larger than parity2.

 

Before rebuild, we always like to repair filesystems, since rebuild is going to result in exactly what is emulated, and emulated disk1 was logging some corruption even though it mounted.

 

Check filesystem on disk1. Be sure to capture the output so you can post it.

[trurl]

Actually, before that, you should shutdown, check all connections, SATA and power, including splitters.

Probably you disturbed connections earlier when you were mucking about inside and that is the real cause of these problems.

 

Then reboot, start the array, and post new diagnostics.

[StewLoft]

OK, will shutdown, check connections and reboot.

 

The spare is a 4TB WD Red. Should I put it in place of disc1 now?

 

[trurl]

2 minutes ago, StewLoft said:

The spare is a 4TB WD Red. Should I put it in place of disc1 now?

Do have enough ports to install it and leave original disk1 in? That will make it easier if we need to do anything with the original disk1, and it will allow us to check SMART for the spare if you put it in before getting diagnostics.

 

Don't assign either disk.

[StewLoft]

No extra ports. It is maxed out.

[StewLoft]

I can order another. I have 2 pcie to sata 4 port cards currently

[trurl]

You have an unassigned SSD you could remove, let's worry about controllers later.

[trurl]

Device Model:     KINGSTON SA400M8240G
 

[trurl]

1 hour ago, StewLoft said:

And an unassigned HDD

[StewLoft]

What about the 6TB HDD that was my original parity? It is still in the system connected. It is dev2 in the unassigned list.

[StewLoft]

The unassigned SSD is my OS for the base system the unraid is built on.

[StewLoft]

I replaced the cable going to disc1 and checked the rest. Power up?

[trurl]

1 minute ago, StewLoft said:

The unassigned SSD is my OS for the base system the unraid is built on.

Do you mean you are running Unraid as a VM?

[StewLoft]

I have a system with windows but it boots to unraid view the USB.

[trurl]

You mean dual boot and not VM?

[StewLoft]

Yes, I guess so. Sorry if I am causing confusion. I use unraid basically for media and backup. I have not ventured into VM's or anything more complicated than basic use.

[trurl]

So while Windows is booted, your Unraid isn't running, and so Windows has no access to your NAS?

[StewLoft]

That is correct.

[StewLoft]

Should I power up and reboot Unraid?

[trurl]

OK

 

That original parity can't be used as parity now as you discovered. Maybe later it can be reused to replace one of the smaller disks.

 

Replace that original parity with the spare 4TB, check all connections, reboot, and post new diagnostics.

[trurl]

Sorry, I'm getting confused now.

 

You might as well use that original parity as a replacement for disk1. Just don't assign it yet.

 

Reboot and post new diagnostics

[StewLoft]

OK.

[StewLoft]

tower-diagnostics-20220806-1537.zip