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.

[SOLVED] SSDs and Raid 1 BTRFS and Retry Unmounting

Featured Replies

I need some help/advise.

 

I had a 240GB SSD for my cache drive.  All was working fine.

 

I got a new 1TB SSD to add.  I opened up my system, added the drive, and booted up.  I added the new 1TB SDD to the cache.  So it would be 1TB + 240GB.  I didn't notice at first it was a weird value.  I went into one of my Docker's(Plex), whose config info is on the 240GB SSD as Cache.  Plex was acting super slow.

 

I checked back to the main page and found the total cache size was 620GB, not what I was expecting it to be(1240GB about).  I went to shutdown the array.  Now the array is stuck in shutdown for "Retrying unmounting disk shares". 

 

While waiting for it to retry, retry, retry.  I looked up why the size doesn't match my expectations and found people mentioning that it creates a raid 1 btrfs between the 2 drives.  Not what I expected.  No mention is given that this would happen when adding the SSD to the cache.

 

I assume the shutdown hanging on the retry unmounting is due to the raid being built?  Is my cache data safe while this is running, and while the array is stuck shutting down?  About how long should this raid build take for the drives? 

 

Ideally the GUI should tell us this will happen, and give us the option of approaching things a different way.  Ideally, it could give us an estimated time.

 

Can I remove the 240GB drive after this is done, and have my cache data be safe and get back the full capacity of the 1TB SSD I just bought? 

 

So many questions, I hope someone has answers.

 

Edit: About an hour later, the array successfully unmounted. It appears the raid finished building on the cache drives. I was then able to change the cache setting to "-dconvert=single -mconvert=raid1" and a short while later, I had a cache 1.24 TB as I originally expected it to do. All data appears to have been fine throughout the process. I was really worried. 

  • Community Expert

For the future, you couldn't stop the array because the cache pool was balancing, this takes some time depending on how much data you have and if you're using SSDs or HDDs, clicking on "cache" will open its webGUI page, if a balance operation is ongoing it's shown there.

  • Author

Ya, found that out after the fact.  It gives you zero indication on the main page that it is doing such a thing. 

Archived

This topic is now archived and is closed to further replies.

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.