> t0 shows > Partition Status Type Start End > Length % > ========= ====== ============ ===== === > ====== === > 1 Active Solaris2 1 30399 > 30399 100 > hows > Partition Status Type Start End > Length % > ========= ====== ============ ===== === > ====== === > 1 EFI 0 30400 > 30401 100 > ously when I added the second disk, it created it > with an EFI > label. I don't remember making any such decision, I > think it's done > this as a default action. > > I suspect what you have is an SMI labelled disk > (c5t0d0) and an EFI labelled disk (c5t1d0). How did > you add the second disk to the root pool? > > > I think you're spot on. I just did `zpool attach > rpool device'. Seems > like it's worked before just by chance. > > (Bootadm should be printing the reason for the > failure. Users should not be expected to activate > secret debugging options just to find out why a > command failed). > > > Absolutely. I half remembered this discussion, and > went looking for the > magic environment variable without success. (Once I > saw the error > message, I also went googling, but couldn't spot the > discussion, now > it's been confirmed I'll go looking again.) > > I'm tempted to just detach the device, try the > activate, reboot into the > new system, fdisk the second device by hand, and > re-attach. Like I say, > it's only a workstation, not a production machine.
That;s probably what I would have done as well, unfortunately it seems that this won't quite work - here is the "safe" way of removing the EFI-labelled disk posted by evanl above: I would follow the instructions Dan Price sent out last week: If you want to remove an EFI labelled disk from your root pool, my advice to you would be to do the following. Note that I have not tested this particular sequence, but I think it will work. Hah. 0) Backup your data and settings. 1) 'zpool detach' the EFI labelled disk from your pool. After you do this YOU MUST NOT REBOOT. Your system is now in a fragile state. 2) Run 'zpool status' to ensure that your pool now has one disk. 3) Edit /etc/boot/solaris/filelist.ramdisk. Remove the only line in the file: etc/zfs/zpool.cache 4) Delete /platform/i86pc/boot_archive and /platform/i86pc/amd64/boot_archive 5) Run 'bootadm update-archive' -- This rebuilds the boot archive, omitting the zpool.cache file. It may also be necessary to do installgrub at this point. Probably, and it wouldn't hurt. 6) Reboot your system, to ensure that you have a working configuration. I hope this helps... -evan Once you've done that you should be OK to manually create the fdisk partition then the required slices within in on the second disk. Cheers Andrew. -- This message posted from opensolaris.org _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
