Hello Mark,
the issue is solved.
We included information for SLES10 into autoyast.xml. There seems
to be a change at SLES 11. We had to remove all storage related modules form
. Now we simply add vmcp and vmur as modules to our initrd.
Kind regards,
Tobias Doerkes.
>>> On 7/9/2012 at 08:16 AM, Tobias Doerkes wrote:
-snip-
> I am now preparing a SLES11 SP2 autoyast profile for initial server
> installation using an LVM layout.
>
> /dev/disk/by-path/ccw-0.0.0201-part1 to /boot
> /dev/disk/by-path/ccw-0.0.0201-part2 is an lvm partition
> /dev/rootvg1/homelv
Hi all,
there was a thread in here in 2009 dealing with lvm2 initialisation on bootup:
http://www.mail-archive.com/linux-390@vm.marist.edu/msg52937.html
but we are running lvm2-2.02.84-3.25.5 now.
I am now preparing a SLES11 SP2 autoyast profile for initial server
installation using an LVM layou
: Tuesday, June 16, 2009 12:07
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Multipathing/LVM problem (was: FCP LUN multipathing /
filesystem problem)
It sounds as if you have a few other issues (I have sent you a private
message, feel free to follow that one if needed).
First you need to make sure that
It sounds as if you have a few other issues (I have sent you a private message,
feel free to follow that one if needed).
First you need to make sure that the following boot.* are set to run at boot up.
chkconfig boot.lvm on
chkconfig boot.multipath on
These need to be on as well, but I suspect
Deric,
Thanks for the response. I believe that is the issue, but I am unsure
how to correct the mess that I'm in.
I tried adjusting the lvm.conf, but because my vg is not on a
/dev/mapper/xxx device it is not recognized at boot. A pvscan shows
that the PV is /dev/dm-0. I added "a|/dev/dm-*
>>> On Tue, Jun 17, 2008 at 9:04 AM, in message
<[EMAIL PROTECTED]>, RPN01 <[EMAIL PROTECTED]> wrote:
-snip-
> This is the last step in adding DASD, and the one that I've forgotten way
> too many times. Given that it has to happen, my question is why YaST doesn't
> perform the mkinitrd and zipl c
On Behalf Of
CHAPLIN, JAMES (CTR)
Sent: Tuesday, June 17, 2008 9:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem. Lost VG info
Were you able to verify that the device is online?
If lscss is unavailable, go to the dev directory:
Determine the device number (say 204) either from an lsda
> online
James Chaplin
Systems Programmer, MVS, zVM & zLinux
Base Technologies, Inc
(703) 921-6220
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Walters, Gene P
Sent: Tuesday, June 17, 2008 9:15 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem.
10 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem. Lost VG info
Also note that the information necessary to recreate the LVM environment
should be stored in the first few blocks of any of the PV devices (I
think
there's actually about five copies there.) Use your favorite tool t
t: Re: LVM problem. Lost VG info
Have you all disks online ?
Issue command :
lscss
and check it.
After then you can try:
vgscan
vgchange -ay
Best regards,
Jakub Szefler
Administrator zOS/zVM
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Walters,
, 2008 2:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: LVM problem. Lost VG info
I'm already having a bad day. I took one of our Linux Instances down to add
more disk space to it. Everything went fine. I used Yast2 to add the new
volumes to the VG. Now when I IPL, it cant find the volume grou
I actually did mkinitrd and zipl and ipl'd, formatted and then did yast.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
RPN01
Sent: Tuesday, June 17, 2008 9:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem. Lost VG info
After adding th
]> wrote:
> Did you try a vgscan?
>
> James Chaplin
> Systems Programmer, MVS, zVM & zLinux
> Base Technologies, Inc
> (703) 921-6220
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Walters, Gene P
> Sent: Tu
UX-390@VM.MARIST.EDU
Subject: Re: LVM problem. Lost VG info
Did you try a vgscan?
James Chaplin
Systems Programmer, MVS, zVM & zLinux
Base Technologies, Inc
(703) 921-6220
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Walters, Gene P
Sent: Tuesday,
After adding the new DASD, did you run mkinitrd and zipl, to fold them into
the boot configuration? I think that on RedHat, you also have to add them to
the parm line in the zipl.conf file
This is the last step in adding DASD, and the one that I've forgotten way
too many times. Given that it h
Did you try a vgscan?
James Chaplin
Systems Programmer, MVS, zVM & zLinux
Base Technologies, Inc
(703) 921-6220
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Walters, Gene P
Sent: Tuesday, June 17, 2008 8:58 AM
To: LINUX-390@VM.MARIST.EDU
Subject:
I'm already having a bad day. I took one of our Linux Instances down to
add more disk space to it. Everything went fine. I used Yast2 to add
the new volumes to the VG. Now when I IPL, it cant find the volume
group.
I ran a PVSCAN, and it shows all my physical volumes are associated to
an unkno
It's so common that I did a share presentation on it:
http://www.linuxvm.org/Present/SHARE108/S9240jb.pdf
If you have any questions that aren't answered by that, let me know and I'll
make sure they make it into the next version.
--
Jay Brenneman
---
>>> On Fri, Mar 30, 2007 at 9:39 AM, in message
<[EMAIL PROTECTED]>,
Tim Hare <[EMAIL PROTECTED]> wrote:
> RPN01 <[EMAIL PROTECTED]> wrote on 03/05/2007 12:05:11 PM:
>
>> Did you run mkinitrd and zipl after adding the disk(s) and setting
them
> up?
>> If not, your system won*t see the disk(s) w
RPN01 <[EMAIL PROTECTED]> wrote on 03/05/2007 12:05:11 PM:
> Did you run mkinitrd and zipl after adding the disk(s) and setting them
up?
> If not, your system won¹t see the disk(s) when the system comes back up,
and
> you¹ll see the problem as one or more LVMs being corrupted.
>
> This is my on
d'origine-
De : Linux on 390 Port [mailto:[EMAIL PROTECTED]
Envoyé : lundi 5 mars 2007 18:05
À : LINUX-390@VM.MARIST.EDU
Objet : Re: LVM problem
Did you run mkinitrd and zipl after adding the disk(s) and setting them up? If
not, your system won¹t see the disk(s) when the system comes ba
erent."
> From: EXT / DUBOIS Laurent <[EMAIL PROTECTED]>
> Organization: S.N.C.F. French Railways
> Reply-To: Linux on 390 Port
> Date: Mon, 5 Mar 2007 18:02:07 +0100
> To:
> Conversation: LVM problem
> Subject: LVM problem
>
> Hi,
>
> I am running SUSE
Hi,
I am running SUSE LINUX Enterprise Server 9 (s390x) - Kernel 2.6.5-7.244-s390x
and I get some problem with LVM.
Under Yast2 I do Add Group (name test) and then I add a full pack disk 3390
After I do Add in order to create a Logical Volume named dubois , I format with
ext2 and mount it at /d
Linux on 390 Port wrote on 07.08.2006 02:52:45:
>
> Now ... if you need an IBM label, then you have to use either
> LDL or CDL. Non-partitioned disks will usually wipe out an IBM label
> as many of the filesystems get too close to the start of their space
> (partitioned or not). So when they'r
On Fri, 28 Jul 2006, Kreiter, Chuck wrote:
> The problem was the lack of a partition on the drive. I manually
> partitioned each one and was able to create the LVM.
Please specify, Chuck, if you were using /dev/dasdx1 or tried
just the /dev/dasdx form of the device name. The latter should
Of
Nix, Robert P.
Sent: Thursday, July 27, 2006 4:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES 10 LVM problem
Work-around: Start yast as "yast &", so that it runs in the background,
and leaves you with a command prompt. Activate and format the disks as
normal, but then dro
On 27-Jul-2006, at 16:25, Nix, Robert P. wrote:
Work-around: Start yast as "yast &", so that it runs in the
background, and leaves you with a command prompt.
This will only work if using the GUI version of YaST. If using the
CLI version (ncurses), just pop up a new terminal window to launch
t
, Chuck
Sent: Thursday, July 27, 2006 7:47 AM
To: LINUX-390@VM.MARIST.EDU
Subject: SLES 10 LVM problem
I'm attempting to create an LVM on SLES 10 (the recent GA DVD). I took
the following steps:
Activated 5 3390-9 devices
Formatted all 5 devices
Start LVM
Create volume group "system"
You won't get a lot of messages from YaST.
It would be easier to debug to use these commands :
pvcreate for initializing the PV - disks (once formatted and partitionned)
vgcreate for creating the VG
lvcreate for creating the LV
mkfs for formatting the LV
See the man page or the LVM howto ( http
I'm attempting to create an LVM on SLES 10 (the recent GA DVD). I took
the following steps:
Activated 5 3390-9 devices
Formatted all 5 devices
Start LVM
Create volume group "system" with 4M Physical Extent size.
Add 5 physical volumes to group "system"
Add logical volume 'test' with size=max and
Phil,
Run fdasd against them to create the partition and use the partition
name in the pvcreate command, eg. pvcreate /dev/dasdm1, and in the
vgcreate command.
Betsie
Phil Smith III wrote:
I'm trying to set up an LVM. I have 3 10MB disks defined at 8001, 8002, 8003;
they appear in /proc/da
I'm trying to set up an LVM. I have 3 10MB disks defined at 8001, 8002, 8003;
they appear in /proc/dasd/devices as:
8001(ECKD) at ( 94: 48) is dasdm : active at blocksize: 4096, 2520 blocks,
9 MB
8002(ECKD) at ( 94: 52) is dasdn : active at blocksize: 4096, 2520 blocks,
9 MB
8003(ECKD
ot;Post, Mark K"
<[EMAIL PROTECTED]To:
LINUX-390@VM.MARIST.EDU
m> cc:
Sent by: Linux on Subject: Re: LVM problem
390 Port
<[EMAIL PROTECTED]
--Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hugo
Rivera
Sent: Wednesday, March 09, 2005 5:54 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem
sing "sed" I could include the new devices (changing dasd=201-212 to
dasd=201-215) in /etc/zipl.
@VM.MARIST.EDU
Subject: Re: LVM problem
sing "sed" I could include the new devices (changing dasd=201-212 to
dasd=201-215) in /etc/zipl.conf, but still have the same errors at boot
time.
Is there some way to tell Linux "DO NOT ACTIVATE LVM"???
Thank you
Hugo Rivera
SSA II
County of Con
You can modify your /etc/fstab to not mount those volumes. That's what I
do.
-Original Message-
From: Hugo Rivera [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 09, 2005 4:54 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: LVM problem
sing "sed" I could include the new de
LINUX-390@VM.MARIST.EDU
<[EMAIL PROTECTED]cc:
com> Subject: Re: LVM problem
Sent by: Linux on
390 Port
<[EMAIL PROTECTED]
IST.
Hi , In that way o need to use x3270 console and sed command to change
the fstab file and reboot the machine . some like that
# sed 's/\/dev\/lvmdev/\#\/dev\/lvmdev/g' /etc/fstab > /etc/fstab.new
# mv /etc/fstab /etc/fstab.orig
# cp /etc/fstab.new /etc/fstab
reboot machine
Em Qua, 2005-03-09 C
I have run into similar problems many times. The Linux system stops
because it cannot find the proper files in /etc/fstab.
I usually boot my recovery system, mount the root file system, chroot to
it, change /etc/zipl.conf to add the missing DASD devices and then run
zipl. A reboot should be fine.
Hello list -
I'm having serious problems trying to fix my LVM configuration.
I just extended the Volume Group lvmdev in 10 G to add 5 G to logical volumes
vol2 and vol4 and everything was fine. I was able
to see the vols with the new sizes and also the data after mount them.
But, after reboot my l
pode me dizer quais foram os passo que tu usaste no lvm?
-Mensagem original-
De: Linux on 390 Port [mailto:[EMAIL PROTECTED] nome de Nilson
Vieira
Enviada em: terga-feira, 13 de julho de 2004 17:31
Para: [EMAIL PROTECTED]
Assunto: Re: LVM problem
yes
- Original Message -
From
Ok, what does
fdasd -p /dev/dasdbp
display?
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Nilson
Vieira
Sent: Tuesday, July 13, 2004 4:31 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM problem
yes
- Original Message -
From: "Post,
yes
- Original Message -
From: "Post, Mark K" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 13, 2004 2:12 PM
Subject: Re: LVM problem
> And does the device node in /dev exist? With the correct major/minor
> number? (254/13)
>
>
>
And does the device node in /dev exist? With the correct major/minor
number? (254/13)
Mark Post
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rich
Smrcina
Sent: Tuesday, July 13, 2004 11:42 AM
To: [EMAIL PROTECTED]
Subject: Re: LVM problem
Since
: 4) is dasdbn:active at blocksize: 4096, 601020 blocks,
> 2347 MB
> 0e91(ECKD) at (254: 8) is dasdbo:active at blocksize: 4096, 601020 blocks,
> 2347 MB
> 0e88(ECKD) at (254: 12) is dasdbp:active at blocksize: 4096, 601020 blocks,
> 2347 MB
> 0e8c(ECKD) at (254: 16) is dasdbq:activ
IL PROTECTED]>
Sent: Tuesday, July 13, 2004 10:51 AM
Subject: Re: LVM problem
Does dasdbp1 exist? Send the output from 'cat /dev/dasd/devices'.
On Tue, 2004-07-13 at 08:14, Nilson Vieira wrote:
> Hi All,
>
> I have LVM 0.9.1 installed on a suse 7.2 production Lpa
Does dasdbp1 exist? Send the output from 'cat /dev/dasd/devices'.
On Tue, 2004-07-13 at 08:14, Nilson Vieira wrote:
> Hi All,
>
> I have LVM 0.9.1 installed on a suse 7.2 production Lpar
>
> When i run vgscan it goes like that
>
> itapoa:/ora-backup # vgscan
> vgscan -- reading all phys
Hi All,
I have LVM 0.9.1 installed on a suse 7.2 production Lpar
When i run vgscan it goes like that
itapoa:/ora-backup # vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "discovg08"
vgscan -- found active volume group "discovg"
:
Thema: Re: Antwort: Re: LVM problem
[EMAIL
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 wh
An: [EMAIL PROTECTED]
Kopie:
: 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
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
On Tuesday 01 October 2002 05:48 pm, Geyer, Thomas L. wrote:
> Thanks for your speedy response. To answer your question yes, I created the
> filesystems but neglected to format.
That's what I meant by "making the filesystems." :-)
In any case, glad you got the problem solved.
--
---
: Tuesday, October 01, 2002 5:41 PM
To: [EMAIL PROTECTED]
Subject: Re: LVM Problem During Installation using Yast
On Tuesday 01 October 2002 05:26 pm, Geyer, Thomas L. wrote:
> When YAST tries to mount the filesystems I
> get the following mount error :
> An error occurred mounting
> -Original Message-
> From: Geyer, Thomas L.
> Sent: Tuesday, October 01, 2002 5:26 PM
> To: '[EMAIL PROTECTED]'
> Subject: LVM Problem During Installation using Yast
>
> I am attempting to install SLES7 in another instance. This time I want to
>
On Tuesday 01 October 2002 05:26 pm, Geyer, Thomas L. wrote:
> When YAST tries to mount the filesystems I
> get the following mount error :
> An error occurred mounting the file system of partition
> "/dev/dasda1"to the directory "/mnt:. Here is the error message of the
> 'mount' command:
I am attempting to install SLES7 in another instance. This time I want to
use LVM and create a volume group that contains /usr and /home. I am
following the procedure in the Redbook - Linux on zSeries and S/390: Systems
Management (SG24-6820) in section 3.2.2. I start the bootstrap program and
log
Sent: Thursday, February 21, 2002 9:46 AM
To: [EMAIL PROTECTED]
Subject: LVM Problem/Query
We added 1 2.3GB disk to the log. Vol. /dev/dali164/lvol1 using
the following commands:
dasdfmt -b 4096 -n 0201
pvcreate /dev/dasdd (is VM-disk 0201)
pvcreate dali164 /dev/dasdd
The vgdisplay show me
3:46 PM
> To: [EMAIL PROTECTED]
> Subject: LVM Problem/Query
>
>
> We added 1 2.3GB disk to the log. Vol. /dev/dali164/lvol1 using
> the following commands:
>
> dasdfmt -b 4096 -n 0201
> pvcreate /dev/dasdd (is VM-disk 0201)
> pvcreate dali164 /dev/dasdd
>
> The
We added 1 2.3GB disk to the log. Vol. /dev/dali164/lvol1 using
the following commands:
dasdfmt -b 4096 -n 0201
pvcreate /dev/dasdd (is VM-disk 0201)
pvcreate dali164 /dev/dasdd
The vgdisplay show me the new VG-Size 4.56GB (before: 2.3GB)
But the filesystem /FS/fs0164 was still 2.3 GB
Though i
Hello,
Is it possible to access LVM logical volume (or a whole volume group) from
another Linux instance?
Due to some modifications on my dasds I can't start one of the linux
clients, but I need the "lost" data.
Thanks,
Michal Sierakowski
PKO BP SA
Department of Technology
ul. Wolczynska 133
63 matches
Mail list logo
