I have a TrueNAS-12.0-U5.1 system with 17 drives. 12 of the drives are in a RAIDZ2 pool and one is a boot drive. The others I used for experimenting and as spares.
When I run gpool status most drives show exactly one partition, but some show two and I don't understand why. For example:
In this caes da4 and da5 are both part of the 12 drive RAIDZ2 pool and their partitioning scheme is the same, yet da5p1 and da5p2 are both listed but only da4p2 is:
da3 is the boot drive, so I'm not surprised that it's glabel status output is different, but da0, da5, da15, and da16 where added to the system using the GUI in the same way that all the other drives were, so there isn't any reason that their swap partition should show up in the gpool status output.
The output from gpart list for is nearly identical as well (though there are differences in the stripesize, stripeoffset, and mode):
One thing that I can think of is that the drives which show multiple partitions in the glabel status output were added to system as replacements when a different version of FreeNAS was being used and so were initialized with unusual settings, however since gpart list shows uuids for both partitions I'm not sure that make sense.
Thanks.
marcos
When I run gpool status most drives show exactly one partition, but some show two and I don't understand why. For example:
Code:
Name Status Components gptid/e8405e1f-4150-11ea-9a62-001a6b51e736 N/A da0p1 gptid/e9d4b812-4150-11ea-9a62-001a6b51e736 N/A da0p2 gptid/f9584dbe-4150-11ea-9a62-001a6b51e736 N/A da1p2 gptid/193abb34-4151-11ea-9a62-001a6b51e736 N/A da2p2 gptid/ff5ce719-8090-11e9-9a5e-001a6b51e736 N/A da3p1 gptid/162c130b-bcb8-11ea-8d04-001a6b51e736 N/A da4p2 gptid/8c0f3bc9-2131-11ec-b384-001a6b51e736 N/A da5p1 gptid/8c2b36d0-2131-11ec-b384-001a6b51e736 N/A da5p2 gptid/1ca64966-4f8f-11ea-adea-001a6b51e736 N/A da6p2 gptid/1e42c9da-4ae2-11ea-a5dc-001a6b51e736 N/A da7p2 gptid/2c71ee85-1e8a-11ec-a91d-001a6b51e736 N/A da8p2 gptid/43aa14d2-4151-11ea-9a62-001a6b51e736 N/A da9p2 gptid/4cf6320d-4151-11ea-9a62-001a6b51e736 N/A da10p2 gptid/d114f4e9-4973-11eb-80b3-001a6b51e736 N/A da11p2 gptid/4b7e8089-1e77-11ec-9077-001a6b51e736 N/A da12p2 gptid/4911aaa9-77b9-11eb-a388-001a6b51e736 N/A da13p2 gptid/d495ff47-52cf-11ea-8d94-001a6b51e736 N/A da14p2 gptid/082b7a58-1ef8-11ea-ba1e-001a6b51e736 N/A da15p1 gptid/0837fc0e-1ef8-11ea-ba1e-001a6b51e736 N/A da15p2 gptid/03ccfcdb-1ef8-11ea-ba1e-001a6b51e736 N/A da16p1 gptid/03dc8e32-1ef8-11ea-ba1e-001a6b51e736 N/A da16p2
In this caes da4 and da5 are both part of the 12 drive RAIDZ2 pool and their partitioning scheme is the same, yet da5p1 and da5p2 are both listed but only da4p2 is:
Code:
gpart show da5
=> 40 7814037088 da5 GPT (3.6T)
40 88 - free - (44K)
128 4194304 1 freebsd-swap (2.0G)
4194432 7809842696 2 freebsd-zfs (3.6T)Code:
gpart show da4
=> 40 7814037088 da4 GPT (3.6T)
40 88 - free - (44K)
128 4194304 1 freebsd-swap (2.0G)
4194432 7809842696 2 freebsd-zfs (3.6T)da3 is the boot drive, so I'm not surprised that it's glabel status output is different, but da0, da5, da15, and da16 where added to the system using the GUI in the same way that all the other drives were, so there isn't any reason that their swap partition should show up in the gpool status output.
The output from gpart list for is nearly identical as well (though there are differences in the stripesize, stripeoffset, and mode):
Code:
Geom name: da4 modified: false state: OK fwheads: 255 fwsectors: 63 last: 7814037127 first: 40 entries: 128 scheme: GPT Providers: 1. Name: da4p1 Mediasize: 2147483648 (2.0G) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e1 efimedia: HD(1,GPT,166f3ac6-bcb8-11ea-8d03-001a6b51e736,0x80,0x400000) rawuuid: 166f3ac6-bcb8-11ea-8d03-001a6b51e736 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 2147483648 offset: 65536 type: freebsd-swap index: 1 end: 4194431 start: 128 2. Name: da4p2 Mediasize: 3998639460352 (3.6T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r1w1e2 efimedia: HD(2,GPT,162c130b-bcb8-11ea-8d04-001a6b51e736,0x400080,0x1d180be08) rawuuid: 162c130b-bcb8-11ea-8d04-001a6b51e736 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 3998639460352 offset: 2147549184 type: freebsd-zfs index: 2 end: 7814037127 start: 4194432 Consumers: 1. Name: da4 Mediasize: 4000787030016 (3.6T) Sectorsize: 512 Stripesize: 4096 Stripeoffset: 0 Mode: r2w2e5 Geom name: da5 modified: false state: OK fwheads: 255 fwsectors: 63 last: 7814037127 first: 40 entries: 128 scheme: GPT Providers: 1. Name: da5p1 Mediasize: 2147483648 (2.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 65536 Mode: r0w0e0 efimedia: HD(1,GPT,8c0f3bc9-2131-11ec-b384-001a6b51e736,0x80,0x400000) rawuuid: 8c0f3bc9-2131-11ec-b384-001a6b51e736 rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 2147483648 offset: 65536 type: freebsd-swap index: 1 end: 4194431 start: 128 2. Name: da5p2 Mediasize: 3998639460352 (3.6T) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147549184 Mode: r1w1e2 efimedia: HD(2,GPT,8c2b36d0-2131-11ec-b384-001a6b51e736,0x400080,0x1d180be08) rawuuid: 8c2b36d0-2131-11ec-b384-001a6b51e736 rawtype: 516e7cba-6ecf-11d6-8ff8-00022d09712b label: (null) length: 3998639460352 offset: 2147549184 type: freebsd-zfs index: 2 end: 7814037127 start: 4194432 Consumers: 1. Name: da5 Mediasize: 4000787030016 (3.6T) Sectorsize: 512 Mode: r1w1e3
One thing that I can think of is that the drives which show multiple partitions in the glabel status output were added to system as replacements when a different version of FreeNAS was being used and so were initialized with unusual settings, however since gpart list shows uuids for both partitions I'm not sure that make sense.
Thanks.
marcos
