Fix was to drop the "-S" from the flarcreate - let it pre-calculate the size of
the system. That stops the "Could not stop the extraction" message and
jumpstart continues to completion, everything works now.
AW
Quote =========
Hi
Got a wee problem, hoping someone can advise. Set up a disk on an ISCSI SAN and
made available to the host. Some relevant config info.
Host: Solaris 10 5/08 s10s_u5wos_10 SPARC
LDOM: 1.0.2 (yeah I know it's old - stuck there for time being)
root at sunhc32> ldm ls -l primary
...
primary-vds0
dev-iscsi /dev/rdsk/c2t600A0B800049C9340000578D4AF99951d0s2
...
root at sunhc32> ldm ls -l dev-iscsi
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
dev-iscsi active -n--- 5001 4 2500M 0.0% 59m
...
VARIABLES
auto-boot?=false
nvramrc=devalias disk /virtual-devices at 100/channel-devices at 200/disk
at 0
use-nvramrc?=true
NETWORK
NAME SERVICE DEVICE MAC
vnet0 primary-vsw0 at primary network at 0
00:14:4f:fb:86:39
DISK
NAME VOLUME TOUT DEVICE SERVER
disk0 dev-iscsi at primary-vds0 disk at 0 primary
VCONS
NAME SERVICE PORT
dev-iscsi primary-vcc0 at primary 5001
Flar created thusly - it's actually already an LDOM, we're reconfiguring
storage and such and trying this for an action plan.
$ flarcreate -n "sunhc32b-devdom" -S -R /? /sunhc1/sunhc32b-devdom.flar
Full Flash
Checking integrity...
Integrity OK.
Running precreation scripts...
Precreation scripts done.
Creating the archive...
cpio: cpio: dpp/tables/DEV2/DEV2iwtables01.dbf: too large to archive in current
mode
cpio: cpio: dpp/tables/DEV2/DEV2iwtables02.dbf: too large to archive in current
mode
cpio: cpio: dpp/tables/DEV2/DEV2temp01.dbf: too large to archive in current mode
cpio: cpio: dpp/indexes/DEV2/DEV2iwindexes01.dbf: too large to archive in
current mode
cpio: cpio: dpp/indexes/DEV2/DEV2iwindexes02.dbf: too large to archive in
current mode
43443829 blocks
5 error(s)
Archive creation complete.
Running postcreation scripts...
Postcreation scripts done.
Running pre-exit scripts...
Pre-exit scripts done.
Uh-oh. Web-wisdom says it's the "-c" option in flarcreate CPIO that causes the
problem. But I tried it without -c and the same problem. Perhaps it's not
relevant.
Did the flar-jumpstart thing, and right at the end...
Extracted 17208.87 MB (100% of 17208.87 MB archive)
ERROR: Could not stop the extraction
ERROR: Could not extract Flash archive
ERROR: Flash installation failed
Solaris installation program exited.
Did an "init 6" anyway, as some people seemed to think it would work. It
didn't. Had to boot net again, and do an installboot to get a boot sector. I
can mount all the slices and see everything there fine. Disks look OK. Did a
"boot" to kick things off again...
The / file system (/dev/rdsk/c0d0s0) is being checked.
WARNING - Unable to repair the / filesystem. Run fsck
manually (fsck -F ufs /dev/rdsk/c0d0s0).
Dropped into maintenance mode:
# ls -l /dev/*dsk
/dev/*dsk: No such file or directory
No /dev/rdsk or /dev/dsk !!
Format won't work, devfsadm won't work, disks won't work. Of course, volume is
read-only at this point. Relevant vfstab looks legit.
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
/dev/dsk/c0d0s1 - - swap - no -
/dev/dsk/c0d0s0 /dev/rdsk/c0d0s0 / ufs 1 no -
/
Any help ? Am stuck here, don't know where to go.
Thanks
AW
====== End quote
Fix was to drop the "-S" from the flarcreate - let it pre-calculate the size of
the system. That stops the "Could not stop the extraction" message and
jumpstart continues to completion, everything works now.
AW
______________________________________________
This email has been scanned by Netintelligence
http://www.netintelligence.com/email
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/ldoms-discuss/attachments/20091127/9ecb1338/attachment.html>
