December 27, 20223 yr 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 Edited December 28, 20223 yr by taflix
December 27, 20223 yr Community Expert Looks more like a cable/connection problem, check/replace cables and/or try a different PSU.
December 28, 20223 yr Author 15 hours ago, JorgeB said: Looks more like a cable/connection problem, check/replace cables and/or try a different PSU. Thanks, I'll replace them. What do I do in the software after I replace them?
December 28, 20223 yr Community Expert Reboot will reset syslog. Post new diagnostics after checking connections. Be sure to check SATA and power, both ends, including splitter.
January 6, 20233 yr Author On 12/27/2022 at 7:12 PM, trurl said: Reboot will reset syslog. Post new diagnostics after checking connections. Be sure to check SATA and power, both ends, including splitter. Hello, I plugged everything back in and now I'm getting this? Quote Stopped. Invalid configuration. Disk 5 is not a new drive but UNRAID thinks that it's a new drive? Edited January 6, 20233 yr by taflix
January 6, 20233 yr Community Expert On 12/27/2022 at 9:12 PM, trurl said: Post new diagnostics after checking connections
January 7, 20233 yr Author 23 hours ago, trurl said: Attached, thank you. taflix-unraid-diagnostics-20230106-1821.zip
January 7, 20233 yr Community Expert Diags after the it happened but disk5 got disabled when disk1 was invalid suggesting you still have hardware issues, we can force enable disk5 to rebuild disk1, but if you are still having the power/connection issues it can happen again, did you already try doing something to solve that, like checking/replacing cables or PSU?
January 7, 20233 yr Author 6 hours ago, JorgeB said: Diags after the it happened but disk5 got disabled when disk1 was invalid suggesting you still have hardware issues, we can force enable disk5 to rebuild disk1, but if you are still having the power/connection issues it can happen again, did you already try doing something to solve that, like checking/replacing cables or PSU? Yes, I did all that. That's what it took days to reply because I was waiting for parts from Amazon.
January 8, 20233 yr Community Expert You can try this, it will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk1 -Start array (in normal mode now) and post new diags
January 15, 20233 yr Author On 1/8/2023 at 4:09 AM, JorgeB said: You can try this, it will only work if parity is still valid: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk1 -Start array (in normal mode now) and post new diags Hello, It will not allow me to start the array while Disk 1 is not assigned? Edited January 16, 20233 yr by taflix
January 15, 20233 yr Community Expert 27 minutes ago, taflix said: It will now allow me to start the array while Disk 1 is not assigned? It should as long as you click the checkbox to confirm this is what you want to do.
January 17, 20233 yr Author 15 hours ago, JorgeB said: Thank you. taflix-unraid-diagnostics-20230116-1925.zip
January 17, 20233 yr Community Expert Emulated disk1 unmountable. Is it supposed to be XFS? Post a screenshot of Main - Array Devices
January 18, 20233 yr Author On 1/17/2023 at 6:47 AM, trurl said: Emulated disk1 unmountable. Is it supposed to be XFS? Post a screenshot of Main - Array Devices Thank you. I don't know if it's XFS, how do I look that up? Edited January 18, 20233 yr by taflix
January 18, 20233 yr Community Expert What is the point of this latest screenshot? What have you done? We need the array started with nothing assigned as disk1 so we can try to repair the emulated filesystem of disk1.
January 18, 20233 yr Author 6 hours ago, trurl said: What is the point of this latest screenshot? What have you done? We need the array started with nothing assigned as disk1 so we can try to repair the emulated filesystem of disk1. 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? Edited January 19, 20233 yr by taflix
January 19, 20233 yr Community Expert Stop array, leave disk1 unassigned, click on disk1 slot to get to its page, set the filesystem to XFS. Start array in maintenance mode, check filesystem on emulated disk1. Capture the output and post it.
January 19, 20233 yr Author 20 minutes ago, trurl said: Stop array, leave disk1 unassigned, click on disk1 slot to get to its page, set the filesystem to XFS. Start array in maintenance mode, check filesystem on emulated disk1. Capture the output and post it. 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.
January 19, 20233 yr Author 4 hours ago, trurl said: Do it again without -n. If it asks for it use -L. Post output 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
January 19, 20233 yr Community Expert 5 hours ago, JorgeB said: Start array in normal mode and post new diags. leave disk1 unassigned
January 20, 20233 yr Author 19 hours ago, JorgeB said: Start array in normal mode and post new diags. Attached, thank you. taflix-unraid-diagnostics-20230119-2201.zip
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.