February 13, 20251 yr Hello, I have been going on for 4 days now trying to repair this issue. It all started when I got a notification that a drive had an error. I matched the drive with the Serial number and pulled it. However, the parity failed also. So I got back to the point where I installed a new parity, rebuilt it, and then did a New Config and put in a new drive to replace the errored drive. Everything was rebuilding perfectly, and I was finally on the right track. Until I reached the point where none of the shared folders showed anywhere, I did an SSH, and I can see they exist. They are just not 'visible' or 'appropriately mounted. Another drive had corrupted information, so I mounted it as a read-only and moved the files to another drive. I was planning on swapping it. But when I tried to stop the array. It took 2 hours with zero progress. I rebooted to see if that would help, and now it is doing a parity check. The parity check has corrected 514 errors so far, but now the drives all say they are 128 GB in size and have only 15% use for each. I also tried to use SSH to see if there is anything on it, but it doesn't return anything even though they are correctly mounted. I need serious help, please.
February 14, 20251 yr Author 12 hours ago, trurl said: You can do parity check later. Don't see how it can help you now anyway. tower-diagnostics-20250214-0720.zip
February 14, 20251 yr There's filesystem corruption on the emulated disk1: Feb 13 21:51:05 Tower kernel: XFS (md1p1): Internal error ir.loaded != ifp->if_nextents at line 1203 of file fs/xfs/libxfs/xfs_bmap.c. Caller xfs_iread_extents+0xb2/0x125 Also, seeing a lot of ATA errors with multiple disks, they are from the disks connect to the Marvell controller with a port multiplier, both things are not recommended, recommend replacing it with a recommended model, then check filesystem on the emulated disk1.
February 14, 20251 yr Author 13 hours ago, trurl said: You can do parity check later. Don't see how it can help you now anyway. tower-diagnostics-20250214-0720.zip Just now, JorgeB said: There's filesystem corruption on the emulated disk1: Feb 13 21:51:05 Tower kernel: XFS (md1p1): Internal error ir.loaded != ifp->if_nextents at line 1203 of file fs/xfs/libxfs/xfs_bmap.c. Caller xfs_iread_extents+0xb2/0x125 Also, seeing a lot of ATA errors with multiple disks, they are from the disks connect to the Marvell controller with a port multiplier, both things are not recommended, recommend replacing it with a recommended model, then check filesystem on the emulated disk1. i am very noob to all this would you be able to give me some guidelines to how to do this please if possible?
February 14, 20251 yr If you are wiling, I wound first recommend replacing that controller: To check filesystem see the link
February 14, 20251 yr Author 2 minutes ago, JorgeB said: If you are wiling, I wound first recommend replacing that controller: To check filesystem see the link So from what I understand. The issue strands from the bad Multi port expansion card and replacing it should help resolve it?
February 14, 20251 yr It should help prevent future issues, but you still need to 2 hours ago, JorgeB said: check filesystem on the emulated disk1. And if it looks OK after that, rebuild the disk, but if you are getting a new controller, recommend doing tall that after getting it.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.