Hi Thomas, this may be unrelated but I can share some hard earned experience with you. I ran into problems when adding a new DASD that had been CMS DDR "cloned" from a DASD that already contained PV/VG information. Because the LVM timestamps etc on the new DASD are identical (due to the cloning) the whole of the VG is ignored (not just the new DASD). Just make sure that any new DASD you add have been low level formatted and re-partitioned before adding them to your system.
Ciao Mark -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Emde Sent: 19 December 2002 07:17 To: [EMAIL PROTECTED] Subject: Antwort: Re: LVM problem Hi, it looks as follows when it's working: dasd=400,410,440 root=/dev/dasda1 noinitrd ctc=noauto vmhalt="M OPERATOR LINUX DOWN" vmpoff="M OPERATOR LINUX DOWN" and like this when not: dasd=400,410,440,450 root=/dev/dasda1 noinitrd ctc=noauto vmhalt="M OPERATOR LINUX DOWN" vmpoff="M OPERATOR LINUX DOWN" 410 and 440 are the pv's which I put together in my vg. best regards, Thomas An: [EMAIL PROTECTED] Kopie: Thema: Re: LVM problem [EMAIL PROTECTED] DU Received : 2002-12-18 21:56 Bitte antworten an Linux on 390 Port Thomas, What does your parmfile look like when it works, and what does your parmfile look like when it fails? Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Emde Sent: Wednesday, December 18, 2002 10:05 AM To: [EMAIL PROTECTED] Subject: LVM problem Hi, I use SuSE Linux/390 7 (2.2.16, quite old I know). I had two 3390 disks put together in a volume group and several logical volumes running. I added a third 3390 disk to the linux (VM minidisk and added to parmfile, ran silo etc). During reboot vgscan reports that no volume groups can be found and after that of course the logical volumes are not existent. When I remove the new disk from my parmfile the lvm devices are found again...Any hint or help would be greatly appreciated. mit freundlichen Grüßen/with best regards Thomas =
