Zyzlt

@JorgeB I found a similiar issue with mulitple lines that you helped out for a cache drive. Would I want to do a similar but set it to below for both drive? I don't know if the zfs_member is correct to only remove ZFS reference and keep xfs. wipefs --backup -a -t zfs_member /dev/md1p1

root@ZyzServer:~# wipefs /dev/md2p1 DEVICE OFFSET TYPE UUID LABEL md2p1 0x0 xfs 0a88549b-ca14-4436-ae0f-568f61240640 md2p1 0x2baa13ff000 zfs_member md2p1 0x2baa13fe000 zfs_member md2p1 0x2baa13fd000 zfs_member md2p1 0x2baa13fc000 zfs_member md2p1 0x2baa13fb000 zfs_member md2p1 0x2baa13fa000 zfs_member md2p1 0x2baa13f9000 zfs_member md2p1 0x2baa13f8000 zfs_member md2p1 0x2baa13f7000 zfs_member md2p1 0x2baa13f6000 zfs_member md2p1 0x2baa13f5000 zfs_member md2p1 0x2baa13f4000 zfs_member md2p1 0x2baa13f3000 zfs_member md2p1 0x2baa13f2000 zfs_member md2p1 0x2baa13f1000 zfs_member md2p1 0x2baa13f0000 zfs_member md2p1 0x2baa13ef000 zfs_member md2p1 0x2baa13ee000 zfs_member md2p1 0x2baa13ed000 zfs_member md2p1 0x2baa13ec000 zfs_member md2p1 0x2baa13eb000 zfs_member md2p1 0x2baa143f000 zfs_member md2p1 0x2baa143e000 zfs_member md2p1 0x2baa143d000 zfs_member md2p1 0x2baa143c000 zfs_member md2p1 0x2baa143b000 zfs_member md2p1 0x2baa143a000 zfs_member md2p1 0x2baa1439000 zfs_member md2p1 0x2baa1438000 zfs_member md2p1 0x2baa1437000 zfs_member md2p1 0x2baa1436000 zfs_member md2p1 0x2baa1435000 zfs_member md2p1 0x2baa1434000 zfs_member md2p1 0x2baa1433000 zfs_member md2p1 0x2baa1432000 zfs_member md2p1 0x2baa1431000 zfs_member md2p1 0x2baa1430000 zfs_member md2p1 0x2baa142f000 zfs_member md2p1 0x2baa142e000 zfs_member md2p1 0x2baa142d000 zfs_member md2p1 0x2baa142c000 zfs_member md2p1 0x2baa142b000 zfs_member md2p1 0x2baa142a000 zfs_member md2p1 0x2baa1429000 zfs_member md2p1 0x2baa1428000 zfs_member

mdp1 root@ZyzServer:~# wipefs /dev/md1p1 DEVICE OFFSET TYPE UUID LABEL md1p1 0x0 xfs 0dec2e41-b9ee-445e-ad63-aea1143c8aed md1p1 0x2baa13ff000 zfs_member md1p1 0x2baa13fe000 zfs_member md1p1 0x2baa13fd000 zfs_member md1p1 0x2baa13fc000 zfs_member md1p1 0x2baa13fb000 zfs_member md1p1 0x2baa13fa000 zfs_member md1p1 0x2baa13f9000 zfs_member md1p1 0x2baa13f8000 zfs_member md1p1 0x2baa13f7000 zfs_member md1p1 0x2baa13f6000 zfs_member md1p1 0x2baa13f5000 zfs_member md1p1 0x2baa13f4000 zfs_member md1p1 0x2baa13f3000 zfs_member md1p1 0x2baa13f2000 zfs_member md1p1 0x2baa13f1000 zfs_member md1p1 0x2baa13f0000 zfs_member md1p1 0x2baa13ef000 zfs_member md1p1 0x2baa13ee000 zfs_member md1p1 0x2baa13ed000 zfs_member

Good morning, Hope someone can help. My server went down and I needed to replace the USB key, I also decided to upgrade my equipment at the same time. When I booted my server back up and attempted to start the array my parity drive would connect but told me all data would be overwritten and 2 of my 4 drive both showing as Unmountable: unsupported or no file system. They are XFS formatted, I attempted to do a few xfs_repair but no luck. Any thing else I can do to attempt to get the drive back connected or get the data off. zyzserver-diagnostics-20250207-0818.zip

Looks like that did let it remount. Thankfully my appdata backup did recover what I was missing. Fixed my shares to go cache to array so hopefully that will get my data over and then I may just remove the cache. zyzserver-diagnostics-20250116-1547.zip

I had this error before with my Cache drive and when i reboot it worked, unfortunately that is not the case anymore. I upgraded from 6.12.6 to 7 and it started happening again. I downgraded back to 6.12.6 but still have the issue. Unfortunately I did not setup my cache - array properly so any way I can either get it mounted or recover the data would be a big help. zyzserver-diagnostics-20250115-1553.zip