Hi all!

I currently have an array with a parity disk, and a pool with an SSD for docker and several hard drives.

The shares are on a single disk; the data isn't spread across disks.

I want to remove the parity disk, without losing any data, of course.

In my new setup, I want to use each disk independently for my shares; I don't want parity or RAID.

What's best?

Just have one pool with all the disks?

Just have the array with all the disks without parity?

Have several pools (and no array), each with a single disk? (I don't think this last one is ideal, since I think data can't be moved from one pool to another)

I don't want lose any data changing to the new config.

Thank you so much.

Disks can all be in the array without parity; any SSDs should be on a single pool, or TRIM won't work.

You can always remove the parity drive(s) without affecting the data on the array disks.

It is not clear if you already have HDD in the array? If so probably easiest to keep them there. Shares can be configured to use specific disks (or pools).

Not sure where you go the idea that data cannot be moved between pools? However unless you have HDD pools then probably no need to have one pool operating as 'cache' for another which seems the only obvious Use Case.

I have both, HDD and SSD, in the array and in the pool...

I only want a "simple" data storages, in different shares... And one of the SSD for docker.

So, from the point of performance and simplicity, all in one pool, HDD and SSD?

Thank you.

1 hour ago, JorgeB said:

Disks can all be in the array without parity; any SSDs should be on a single pool, or TRIM won't work.

When you say "single pool", you mean multiple pools, any SSD alone in their own pool?

44 minutes ago, Nelo3D said:

any SSD alone in their own pool?

Correct, if you have multiple.

Ok, but I don't know why...

What is the difference for one disc alone in a pool and sharing pool with other discs?

So, for my case the best option is n pools of one disk every one, right?

Thank you so much!

Multiple disks in the same pool can only be used if they are all part of the same btrfs or zfs filesystem, they cannot be used together with seperate filesystems.

Wow, I don't know how I have multiple mixed SSD and HDD in one pool. I was very wrong.

I have all my disks as xfs, by the way.

So, I will go to a new config, with as pools as disks I have.

You're great, Jorge, thank you.

1 hour ago, Nelo3D said:

I don't know how I have multiple mixed SSD and HDD in one pool

I have all my disks as xfs, by the way.

That must be the array, not a pool

3 minutes ago, JorgeB said:

That must be the array, not a pool

I'm confused know. Sorry.

So, for my new config, I must put all disks ( without parity ) in the array, HDD and SSD?

SSDs in the array cannot be trimmed, and can only be written at parity speed.

HDDs in array, with or without parity.

SSDs in a pool outside the array.

Would probably save a lot of back and forth and guess work if you

Attach Diagnostics ZIP to your NEXT post in this thread.

1 minute ago, trurl said:

SSDs in a pool outside the array.

Or in multiple pools depending. You can have multiple pools outside the array, each pool can have multiple disks. Multidisk pools must be btrfs or ZFS.

18 minutes ago, trurl said:

Or in multiple pools depending. You can have multiple pools outside the array, each pool can have multiple disks. Multidisk pools must be btrfs or ZFS.

Currently I have xfs in the pool.

The objective is disable parity, and add this disk as data, all disks as data indeed, except the appdata/docker SSD.

nuvol-diagnostics-20260506-1755.zip

34 minutes ago, Nelo3D said:

The objective is disable parity, and add this disk as data, all disks as data indeed, except the appdata/docker SSD

You can assign all disks to the array as individual data disks without parity; any SSDs should be assigned as a pool. You can do a new config to reconfigure (Tools - New config)

OK, so the array and two pools, one for appdata and another for the cloud SSD.

Thank you!

PD: I assume that with the new config I will not lose any data. I can stay on xfs filesystem.

1 hour ago, Nelo3D said:

PD: I assume that with the new config I will not lose any data. I can stay on xfs filesystem.

It will import the data from any disk assigned to the array as data, and any pools; just make sure you don't assign any data disk as parity.