Bernard Wu wrote:
The adresses are real addresses. Also, I am using a mixture of both mini disks and dedicates. The LVM's ( 2500-2504 ) are dedicated and the others are mini-disks.DASD 2061 CP SYSTEM VMD001 2 . . DASD 2500 ATTACHED TO LNXCAPD 2500 R/W 0X2500 DASD 2501 ATTACHED TO LNXCAPD 2501 R/W 0X2501 DASD 2502 ATTACHED TO LNXCAPD 2502 R/W 0X2502 DASD 2503 ATTACHED TO LNXCAPD 2503 R/W 0X2503 DASD 2504 ATTACHED TO LNXCAPD 2504 R/W 0X2504
Linux does not need to know about the real device numbers -- it sees only the virtual device numbers. The fact that you've DEDICATEd the DASDs with the same virtual device number as it's real device number is probably helping to confuse you. ;) In the directory for your LNXCAPD guest, the minidisk you have defined on real DASD 2061 will have a virtual device number. This is the number that must appear in the "dasd=" line. It does not need to be the same number as the real device number of the host DASD (and should not really be: after all, the minidisk can reside on any suitable DASD). As Mike and Carsten both indicated, the order of numbers in the "dasd=" line will determine which DASD shows up as dasda, dasdb, dasdc, etc. <rant type=minor> If the installer had added the dasd parameter line it used to the zipl.conf it created, you might have had some help toward knowing what was needed. The dasd parameter "missing" from zipl.conf has caught me out on a couple of occasions. After install the system boots fine (the installer having built the initrd/boottext correctly), but the first time you run zipl (say, for a kernel update) stops the machine from booting. When the dasd parameter is not provided the driver senses all DASD, and when you use the de-facto standard of Linux disks starting at 200 your CMS disks (191 and friends) pop in ahead and b0rk up your DASD naming... </rant> If you have moved part of your system (/usr, /var, etc) into the LVM, you will need to run mkinitrd to ensure that the LVM activation commands are added to the initrd. This will make sure that all required filesystems are available for the boot to complete. Cheers, Vic Cross ---------------------------------------------------------------------- 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
