Jump to content

Cache: Unmountable: Unsupported or no file system (after update)

BBenja

By BBenja
in General Support

Go to solution Solved by JorgeB,

Recommended Posts

  • 1 month later...
mrderrickc Noob

mrderrickc

Posted
Posted
1 hour ago, JorgeB said:

Check filesystem on cache, run it without -n.

 

Couldn't run it via the GUI as it didn't have the option for the cache drive. Ran it via the CLI and got the following...

  


xfs_repair /dev/nvme0n1
Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
.found candidate secondary superblock...
unable to verify superblock, continuing...
.found candidate secondary superblock...
unable to verify superblock, continuing...
.found candidate secondary superblock...
unable to verify superblock, continuing...

....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

 

Sorry, could not find valid secondary superblock Exiting now.

Link to comment
JorgeB Grand Master

JorgeB

Posted
Posted
18 minutes ago, mrderrickc said:

Couldn't run it via the GUI as it didn't have the option for the cache drive.

It should have.

 

18 minutes ago, mrderrickc said:

Ran it via the CLI and got the following...

That's not correct, type:

  

xfs_repair /dev/nvme0n1p1

 

Link to comment
mrderrickc Noob

mrderrickc

Posted
Posted
20 minutes ago, JorgeB said:

It should have.

 

That's not correct, type:

  

xfs_repair /dev/nvme0n1p1

 

 

This is what is shows in the GUI.

1371996366_Screenshot2024-01-06221154.thumb.png.700c223751ef9a19ab0d188b05ae9706.png

 

2082343141_Screenshot2024-01-06221252.thumb.png.2bfa258297de4fabf31182ab72d556af.png

 

Ran the above code and got this.

  


xfs_repair /dev/nvme0n1p1
Phase 1 - find and verify superblock...
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.

Link to comment
  • 4 weeks later...
tomas. Noob

tomas.

Posted
Posted (edited)

Edit: I decided to create a new thread instead, as this one is marked as solved. 

 

 

Hello, I am having the same problem where by cache drive is "unmountable", file system was btrfs. I tried running some of the commands that you recommended in this thread but I only got this as a response. This problem appeared out of nowhere.

 

1275894787_Screenshot2024-02-04at21_38_56.png.18d21ae6a72a73fe9dcb278144788d33.png

 

2103100499_Screenshot2024-02-04at21_37_55.thumb.png.12a4ee8e0ae0273b115191b59f5a023f.png

Tower Diagnostics 20240204 2135.zip

Edited by tomas.
new thread
Link to comment
2112 Noob

2112

Posted
Posted (edited)
1 hour ago, JorgeB said:

And where are they? And what is the problem?

 

My cache drives are showing up as "unmountable:  unsupported or no file system."  I am unable to stop/start my array and assign these drives but the highlighted message below keeps showing.  Unraid will let me format these but I don't want to lose my appdata contents.  Any help or guidance would be appreciated.

 

image.thumb.png.b727ca738bd87771b7680c5fe3aff740.png

 

Edited by 2112
Link to comment
2112 Noob

2112

Posted
Posted
12 minutes ago, JorgeB said:

Try clearing the log tree, if that is the only problem it may fix it:

  

btrfs rescue zero-log /dev/sdh1

 

Then restart the array.


YOU ARE THE MAN!  That worked.  Lesson learned, I will not be backing up my appdata folder.  

 

I owe you one, seriously!

  • Like 1
Link to comment
  • 4 weeks later...
youngnapoleon Noob

youngnapoleon

Posted
Posted
On 7/5/2023 at 11:51 PM, JorgeB said:

It wouldn't because it may have the same end result but 's not the same problem, log tree is damaged, if that is the only issue this may help:

  

btrfs rescue zero-log /dev/sdj1

 

Then re-start array.

I know this is old, but just wanted to thank you because I was really stressing out & this saved me big time. God/Allah/Bob Dylan/all of them bless you.

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.

×
Go to topic listing
×
×
  • Create New...