Array Won't Stop of Shutdown

[itimpi]

11 minutes ago, Scuba_Steve said:

When I try mounting the drive it will not mount and I am not able to view the contents of the drive.

 

 

Have you run a repair on /dev/sdg1 without the -n (no modify) flag to carry out a repair?

[JorgeB]

Post new diags after trying to mount the old disk with the UD plugin.

[Scuba_Steve]

@JorgeB What old disk?

[JorgeB]

Old disk1 one that you were trying to mount with UD, is there another problem disk?

[Scuba_Steve]

I will post diags from disk 1 tonight when I get home.  Thank you.

[JorgeB]

Just now, Scuba_Steve said:

I will post diags from disk 1 tonight when I get home

Just to clear, diags after trying to mount that disk with UD

[Scuba_Steve]

I have a question.  I think my parity drive did not rebuild properly since it only took less then 1hr and it is 18TB.  Why can I not put the original 20TB parity drive back?

[Scuba_Steve]

@itimpi  I did not run a xfs repair using CLI  command /dev/sdg1 

I can try it tonight.

[itimpi]

44 minutes ago, Scuba_Steve said:

@itimpi  I did not run a xfs repair using CLI  command /dev/sdg1 

I can try it tonight.

If you ran it from the GUI then make sure you run without the -n option.

[Scuba_Steve]

@itimpi  I  ran it in the GUI without -n

[Scuba_Steve]

It will not mount using UD.uss-enterprise-diagnostics-20240823-1926.zip

[trurl]

6 hours ago, Scuba_Steve said:

@itimpi  I  ran it in the GUI without -n

Can you post the output from that?

[Scuba_Steve]

[trurl]

6 hours ago, Scuba_Steve said:

@itimpi  I  ran it in the GUI without -n

That screenshot shows you running it WITH -n.

 

But it doesn't matter since it isn't working anyway.

 

Looks like you were having I/O errors on multiple disks. Maybe a power or controller problem. If you get that fixed maybe some progress could be made.

[Scuba_Steve]

First screenshot has nothing.  I ran it without any switches.  The 2nd screenshot is showing after I selected Check with any parameters.

I keep getting different xfs repair outputs.

Edited August 24 by Scuba_Steve

[Scuba_Steve]

I rebooted and ran XFS Repair from GUI again without any parameters.  Here is the output.

uss-enterprise-diagnostics-20240823-2007.zip

Edited August 24 by Scuba_Steve
Adding Diags

[trurl]

9 hours ago, Scuba_Steve said:

I have a question.  I think my parity drive did not rebuild properly since it only took less then 1hr and it is 18TB.  Why can I not put the original 20TB parity drive back?

Maybe we could try that. It would have to be New Config/Trust parity, then disable disk1 to see if it can be emulated.

 

But I am not confident you don't still have a hardware problem.

 

26 minutes ago, trurl said:

Looks like you were having I/O errors on multiple disks. Maybe a power or controller problem. If you get that fixed maybe some progress could be made.

  

On 8/22/2024 at 7:52 AM, Scuba_Steve said:

How can I have so many issues just from changing my parity drive.  How can I replace my original parity drive?

 

Disturbing connections when replacing drives is very common.

 

Any power splitters in your setup?

[Scuba_Steve]

Please treat me like a newbie, I haven't had to do anything since unRAID has been rock solid until I swapped my parity drive.  Since then it has been a nightmare.

How do I proceed with a Config/Trust parity?

 

Yes, I have power splitter cables.

[trurl]

Check all connections, all disks, both ends, SATA and power, including splitters.

 

Ideally no more than 4 drives per PSU cable.

 

If you can also connect original parity along with all the other disks, that would allow us to see if the disk is good and all are connected well.

 

Then new diagnostics so we can see if there are any obvious hardware problems. Don't try to start the array or change anything else yet.

[JorgeB]

There's some confusing going on here, you are trying to mount the actual disk1 with UD, that is failing because there's filesystem corruption, but then you are checking filesystem on the emulated disk. not the actual disk, type this in the CLI and post the output:

 

xfs_repair -v /dev/sdg1

 

 

[Scuba_Steve]

@JorgeB  Here is the output from running xfs_repair -v /dev/sdg1.

uss-enterprise-diagnostics-20240824-1342.zip

[Scuba_Steve]

I am trying to get my array back online without any errors.  My unRAID server was running great until I down sized my 20TB parity drive for a 18TB drive.  When I swapped the drive, something happened and my 18TB parity drive did not rebuild properly since it only took less than an hours.

 

Thank you.

[Scuba_Steve]

I swapped my parity back to the original 20TB drive.  Should I try and start the array?

It will not allow me to start the array.

Edited August 24 by Scuba_Steve

[JorgeB]

14 hours ago, Scuba_Steve said:

Here is the output from running

That doesn't make any sense, it worked before, post a screenshot showing the start of the command.

[trurl]

You can't start the array because you can't change parity when you already have disk1 invalid.

 

The most recent diagnostics you posted did not include 20TB disk that you wanted to reassign as parity.

 

But they do show I/O errors with the 18TB parity disk.

 

On 8/23/2024 at 10:43 PM, trurl said:

Check all connections, all disks, both ends, SATA and power, including splitters.

 

Ideally no more than 4 drives per PSU cable.

 

If you can also connect original parity along with all the other disks, that would allow us to see if the disk is good and all are connected well.

 

Then new diagnostics so we can see if there are any obvious hardware problems. Don't try to start the array or change anything else yet.