/ mirror borked by jumpstart - prtvtoc info all screwed up Solaris 9
I set my profile up as follows:
metadbc1t0d0s7 size 8192 count 2
metadbc1t1d0s7 size 8192 count 2
metadbc1t2d0s7 size 8192 count 2
metadbc1t3d0s7 size 8192 count 2
filesysmirror:d0 c1t0d0s0 c1t1d0s0 10240 /
filesysmirror:d10 c1t0d0s1 c1t1d0s1 1024 swap
filesysmirror:d50 c1t0d0s5 c1t1d0s5 7120 /var
filesysmirror:d30 c1t0d0s3 c1t1d0s3 7120 /usr
filesysmirror:d40 c1t2d0s0 c1t3d0s0 33720 /opt
filesysmirror:d60 c1t0d0s6 c1t1d0s6 5120 /export
The metastat output says:
d0: Mirror
Submirror 0: d1
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 20971251 blocks (10.0 GB)
d1: Submirror of d0
State: Okay
Size: 20971251 blocks (10.0 GB)
Stripe 0:
DeviceStart Block DbaseState Reloc Hot Spare
c1t0d0s0 0NoOkayYes
d2: Concat/Stripe
Size: 20974140 blocks (10 GB)
Stripe 0:
DeviceStart Block DbaseReloc
c1t1d0s0 0NoYes
And it will not allow me to attach the second side of the mirror. I did a prtvtoc and I noticed this:
FirstSectorLast
* Partition Tag FlagsSectorCountSector Mount Directory
02002097414 20971251 23068664
1301 020974142097413
2500 0 71127180 71127179
340023068665 14580783 37649447
570037649448 14580783 52230230
680052230231 10484181 62714411
70006271441217334 62731745
The 0 sector starts at slice 1 instead of 0. Could this be the cause of the problem? If so, why is jumpstart doing this?
