taflix

I don't see any scrub option on that screen?

Sorry, I think I figured this out, updated post. Thank you!

As requested Jorge, please let me know if I got what you needed. Thank you sir! taflix-unraid-diagnostics-20250228-1138.zip

I just found out today that my cache is full and that my mover isn't working either. Has anyone found a fix, I've tried uninstalling CA Mover Tuner. The standard mover says: But, it's not actually moving anything. I'm glad that I'm not the only one with this same issue. I hope it gets fixed soon.

That's a good find, very informative, thank you Frank!

Hahaha, thanks that makes sense. I actually have always used shucked drives for NAS. I was more curious to find out of there's any adv / disadv to using HAMR drives for UNRAID?

I've been reading mixed opinions about using HAMR drives for UNRAID? Thank you!

Thank you! Stop array. Then, follow instructions. Start array. Rescan for errors. No errors found. Yay! 😄 The "stop array" step should be included in the instructions.

SUGGESTED FIX: Macvlan and bridging has been found. This might cause issues with stability on your server. More Information Going to that link, it says: But the option is READ-ONLY? Help, please?

Your server has detected hardware errors. You should install mcelog via the NerdPack plugin, post your diagnostics and ask for assistance on the Unraid forums. The output of mcelog (if installed) has been logged. Diagnostics attached. However, I didn't install the NerdPack plugin. Thank you. taflix-unraid-diagnostics-20230210-0850.zip

Thank you man, you're the best Jorge!

It just completed! Faster than before. Diags attached, looks okay? taflix-unraid-diagnostics-20230121-1512.zip

Thank you! Takes about 2 days to rebuild. Crossing fingers.

Attached, thank you. taflix-unraid-diagnostics-20230119-2201.zip

Done and here it is. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agf_freeblks 30707057, counted 27561294 in ag 0 agf_longest 30497022, counted 27351294 in ag 0 agi_freecount 72, counted 73 in ag 0 agi_freecount 72, counted 73 in ag 0 finobt sb_ifree 1076, counted 1077 sb_fdblocks 848592036, counted 887661172 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 entry " �" in shortform directory 128 references invalid inode 35325186126341231 entry #2 extends past end of dir in shortform dir 128, junking 1 entries corrected entry count in directory 128, was 3, now 2 corrected directory 128 size, was 70, now 48 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 4 - agno = 3 - agno = 6 - agno = 7 - agno = 5 - agno = 1 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:196429) is ahead of log (1:134657). Format log to cycle 4. done

Thank you, here are the results: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... agf_freeblks 30707057, counted 27561294 in ag 0 agf_longest 30497022, counted 27351294 in ag 0 agi_freecount 72, counted 73 in ag 0 agi_freecount 72, counted 73 in ag 0 finobt sb_ifree 1076, counted 1077 sb_fdblocks 848592036, counted 887661172 - 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 " �" in shortform directory 128 references invalid inode 35325186126341231 entry #2 extends past end of dir in shortform dir 128, would junk 1 entries would have corrected entry count in directory 128 from 3 to 2 would have corrected directory 128 size from 70 to 48 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 entry " �" in shortform directory 128 references invalid inode 35325186126341231 - agno = 6 entry #2 extends past end of dir in shortform dir 128 - agno = 4 - agno = 2 - agno = 7 , would junk 1 entries would have corrected entry count in directory 128 from 3 to 2 - agno = 5 would have corrected directory 128 size from 70 to 48 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... Metadata corruption detected at 0x467810, inode 0x80 data fork couldn't map inode 128, err = 117 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 132, would move to lost+found disconnected dir inode 12889078397, would move to lost+found Phase 7 - verify link counts... Metadata corruption detected at 0x467810, inode 0x80 data fork couldn't map inode 128, err = 117, can't compare link counts Maximum metadata LSN (1:196355) is ahead of log (1:134657). Would format log to cycle 4. No modify flag set, skipping filesystem flush and exiting.

I have done what you asked, post a screen shot of Main - Array Devices Started the array with nothing assigned as Disk1 Next step, please?

Thank you. I don't know if it's XFS, how do I look that up?

Thank you. taflix-unraid-diagnostics-20230116-1925.zip

Hello, It will not allow me to start the array while Disk 1 is not assigned?

Yes, I did all that. That's what it took days to reply because I was waiting for parts from Amazon.

Attached, thank you. taflix-unraid-diagnostics-20230106-1821.zip

Hello, I plugged everything back in and now I'm getting this? Disk 5 is not a new drive but UNRAID thinks that it's a new drive?

Thanks, I'll replace them. What do I do in the software after I replace them?

Hello, My array is experienced several different errors? I've replaced 3 HDD's with BRAND NEW drives since I started using UNRAID for the first time. What do I need to do to have a reliable, error-free experience? Thank you. Diagnostics attached. taflix-unraid-diagnostics-20221226-2105.zip