Hello, I tried that already format shows only a Solaris partition.
I did label the disk too but r...@yajug:~# zpool attach rpool mirror c4t1d0 cannot label 'c4t1d0': EFI labeled devices are not supported on root pools. Seb --- Sébastien Stormacq Senior Software Architect GSS Software Practice, Sun Microsystems Luxembourg On 23 Jan 2009, at 23:42, Evan Layton wrote: > Try running format, choose that disk, run fdisk and remove the EFI > fdisk partition and create a Solaris partition. Then in format label > the disk. > > -evan > > Sébastien Stormacq wrote: >> OK will try this >> Any suggestion to repartition ? I can't remind the exact errors >> but it seems that fdisk is not happy at all with the EFI >> partition :-( >> thanks >> --- >> Sébastien Stormacq >> Senior Software Architect >> GSS Software Practice, >> Sun Microsystems Luxembourg >> On 23 Jan 2009, at 23:26, Evan Layton wrote: >>> >>> On Jan 23, 2009, at 3:15 PM, Sébastien Stormacq <sebastien.storm...@sun.com >>> > wrote: >>> >>>> Evan, >>>> >>>> Using BE_PRINT_ERR=true (instead of 1 ;-) gives one more line >>>> that point to the error >>>> >>>> s...@yajug:~# beadm activate opensolaris-1 >>>> be_do_installgrub: installgrub failed for device c4t1d0s2. >>>> >>>> >>>> c4t1d0s2 is a mirror in my zpool >>>> >>>> s...@yajug:~# zpool status >>>> pool: rpool >>>> state: ONLINE >>>> scrub: resilver completed after 0h4m with 0 errors on Wed Jan 21 >>>> 13:57:10 2009 >>>> config: >>>> >>>> NAME STATE READ WRITE CKSUM >>>> rpool ONLINE 0 0 0 >>>> mirror ONLINE 0 0 0 >>>> c4t0d0s0 ONLINE 0 0 0 23.9M resilvered >>>> c4t1d0s2 ONLINE 0 0 0 4.16G resilvered >>>> >>>> errors: No known data errors >>>> >>>> >>>> I did not install grub (yet) on the second disk >>>> Actually, I had a whole bunch of issues to include that disk in >>>> the mirror because it is EFI partitioned >>>> >>>> Any suggestion ? >>> >>> EFI labeled disks are not supported for root pools. The only thing >>> I can suggest is to remove that device from the pool and remove >>> the EFI labeled partition, create a solaris fdisk partition (vtoc) >>> and re-attach the device. >>> >>> -evan >>> >>>> >>>> >>>> Thanks for your help >>>> >>>> >>>> --- >>>> Sébastien Stormacq >>>> Senior Software Architect >>>> GSS Software Practice, >>>> Sun Microsystems Luxembourg >>>> >>>> On 23 Jan 2009, at 23:11, Evan Layton wrote: >>>> >>>>> Sébastien Stormacq wrote: >>>>>> Hello, >>>>>> I installed OpenSolaris 2008.11 on a Sun v40z machine. >>>>>> Unfortunately the build I use, although being 101b was not the >>>>>> latest one, i.e. it was a couple of hours before GA : >>>>>> Sun Microsystems Inc. SunOS 5.11 snv_101b >>>>>> November 2008 >>>>>> I tried to update to GA with image-update >>>>>> r...@yajug:~# pkg list -u >>>>>> NAME (AUTHORITY) VERSION >>>>>> STATE UFIX >>>>>> entire 0.5.11-0.101 >>>>>> installed u--- >>>>>> r...@yajug:~# pkg image-update >>>>>> PHASE ACTIONS >>>>>> Update Phase 1/1 >>>>>> PHASE ITEMS >>>>>> Reading Existing Index 9/9 >>>>>> Indexing Packages 1/1 >>>>>> pkg: unable to activate opensolaris-1 >>>>>> r...@yajug:~# beadm activate opensolaris-1 >>>>>> Unable to activate opensolaris-1. >>>>>> Unknown external error. >>>>>> How can I further diagnose / solve this ?? >>>>> >>>>> Can you set "export BE_PRINT_ERR=true" before running beadm >>>>> activate and send the debug output? That should help narrow down >>>>> where the problem is. >>>>> >>>>> Thanks, >>>>> -evan >>>>> >>>>>> I followed the same procedure with the same image on a couple >>>>>> of VMs and it was always OK >>>>>> Thanks for your help >>>>>> --- >>>>>> Sébastien Stormacq >>>>>> Senior Software Architect >>>>>> GSS Software Practice, >>>>>> Sun Microsystems Luxembourg >>>>>> _______________________________________________ >>>>>> indiana-discuss mailing list >>>>>> indiana-discuss@opensolaris.org >>>>>> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss >>>>> >>>> > _______________________________________________ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
