tjm

I probably have to click 'Sync' then, even though it doesn't say that in the instructions. Right? Is there someone I should reach out to to get the instructions updated?

I followed these steps to get them rebuilt, and I did get notifications that they are being rebuilt: But I dont see a progress status notification or anything. And the 'main' page just has them listed with exclamation marks: Is there somewhere I can see progress? Or something else I need to do?

Thanks again. What are the next steps I should take from here to get back up-and-running? Thanks!

Sorry, I'm not sure I know how do to that. Could you provide more in-depth instructions? Thanks!

Diags attached rraid-diagnostics-20260428-0738.zip

There is no "fix" option, just a "check" option since there doesn't seem to be any corruption:

d5: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - 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 = 2 - agno = 3 - agno = 5 - agno = 6 - agno = 9 - agno = 10 - agno = 12 - agno = 13 - agno = 7 - agno = 4 - agno = 14 - agno = 15 - agno = 17 - agno = 18 - agno = 16 - agno = 8 - agno = 11 - agno = 19 - agno = 20 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. d19: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 7 - agno = 4 - agno = 5 - agno = 0 - agno = 6 - agno = 14 - agno = 8 - agno = 9 - agno = 13 - agno = 10 - agno = 2 - agno = 15 - agno = 11 - agno = 12 - agno = 16 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.

I tried rebooting as it didnt seem like there were many other options. But d5 & d19 are still showing 'device disabled, contents emulated'. What should I do?

i dont. what should i do to get this unstuck?

I tried stopping and restarting array but it seems to be stuck at this: "Array Stopping•Retry unmounting user share(s)..."

Logs have been zero'ed. Is that it? Do I now stop the array and restart in normal mode?

d5: 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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. d19: 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 the filesystem is a snapshot of a mounted filesystem, you may need to give mount the nouuid option. 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.

I'm assuming I should attempt a "fix" from here?

d5: 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.d19: 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.

Hey Everyone - I had an unclean shutdown and 2 of my disks are showing "unmountable". Diagnostics are attached. How should I fix this? Thanks! rraid-diagnostics-20260426-1411.zip

No, this does not work either. Status bar shows "Array Stopped" and it does not attempt to start.

new diags attached. I did toggle NFS before stopping/attempting to restart. I couldn't toggle SMB prior to this as it said SMB needed the array stopped to change: rraid-diagnostics-20260311-0810.zip

Could someone please assist with this? I am having a hell of a time adding/removing/swapping disks since I am unable to start array. Attached are diag, though I don't think they show anything. Any and all assistance is greatly appreciated. Thanks! rraid-diagnostics-20260310-1034.zip

I posted in what I think is the right channel (https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/page/475/) about 5-6 days ago, but haven't received any responses. Is that the right channel? Do y'all know of someone I could try to chase to get this resolved? Thanks!

Hope this is the right place to post. I'm following up from this thread: https://forums.unraid.net/topic/197199-array-wont-start-after-stopping/page/3/ In short, I have UD installed and I am able to stop and start the array. But as soon as I create a share (SMB), I am able to stop the array but not start it again. Any thoughts or help on being able to fix this would be greatly appreciated. Thanks!

same outcome. i uninstalled the plugin, i deleted everything related to unassigned.devices from here: rebooted then reinstalled plugin. with UD installed, can stop and start with share added, can stop cannot start diag attached from after clicking 'start' 3 or 4 times have rebooted since to get the array back up. unraid-diagnostics8.zip

im relieved to hear this. but current situation im in is: UD installed, can stop and start array UD installed and SMB shared added (not mounted), can stop but cannot start array any thoughts?

thanks for the info. im pretty sure i listed to the AI and deleted the /mnt/remotes/whatever path. any idea how i fix what ive broke?

new diags with share added attached yeah, this makes sense. but what AI was telling me that also made sense at the time was that if nothing is mounted in UD then /mnt/remotes/whatever is a temporary path in my ram that UD is storing files until the mount becomes available again. and i had some "stale" files in there, that AI recommended I delete. and this is why I deleted them. I swear, it made sense at the time it was told to me unraid-diagnostics7.zip