Jump to content

Two disk issue?: 1 disk with Red x and another Disk showing as unmountable


Recommended Posts

Hi everyone.

Hope you are all well.

 

Issue

Disk 6 disk has a Red X

Disk 24 is showing as unmountable

 

How it happened

Disk 6 came up with an error.

I did the SMART tests and rebooted and all seemed fine.

 

Did a further re-boot and now Disk 6 is now showing the Red X

And Disk 24, out of nowhere is showing as unmountable.

 

Help please.

Last time I tried this on my own, I ended up loosing data so, following the community advise I am reaching out to you guys first.

 

Appreciate your help with this.

 

Many thanks

Al

 

s1.jpg

kraken-diagnostics-20210509-1108.zip

Link to comment

Disk 6
SMART log attached - no error but still Red X

 

Disk 24

Ran xfs_repair

 

root@Kraken:~# xfs_repair -v /dev/md24
Phase 1 - find and verify superblock...
        - block cache size set to 1476248 entries
Phase 2 - using internal log
        - zero log...
Log inconsistent (didn't find previous header)
failed to find log head
zero_log: cannot find log head/tail (xlog_find_tail=5)
ERROR: The log head and/or tail cannot be discovered. Attempt to mount the
filesystem to replay the log or use the -L option to destroy the log and
attempt a repair.
root@Kraken:~# 

 

kraken-smart-20210509-1200.zip

Link to comment

Tried with -vn.

Log below.

Awaiting your reply before I try the -L (if that is the way to go) :)

 

 

 

root@Kraken:~# xfs_repair -vn /dev/md24
Phase 1 - find and verify superblock...
        - block cache size set to 1476248 entries
Phase 2 - using internal log
        - zero log...
Log inconsistent (didn't find previous header)
failed to find log head
zero_log: cannot find log head/tail (xlog_find_tail=5)
        - 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
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 5
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 6
        - agno = 4
        - agno = 7
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
        - agno = 6
        - agno = 7
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
Maximum metadata LSN (64:1023353) is ahead of log (0:0).
Would format log to cycle 67.
No modify flag set, skipping filesystem flush and exiting.

        XFS_REPAIR Summary    Sun May  9 12:17:29 2021

Phase           Start           End             Duration
Phase 1:        05/09 12:17:17  05/09 12:17:17
Phase 2:        05/09 12:17:17  05/09 12:17:17
Phase 3:        05/09 12:17:17  05/09 12:17:28  11 seconds
Phase 4:        05/09 12:17:28  05/09 12:17:28
Phase 5:        Skipped
Phase 6:        05/09 12:17:28  05/09 12:17:29  1 second
Phase 7:        05/09 12:17:29  05/09 12:17:29

Total run time: 12 seconds

Link to comment

root@Kraken:~# xfs_repair -Lv /dev/md24
Phase 1 - find and verify superblock...
        - block cache size set to 1476248 entries
Phase 2 - using internal log
        - zero log...
Log inconsistent or not a log (last==0, first!=1)
empty log check failed
zero_log: cannot find log head/tail (xlog_find_tail=22)
        - scan filesystem freespace and inode maps...
        - 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
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 4
        - agno = 1
        - agno = 3
        - agno = 6
        - agno = 5
        - agno = 7
        - agno = 2
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Maximum metadata LSN (64:1025259) is ahead of log (1:2).
Format log to cycle 67.

        XFS_REPAIR Summary    Sun May  9 12:57:07 2021

Phase           Start           End             Duration
Phase 1:        05/09 12:53:07  05/09 12:53:08  1 second
Phase 2:        05/09 12:53:08  05/09 12:54:06  58 seconds
Phase 3:        05/09 12:54:06  05/09 12:54:18  12 seconds
Phase 4:        05/09 12:54:18  05/09 12:54:18
Phase 5:        05/09 12:54:18  05/09 12:54:20  2 seconds
Phase 6:        05/09 12:54:20  05/09 12:54:21  1 second
Phase 7:        05/09 12:54:21  05/09 12:54:21

Total run time: 1 minute, 14 seconds
done
root@Kraken:~# 

Link to comment
33 minutes ago, alinkognito said:

Disk 6 SMART is stuck on 10%

I think it's gone bye bye

Ordered a new one and will swap it for the new one once it is in.

Needed more space anyway :)

 

Nevertheless, thank you SO MUCH for all your help.

You are a superstar!!!

x

How long has it been stuck?    Running an extended test will take many hours and I think it only updates every 10% of so it could stick on a particular value for quite some time.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...