Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Cache drive failed, shown as unnassigned instead of missing?

Featured Replies

Hi,

 

My current setup has 4 cache drives set to btrfs raid1.

One of those 4 drives seems to have died and I wanted to make sure that I am doing things by the book to prevent any data loss.

 

When I boot the server, it shows the failed drive as unassigned (which is a little weird to me, cause with array drives, they usually show as missing + drive name).

 

When I start the array without the failed drive attached, my docker containers seem to be missing. Shouldn't those still show up as the cache pool is set as a raid1 and therefor no data should've been lost?

 

When a spare drive is connected, I have the option to add it to the cache pool and format it, but I want be sure that if I do that, it will just rebuild the raid and give me back my docker containers?

 

Any advice?

Thx in advance

  • Community Expert

Diags after array start please.

  • Author
19 minutes ago, JorgeB said:

Error suggests superblock is damaged in one ore more devices, try the safe recovery options described here first:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=543490

 

 

Thx for the response.

I am getting the following error on all of my remaining cache drives:

 

> ERROR: cannot read chunk root
> Could not open root, trying backup super

 

Wanted to check if the only thing I can do is go for the btrfs check --repair command, as you state it is not a preferable solution?

  • Community Expert

If even the backup supers don't work unlikely that check --repair will also work, before trying that try this, on all 3 devices:

 

btrfs-select-super -s 1 /dev/sdX1

 

  • Author
1 minute ago, JorgeB said:

If even the backup supers don't work unlikely that check --repair will also work, before trying that try this, on all 3 devices:

 

btrfs-select-super -s 1 /dev/sdX1

 

 

no luck:

 

ERROR: cannot read chunk root
Open ctree failed

 

Will try --repair now

 

btrfs check --repair /dev/sdX1

 

  • Author

yeah, like you said, it didn't work either

 

ERROR: cannot read chunk root
ERROR: cannot open file system

 

So I have to live with the fact that all of my cache data is gone?

  • Community Expert

You can try this mentioned in the link:

 

If all else fails ask for help on the btrfs mailing list or #btrfs on libera.chat

 

Other than that can't help more with that error, since apparently all superblocks are damaged.

  • Author
Just now, JorgeB said:

You can try this mentioned in the link:

 

If all else fails ask for help on the btrfs mailing list or #btrfs on libera.chat

 

Other than that can't help more with that error, since apparently all superblocks are damaged.

 

Aight, thx for the help

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.