Hey guys, I have a problem and I think it's my own fault... I played around with hardware quiet a lot in the last weeks and now my main drives are not recognized by the array. I mounted them while the array was offline by using Unassigned Devices and I think that might have caused the issue... The disks are in the right order. The first image shows the array before start up. The second image shows its state a fter start up. I'm happy to run diagnostic tools and upload diagnostic files, I just don't know which ones/where they are. Thank you for any advice.

Please post the diagnostics.

Thank you for linking that page

diagnostics-20240617-1644.zip

Edited June 17, 20242 yr by BlackCube

First check filesystem on disks 1 and 2, run it without -n.

As can be seen in the screenshots, the two drives behave differently. I can mount the first drive when the array is offline and all data is still accessible. The second drive can't be mounted at all, but it's less important since it contained less data.

 

I checked the filesystems.

drive 1.txtdrive 2.txt

Drive 2 needd xfs_repair to be run with the -L option for it to be mountable.

What does the -L option do?
Also I checked the first drive again and got this:drive 1 second try.txt

2 minutes ago, BlackCube said:

What does the -L option do?

It does what the report says it will do - it discards the log and then repairs the drive.

 

The rerun on disk1 looks clean, but the output from the first repair attempt suggests to me that a lot of its data has probably been moved to the lost+found folder and that will probably take a lot of manual effort to resolve.

Oh noooo I see what you mean. There is a giant lost+found folder now. How did that happen!? Was it allready there before the filesystem check?

The first drive is now part of the array again but it still shows "Device is disabled" and what can I do about Disk 2

Since Disk 1 was my main drive all my Dockers/VMs are not working anymore now. I said I played around a lot with hardware over the last few weeks but it was working until last friday. Then I was gone over the weekend and my array was suddenly offline. The Server mind you was still on

The lost+found share is <500gb big T.T
I need a backup but backing up 20TB is so expensive

I did this screenshot before using check filesystem. As seen in the screenshot the first disk was containing more data before the check. Why is that? It seemed ok/mountable before. Just not inside the array. Where did all of that data go?

55 minutes ago, BlackCube said:

There is a giant lost+found folder now. How did that happen!?

That is where the repair process puts any files/folders for which it cannot find the directory entry to give the correct name,

5 minutes ago, BlackCube said:

I did this screenshot before using check filesystem. As seen in the screenshot the first disk was containing more data before the check. Why is that? It seemed ok/mountable before. Just not inside the array. Where did all of that data go?

That is the physical disk.   Since disk 1 had been disabled the repair process ran against the emulated drive leaving the physical drive unaffected.    At this point your best bet will be to copy the files from the physical drive mounted as an Unassigned Device back to the array.

OK, I think I got you. Thank you very much. Do you have any idea what I can do about disk 2?

For disk2 should check filesystem.

I get this response every time I check the filesystem on drive 2:
drive 2.txt

xfs_repair is unbale to fix that filesystem, you can try a file recovery app like UFS Explorer.

So I managed to break this drive real bad ^^'
Oh boy... Thank you for your support guys I am very grateful