Did you define the DASDs as 'unsupported' in z/VM?
z/VM imagining the device to be supported by itself
prevents it from allowing a SetPathGroupID.
Best Regards
Holger Smolinski
--
Dr. Holger Smolinski, Tech. Planning (Storage I/O) for Linux on zSeries
IBM Deutschland Entwicklung GmbH,Sch�naicher Str. 220, 71032 B�blingen
FAX: +49-7031-16-3456, Tel. +49-7031-16-4652
|--------+----------------------------------->
| | "Ferguson, Neale" |
| | <Neale.Ferguson@SoftwareA|
| | G-USA.com> |
| | Sent by: Linux on 390 |
| | Port |
| | <[EMAIL PROTECTED]>|
| | |
| | |
| | 29.01.02 15:44 |
| | Please respond to Linux |
| | on 390 Port |
| | |
|--------+----------------------------------->
>-----------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: dedicate DASD "not operational" under z/VM 4.1
|
|
|
|
|
>-----------------------------------------------------------------------------------------------------------|
What does a query of the real devices show? What does the
CP directory entry of the Linux guest look like?
> -----Original Message-----
> Hi,
> We installed Linux under z/VM 4.1 which is upgraded
> from VM 2.4. Yesterday we restart the VM include all
> related hardware power off/power on because of
> maintainence reason (just restart, not change in
> system), but after that we cannot start the linux
> servers properly. Now Linux can only detect the
> minidisk but not dedicate volumes any more.
> The System log is:
>
> Ready; T=0.01/0.01 09:06:08
> i 100
> Linux version 2.2.19 ([EMAIL PROTECTED]) (gcc
> version 2.95.2.1 19991024 (release)) #1 SMP Thu May 24
> 12:43:49 PDT 2001
> Command line is: root=/dev/dasda1 ro noinitrd
> dasd=100,200,1729-172b,119
