Adrian Florea wrote:
> I think is doing this because the / filesystem is
> built on top of a metadevice (that is a mirror)
> consisting of a single submirror (i.e. built on a
> single slice). 
>   
Actually, the 1 way mirror shouldn't matter. A 1 way mirror is legal and 
should mount ok.  My suggestion would be to try this using the 
underlying slice name, not the SVM metadevice name. Could be a problem 
with SVM for some reason. If it works when you specify the underlying 
slice name then we can start to debug this with the SVM folks.

sarah
*****
> So you can try one of:
>
> - try to have / on a correctly setup two way mirror
> and then LU (I did this on SPARC without problems, on
> Solaris 10)
>
> - don't use mirror for / if is built on only one
> slice.
>
>
> maybe this helps,
> Adrian
>
>
> --- Moritz Willers <mo at wit.ch> wrote:
>
>   
>> thanks for the suggestion, but nope.  Exactly the
>> same.
>>
>> # lucreate -c snv_40 -n snv_46 -C /dev/dsk/c2d0s0 -m
>> /:/dev/md/dsk/ 
>> d30:ufs
>> ..
>> Integrity check OK.
>> Populating contents of mount point </>.
>> Copying.
>> Creating shared file system mount points.
>> Creating compare databases for boot environment
>> <snv_46>.
>> Creating compare database for file system </>.
>> Updating compare databases on boot environment
>> <snv_46>.
>> Making boot environment <snv_46> bootable.
>> Updating bootenv.rc on ABE <snv_46>.
>> Generating partition and slice information for ABE
>> <snv_46>
>> Setting root slice to Solaris Volume Manager
>> metadevice </dev/md/dsk/ 
>> d30>.
>> mount: /dev/md/dsk/d10 write-protected
>> ERROR: Cannot mount boot slice </dev/md/dsk/d10>.
>> Cannot update GRUB  
>> menu
>> ERROR: Unable to delete GRUB menu entry for boot
>> environment <snv_46>.
>> ERROR: Cannot make file systems for boot environment
>> <snv_46>.
>> wicked# df /
>> /                  (/dev/md/dsk/d40   ):17123206
>> blocks  1184519 files
>> wicked# metastat -p d40
>> d40 -m /dev/md/rdsk/d10 1d10 1 1 /dev/rdsk/c2d0s0
>>
>> guess it's time to try without DiskSuite.  What's
>> going to break  
>> next, though?  Would I'd better of abandoning LU?
>>
>> What other option would I have to keep my
>> OpenSolaris system up to  
>> date, that would not involve burning a DVD on a
>> regular basis and  
>> booting of that to upgrade, nor having a second
>> netboot/install  
>> server on the home network?
>>
>> - mo
>>
>> On 29 Aug 2006, at 19:52, Dave Miner wrote:
>>
>>     
>>> I suspect it's a bug in handling the 'preserve'
>>>       
>> option, which I  
>>     
>>> don't think gets exercised all that widely - I
>>>       
>> don't personally  
>>     
>>> know anyone who uses it on a regular basis.  I
>>>       
>> would guess that the  
>>     
>>> lucreate without that would work fine and you'd be
>>>       
>> on your way,  
>>     
>>> though obviously it'll take the time to copy the
>>>       
>> data.
>>
>> _______________________________________________
>> install-discuss mailing list
>> install-discuss at opensolaris.org
>>
>>     
> http://opensolaris.org/mailman/listinfo/install-discuss
>   
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> install-discuss mailing list
> install-discuss at opensolaris.org
> http://opensolaris.org/mailman/listinfo/install-discuss
>
>   


Reply via email to