Hi Sebastien,
You can test booting from the second disk just by selecting the second
disk to boot at the BIOS level.
You can review this error scenario and other ZFS troubleshooting issues,
here:
http://www.solarisinternals.com/wiki/index.php/ZFS_Troubleshooting_Guide
Not everything in this wi
Hello Cindy,
Looks like everything went fine this tile.
Thanks for the detailed procedure.
Just one last question : how to check the boot on the second disk
(step 7) ?
Is it as simple as removing my primary disk from the pool and reboot ?
or a more complex procedure ?
Thanks
Seb
---
Sébastien
Hi Sebastien,
I've outlined steps below to help you recovery from the label problem.
Make sure you can boot from the primary disk, c4t0d0s0, before you
begin.
I've reproduced these steps correctly on my Nevada, build 104 system
because my OpenSolaris system doesn't have two disks.
An easier reco
ore
From: Sébastien Stormacq
To: Evan Layton
Cc:
"indiana-discuss@opensolaris.org"
Sent: Saturday,
January 24, 2009 12:24:50 PM
Subject: Re:
[indiana-discuss] Cannot activate BE
Hello,
I tried that already
format shows only a Solaris partition.
I did label the disk too
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 Practi
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 no
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 Lay
On Jan 23, 2009, at 3:15 PM, Sébastien Stormacq 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 m
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
Thanks Brock,
Here it is
s...@yajug:~# export BE_PRINT_ERR=1
s...@yajug:~# beadm activate opensolaris-1
Unable to activate opensolaris-1.
Unknown external error.
s...@yajug:~# zfs list
NAMEUSED AVAIL REFER MOUNTPOINT
rpool 7.43G 59.5G 72
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_101bNovember 2008
>
> I tr
First thing to try is setting BE_PRINT_ERR=1 then running the beadm
activate command again.
If that doesn't make things clear, please show us the output of beadm
list and zfs list, and then perhaps trying running truss on beadm activate.
Hope that helps,
Brock
Sébastien Stormacq wrote:
> Hello
12 matches
Mail list logo
