December 13, 20241 yr I'm running v 6.12.13 In addition to the Parity and Disk 10 Error, I get a warning that says Array has 23 disks with read errors, I'm not sure why all the disks got errors all at once. About a week ago I added in a new 18TB drive, everything had been working fine, I was planning on moving over some of the data to it to start reducing the number of drives but I have not started that yet. I was going to just copy over data from Disk 10 to the newer drive but when I try to browse the emulated disk I get an "Invalid path" displayed where the shares normally are. When I've had disk go bad in past I simply replace and rebuild but this time a parity is down at same time so I want to be careful before I take any action. Attached is my diag. unraid-diagnostics-20241213-0817.zip
December 13, 20241 yr Community Expert All disks dropped offline at the same time, suggesting some kind of power/connection issue, doesn't appear to be a controller issue, reboot and post new diags after array start.
December 13, 20241 yr Author After reboot Disk 10 now shows "Unmountable: Unsupported or no file system" and no option to even browse. unraid-diagnostics-20241213-0850.zip
December 13, 20241 yr Author Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
December 13, 20241 yr Author Phase 1 - find and verify superblock... sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_icount 0, counted 115328 sb_ifree 0, counted 985 sb_fdblocks 732208911, counted 23931576 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 bad CRC for inode 128 bad CRC for inode 128, will rewrite cleared root inode 128 - agno = 1 - agno = 2 - agno = 3 - 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 = 3 - agno = 1 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... reinitializing root directory - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 131, moving to lost+found disconnected dir inode 133, moving to lost+found disconnected dir inode 472750569, moving to lost+found disconnected dir inode 472750581, moving to lost+found disconnected dir inode 2565674431, moving to lost+found disconnected dir inode 2565674432, moving to lost+found disconnected dir inode 4594701663, moving to lost+found disconnected dir inode 4594701664, moving to lost+found disconnected dir inode 4594701665, moving to lost+found disconnected dir inode 6695536270, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 1227 nlinks from 2 to 12 Maximum metadata LSN (2:2738601) is ahead of log (1:2). Format log to cycle 5. done
December 13, 20241 yr Community Expert Now start in normal mode, the disk should mount, and if contents look correct you can rebuild on top.
December 13, 20241 yr Author well it mounted that time, when I look in it, it just has lost+found. Do I need to copy that over to another drive for safe keeping before I try to rebuild? Will rebuild restore it back to the way it was?
December 13, 20241 yr Community Expert 4 minutes ago, meat said: Will rebuild restore it back to the way it was? Nope, a rebuild will restore the exact same thing you are seeing, if the contents for the emulated disk don't look good, you can check the actual disk, since SMART looks OK. Stop the array, unassign disk10, use the UD plugin to mount disk10 and check contents, if it looks OK, you can do a new config, and er-sync parity instead (parity2 you may keep as is, then it should just correct a few sync errors)
December 13, 20241 yr Author OK, so when mounting it as an unassigned disk it looks correct. So now just re-assign into disk 10 and do a new config?
December 13, 20241 yr Author just want to make sure I don't screw up this "new config" step. I had to do it once in the past a few years ago but I don't remember exactly what was involved. Right now the array is stopped. Disk 10 is unassigned. The disk with the data is an unassinged drive right now and all the data appears to be intact. Parity had a read error but Parity 2 is good. Do I re-assign the drive into Disk 10? Then chose Preserve ALL on the New Config and hit apply?
December 13, 20241 yr Community Expert Solution Go to tools - new config - keep all - apply All disk icons must turn blue, then re-assign disk10, "check parity is already valid" and start the array, run a correcting parity check, a few sync errors are expected.
December 13, 20241 yr Author Thank you for your help today. I'll let that run. Not sure how that happened, maybe my UPS is bad and we had a quick power failure.
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.