Bob, thanks for your reply.
> > > 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 used luactivate. luactivate will not let me go back to BE_disk2_slice4. What I've discovered is that I can mount BE_disk2_slice4 using its device name, i.e. mount /dev/dsk/c2d0s4 /mnt > 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. Oh. that's a bummer. I thought I was understanding what was going on. :-( > 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. There were in fact two file names in that directory (although I haven't graduated to zfs yet :-)) home-amd:dws: ls /boot/grub/bootsign BE_disk1_slice0 BE_disk2_slice4 And in the BE_disk2_slice4 lu, there was only one name. home-amd:dws: ls /mnt/boot/grub/bootsign BE_disk2_slice4 Thinking this would be simple, I removed BE_disk2_slice4 and rebooted. I did get messages that update_archive couldn't be written to BE_disk1_slice0 on going down. Perhaps that is why on the reboot, I find I am in the same spot? home-amd:dws: lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ ---------- disk2_slice0 yes no no yes - disk2_slice3 yes no no yes - disk2_slice4 yes yes yes no - disk1_slice0 yes no no yes - And the actual disk mounted is the 500G disk. Was there something more to do? > > I don't recommend trying to outsmart LU (it has > absolutely no sense of > humor yet an unending capacity for irony and > revenge), Yeah I sort of get that. I hate to do it but perhaps I have no choice but to remove the lu configuration completely? >you can also try > replacing findroot with root(hd0,x,y) or root > (hd1,x,y). So the changes to menu.lst would be findroot (BE_disk2_slice0,0,a) -> findroot (hd1,0,a) findroot (BE_disk2_slice3,0,d) -> findroot (hd1,0,d) findroot (BE_disk2_slice4,0,e) -> findroot (hd1,0,e) findroot (BE_disk1_slice0,0,a) -> findroot (hd0,0,a) But since I am getting errors about not being able to write boot_archive, perhaps this won't do anything different? Thanks for your help. -- This message posted from opensolaris.org _______________________________________________ sysadmin-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss
