What should I do here?

[physikal]

I know it says unmount and repair but unmount what?

[macros the black]

You should check this out https://wiki.unraid.net/Check_Disk_Filesystems. Hopefully this will help. 

[trurl]

attach diagnostics to your NEXT post in this thread

[physikal]

6 hours ago, trurl said:

attach diagnostics to your NEXT post in this thread

Roger that. As soon as I get home I will. 

[physikal]

On 8/28/2022 at 12:54 PM, trurl said:

attach diagnostics to your NEXT post in this thread

Alright here are the diags.

tower-diagnostics-20220828-0833.zip

[trurl]

Disk1 is mounted as is emulated/rebuilding disk4.

 

Nothing assigned as disks 7-10, is that correct?

 

Why did you have to rebuild disk4?

 

Are your disks connected USB?

[physikal]

Disc4 is rebuilding because it was a drive that was running crazy hot (up to 54c) so I replaced it with a newer drive that I think would (and is) running cooler. I'm starting to wonder if temp was a reason for the kernel panic. So it was more of a preventative thing.  Only my UnraidOS is running on USB.  Correct - nothing assigned to disc 7-10.

 

Thanks!

[trurl]

The screenshot seemed to indicate filesystem corruption on disk1, but I don't see that in diagnostics now and disk1 is mounted.

 

Let disk4 rebuild complete, then check filesystem on disk1

[physikal]

1 hour ago, trurl said:

The screenshot seemed to indicate filesystem corruption on disk1, but I don't see that in diagnostics now and disk1 is mounted.

 

Let disk4 rebuild complete, then check filesystem on disk1

 Thank you so much for your help.  I'll do that asap.

[physikal]

2 hours ago, trurl said:

The screenshot seemed to indicate filesystem corruption on disk1, but I don't see that in diagnostics now and disk1 is mounted.

 

Let disk4 rebuild complete, then check filesystem on disk1

This is the result:

 

Phase 1 - find and verify superblock...
        - block cache size set to 8461064 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 1998769 tail block 1998769
        - 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
bad CRC for inode 5967449771
bad CRC for inode 5967449771, would rewrite
Bad atime nsec 2173239295 on inode 5967449771, would reset to zero
would have cleared inode 5967449771
        - agno = 3
        - agno = 4
        - agno = 5
        - 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 = 1
        - agno = 5
bad CRC for inode 5967449771, would rewrite
Bad atime nsec 2173239295 on inode 5967449771, would reset to zero
would have cleared inode 5967449771
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Tue Aug 30 20:34:12 2022

Phase		Start		End		Duration
Phase 1:	08/30 20:32:49	08/30 20:32:49
Phase 2:	08/30 20:32:49	08/30 20:32:58	9 seconds
Phase 3:	08/30 20:32:58	08/30 20:33:54	56 seconds
Phase 4:	08/30 20:33:54	08/30 20:33:55	1 second
Phase 5:	Skipped
Phase 6:	08/30 20:33:55	08/30 20:34:12	17 seconds
Phase 7:	08/30 20:34:12	08/30 20:34:12

Total run time: 1 minute, 23 seconds

 

[JorgeB]

Run it again without -n.