andrew wrote:
> Booting a ZFS pool from an EFI labelled disk has never been supported. I
> suspect they have just added checking for an EFI labelled disk in a recent
> build of beadm.
>
> Can you possibly post the output of these commands:
>
> fdisk /dev/rdsk/c5t0d0p0
> fdisk /dev/rdsk/c5t1d0s0
>
t0 shows
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 Active Solaris2 1 30399 30399 100
t1 shows
Partition Status Type Start End Length %
========= ====== ============ ===== === ====== ===
1 EFI 0 30400 30401 100
Obviously 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.
Rob
--
E-Mail: [EMAIL PROTECTED] PHONE: +44 24 7652 3037
Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
