Moritz Willers wrote:
>>> Why does it claim that d30 is not a single-disk stripe? (and why  
>>> did it work just fine before?)
>> I'm not sure why it's not working, that should be detected  
>> correctly; when you say it worked fine before, what build was that?
> 
> the earlier upgrade was from snv_34 to snv_40
> 
> 
>>> Any chance the source to liveupgrade will be put out into the  
>>> open, so I wouldn't have to dig in the dark with closed binaries  
>>> trying to upgrade my otherwise open source system?
>> You can try setting the environment variable LU_DEBUG to some  
>> integer value and see what additional info you can get out of it.
> 
> nothing more :(
> 
> wicked# export LU_DEBUG=1

Actually, try it with a value of 2 or higher, and you'll get more.

> wicked# lucreate -n snv_45 -m /:d30:ufs,preserve
> Discovering physical storage devices
> Discovering logical storage devices
> Cross referencing storage devices with boot environment configurations
> Determining types of file systems supported
> Validating file system requests
> The device name <d30> expands to device path </dev/md/dsk/d30>
> Preparing logical storage devices
> Preparing physical storage devices
> Configuring physical storage devices
> Configuring logical storage devices
> Analyzing system configuration.
> Comparing source boot environment <snv_40> file systems with the file
> system(s) you specified for the new boot environment. Determining which
> file systems should be in the new boot environment.
> Updating boot environment description database on all BEs.
> Searching /dev for possible boot environment filesystem devices
> 
> ERROR: Mirror </dev/md/dsk/d30> submirror </dev/md/rdsk/d20> is not  
> single disk stripe.
> ERROR: Cannot determine boot device for Solaris Volume Manager  
> metadevice
> </dev/md/dsk/d30>. The only metadevices that support the root file  
> system
> are a stripe with only a single disk or a mirror on a single-disk  
> stripe.
> wicked#
> 
> the successful attempt read
> 
> Searching /dev for possible boot environment filesystem devices
> 
> Updating system configuration files.
> The device </dev/dsk/c1d0s0> is not a root device for any boot  
> environment.
> Creating configuration for boot environment <snv_40>.
> 
> at that point.
> 
> I don't know if it's worth noting that I went from / on d30 to the  
> upgraded / on d40 and now I'm going back again.
> 

I don't know whether that will make a difference.

Dave


Reply via email to