Than you for anwering, Stefan.
No, as far as I understood one of my zLinux-staff colleagues his boot
parameters
mark dasd-device addresses as ???? ('all will be sensed and taken' ...).
After formating the phys. volumes, defining LVM's and appropr. group via
Yast we shutdown
and reboot SLES9. And then does not come up properly. I can only logon via
virt. 3270-console and replace /etc/fstab with an older version without LVM
... :-(
But we can try the method you proposed and I'll keep you informed about the
results
(i.e. screenshots).
ciao Lutz
-------------------------------------------------------------------------
Lutz Hamann
BETA Systems Software AG
z/OS System Engineering
-------------------------------------------------------------------------
Stefan Bader
<[EMAIL PROTECTED]
ibm.com> To
Sent by: Linux on [email protected]
390 Port cc
<[EMAIL PROTECTED]
IST.EDU> Subject
Re: DS8000 usage for SLES9 guest
18.07.2005 18:03
Please respond to
Linux on 390 Port
<[EMAIL PROTECTED]
IST.EDU>
Hi,
Linux on 390 Port <[email protected]> wrote on 15.07.2005 16:44:39:
>
> But up to now we run into problems defining LVM2-groups including these
> large Mdisks. After definition SLES9-guest comes not up properly,
> only in S-mode (maintenance).
>
There shouldn't be a problem with the size of the mdisks in lvm2. Are the
DASDs included in the range of devices that are set online after boot? Did
mkinitrd run and add the lvm2 commands to the initrd?
Maybe you could post the boot messages...
Regards,
Stefan
----------------------------------------------------------------------
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
