Hi.

I recently performed a platform upgrade to my server and in the process added a second cache drive and a new 14tb drive. All went well and the server seemed to be running fine until today where one of my users mentioned that a tv series they were watching was no longer available on plex which had been working yesterday.

 

I then went to check the files and it appeared they had disappeared, along with all the other files I had downloaded to cache and then the mover moved to array this morning as per my settings.

 

I went into fix common problems and saw this warning - Your drive is either completely full or mounted read-only (for disk6, the new drive I had added). I stopped the array and took the first diagnostics download. I rebooted and then saw the Unmountable: Unsupported partition layout warning beside drive6 as seen in the second diagnostics download. I could see the lines:

 

XFS (sdi1): Unmount and run xfs_repair

&

Mount of 'sdi1' failed: 'mount: /mnt/disks/ZL20A875: mount(2) system call failed: Structure needs cleaning. dmesg(1) may have more information after failed mount system call.'

 

With this I then ran the xfs_repair on the drive in maintenance mode and all seems to be okay now.

 

My question is, why did this happen? Is it common? I have never had to do this before and the server has been running for years with unraid. Are there preventative measures I can take to prevent this happening in the future when adding more drives and is this likely to happen again on the same drive? SMART says there are no errors but I am still within the time limit to return the drive if anyone thinks this could be an issue with the hardware. 

 

I do recall the Unmountable: Unsupported partition layout warning with the drive when trying to add it to the array the first time after preclearing but I believe a restart and destrutive mode and deleting the partitions fixed that - could this have been the point where I should have ran the xfs_repair?

 

Thanks in advance.

terabyte-diagnostics-20241208-1504.zip terabyte-diagnostics-20241208-1516.zip

I have also seen this in the first log. I am unsure what the md6p1 drive is? I am assuming it is a partition on the drive that was corrupt?

 

Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): SB summary counter sanity check failed
Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): Metadata corruption detected at xfs_sb_write_verify+0xc1/0x11a [xfs], xfs_sb block 0x0 
Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): Unmount and run xfs_repair
Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): First 128 bytes of corrupted metadata buffer:
Dec  8 02:40:04 TERABYTE kernel: 00000000: 58 46 53 42 00 00 10 00 00 00 00 00 cb bb ff f3  XFSB............
Dec  8 02:40:04 TERABYTE kernel: 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Dec  8 02:40:04 TERABYTE kernel: 00000020: 40 7d 36 3a 44 61 45 ad a2 1d 61 01 89 5c bc 98  @}6:DaE...a..\..
Dec  8 02:40:04 TERABYTE kernel: 00000030: 00 00 00 00 60 00 00 09 00 00 00 00 00 00 00 80  ....`...........
Dec  8 02:40:04 TERABYTE kernel: 00000040: 00 00 00 00 00 00 00 81 00 00 00 00 00 00 00 82  ................
Dec  8 02:40:04 TERABYTE kernel: 00000050: 00 00 00 01 0f ff ff ff 00 00 00 0d 00 00 00 00  ................
Dec  8 02:40:04 TERABYTE kernel: 00000060: 00 07 f6 00 bc b5 10 00 02 00 00 08 00 00 00 00  ................
Dec  8 02:40:04 TERABYTE kernel: 00000070: 00 00 00 00 00 00 00 00 0c 0c 09 03 1c 00 00 05  ................
Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): Corruption of in-memory data (0x8) detected at __xfs_buf_submit+0xff/0x199 [xfs] (fs/xfs/xfs_buf.c:1552).  Shutting down filesystem.
Dec  8 02:40:04 TERABYTE kernel: XFS (md6p1): Please unmount the filesystem and rectify the problem(s)

1 hour ago, big_boss said:

md6p1

 

It means disk6, there's always only one partition.

 

If this is a one-time thing, I wouldn't worry for now, but if it happens again in the near future it may indicate an underlying hardware issue, like bad RAM.

1 hour ago, JorgeB said:

 

It means disk6, there's always only one partition.

 

If this is a one-time thing, I wouldn't worry for now, but if it happens again in the near future it may indicate an underlying hardware issue, like bad RAM.

Thanks for the advice, I did install a new ram kit along with the existing ram while doing the upgrade. Might be worth doing some mem tests. Thanks for your help