Array Won't Stop of Shutdown

[trurl]

7 hours ago, JorgeB said:

doesn't make any sense

This post on the previous page, even though run with -n, showed no corruption on sdg1. I think we aren't being told everything that is happening.

 

 

[Scuba_Steve]

I have checked all the cables and verified the cable are snug and only have 4 drives per splitter.

I connected the 18TB parity drive back too.  I have not started the array and attached my diags.

uss-enterprise-diagnostics-20240825-1339.zip

[Scuba_Steve]

I checked all the cables on all disks both SATA and power cables.

I have reverted back to my 18TB parity drive along with Disk 1 (18TB)

Posting diags without starting the array.  

Please advise how I can proceed.

 

Thank you.

uss-enterprise-diagnostics-20240826-1957.zip

[JorgeB]

Note that if disk1 is still unmountable, rebuilding won't fix that.

[Scuba_Steve]

@JorgeB I am not trying to rebuild disk 1. I am trying to get my array back online and working.

[JorgeB]

The current status from the screenshot you posted will rebuild disk1

[Scuba_Steve]

I am not sure why.  If you look at my previous screenshots in this thread that is the same parity and disk 1 I have been having issue not able to start.

[JorgeB]

Disk1 is showing "invalid", this means it will start to rebuild after array start, and to be with that status, it means a rebuild was already attempted before, but it was aborted or canceled.

[Scuba_Steve]

What is my next step to getting my array back online?

[JorgeB]

Starting the array will bring it online, but like mentioned it won't bring disk1 back if it was unmountable, but that's likely no longer possible anyway, assuming the current disk assigned to disk1 was the original disk1.

[trurl]

If I remember correctly, new parity build had problems. And emulated disk1 was unmountable. And physical disk1 is also unmountable with UD. And xfs repair fails with either.

 

New parity was replaced with original parity, so the array cannot be started due to parity change with invalid disk1.

 

The idea with this was to New Config/Trust Parity with the original parity, then disable disk1 to see if it can be emulated from original parity.

 

Does this sound right?

[Scuba_Steve]

@JorgeB  How do I proceed with creating a new Config/Trust parity.  I don't want to mess anything up. 

I am assuming I should use the 18TB that is currently in my system.

 

Thank you

[JorgeB]

1 hour ago, trurl said:

New parity was replaced with original parity, so the array cannot be started due to parity change with invalid disk1.

But parity is showing valid in the screenshot posted.

 

Very difficult to give instructions if the problem is not clear, which disk is old parity?

[Scuba_Steve]

My 20TB hdd was the original parity before I swapped it to the 18TB hdd, that is when I started having the issues. My array would not start anymore.

Will I lose a lot of data from disk 1?

Edited August 28 by Scuba_Steve

[JorgeB]

Difficult to say for now, if old parity is still valid it should be recoverable.

[Scuba_Steve]

Seems like only parity drive that is mountable is the 18TB drive, but disk 1 will not mount.  

Can I copy the files from disk 1 and format and try to mount?

[JorgeB]

I'm not sure what you mean, parity doesn't have a filesystem and cannot be mounted.

[Scuba_Steve]

I was asking if I could copy the data from disk 1 to a spare disk.  Since disk 1 is unmountable.

[JorgeB]

How can you copy the data if the disk is not mounting?

[trurl]

19 hours ago, Scuba_Steve said:

My 20TB hdd was the original parity before I swapped it to the 18TB hdd, that is when I started having the issues. My array would not start anymore.

It won't let you replace parity with a smaller disk. The only way to make that happen is New Config (resetting disk assignments). Then it will let you rebuild parity onto the smaller replacement. Is that what you did?

[trurl]

2 hours ago, Scuba_Steve said:

disk 1 is unmountable.

33 minutes ago, JorgeB said:

How can you copy the data if the disk is not mounting?

 

When the OS "mounts" a disk, it accesses the filesystem information in preparation for accessing its files. If a disk is unmountable (can't be successfully mounted), its files cannot be accessed.

[trurl]

19 hours ago, Scuba_Steve said:

My 20TB hdd was the original parity before I swapped it to the 18TB hdd, that is when I started having the issues. My array would not start anymore.

OK, then maybe original 20TB parity can be made to emulate disk1? Were you ever able to  start the array after you did the swap?

[Scuba_Steve]

2 hours ago, trurl said:

It won't let you replace parity with a smaller disk. The only way to make that happen is New Config (resetting disk assignments). Then it will let you rebuild parity onto the smaller replacement. Is that what you did?

I was advised in a different thread I could swap parity from 20TB to an 18TB for parity since 18TB is the largest drive in my array

[itimpi]

Just now, Scuba_Steve said:

I was advised in a different thread I could swap parity from 20TB to an 18TB for parity since 18TB is the largest drive in my array

As far as I know that is fine.  What I do not think you can do is down-size a data disk without going via New Config.

 

However what you cannot do is get Unraid to revert to the old parity drive without rebuilding its contents OR going via New Config and using the "parity is valid" checkbox

[Scuba_Steve]

2 hours ago, trurl said:

OK, then maybe original 20TB parity can be made to emulate disk1? Were you ever able to  start the array after you did the swap?

How can I proceed to use my 20TB parity to emulate.  When I connect it, the option to start the array is greyed out and I am not able to start the array.