From: Michael D. Steeves (msteeves+sunmanagers@eecs.tufts.edu)
Date: Wed Sep 28 2005 - 13:49:50 EDT
I'm trying to use Jumpstart to set up the disks as metadevices, and am
having no luck. I'm trying to do this on a Sun V120, with OpenBoot
4.0 and a pair of internal drives.
I've got the 9/04 Solaris set up, and can use it to jump systems, but
if I try to encapsulate the disks as metadevices using SVM, the
install bombs because (it appears) any metadevice operations after the
first one cause a segfault (and then the disks aren't "there" for the
install):
...snip a lot of package selection stuff, that shouldn't be relevant
here....
- Selecting all disks
- Configuring boot device
- Configuring SVM State Database Replica on (c0t0d0s7)
- Configuring SVM State Database Replica on (c0t1d0s7)
- Configuring overlap (c0t0d0s2)
- Configuring overlap (c0t1d0s2)
- Configuring SVM Mirror Volume on / (c0t0d0s0)
- Configuring SVM Mirror Volume on (c0t1d0s0)
- Configuring SVM Mirror Volume on swap (c0t0d0s1)
- Configuring SVM Mirror Volume on SWAP_MIRROR (c0t1d0s1)
- Configuring SVM Mirror Volume on /tmp (c0t0d0s3)
- Configuring SVM Mirror Volume on (c0t1d0s3)
- Configuring SVM Mirror Volume on /opt (c0t0d0s4)
- Configuring SVM Mirror Volume on (c0t1d0s4)
- Configuring SVM Mirror Volume on /var (c0t0d0s5)
- Configuring SVM Mirror Volume on (c0t1d0s5)
- Configuring SVM Mirror Volume on /usr (c0t0d0s6)
- Configuring SVM Mirror Volume on (c0t1d0s6)
Verifying disk configuration
- WARNING: Unused disk space (c0t0d0)
- WARNING: Unused disk space (c0t1d0)
Verifying space allocation
- Total software size: 2780.73 Mbytes
Preparing system for Solaris install
Configuring disk (c0t0d0)
- Creating Solaris disk label (VTOC)
Configuring disk (c0t1d0)
- Creating Solaris disk label (VTOC)
Creating and checking UFS file systems
- Creating / (c0t0d0s0)
- Creating /tmp (c0t0d0s3)
- Creating /opt (c0t0d0s4)
- Creating /var (c0t0d0s5)
- Creating /usr (c0t0d0s6)
Creating SVM Meta Devices
- Creating SVM State Replica on disk c0t0d0s7
- Creating SVM State Replica on disk c0t1d0s7
- metadb: waiting on /etc/lvm/lock
- metadb: Segmentation Fault
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d0 (/)
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d3 (swap)
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d6 (/tmp)
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d9 (/opt)
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d12 (/var)
- Segmentation Fault - core dumped
- Segmentation Fault - core dumped
- Creating SVM Mirror Volume d15 (/usr)
ERROR: Could not mount /usr (/dev/md/dsk/d15)
ERROR: Could not mount the configured file system(s)
ERROR: System installation failed
At this point, the metadb does have the first slice in there:
# metadb
flags first blk block count
a u 16 8192 /dev/dsk/c0t0d0s7
a u 8208 8192 /dev/dsk/c0t0d0s7
a u 16400 8192 /dev/dsk/c0t0d0s7
If I boot the machine into single-user mode off the network, then I
can by hand create the metadb with "metadb -a -f -c 3
/dev/dsk/c0t0d0s7", but then when I try to add the second disk slice
with "metadb -a -c 3 /dev/dsk/c0t1d0s7", it gives me another
segmentation fault error.
The disk layout I'm (trying) to work with is:
install_type initial_install
system_type standalone
partitioning explicit
filesys c0t0d0s2 all overlap
filesys c0t1d0s2 all overlap
filesys mirror c0t0d0s0 c0t1d0s0 1024 / logging
filesys mirror c0t0d0s1 c0t1d0s1 6144 swap
filesys mirror c0t0d0s3 c0t1d0s3 4096 /tmp
filesys mirror c0t0d0s4 c0t1d0s4 4096 /opt logging
filesys mirror c0t0d0s5 c0t1d0s5 4096 /var logging
filesys mirror c0t0d0s6 c0t1d0s6 4096 /usr logging
metadb c0t0d0s7 size 8192 count 3
metadb c0t1d0s7 size 8192 count 3
I've tried specifying the metadevice names, and also dropping all
references to the second disk, but nothing's really done the trick for
me. If I install "normally", and then encapsulate the disks, then it
works without problem.
Am I missing something? Google's turned up nothing, so I'm not sure
where to turn for this one. I can always just install, and then
encapsulate afterwards, but if I can remove that step, and just do it
as part of the base install, I'd be much happier.....
-Mike
-- Michael Steeves | Unix Network Administrator msteeves@eecs.tufts.edu | Tufts University Department of ECE and CS Phone: 617-627-2601 | 161 College Avenue FAX: 617-627-3220 (Dept. Fax)| Medford, MA 02155 _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:51 EDT