Brad, this can be done. I don't remember the exact procedure (since we built one and cloned the rest quite a while ago), but an ASv4 install using the text based anaconda allowed this, plus skipping default swap build (with a warning). My two volume (3390-9) model system consists of a 100M /boot on /dev/dasdl1, then /dev/dasdl2 has PV along with /dev/dasdm1:
[EMAIL PROTECTED] ~]# df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup00-LogVol00 14G 3.1G 9.7G 24% / /dev/dasdl1 97M 21M 72M 22% /boot ----------------------------------------------------------- [EMAIL PROTECTED] ~]# pvdisplay --- Physical volume --- PV Name /dev/dasdm1 VG Name VolGroup00 PV Size 6.88 GB / not usable 2.41 MB Allocatable yes (but full) PE Size (KByte) 32768 Total PE 220 Free PE 0 Allocated PE 220 PV UUID 6V2hVT-BGXQ-MN53-XLJg-cmDN-QUJ6-jszkYf --- Physical volume --- PV Name /dev/dasdl2 VG Name VolGroup00 PV Size 6.78 GB / not usable 30.42 MB Allocatable yes PE Size (KByte) 32768 Total PE 216 Free PE 2 Allocated PE 214 PV UUID 1y67zi-nS56-tisg-CB7n-2Aul-Eg23-0wfpwb ---------------------------------------------------------------- [EMAIL PROTECTED] ~]# vgdisplay --- Volume group --- VG Name VolGroup00 System ID Format lvm2 Metadata Areas 2 Metadata Sequence No 2 VG Access read/write VG Status resizable MAX LV 0 Cur LV 1 Open LV 1 Max PV 0 Cur PV 2 Act PV 2 VG Size 13.62 GB PE Size 32.00 MB Total PE 436 Alloc PE / Size 434 / 13.56 GB Free PE / Size 2 / 64.00 MB VG UUID 0k7UXY-OvjY-CrwH-9y6z-J6gp-7SZ0-n5S5G9 ----------------------------------------------------------------- Swap was built after the fact using VDISK with a backup disk: [EMAIL PROTECTED] ~]# swapon -s Filename Type Size Used Priority /dev/dasde partition 32772 0 9 /dev/dasdf partition 32772 0 8 /dev/dasdg partition 32772 0 7 /dev/dasdh partition 32772 0 6 /dev/dasdi partition 65540 0 5 /dev/dasdj partition 65540 0 4 /dev/dasdk1 partition 7211416 0 1 --------------------------------------------------------------------------- [EMAIL PROTECTED] ~]# cat /proc/dasd/devices 0.0.0100(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 1802880 blocks, 7042 MB 0.0.0101(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 1802880 blocks, 7042 MB 0.0.0102(ECKD) at ( 94: 8) is dasdc : active at blocksize: 4096, 1802880 blocks, 7042 MB 0.0.0103(ECKD) at ( 94: 12) is dasdd : active at blocksize: 4096, 131400 blocks, 513 MB 0.0.0104(FBA ) at ( 94: 16) is dasde : active at blocksize: 512, 65560 blocks, 32 MB 0.0.0105(FBA ) at ( 94: 20) is dasdf : active at blocksize: 512, 65560 blocks, 32 MB 0.0.0106(FBA ) at ( 94: 24) is dasdg : active at blocksize: 512, 65560 blocks, 32 MB 0.0.0107(FBA ) at ( 94: 28) is dasdh : active at blocksize: 512, 65560 blocks, 32 MB 0.0.0108(FBA ) at ( 94: 32) is dasdi : active at blocksize: 512, 131096 blocks, 64 MB 0.0.0109(FBA ) at ( 94: 36) is dasdj : active at blocksize: 512, 131096 blocks, 64 MB 0.0.0200(ECKD) at ( 94: 40) is dasdk : active at blocksize: 4096, 1802880 blocks, 7042 MB 0.0.0201(ECKD) at ( 94: 44) is dasdl : active at blocksize: 4096, 1802880 blocks, 7042 MB 0.0.0202(ECKD) at ( 94: 48) is dasdm : active at blocksize: 4096, 1802880 blocks, 7042 MB => FYI, the 100-104 MDISK's (RO shared libs, iso's, etc.) & 104-109 VDISK's, 200 swap disk -- [EMAIL PROTECTED] ITS/CS Network Systems Programmer State of North Carolina Office of Information Technology Services ----- NOTICE: E-mail correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized State officials. ----- -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Tuesday, April 08, 2008 10:06 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What is a good generic disk layout? Hi all, Just a followup question (Mike and I are working together on this): We're considering this layout due to some difficulty we had in the SLES installer. Ideally, we'd like a 3338 cylinder 100 disk with /boot (ext3 filesystem) and the remaining space used for an LVM volume, so 2 partitions total. However, when we create the /boot ext3 partition, the LVM button doesn't allow us to use dasda any longer for a Volume Group. If we take off /boot, we can use dasda, but since /boot can't be on the LVM this won't work either. It's almost like once you put an ext3 filesystem on dasda, you can no longer use it for LVM. Has anyone run into this situation before? If so, is there a way to put 2 partitions (1 ext3, 1 LVM PV) on dasda during install? Thanks, -Brad ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390