In this state, I cannot lumount disk2_slice4. It is busy. That also makes sense 
based on the
lustatus output but how do I get this straightened out?
Did you luactivate the boot environment or just add a grub menu entry for
it ?

I'm reasonably sure the problem is caused by my grub menu, but I have not 
managed
to get a change to take effect. The grub menu shows pointers to disk 
(luname,0,slice) Any edit or change I have tried to do to this menu so that one 
of the middle numbers is 1 for one disk
and  0 for the other disk has been wiped out when I use  the lu utilities or it 
appears  update_archive.

The middle number is not the disk, it is the partition number.


title disk2_slice0
findroot (BE_disk2_slice0,0,a)                            
<<<<<<<<<<<<<------------------------------
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive

title disk2_slice0 failsafe
findroot (BE_disk2_slice0,0,a)
kernel /boot/multiboot kernel/unix -s
module /boot/x86.miniroot-safe
Take a look at /<rpool name>/boot/grub/bootsign looking for a
zero length file name that matches the first argument to
findroot.  This may be why you are selecting the wrong drive.

I don't recommend trying to outsmart LU (it has absolutely no sense of
humor yet an unending capacity for irony and revenge), you can also try
replacing findroot with root(hd0,x,y) or root (hd1,x,y).


Bob
_______________________________________________
sysadmin-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss

Reply via email to