[OpenIndiana-discuss] getting over my head on rpool mirror

Reginald Beardsley pulaskite at yahoo.com
Sun Aug 3 21:05:45 UTC 2014


If you didn't select an EFI label then I'm pretty sure there's an old EFI label on one or more of  the disks which needs to be wiped.  If you did select an EFI label, don't do that for boot disks.  There's no support for EFI boot.  That's why my NL40 was built using 2 TB disks instead of 3s.

dd if=/dev/zero bs=2048 count=1000 of=/dev/????

and then rerun fdisk.

You can use EFI labels, just not for booting.

Reg

--------------------------------------------
On Sun, 8/3/14, Harry Putnam <reader at newsguy.com> wrote:

 Subject: [OpenIndiana-discuss] getting over my head on rpool mirror
 To: openindiana-discuss at openindiana.org
 Date: Sunday, August 3, 2014, 2:42 PM
 
 I've created rpool mirrors before as
 a practice on vbox oi guests but
 now, on different hardware where its the real deal this
 time, I'm
 running into things I didn't have to deal with before.
 
 Setup: oi 151_9 running on HP xw8600 2x cpu (5470)
 
 First I'll show what fdisk sees on each disk.  Perhaps
 I made a
 mistake during install when I selected to use the whole disk
 for
 install?
 
 Here is the linup:
 format:
 
 AVAILABLE DISK SELECTIONS:
 
 ,----
 | These are the two for rpool:
 |        0. c0d0
 <Unknown-Unknown-0001 cyl 30398 alt 2 hd 255 sec 63>
 |           /pci at 0,0/pci-ide at 1f,2/ide at 0/cmdk at 0,0
 |        1. c0d1
 <Unknown-Unknown-0001 cyl 30398 alt 2 hd 255 sec 63>
 |           /pci at 0,0/pci-ide at 1f,2/ide at 0/cmdk at 1,0
 `----
        2. c1d0
 <Unknown-Unknown-0001 cyl 60797 alt 2 hd 255 sec 126>
           /pci at 0,0/pci-ide at 1f,2/ide at 1/cmdk at 0,0
        3. c1d1
 <Unknown-Unknown-0001 cyl 60797 alt 2 hd 255 sec 126>
           /pci at 0,0/pci-ide at 1f,2/ide at 1/cmdk at 1,0
 
 select 0:
 
 fdisk
 
              Total
 disk size is 30401 cylinders
          
    Cylinder size is 16065 (512 byte) blocks
 
                
                
            
    Cylinders
       Partition   Status 
   Type         
 Start   End   Length 
   %
       =========   ====== 
   ============ 
 =====   ===   ======   ===
           1   
    Active    Solaris2   
       1  30400    30400 
   100
 
 -------       -------   
    ---=---   
    -------   
    -------
 -------       -------   
    ---=---   
    -------   
    ------- 
 
 select 1:
 
 fdisk
 
              Total
 disk size is 30401 cylinders
          
    Cylinder size is 16065 (512 byte) blocks
 
                
                
            
    Cylinders
       Partition   Status 
   Type         
 Start   End   Length 
   %
       =========   ====== 
   ============ 
 =====   ===   ======   ===
           1   
    Active    Solaris2   
       1  30400    30400 
   100
 
 
 -------       -------   
    ---=---   
    -------   
    ------- 
 -------       -------   
    ---=---   
    -------   
    -------
 
 So, I'm thinking they are setup the same.  But maybe
 that is not what
 the above ouput shows because:
 
 Trying 
 
 zpool attach rpool c0d0 c1d0
 cannot label 'c1d0': EFI labeled devices are not supported
 on root
 pools.
 
 OK, doing a little research with google I hit on this:
 https://community.oracle.com/thread/2321898?tstart=0
 
 Which gives these steps to fix it:
 
   1. Get VTOC c0d0
   prtvtoc /dev/rdsk/c0d0s0
 
   2. Create same slice on c0d2. Use format or
   prtvtoc /dev/rdsk/c0d0s0| fmthard -s -
 /dev/rdsk/c0d2s0
 
   3. Attach slice.
   zpool attach -f rpool c0d0s0 c0d2s0
 
 First, let me ask where the mysterious appended `s0' came
 from?  I
 guess it means slice number 0?
 
 But anyway, going thru the steps I hit more troubles:
 
 
 Went smooth until arriving at step 3.  And note that
 after running  step 2: 
    prtvtoc /dev/rdsk/c0d0s0| fmthard -s -
 /dev/rdsk/c0d1s0
 
 I checked both disks vtoc with `prtvtoc $disk' on each
 disk.  The output
 looks identical.  And I inspected pretty closely.
 
   # zpool attach rpool c0d0s0 c0d1s0
   invalid vdev specification
   use '-f' to override the following errors:
   /dev/dsk/c0d1s0 overlaps with /dev/dsk/c0d1s2
 
 So, is it wise to use the -f flag and override the
 mismatch?
 
 
 _______________________________________________
 openindiana-discuss mailing list
 openindiana-discuss at openindiana.org
 http://openindiana.org/mailman/listinfo/openindiana-discuss
 



More information about the openindiana-discuss mailing list