Hello,

I am part way through building my next unRAID 'Media' Server where I plan to use only SSDs. I have a mixture of 960 GB, 2 TB, 3.84 TB and 4 TB SATA SSDs (the 960 GB and 3.84 TB SSDs are Enterprise SSDs) - 22 SSDs at present.

With the prices of SSDs now being silly prices, I would like to maximise the amount of storage space available, minimise File System overhead whilst making things easy to manage.

My original plan was to configure an unRAID SSD only Array WITHOUT parity disks (and no plans to ever add these) using BTRFS (with compression configured) for each disk. Then create a 'media' Share using the 'Fill-up' Allocation method. Utilising a Array allows each (SSD) disk to be individually 'spun up/spun down' (even with low power SSDs) and I can easily create an exact list of files and folders present on each disk that could be used to restore contents if a disk failed.

I understand that an all SSD unRAID Array WITH Parity is unsupported as TRIM can invalidate Parity and that unRAID has disabled TRIM support on Array SSDs.

I have attempted to manually run TRIM (e.g. fstrim -v /mnt/disk1) on an Array SSD and it returns "the discard operation is not supported".

I can also see that other BTRFS based Pools/Disks have the discard=async enabled which enables "automatic" TRIM.

Is it possible to:

1. Manually run TRIM on an Array SSD(s)?

2. Amend the default mount-ing process for the BTRFS-based Array SSDs so that they have discard=enabled on each Array SSD?

3. Use an alternative approach (stop Array, manually mount each Array SSD run TRIM then dismount each Array SSD)?

I know I can configure multiple Pools (using ZFS Stripes to maximise storage space) but would lose out on having a single Share for management plus would need to restore a whole (ZFS) Pool if a single disk failed.

Another idea would be to use individual single disk Pools, create a 'media' Share and then manually create a 'media' top-level folder on each single-pool disk and let FUSE 'merge' these together. This is far from ideal as I would then need to manually manage filling up each disk (although 95%+ of the media files present are write once, read many).

Suggestions and ideas welcome!

Thanks.

Array devices cannot be trimmed, with or without parity, though if you are running without parity, you could once a month or mount the devices outside the array and trim them.

Thanks Jorge,

I will investigate stopping the Array, manually mounting then TRIMing.

👍