bennymundz

No it did not.

WebUI The process i used On the main page > clicked disk number (Disk1 in my instance) > Scrolled down to Check Filesystem Status section > Pressed check and let it run.

Outcome. It now detects as XFS but is not emulating the contents of the drive. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x49620d, xfs_rmapbt block 0x200000040/0x1000 btree block 4/12 is suspect, error -74 invalid start block 1925355057 in record 63 of rmap btree block 4/12 out-of-order rmap btree record 75 (2644636 8611223038 0 8) block 4/12 invalid start block 4274348048 in record 83 of rmap btree block 4/12 invalid flags in record 84 of rmap btree block 4/12 invalid start block 1764285104 in record 85 of rmap btree block 4/12 invalid length 536870968 in record 87 of rmap btree block 4/12 invalid flags in record 88 of rmap btree block 4/12 invalid flags in record 89 of rmap btree block 4/12 invalid start block 3426770109 in record 90 of rmap btree block 4/12 invalid owner in rmap btree record 91 (40694836542534 4) block 4/12 invalid start block 4292289813 in record 92 of rmap btree block 4/12 invalid start block 405330670 in record 93 of rmap btree block 4/12 invalid flags in record 94 of rmap btree block 4/12 invalid flags in record 95 of rmap btree block 4/12 invalid flags in record 96 of rmap btree block 4/12 invalid start block 2681123853 in record 97 of rmap btree block 4/12 invalid flags in record 105 of rmap btree block 4/12 invalid length 680760619 in record 106 of rmap btree block 4/12 invalid flags in record 125 of rmap btree block 4/12 invalid flags in record 126 of rmap btree block 4/12 invalid flags in record 127 of rmap btree block 4/12 invalid flags in record 128 of rmap btree block 4/12 invalid length 1761607721 in record 129 of rmap btree block 4/12 invalid flags in record 130 of rmap btree block 4/12 invalid start block 2455921752 in record 131 of rmap btree block 4/12 invalid flags in record 132 of rmap btree block 4/12 invalid flags in record 133 of rmap btree block 4/12 invalid owner in rmap btree record 134 (867234299387003825 1) block 4/12 invalid start block 4292289056 in record 136 of rmap btree block 4/12 invalid flags in record 137 of rmap btree block 4/12 invalid flags in record 138 of rmap btree block 4/12 invalid flags in record 139 of rmap btree block 4/12 invalid flags in record 145 of rmap btree block 4/12 invalid owner in rmap btree record 148 (5585902498079523734 52) block 4/12 invalid start block 4292288719 in record 149 of rmap btree block 4/12 invalid owner in rmap btree record 160 (140750440317889 1) block 4/12 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 entry " ,gdia�" in shortform directory 128 references invalid inode 562949953488228 entry contains illegal character in shortform dir 128 would have junked entry ",gdia�" in directory inode 128 entry " 0Photos" in shortform directory 128 references invalid inode 0 entry #1 extends past end of dir in shortform dir 128, would junk 5 entries would have corrected entry count in directory 128 from 6 to 1 would have corrected i8 count in directory 128 from 4 to 0 would have corrected directory 128 size from 159 to 118 directory 128 offsets too high would have corrected entry offsets in directory 128 would have corrected root directory 128 .. entry from 83910861 to 128 xfs_repair: dir2.c:1551: process_dir2: Assertion `(ino != mp->m_sb.sb_rootino && ino != *parent) || (ino == mp->m_sb.sb_metadirino && (ino == *parent || need_metadir_dotdot == 1)) || (ino == mp->m_sb.sb_rootino && (ino == *parent || need_root_dotdot == 1))' failed

Ill give it a go now

Thanks JorgeB I followed the steps there is the diags hammertime-diagnostics-20260301-0627.zip

Background - I have x3 10tb one of which was parity other two were data and x3 8tb. All of the 8tb drives along with one of the 10tb drives were empty and not being written to by unraid. Long story short since on of the 10 tb drives were not being used I figured it would be a good idea to remove the drive from my array and have it as a warm spare for my parity drive. This is where the F up started. I jumped ahead and hit the new config, and elected to not preserve anything, as I through I knew the drive layout (HUGE mistake). I wiped the config, re allocated the drives in the order I thought I remembered and hit parity sync. Immediately I noticed the one 10 tb drive that I though had my data had an unreadable file system, and I immediately knew I got the parity and the data drive around the wrong way and just wiped my data drive. Now the question is, since I have my "old configuration's parity drive" still intact and I essentially have just gone through a dead drive situation, how can I convince the configuration I have is valid so I can re assign the drives in the correct order and perform a rebuilt of the one drive I wiped? No, this is the 2nd F up, I didn't backup my config that I know of. It's connected to the unraid online which I though backed up my config, but upon looking can't see that being the case. Any help would be really appreciated. Thank you

Did you get this fixed? I am having the same issue. Did you get this fixed? I am having the exact same issue. Update, i wasn't following the instructions properly and got this working with freedns :-) I love this app

Hey there, what model SuperMicro case is this?

Hi Unraid team, I had a disk die (disk4 in my array) in my unraids, when I was in the process of replacement of the one dead disk (disk 4 data disk), a second (disk 1 data disk) decided to also give up. I pulled both out of the unraid and connected to USB to SATA device to check how dead they were with some tools. One is completely dead and will not even detect, however the 2nd (the more recent) failure was actually readable via Paragon through windows. (She isn't healthy tho) My question is, is there a way to force unraid to believe (data disk 1) is okay, so I can use parity to rebuilt data disk 4, then once that is rebuilt use parity to rebuild on a new disk data disk 1? data disk 4 simply wont detect - so no smart reports data disk 1 fails smart test at either 10% or 90% I run one parity disk and both drive failures are on data disks. Parity drive is good.

Sorry my fault, I should have explained... It just hangs at the last line and never progresses. I am going to be looking into what is in PCI slot 9 where it hangs, clearly that card doesn't want to play nice and then working backwards from there today. It's something up with the linux builds in those later versions 6.1.x linux versions

6.12.0 and 6.12.1 both killed my unraid box. I manually downgraded to 6.11.5 and back up and running fine. I tried disabling the power management in bios and upgrading to latest bios with no avail.

Gee wizz people are creative. My attempt would have been along the line of the OP, but i would have forgotten to use colour. Great work to all the submitters you are really skillful.

Nope i did not see that there. Thank you

I asked this in the general support forum without realising that there is a thread for this plug-in. Can someone please tell me how i would go about assigning a NFS share to a disk which is mounted by unassigned devices. The disk gets mounted, a SMB share get created but i would like to assign a NFS share to it. I would appreciate any guidance / assistance provided.