Bad Mirror

[Marcelo F. P. Junior]

Hi guys,

I create a mirror bot disc and when I to boot with this disc i received the message "Bad number in path spec" below is the Howto to make this Mirror Boot Disk:

1. pvcreate -B /dev/rdsk/c2t6d0
2. vgextend /dev/vg00 /dev/dsk/c2t6d0
3. mkboot /dev/rdsk/c2t6d0
4. mkboot -a "hpux (disk;0)/stand/vmunix" \
/dev/rdsk/c2t6d0
5. lvextend -m 1 /dev/vg00/lvol1 \
/dev/dsk/c2t6d0
6. lvextend -m 1 /dev/vg00/lvol2 \
/dev/dsk/c2t6d0
7. lvextend -m 1 /dev/vg00/lvol3 \
/dev/dsk/c2t6d0
8. lvextend -m 1 /dev/vg00/lvol4 \
/dev/dsk/c2t6d0
9. lvextend -m 1 /dev/vg00/lvol5 \
/dev/dsk/c2t6d0
10. lvextend -m 1 /dev/vg00/lvol6 \
/dev/dsk/c2t6d0
11. lvextend -m 1 /dev/vg00/lvol7 \
/dev/dsk/c2t6d0

12. setboot -a 0/0/2/1.6.0
13. /usr/sbin/lvlnboot -v -r /dev/vg00/lvol1
14. /usr/sbin/lvlnboot -s /dev/vg00/lvol2
15. /usr/sbin/lvlnboot -R /dev/vg00
Follow my ioscan -fnC disk

disk 873 0/0/1/0.1.0 sdisk CLAIMED DEVICE HP DVD-ROM 304
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0
disk 1 0/0/2/0.6.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 2 0/0/2/1.6.0 sdisk CLAIMED DEVICE IBM DMVS18D
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0

Follow my lvmtab:
/dev/vg00
/dev/dsk/c1t6d0
/dev/dsk/c2t6d0

Follow my lvlnboot:

Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t6d0 (0/0/2/0.6.0) -- Boot Disk
/dev/dsk/c2t6d0 (0/0/2/1.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Root: lvol3 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c1t6d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c1t6d0, 0

in lvdisplay all the lvols is mirrored but this disc don`t boot.

Tks

Marcelo

[Marcelo F. P. Junior]

Sorry,

I forget the setboot command:

Primary bootpath : 0/0/2/0.6.0
Alternate bootpath : 0/0/2/1.6.0

[Duncan Edmonstone]

Marcelo,

I think this is your problem:

4. mkboot -a "hpux (disk;0)/stand/vmunix" \
/dev/rdsk/c2t6d0


If you *really want to specify the device manager is to be of type disk (actually disc is the coreect spelling), it should be like this:

mkboot -a "hpux disc(;0)/stand/vmunix" \
/dev/rdsk/c2t6d0

Note that the deice manager specification comes outside the brackets. But there's really no need to specify the device manager at all so in fact:

mkboot -a "hpux (;0)/stand/vmunix" \
/dev/rdsk/c2t6d0

should work fine.

See the man page for hpux(1m) for more details.

HTH

Duncan

[Andrew Rutter]

hi,

On top of what Duncan has said, it would also be better if you created it with the -lq option aswell, so the system boots even if the disk is dead/removed.

mkboot -a "hpux -lq(;0)/stand/vmunix" \
/dev/rdsk/c2t6d0

Andy

[Rasheed Tamton]

Hi Marcelo,

As said above, mkboot -a "hpux -lq" /dev/rdsk/c2t6d0 is good enough.

Also use lifls -l /dev/rdsk/c2t6d0 to see the lif dir - run it on both disks to see the contents.

more /stand/bootconf
(bootconf - boot device configuration table)
In rare cases when either the
system configuration cannot be automatically determined or additional
and/or alternate boot devices should be automatically updated, the
administrator must edit the /stand/bootconf file manually.


Rgds,
Rasheed Tamton.

[SAJ_3]

Hi,

check the entires in the /stand/bootconf and
confirm the entry for the new disk is there.

one more thing please tell only
/usr/sbin/lvlnboot -v -r /dev/vg00/lvol1
/usr/sbin/lvlnboot -s /dev/vg00/lvol2

updated.