Cache pool disk replacement went wrong?


Recommended Posts

My Cache pool consists of two NVMe M.2 SSDs. I need to increase them. So I thought stop the Server, replace one of the two disks and start the Server.

 

To my surprise the array comes up (different from replacing array drives). It shows a missing disk but I can't stop the array. Balance running is the message. What is balancing what? There's only one disk of the two-disk cache pool left. The new cache disk shows up under Unassigned devices.

 

What went wrong?

 

Any help is highly appreciated.

 

***EDIT*** Screenshot attached, values of Cache pool are complete nonsense now. 250 GB disk shows 500 GB. Empty space is now 64 GB, it was 10 GB. Is balancing deleting the Cache disk that is left?

 

 

tower-diagnostics-20200902-1011.zip

bla.jpg

Edited by hawihoney
Link to comment

I can't stop. BTRFS operation in progress. Stop button unavailable.

 

What did I wrong? I stopped the server, replaced the disk and started the server. Cache pool started with missing disk and is pondering the remaining cache disk.

 

I don't understand that. Consider a cache pool with a failing disk, and the first thing that BTRFS does is hammering the remaining good disk? This disk is at 62 degree currently during that balance operation.

 

I fear the good disk will fail too shortly.

 

 

Edited by hawihoney
Link to comment

One hour later. The balance of the remaining disk took an hour.

 

Stopped array, set new disk in second slot, and started array. What happens now? BTRFS is again writing at high speed to the remaining disk plus writing to the new disk.

 

Sorry BTRFS, this is a good laugh. During replacement of a (failing) disk BTRFS _writes_ at high speed to the remaining good disk _twice_. I would expect to read from the remaining disk and write to the new disk as the array does. I have no FS knowledge but this can't be serious.

 

bla2.jpg

Link to comment

There's a difference.

 

Unraid array, disk fails:

Stop server, replace array disk, start server

Array will not be started, set new disk in place, start array

All disks except new disk are read, the new disk is written

 

Unraid cache pool, disk fails:

Stop server, replace cache pool disk, start server

Array/pool will start up with missing cache disk

Remaining cache disk is written, stop not possible

When balance finished, stop array

Set new disk in place, start array

All disks are written

 

Don't you see the difference?

 

The array reads all remaining disks once and writes to the new disk once.

The cache pool reads all remainig disks twice and writes to the new disk twice.

 

Edited by hawihoney
Link to comment

I don't get that. What would you do exactly?

 

I stopped the server, replaced the cache pool disk and started server. The array starts immediately and cache pool starts immediately with balance of remaining disk. No chance to select the new cache pool disk. New disk is added to Unassigned devices instead.

 

What's wrong, what should I do?

 

***EDIT*** I see. What you suggest is not possible. I'm talking about two NVMe M.2 SSDs, for two available slots. I can't add a third one.

 

Edited by hawihoney
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.