taflix

Results Phase 1 - find and verify superblock... - block cache size set to 462432 entries Phase 2 - using internal log - zero log... zero_log: head block 38823 tail block 38823 - scan filesystem freespace and inode maps... ir_freecount/free mismatch, inode chunk 0/128, freecount 7 nfree 1 finobt ir_freecount/free mismatch, inode chunk 0/108071680, freecount 5 nfree 3 agi_freecount 19, counted 11 in ag 0 agi_freecount 19, counted 7 in ag 0 finobt agi unlinked bucket 3 is 131 in ag 0 (inode=131) agi unlinked bucket 26 is 128617114 in ag 0 (inode=128617114) sb_ifree 368, counted 376 - 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 bad inode format in inode 131 bad inode format in inode 131 would have cleared inode 131 imap claims in-use inode 108073626 is free, correcting imap - 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 = 3 - agno = 4 - agno = 5 - agno = 2 - agno = 6 entry "Movies" in shortform directory 128 references free inode 131 - agno = 7 would have junked entry "Movies" in directory inode 128 - agno = 1 bad inode format in inode 131 would have cleared inode 131 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Aug 13 08:27:40 2022 Phase Start End Duration Phase 1: 08/13 08:27:38 08/13 08:27:38 Phase 2: 08/13 08:27:38 08/13 08:27:39 1 second Phase 3: 08/13 08:27:39 08/13 08:27:40 1 second Phase 4: 08/13 08:27:40 08/13 08:27:40 Phase 5: Skipped Phase 6: Skipped Phase 7: Skipped Total run time: 2 seconds What do you think?

Hi Jorge, Cables arrived early, replaced. However, Disk 4 still showing up as unmountable? Updated diags attached. What do you think? taflix-unraid-diagnostics-20220811-2148.zip

Hi, I just completed the extended test for Disk 2, it said: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 1752 - I'm assuming the full details will be in the diags? Attached a fresh copy. taflix-unraid-diagnostics-20220810-0835.zip I'm leaning towards this being data / power cable issue? I ordered some new cables and they should be delivered by this weekend. I already got new cables the first time, but I guess with most Amazon stuff, quality control is hit or miss.

I'm running an extended test for Disk 2.

Thank you. Funny thing is that Disk 2 was never originally an issue. Ok, I will double check the power connection to Disk 2. I did swap in a fresh set of new cables. If the errors on Disk 2 continue after this, what would be the next step?

Those diags were taken after the re-seating. Currently, UNRAID is: Fresh diags attached. Thank you so much for those easy to understand and well-organized explanations! taflix-unraid-diagnostics-20220807-2257.zip

I still have the original disk. In the other thread, it was giving me read errors. The advice was to just remove it from the array and have UNRAID rebuild it. That process was successful. Then, recently, it started showing disk read errors again. I tried the same solution but it wouldn't rebuild without stopping due to read errors. So, that's when I purchased a new disk.

Disk 4 is a new disk. Does it have to be precleared before adding to the array? Does it have to be formatted? I'm getting this message while Disk 4 is being rebuilt? "Unmountable: Wrong or no file system" fresh daigs attached taflix-unraid-diagnostics-20220807-1424.zip I unplugged and reseated all data and power cables. Looked like it was running well for about 30 seconds but Disk 2 is still getting errors? Should I allow the rebuild process to continue or stop? I'll pause it for now.

Hello, I replaced 8 cables in my system and now I'm getting read errors from a different drive? Diags attached taflix-unraid-diagnostics-20220807-1205.zip

Thank you, done. taflix-unraid-diagnostics-20220803-2223.zip

I sort of just started doing everything all at once. I've since turned off the machine. Reseated the cables. That fixed the issue with Disk 2. However Disk 5 is still showing tons of errors: What should I do? It's currently rebuilding.

Yes. This issue popped up again: I tried the same solution: Stop array Unassign drive Start array Stop array Assign drive Start array Except this time, it would get read errors and stop rebuilding.

Disk 4 started rebuilding after I assigned it to the array. However, UNRAID reported read errors from 2 additional drives, please help! Diagnostics attached. taflix-unraid-diagnostics-20220803-1841.zip Short self tests on drives 2 and 5 show:

Thanks sir! It is showing this: I'm not familiar with the concept of "emulated"? And those instructions are much better! The disk is now being reconstructed:

Thank you. I've never rebuilt before. Is this the process? https://wiki.unraid.net/Replacing_a_Data_Drive Since the drive is fine and I'm not replacing the drive, what would the process be?

The extended test shows: Completed without error The results are attached. Whenever you get around to this, let me know what we should do next? Thanks! taflix-unraid-smart-20220704-0859.zip

Okay, the READ CHECK was 25.7% done when I stopped it and it showed no errors. I started the extended self test, it probabl won't be done until tomorrow. It's at 50% since I started it 10 hrs ago. Happy 4th of July! 🧨

Thanks guys. I started a READ CHECK last night. Should I stop it and do the extended test?

Diagnostics attached. I have a new array of 14 TB drives. One of them was disabled a few hours ago. What should I do? The short self test said: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 840 - taflix-unraid-diagnostics-20220702-2253.zip

Thanks, but I figured it out. I added SSD drives as cache pools. Upon initializing the drives, the default file system is XFS. However, after poking about in the forums, reddit, and other sites... many suggested that BTRFS is better for SSD cache pools. I changed the file system but didn't reformat the drives. The common errors plugin could probably be tweaked to take into consideration this scenario. I'll leave the solution here for future googlers to find.

How exactly do we fix this error? What does this part mean exactly? Can someone post a screenshot of what it's talking about? It's not really clear for new users what we need to do to fix this? Thank you.