Hi all,

 

Somewhere last week I noticed that one of my data drives was disabled. Started some investigation and it looked like the filesystem was corrupted. Started a filesystem rebuild, succesfully finished it and there was a lost+found folder with quite some data in it. Thought I would sort that out after the weekend, cause I was quite busy with work etc.

 

Then during the weekend a power outtage happened. Luckily I have a UPS so the server gracefully shut down. But after restarting it the lost+found folder was gone...

 

And now the disk still shows as; Unmountable: Wrong or No filesystem. Even after a XFS rebuild..

 

Unfortunately I didnt save any logs..

 

I must confess that I'm a novice user when it comes to filesystem repair etc. So the first time I followed intructions from a post here and it worked. Second time around I had less luck..

 

I don't really know what to do now. It's a 2TB drive that was 75% filled, and I can't seem to get the data back now. 

 

Didnt do any formatting or rebuilding. 

 

Any advice? Thanks in advance.

Please post current diagnostics with array started.

1 hour ago, JorgeB said:

Please post current diagnostics with array started.

Hereby the diagnostics

tower-diagnostics-20230309-2040.zip

Check filesystem on disk4, but there are what look like power/connections issues with parity, you need to fix that first:

 

Mar  9 11:50:00 Tower kernel: ata4.00: status: { DRDY }
Mar  9 11:50:00 Tower kernel: ata4: hard resetting link
Mar  9 11:50:05 Tower kernel: ata4: link is slow to respond, please be patient (ready=0)
Mar  9 11:50:10 Tower kernel: ata4: COMRESET failed (errno=-16)
Mar  9 11:50:10 Tower kernel: ata4: hard resetting link
Mar  9 11:50:12 Tower kernel: ata4: SATA link down (SStatus 0 SControl 310)
Mar  9 11:50:12 Tower kernel: ata4: hard resetting link
Mar  9 11:50:17 Tower kernel: ata4: link is slow to respond, please be patient (ready=0)
Mar  9 11:50:22 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Mar  9 11:50:22 Tower kernel: ata4.00: configured for UDMA/133
Mar  9 11:50:22 Tower kernel: sd 4:0:0:0: [sde] tag#15 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=112s
Mar  9 11:50:22 Tower kernel: sd 4:0:0:0: [sde] tag#15 Sense Key : 0x5 [current]
Mar  9 11:50:22 Tower kernel: sd 4:0:0:0: [sde] tag#15 ASC=0x21 ASCQ=0x4
Mar  9 11:50:22 Tower kernel: sd 4:0:0:0: [sde] tag#15 CDB: opcode=0x88 88 00 00 00 00 00 ae b1 01 50 00 00 00 10 00 00
Mar  9 11:50:22 Tower kernel: I/O error, dev sde, sector 2930835792 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Mar  9 11:50:22 Tower kernel: md: disk0 read error, sector=2930835728
Mar  9 11:50:22 Tower kernel: md: disk0 read error, sector=2930835736

 

Found the issue with the parity drive, faulty cabling.

But you say disk 4? It is disk 1 that has the problem.. Are you sure?

Sorry if I dont see the problem but I just want to be sure..

Missed disk1, you have two disks with filesystem issues:

 

Mar  9 11:38:15 Tower kernel: XFS (md1): Unmount and run xfs_repair
...
Mar  9 12:06:18 Tower kernel: XFS (md4): Unmount and run xfs_repair

 

So check fs on both.

Okay that worked, now I got a lost+found share again.

Should I now just let the parity sync finish?

Will that bring the files back to where they were or do I need to put everything back from the lost+found folder in to the right shares?

And also, there wouldn't be an easy way to do that? Because the folder is 500GB+ :')

 

Thanks very much Jorge!

17 minutes ago, mharmsen538 said:

Should I now just let the parity sync finish?

I assume you mean disk rebuild?

 

17 minutes ago, mharmsen538 said:

Will that bring the files back to where they were or do I need to put everything back from the lost+found folder in to the right shares?

You have to sort those files manually.

 

 

 

Yes I meant disk rebuild. Okay, will be quite the task but at least its not gone. Thanks a lot for the help mate, really appreciated!