Creating distinct Pool/Volume on HDD (Tos6 Beta 6.0.460)
Posted: 29 Aug 2024, 00:00
I have installed a clean (wiped) HDD in my F2-424 with 2 Nvme drives in Traid carrying the os and Volume1/Pool1 (BTRFS)
If I then opt to install a second volume (Volume2) on the new HDD (Still with BTRFS and Traid) the action results in os partitions being automatically written to the hdd and the hdd becomes (??default??) a system drive. {Pool2 being created automatically). This shows itself on re-boot.
The side effect is that one of the nvme drives is 'stripped' of it's system drive status. Previous testing along these lines tells me that configuration changes after such an event are not written to the non-system drive nvme despite the os partitions still being visible. Even, it still is apparently part of the raid1 mirror.
[edited slightly to remove unprintable characters ]
[sda is an unmounted hdd, subject of another thread]
The aim, of course is to maintain the initially chosen drives as system drives and NOT have the os partitions created on the added hdd.
Answers on a post-card.
If I then opt to install a second volume (Volume2) on the new HDD (Still with BTRFS and Traid) the action results in os partitions being automatically written to the hdd and the hdd becomes (??default??) a system drive. {Pool2 being created automatically). This shows itself on re-boot.
The side effect is that one of the nvme drives is 'stripped' of it's system drive status. Previous testing along these lines tells me that configuration changes after such an event are not written to the non-system drive nvme despite the os partitions still being visible. Even, it still is apparently part of the raid1 mirror.
Code: Select all
xxxxxxxx@NAS-T:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 5.5T 0 disk
sda1 8:1 0 5.5T 0 part
sdb 8:16 0 5.5T 0 disk
sdb1 8:17 0 285M 0 part
sdb2 8:18 0 7.6G 0 part
md9 9:9 0 7.6G 0 raid1 /
sdb3 8:19 0 1.9G 0 part
md8 9:8 0 1.9G 0 raid1 [SWAP]
sdb4 8:20 0 5.4T 0 part
md1 9:1 0 5.4T 0 raid1
vg1-lv1 252:1 0 5.4T 0 lvm /Volume2
nbd0 43:0 0 0B 0 disk
nbd1 43:32 0 0B 0 disk
nbd2 43:64 0 0B 0 disk
nbd3 43:96 0 0B 0 disk
nbd4 43:128 0 0B 0 disk
nbd5 43:160 0 0B 0 disk
nbd6 43:192 0 0B 0 disk
nbd7 43:224 0 0B 0 disk
sdzb 259:0 0 465.8G 0 disk
sdzb1 259:1 0 285M 0 part
sdzb2 259:2 0 7.6G 0 part
md9 9:9 0 7.6G 0 raid1 /
sdzb3 259:3 0 1.9G 0 part
md8 9:8 0 1.9G 0 raid1 [SWAP]
sdzb4 259:4 0 455.9G 0 part
md0 9:0 0 455.8G 0 raid1
vg0-lv0 252:0 0 455.8G 0 lvm /home
/Volume1
sdza 259:5 0 465.8G 0 disk
sdza1 259:6 0 285M 0 part
sdza2 259:7 0 7.6G 0 part
md9 9:9 0 7.6G 0 raid1 /
sdza3 259:8 0 1.9G 0 part
md8 9:8 0 1.9G 0 raid1 [SWAP]
sdza4 259:9 0 455.9G 0 part
md0 9:0 0 455.8G 0 raid1
vg0-lv0 252:0 0 455.8G 0 lvm /home
/Volume1
nbd8 43:256 0 0B 0 disk
nbd9 43:288 0 0B 0 disk
nbd10 43:320 0 0B 0 disk
nbd11 43:352 0 0B 0 disk
nbd12 43:384 0 0B 0 disk
nbd13 43:416 0 0B 0 disk
nbd14 43:448 0 0B 0 disk
nbd15 43:480 0 0B 0 disk
[sda is an unmounted hdd, subject of another thread]
The aim, of course is to maintain the initially chosen drives as system drives and NOT have the os partitions created on the added hdd.
Answers on a post-card.