Bug #15902
open
usr/sbin/format does not allow to change partitions 8, 9
0%
Description
whilst tryxing to prepare a disk to use as an additional mirror disk for the root pool (currently mirror with two 500G disks)
i tried to align the slices. The "problem" i try to solve is that the boot partition on the new disk is smaller(1M) than that of the current disks (8M boot slice) in the pool
partition> print Current partition table (original): Total disk cylinders available: 976739 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 3 - 976489 953.60GB (976487/0/0) 1999845376 1 unassigned wu 0 0 (0/0/0) 0 2 backup wu 0 - 976740 953.85GB (976741/0/0) 2000365568 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 unassigned wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 8 boot wu 0 - 0 1.00MB (1/0/0) 2048 9 alternates wm 0 0 (0/0/0) 0 partition> 8 `8' is not expected.
P.S. fmthard is not an option(i believe?) because i am going to increase the pool size by migrating to bigger disks (500G->1TB)
P.S. Yes i have the data inside the root pool, because i have no room for more disks on this machine
Updated by Toomas Soome 21 days ago
Stephan Althaus wrote:
whilst tryxing to prepare a disk to use as an additional mirror disk for the root pool (currently mirror with two 500G disks)
i tried to align the slices. The "problem" i try to solve is that the boot partition on the new disk is smaller(1M) than that of the current disks (8M boot slice) in the pool[...]
P.S. fmthard is not an option(i believe?) because i am going to increase the pool size by migrating to bigger disks (500G->1TB)
P.S. Yes i have the data inside the root pool, because i have no room for more disks on this machine
Those are actually issue about documentation; with VTOC16, slices 8 and 9 are "special". 9 is space allocated for "alternate" sectors, which are actually used to store fabricated device id (same as reserved partition in case of GPT).
boot slice is dedicated raw (without file system) space for boot blocks. With Solaris2 MBR partition, the first cylinder is allocated there, and it will encapsulate relative sector 0 (partition boot record), relative sector 1 (location of VTOC). And normally, your slice 0 would start from cylinder 1 (thats relative from start of the Solaris2 MBR partition).