Hi, I tried to install an UPS and during this process I killed my unraid by removing power during running Unraid 🫣

I was running 7.1.3

I worked with Disk 1 and had 2 parities.
Now after reboot I see:
Parity disabled
Parity 2 active
Disk 1 disabled

All harddrives use XFS.

I stopped the array, restarted with Maintenance box checked and ran "Check Filesystem Status Disk 1 with these results for

xfs_repair status
<code>
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 = 0
        - agno = 2
        - agno = 3
        - agno = 1
        - 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
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.
<\code>

No file system corruption detected.

Is this now the right procedure?:
Alternative A)
1. Stop the array.

2. Go to Main → Array Devices.

3. Unassign Disk 1 (set it to “No Device”).

4. Start the array. (yes, without Disk 1 temporarily)

5. Stop the array again.

6. Reassign the same disk to Disk 1.

7. Start the array.

• Unraid will now offer an option like: Disk 1 appears to be disabled but contents are emulated — do you want to rebuild the disk onto itself?

8. Click “Yes” to start rebuild.

This will rebuild Disk 1 onto itself, which is safe and keeps your data.

OR would it be saver to do it this way?:
Alternative B)
1. Stop the array.
2. Go to Main -> Array Devices
3. Unassign Disk 1 AND the disabled Parity
4. Start the array
5. Stop the array again.
6. Reassign the "old" Parity to Parity but do not yet reassign Disk 1.
7. Start the array.
• Unraid will now offer an option like: Parity appears to be disabled but contents are emulated — do you want to rebuild the disk onto itself?

8. Click “Yes” to start rebuild.
9. If successful repeat the same procedure now as described in Alternative A.

Question: What should I do next?!?

Thanks for your help, best, Michael

tower-1-diagnostics-20250618-0009.zip

Edited June 19, 20251 yr by MichaelD

10 hours ago, MichaelD said:

Alternative B)

You can do this, just make sure the emulated disk1 is mounting and contents look correct before rebuilding on top.

1 minute ago, MichaelD said:

Hi, I tried to install an UPS and during this process I killed my unraid 🫣

I worked with Disk 1 and had 2 parities.
Now after reboot I see:
Parity disabled
Parity 2 active
Disk 1 disabled

All harddrives use XFS.

I stopped the array, restarted with Maintenance box checked and ran "Check Filesystem Status Disk 1 with these results for

xfs_repair status
<code>
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 = 0 - agno = 2 - agno = 3 - agno = 1 - 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 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.
<\code>

No file system corruption detected.

Question: What should I do next?

Thanks for your help, best, Michael

This Alternative B worked well, it rebuild first my second parity. Then I followed with Alternative A which rebuild my Disk 1.

Thanks @JorgeB for your support!!!!