Okay, first part done:

# cp /etc/vfstab /etc/vfstab.orig [backup]

# vi /etc/vfstab [# at begin of line with "/second_root"]

# umount /second_root/

# lustatus 
[2 lines with ERROR; that is okay, no boot environment created yet]

# lucreate -m /:/dev/dsk/c1d0s4:ufs -c nv81 -n nv91
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
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
No name for current boot environment.
Current boot environment is named <nv81>.
Creating initial configuration for primary boot environment <nv81>.
The device </dev/dsk/c1d0s0> is not a root device for any boot environment; 
cannot get BE ID.
PBE configuration successful: PBE name <nv81> PBE Boot Device </dev/dsk/c1d0s0>.
Comparing source boot environment <nv81> 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
                             
Updating system configuration files.
The device </dev/dsk/c1d0s4> is not a root device for any boot environment; 
cannot get BE ID.
Creating configuration for boot environment <nv91>.
Source boot environment is <nv81>.
Creating boot environment <nv91>.
Checking for GRUB menu on boot environment <nv91>.
The boot environment <nv91> does not contain the GRUB menu.
Creating file systems on boot environment <nv91>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c1d0s4>.
Mounting file systems for boot environment <nv91>.
Calculating required sizes of file systems for boot environment <nv91>.
Populating file systems on boot environment <nv91>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Copying.
WARNING: The file </tmp/lucopy.errors.2685> contains a list of <2>
potential problems (issues) that were encountered while populating boot
environment <nv91>.
INFORMATION: You must review the issues listed in
</tmp/lucopy.errors.2685> and determine if any must be resolved. In
general, you can ignore warnings about files that were skipped because
they did not exist or could not be opened. You cannot ignore errors such
as directories or files that could not be created, or file systems running
out of disk space. You must manually resolve any such problems before you
activate boot environment <nv91>.
Creating shared file system mount points.
Copying root of zone <t-zone>.
Creating compare databases for boot environment <nv91>.
Creating compare database for file system </>.
Updating compare databases on boot environment <nv91>.
Making boot environment <nv91> bootable.
Updating bootenv.rc on ABE <nv91>.
Population of boot environment <nv91> successful.
Creation of boot environment <nv91> successful.

The two problems are:
cpio: Error during chown() of "/.alt.tmp.b-hR.mnt/dev/zcons/t-zone/masterconsole
", errno 22, Invalid argument
cpio: Error during chown() of "/.alt.tmp.b-hR.mnt/dev/zcons/t-zone/zoneconsole",
 errno 22, Invalid argument
, but that should be okay when you're not running zones ...

# lustatus 
Boot Environment           Is       Active Active    Can    Copy      
Name                       Complete Now    On Reboot Delete Status    
-------------------------- -------- ------ --------- ------ ----------
nv81                       yes      yes    yes       no     -         
nv91                       yes      no     no        yes    -         

# bootadm list-menu
The location for the active GRUB menu is: /boot/grub/menu.lst
default 0
timeout 10
0 Solaris Express Community Edition snv_81 X86
1 Solaris xVM
2 Solaris failsafe

This shows that after a reboot nv81 will be booted. [default 0 == snv_81]

Next I'll try a reboot. This is so exciting, I did almost the same some months 
ago, and then it didn't boot, and nobody could help me to recover the system. I 
think I didn't uncomment the second_root in vfstab then, though.

And tell me nobody, this was easy and foolproof. I had made a mistake, 
originally, here:
# lucreate -m /:/dev/dsk/c0d0s4:ufs -c nv81 -n nv91
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
[...]

until I noticed my mistake and issued Ctrl-C ;)

though there is no c0d0!:
# format
Searching for disks...

The device does not support mode page 3 or page 4,
or the reported geometry info is invalid.
WARNING: Disk geometry is based on capacity data.

The current rpm value 0 is invalid, adjusting it to 3600
done

c2t0d0: configured with capacity of 298.07GB


AVAILABLE DISK SELECTIONS:
       0. c1d0 <DEFAULT cyl 9725 alt 2 hd 255 sec 63>
          /pci at 0,0/pci-ide at 9/ide at 0/cmdk at 0,0
       1. c2t0d0 <Maxtor-OneTouch-0200 cyl 38911 alt 2 hd 255 sec 63>
          /pci at 0,0/pci1565,3409 at 2,1/storage at 2/disk at 0,0

I wonder on which disk it did what it did?
 
 
This message posted from opensolaris.org

Reply via email to