@Tex1954 Hello again.
Just wanted to chip in on this one:
But your could move them to a fresh Rockstor install. Or for that matter read the pools with any modern linux distribution. But a Rockstor install can import them far easier with far less knowledge required.
See: Import BTRFS Pool: Disks — Rockstor documentation
And you get the familiar representation. A modern Rockstor can import any prior Rockstor created btrfs volume (Pool in Rockstor speak). And we use vanilla btrfs. Hence the any modern linux install also being able to mount our Pools. Note however that the reverse is not true. We use a specific subset / arrangement of btrfs subvolumes and will ignore subvols that are not in this arrangement. However if a subvol (Share in Rockstor) is created on another linux distro and it is within the existing heierarcy used by Rockstor then it will import identically to any other Rockstor ‘native’ share. It’s just the location/arrangement of them that is important.
We also have the config backup and restore capability:
https://rockstor.com/docs/interface/system/config_backup.html
So if you take care not to use the system pool (which currently has no redundancy capabilities) and in this scenario is ‘lost’ anyway, then you can import a pool into a fresh install and restore you config (assuming you made one and downloaded it) and be pretty much were you were. If you are on a stable subscription version of Rockstor you can also, with immediate effect, transition your subscription to the new systems Appliance ID (it’s taken from the motherboard) via Appman (https://appman.rockstor.com/).
Also, re your performance testing. I’m assuming this was done on a v3 (CentOS) variant. Is that the case? Our v4 should be significantly better performing I’m guessing. Would be interesting to know.
Hope that helps.