March 12, 20251 yr having an issue with a drive showing up as unmountable I removed it from array and started it - hoping it would get emulated, but unfortunately shows up as "Not installed" and data is still not available. I tried to use Unassigned devices to mount it, but it gets an error saying Mar 13 00:15:41 Omar root: Cannot use device /dev/sdc1 which is in use (already mapped or mounted). Mar 13 00:15:41 Omar root: Warning: keyslot operation could fail as it requires more than available memory. Mar 13 00:15:41 Omar emhttpd: shcmd (2030): exit status: 5 Mar 13 00:15:41 Omar emhttpd: read SMART /dev/sdc Mar 13 00:15:41 Omar unassigned.devices: luksOpen result: Error: Passphrase or Key File not found. I tried to add a keyfile to unassigned devices, but can only seem to insert a passphrase, not a keyfile Would appreciate any help, thank you!
March 12, 20251 yr Community Expert 1 hour ago, bucketphobia said: I removed it from array and started it - hoping it would get emulated, but unfortunately shows up as "Not installed" and data is still not available. It is emulated, but rebuild is not the way to fix unmountable. Attach Diagnostics to your NEXT post in this thread.
March 12, 20251 yr Author Just now, trurl said: It is emulated, but rebuild is not the way to fix unmountable. Attach Diagnostics to your NEXT post in this thread. Attached, thank you! omar-diagnostics-20250313-0121.zip
March 12, 20251 yr Community Expert Just now, trurl said: It is emulated, but rebuild is not the way to fix unmountable. Here is a post I made just today explaining disabled vs unmountable:
March 12, 20251 yr Community Expert Disk6 is missing, and emulated disk6 is unmountable. Check filesystem on emulated disk6.
March 12, 20251 yr Community Expert 1 hour ago, bucketphobia said: I removed it from array and started it - hoping it would get emulated That didn't help anything. It just made it so you will have to rebuild it after repairing emulated disk6. 2 minutes ago, trurl said: Check filesystem on emulated disk6. Post the output from that.
March 12, 20251 yr Author 14 minutes ago, trurl said: That didn't help anything. It just made it so you will have to rebuild it after repairing emulated disk6. Post the output from that. Started in maintenance mode, went to the disk and checked filesystem status, this is what pops up - should I continue with Fix? 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... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.
March 12, 20251 yr Community Expert 4 minutes ago, bucketphobia said: should I continue with Fix? yes, and post the output from that.
March 12, 20251 yr Author 2 minutes ago, trurl said: yes, and post the output from that. 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 root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 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.
March 12, 20251 yr Community Expert Just now, bucketphobia said: f you are unable to mount the filesystem, then use the -L option Unraid has already determined the disk is unmountable. Use -L. Post the output
March 12, 20251 yr Author 46 minutes ago, trurl said: Unraid has already determined the disk is unmountable. Use -L. Post the output Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 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 25472 sb_ifree 0, counted 14336 sb_fdblocks 3417569701, counted 2424849617 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - 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 = 7 - agno = 10 - agno = 1 - agno = 12 - agno = 8 - agno = 9 - agno = 6 - agno = 3 - agno = 4 - agno = 11 - agno = 5 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:399930) is ahead of log (1:2). Format log to cycle 4. done Ran check afterwards, says "no filesystem corruption detected"
March 13, 20251 yr Author Booted up array normally (but without adding the drive back in, leaving it emulated) - drive is fine with all content intact it seems! (no lost+found folder either) I assume next step is to just verify that everything is intact, then re-add the drive and rebuild parity? Thanks a ton for all the help btw, super appreciated!!
March 13, 20251 yr Author 2 minutes ago, trurl said: rebuild disk6 Yeah sorry, that’s what I meant - Stop array, readd disk, let it do its thing?
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.