Hej Mark,
On 13:04 Sat 15 Aug , Mark Post wrote:
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com
wrote:
In my case the system would not boot anymore because the second DASD was
still masked by cio-ignores and the kernel couldn't build the btrfs (no
support for
Hej Mark,
On 10:27 Sun 16 Aug , Mark Post wrote:
On 8/15/2015 at 07:35 PM, Frank M. Ramaekers framaek...@ailife.com
wrote:
I was looking how to do the initrd zipl, but got lost:
ls -l /etc/zipl.conf
ls: cannot access /etc/zipl.conf: No such file or directory
zipl -V
Using
Hej Frank,
On 18:35 Sat 15 Aug , Frank M. Ramaekers wrote:
Well, performed reinstall and got SLES 12 to us LVM, added a volume and
expanded the volume group:
--- Volume group ---
VG Name system
System ID
Formatlvm2
Metadata Areas2
On 12:29 Mon 17 Aug , Benjamin Block wrote:
Hej Mark,
On 13:04 Sat 15 Aug , Mark Post wrote:
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com
wrote:
In my case the system would not boot anymore because the second DASD was
still masked by cio-ignores and
@VM.MARIST.EDU
Subject: Re: Adding DASD to a btrfs
Just to follow up on that. I just gave it a try and that still doesn't cut it
completely. You still have to update the initrd of the kernel you want to
use, otherwise the system remains un-bootable.
Which means, if you use the feature, you have
On 8/15/2015 at 10:17 PM, Don Williams donbwms.foru...@gmail.com wrote:
What was the
reason, the VM designers chose VARY ON and DEATTACH CYL 0?
I would say for the same reason a lot of decisions got made, way back when.
Sharing DASD between disparate operating systems wasn't particularly
, August 17, 2015 8:42 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a btrfs
On 12:29 Mon 17 Aug , Benjamin Block wrote:
Hej Mark,
On 13:04 Sat 15 Aug , Mark Post wrote:
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com
wrote:
In my case the system
On 8/15/2015 at 07:35 PM, Frank M. Ramaekers framaek...@ailife.com
wrote:
I was looking how to do the initrd zipl, but got lost:
ls -l /etc/zipl.conf
ls: cannot access /etc/zipl.conf: No such file or directory
zipl -V
Using config file '/etc/zipl.conf'
Error: Config file
: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Sunday, August 16, 2015 11:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a btrfs
On 8/15/2015 at 07:35 PM, Frank M. Ramaekers framaek...@ailife.com
wrote:
I was looking how to do the initrd zipl
: Adding DASD to a btrfs
Hej Frank,
I am also relatively new to z Systems, so I may not know everything, sry for
that :)
On 11:10 Fri 14 Aug , Frank M. Ramaekers wrote:
Well, I'm not married to this (fresh) install, but I do want to be able to
expand the root fs when necessary. I'd
machine, whether mdisk or dedicated dasd.
Alan Altmark
Senior Managing Consultant
IBM Systems Lab Services
Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest ---
From:Neale Ferguson ne...@sinenomine.netTo:
LINUX-390@VM.MARIST.EDUDate:Sat, Aug 15, 2015 12:19 PMSubject:Re:
[LINUX
Volume labels are read at VARY ON and any time cylinder 0 is detached from a
virtual machine, whether mdisk or dedicated dasd.
Alan Altmark
Senior Managing Consultant
IBM Systems Lab Services
Neale Ferguson --- Re: [LINUX-390] Adding DASD to a guest ---
From:Neale Ferguson ne
DASD to a guest ---
From:Neale Ferguson ne...@sinenomine.netTo:
LINUX-390@VM.MARIST.EDUDate:Sat, Aug 15, 2015 12:19 PMSubject:Re:
[LINUX-390] Adding DASD to a guest
I thought vol1 labels were read at vary on time but that may have
changed to attach/detach. Try varying the volume off
But I seem to recall a change around VM/ESA that caused it to happen at
attach time.
Original message
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system
, 2015 at 1:39 PM Neale Ferguson ne...@sinenomine.net wrote:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here
cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system logged in as MAINT. When I q dasd free, I do not see these disks
listed as free
:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach
: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here is a clue to the problem, I think: I attach volumes 2108-210a to
system logged in as MAINT. When I q dasd free, I do not see these
disks
ne...@sinenomine.net
wrote:
Yes, you need to ATTACH rdev SYSTEM
Original message
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 13:32 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
Here
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote:
In my case the system would not boot anymore because the second DASD was
still masked by cio-ignores and the kernel couldn't build the btrfs (no
support for degraded raids). I have not found a solution that would
cover
On 8/14/2015 at 10:49 AM, Benjamin Block bbl...@linux.vnet.ibm.com wrote:
I have done the same thing on a test vm - adding a second DASD to a
existing root-btrfs filesystem. In short: be very cautious. The
btrfs-function works as you can find it in various help-texts, but the
problem is, you
But I seem to recall a change around VM/ESA that caused it to happen at
attach time.
Original message
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015 at 11:56 AM
Subject: [LINUX-390] Adding DASD to a guest
Any ideas why I'm seeing this? I went through the steps to format, label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted
HCPLNM108E LNX065 E153
From: Cameron Seay cws...@gmail.com
Date: 2015/08/15 11:56 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Adding DASD to a guest
Any ideas why I'm seeing this? I went through the steps to format, label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151
From: Mark Post mp...@suse.com
Date: 2015/08/15 12:31 (GMT-05:00)
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Adding DASD to a guest
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote:
Any ideas why I'm seeing this? I went through the steps to format, label
and attach
Any ideas why I'm seeing this? I went through the steps to format, label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not mounted
HCPLNM108E LNX065 E153 not linked; volid LNX365 not mounted
--
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote:
Any ideas why I'm seeing this? I went through the steps to format, label
and attach these to guest lnx065...
HCPLNM108E LNX065 E151 not linked; volid LNX165 not mounted
HCPLNM108E LNX065 E152 not linked; volid LNX265 not
I thought vol1 labels were read when to ATTACH dev TO SYSTEM. Once ATTACHed
to SYSTEM, then minidisk on that volume would be available to LINK to
guests.
On Sat, Aug 15, 2015 at 12:31 PM Mark Post mp...@suse.com wrote:
On 8/15/2015 at 11:56 AM, Cameron Seay cws...@gmail.com wrote:
Any ideas
Hej Frank,
On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote:
I'm new to both SLES (12 in my case) and btrfs. I just recently
installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't
see a way to combine the two into a single fs). I want to add the other
3390-9 to the btrfs
, 2015 9:49 AM
To: Frank M. Ramaekers
Cc: Linux on 390 Port
Subject: Re: Adding DASD to a btrfs
Hej Frank,
On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote:
I'm new to both SLES (12 in my case) and btrfs. I just recently
installed SLES 12 onto a 3390-9 (I had an additional 3390-9
Correction:
Bootloader support for /boot, allowing to boot from a Btrfs partition
Frank M. Ramaekers Jr.
-Original Message-
From: Frank M. Ramaekers
Sent: Friday, August 14, 2015 11:11 AM
To: 'Benjamin Block'
Cc: Linux on 390 Port
Subject: RE: Adding DASD to a btrfs
Well, I'm
AM
To: Frank M. Ramaekers
Cc: Linux on 390 Port
Subject: Re: Adding DASD to a btrfs
Hej Frank,
On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote:
I'm new to both SLES (12 in my case) and btrfs. I just recently
installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but
didn't see
: Friday, August 14, 2015 9:49 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a btrfs
Hej Frank,
On 09:08 Thu 13 Aug , Frank M. Ramaekers wrote:
I'm new to both SLES (12 in my case) and btrfs. I just recently
installed SLES 12 onto a 3390-9 (I had an additional 3390-9
I'm new to both SLES (12 in my case) and btrfs. I just recently
installed SLES 12 onto a 3390-9 (I had an additional 3390-9, but didn't
see a way to combine the two into a single fs). I want to add the other
3390-9 to the btrfs (/) for expansion purposes.
lsdasd
Bus-ID Status Name
on cc
390 Port
linux-...@vm.mar Subject
IST.EDU Adding DASD to a btrfs
@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
At which point are you getting that error?
If you do a fresh install then just add these dasds your virtual machine before
initializing install process (attach or better define minidisks) and let the
installator do the job.
Installator
On Tue, 11 Aug 2015 21:30:09 -0400 (EDT), Howard V. Hardiman wrote:
Okay.. Your help and advice is appreciated. I think I see the
picture better now. As a result, I am now starting a fresh install
to do so with LVM. I can create vg and lv's just fine (I think, yet
to test completely). But
Fair enough I have tried that list before with no response.
HH
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen
Powell
Sent: Wednesday, August 12, 2015 5:11 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
On Wed, 12 Aug 2015 17:37:29 -0400 (EDT), Howard V. Hardiman wrote:
Fair enough I have tried that list before with no response.
I'm sorry to hear that. But I'll be watching for it. If you post
this issue to debian-s...@lists.debian.org, you'll get at least one
response: mine.
--
.''`.
like normal?
HH
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen
Powell
Sent: Tuesday, August 11, 2015 8:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
On Tue, 11 Aug 2015 12:27:08 -0400 (EDT
Powiedziuk
Sent: Tuesday, August 11, 2015 12:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
It should be possible depending on what you did so far.
If your “/“ is on LVM then you should be able to add new dasd to it’s
volume group and extend the logical volume where
Subject: Re: Adding DASD to a Debian guest
On Fri, Aug 07, 2015 at 08:13:02AM -0500, Frank M. Ramaekers wrote:
I'd like to pick your brain on your Debian install. I've struggled,
the biggest obstacle was ZIPL installit appears that partition has
to be laid down just right (/ before any other
@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
Can you see them when you do
cat /proc/dasd/devices ?
If not than first bring them online (chccwdev -e 0.0.) and then check
again.
If they are there, than you are ready to do a low level format with dasdfmt
/dev/dasdX (/proc
?
HH
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz
Powiedziuk
Sent: Tuesday, August 11, 2015 12:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
It should be possible depending on what you did so far.
If your
[mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Stephen
Powell
Sent: Tuesday, August 11, 2015 8:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote:
Make sure that when you restart linux, these dasd
On Tue, 11 Aug 2015 12:27:08 -0400 (EDT), Grzegorz Powiedziuk wrote:
Make sure that when you restart linux, these dasd will automatically
show up in /proc/dasd/devices. Stephen suggested over here creating
these empty files in /etc/sysconfig/hardware - I don’t know about that.
I have never
help you can provide.
HH
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Grzegorz
Powiedziuk
Sent: Thursday, August 6, 2015 3:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding DASD to a Debian guest
Can you see them when you do
cat /proc/dasd
On Fri, Aug 07, 2015 at 08:13:02AM -0500, Frank M. Ramaekers wrote:
I'd like to pick your brain on your Debian install. I've struggled,
the biggest obstacle was ZIPL installit appears that partition has
to be laid down just right (/ before any other fs), for instance.
Had problems
To: LINUX-390@VM.MARIST.EDU
Subject: Adding DASD to a Debian guest
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees the
new dasd, but of course Debian can't see it until it's in a Linux filesystem.
We don't know how to format it while in Debian.
Any suggestions
On Thu, 06 Aug 2015 15:04:10 -0400 (EDT), Cameron Seay wrote:
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
Any suggestions?
All steps
in debian as far as I remember it was just a matter of adding a new dasd to
zipl.conf , running zipl and that’s it.
Gregory Powiedziuk
On Aug 6, 2015, at 3:17 PM, Mark Post mp...@suse.com wrote:
On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote:
I have attached 3 mod-9s to a
On 8/6/2015 at 03:04 PM, Cameron Seay cws...@gmail.com wrote:
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
The same as any other
Isn't dasdfmt, lsdasd, et al there? How did you install Debian? Are
the ibm driver tools installed?Linux should be able to see it as soon
as it's online. You may have to issue chccwdev -e for the disk if it
doesn't happen automatically. cat /proc/partitions should give you some
I have attached 3 mod-9s to a guest where Debian is the OS. Q DASD sees
the new dasd, but of course Debian can't see it until it's in a Linux
filesystem. We don't know how to format it while in Debian.
Any suggestions?
--
For
Can you see them when you do
cat /proc/dasd/devices ?
If not than first bring them online (chccwdev -e 0.0.) and then check
again.
If they are there, than you are ready to do a low level format with dasdfmt
/dev/dasdX (/proc/dasd/devices will tell you which dasdX is that).
After
All:
I got this with my DIRM RLDE command while trying to add a MOD-9 volume to
a guest. Help. Cameron
DVHREQ2288I Your RLDEXTN request for MAINT at * has been
accepted.
DVHILZ3510I Starting DVHINITL with directory: USER DIRECT
E
DVHILZ3510I DVHINITL Parms: BLDMONO BLDDASD
BLDLINK
If you didn't mistype -- then I would guess 3309-09 should be 3390-09 ?
Scott Rohling
On Tue, Aug 12, 2014 at 4:17 PM, Cameron Seay cws...@gmail.com wrote:
All:
I got this with my DIRM RLDE command while trying to add a MOD-9 volume to
a guest. Help. Cameron
DVHREQ2288I Your RLDEXTN
I hit enter instead of starting new paragraph: In EXTENT CONTROL
:REGIONS - I would guess you defined LNX448 as device type 3309-09 by
mistake -- and DIRMAINT is complaining he doesn't know about such a type..
so correct this record in EXTENT CONTROL and then do the DIRM RLDE..
Scott Rohling
-390@vm.marist.edu wrote on 08/12/2014 04:17:22
PM:
From: Cameron Seay cws...@gmail.com
To: LINUX-390@vm.marist.edu
Date: 08/12/2014 04:19 PM
Subject: Error code when adding DASD
Sent by: Linux on 390 Port LINUX-390@vm.marist.edu
All:
I got this with my DIRM RLDE command while trying
: Error code when adding DASD
Sent by: Linux on 390 Port LINUX-390@vm.marist.edu
All:
I got this with my DIRM RLDE command while trying to add a MOD-9 volume
to
a guest. Help. Cameron
DVHREQ2288I Your RLDEXTN request for MAINT at * has been
accepted.
DVHILZ3510I Starting
On 7/6/2014 at 07:24 PM, Cameron Seay cws...@gmail.com wrote:
On x86 LVM is done
during the install. I have not figured out a way to do it during install
with Linux on z.
I seem to recall seeing in one of your previous emails that you're running
SLES11. If so, the Deployment Guide talks
With SLES 11, during the install you have the option of specifying a
display type of VNC and a VNC password. Once you receive a message
indicating something to the effect ³You can connect to nnn.nnn.nnn.nnn,
display:1 now with vncviewer Or use a Java capable browser on
On 7/7/2014 at 03:02 PM, Ted Allen ted.al...@wellsfargo.com wrote:
With SLES 11, during the install you have the option of specifying a
display type of VNC and a VNC password. Once you receive a message
indicating something to the effect *You can connect to nnn.nnn.nnn.nnn,
display:1 now
Can I add a DASD volume to an existing partition? I am using MOD-9s, and
for example I would like to add one or more to the /opt partition. Or
would it just be better to use LVM?
Thanks
--
For LINUX-390 subscribe / signoff /
The only way to do that is LVM (or something similar).
On 07/06/2014 03:16 PM, Cameron Seay wrote:
Can I add a DASD volume to an existing partition? I am using MOD-9s, and
for example I would like to add one or more to the /opt partition. Or
would it just be better to use LVM?
Thanks
Yeahh... I figured I could not get around LVM. On x86 LVM is done
during the install. I have not figured out a way to do it during install
with Linux on z. Well, I gotta do it sooner or later. Thanks, Rich.
On Sun, Jul 6, 2014 at 3:40 PM, Rich Smrcina r...@velocitysoftware.com
wrote:
I haven't been able to figure out how to do get it started after the install.
At that
point it's a combination of command line and YaST.
pvcreate /dev/dasdx1 /dev/dasdy1
(or whatever your fresh partitions are called)
vgcreate opt /dev/dasdx1 /dev/dasdy1
(again, your partitions here)
Then the
...@us.ibm.com (IBM business)
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
From: Cameron Seay cws...@gmail.com
To: LINUX-390@vm.marist.edu,
Date: 07/06/2014 04:40 PM
Subject:Re: Adding DASD to a partition
Sent by:Linux on 390 Port LINUX-390
Create LV for /
Done
Chuck Tribolet
trib...@us.ibm.com (IBM business)
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
From: Cameron Seay cws...@gmail.com
To: LINUX-390@vm.marist.edu,
Date: 07/06/2014 04:40 PM
Subject:Re: Adding DASD
://www.almaden.ibm.com/cs/people/triblet
From: Mauro Souza thoriu...@gmail.com
To: LINUX-390@vm.marist.edu,
Date: 07/06/2014 08:06 PM
Subject:Re: Adding DASD to a partition
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu
I don't like to have / on LVM. It makes things very difficult
to
Linux on 390 Port LINUX-390@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: sles11 - adding dasd yast problem
On 1/8/2010 at 07:52 AM, Samir Reddahi samir.redd...@securex.be
wrote:
-snip-
You can also add an options dasd_mod dasd= line to the
/etc/modprobe.conf.local with all
On 1/11/2010 at 05:25 AM, Samir Reddahi samir.redd...@securex.be wrote:
Hi Mark,
Do you have an idea in what cases this wouldn't work? This method in
combination with the default dasd udev rules seems to be working for me in
SLES11.
Not really. I just know that the default rules in
- adding dasd yast problem
I have just finished installing Sles 11, and now I need to add two
mini-disks. The first is read only, the second is read-write. I tried
running mkinitrd zipl like I would for sles10, but it doesn't seem to
be working. Mkinitrd is only writing 6 or 8 lines
On 1/8/2010 at 07:52 AM, Samir Reddahi samir.redd...@securex.be wrote:
-snip-
You can also add an options dasd_mod dasd= line to the
/etc/modprobe.conf.local with all the dasd devices you want to get online
after IPL. After that you run mkinitrd en zipl.
for example:
options dasd_mod
mind.
--- On Thu, 1/7/10, Sue Sivets ssiv...@fdrinnovation.com wrote:
From: Sue Sivets ssiv...@fdrinnovation.com
Subject: sles11 - adding dasd yast problem
To: LINUX-390@VM.MARIST.EDU
Date: Thursday, January 7, 2010, 4:18 AM
I have just finished installing Sles
11, and now I need to add two
On 1/8/2010 at 04:41 PM, Sue Sivets ssiv...@fdrinnovation.com wrote:
-snip-
*suse11:~ #* yast2
Xlib: extension RANDR missing on display localhost:10.0.
The program 'y2controlcenter-gnome' received an X Window System error.
This probably reflects a bug in the program.
The error was
of crossing my mind.
--- On Thu, 1/7/10, Sue Sivets ssiv...@fdrinnovation.com wrote:
From: Sue Sivets ssiv...@fdrinnovation.com
Subject: sles11 - adding dasd yast problem
To: LINUX-390@VM.MARIST.EDU
Date: Thursday, January 7, 2010, 4:18 AM
I have just finished installing Sles
11, and now I need
-
|From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
|Sue Sivets
|Sent: Wednesday, January 06, 2010 9:18 PM
|To: LINUX-390@VM.MARIST.EDU
|Subject: sles11 - adding dasd yast problem
|
|I have just finished installing Sles 11, and now I need to add two
|mini-disks. The first is read
: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
||Sue Sivets
||Sent: Wednesday, January 06, 2010 9:18 PM
||To: LINUX-390@VM.MARIST.EDU
||Subject: sles11 - adding dasd yast problem
||
||I have just finished installing Sles 11, and now I need to add two
||mini-disks. The first
On 1/6/2010 at 10:18 PM, Sue Sivets ssiv...@fdrinnovation.com wrote:
-snip-
Problem #2 - When I try to run yast2, I get an error message that Xlib:
extension RANDR missing on display localhost:10.0 along with a bunch
of other messages.
That is not an error message, but an informational one.
: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
||Sue Sivets
||Sent: Wednesday, January 06, 2010 9:18 PM
||To: LINUX-390@VM.MARIST.EDU
||Subject: sles11 - adding dasd yast problem
||
||I have just finished installing Sles 11, and now I need to add two
||mini-disks. The first
I have just finished installing Sles 11, and now I need to add two
mini-disks. The first is read only, the second is read-write. I tried
running mkinitrd zipl like I would for sles10, but it doesn't seem to
be working. Mkinitrd is only writing 6 or 8 lines to the console (it
writes almost a
Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Sue Sivets
Sent: Wednesday, January 06, 2010 7:18 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] sles11 - adding dasd yast problem
I have just finished installing Sles 11, and now I need to add two
mini-disks
/09, Mark Post mp...@novell.com wrote:
From: Mark Post mp...@novell.com
Subject: Re: adding DASD on SUSE
To: LINUX-390@VM.MARIST.EDU
Date: Friday, November 13, 2009, 11:01 PM
On 11/13/2009 at
4:41 PM, Mark Ver mark...@us.ibm.com
wrote:
What I was really interested in was the Linux side
-...@vm.marist.edu] On Behalf Of Marian
Gasparovic
Sent: den 20 november 2009 11:26
To: LINUX-390@VM.MARIST.EDU
Subject: Re: adding DASD on SUSE
Mark,
as dasd= parm in zipl.conf is not used now, how can I check which DASDs were
supposed to be online ?
Thank you
===
Marian Gasparovic
.
--- On Fri, 11/20/09, Agblad Tore tore.agb...@volvo.com wrote:
From: Agblad Tore tore.agb...@volvo.com
Subject: Re: adding DASD on SUSE
To: LINUX-390@VM.MARIST.EDU
Date: Friday, November 20, 2009, 11:40 AM
sudo /sbin/lsdasd to se what
dasd is online
su - (just for simplicity)
lsdasd
On Fri, Nov 20, 2009 at 12:02 PM, Marian Gasparovic mar...@yahoo.com wrote:
lsdasd shows disks that are online. My question is how ot find which disks
were supposed to be online, in other words, which disks were configured by
dasd_configure to be online on the next boot.
Say you have 20
than 11), boot.local,
initrd, ...
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Marian Gasparovic
Sent: Friday, November 20, 2009 6:02 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: adding DASD on SUSE
Tore,
lsdasd shows disks
On 11/20/2009 at 5:26 AM, Marian Gasparovic mar...@yahoo.com wrote:
Mark,
as dasd= parm in zipl.conf is not used now, how can I check which DASDs were
supposed to be online ?
Look in /etc/sysconfig/hardware/ for hwcfg files for DASD.
Mark Post
Gasparovic
===
The mere thought hadn't even begun to speculate about the merest
possibility of crossing my mind.
--- On Fri, 11/20/09, Agblad Tore tore.agb...@volvo.com wrote:
From: Agblad Tore tore.agb...@volvo.com
Subject: Re: adding DASD on SUSE
To: LINUX-390
about the merest
possibility of crossing my mind.
--- On Fri, 11/20/09, Mark Post mp...@novell.com wrote:
From: Mark Post mp...@novell.com
Subject: Re: adding DASD on SUSE
To: LINUX-390@VM.MARIST.EDU
Date: Friday, November 20, 2009, 4:15 PM
On 11/20/2009 at
5:26 AM, Marian Gasparovic mar
On 11/20/2009 at 10:34 AM, Marian Gasparovic mar...@yahoo.com wrote:
Sorry, I was talking about SLES 11 which does not support dasd= parameter and
does not use hwcfg files.
Oh. In that case, look in /etc/udev/rules.d/ for 51-dasd-*.rules files.
Mark Post
...@novell.com
Subject: Re: adding DASD on SUSE
To: LINUX-390@VM.MARIST.EDU
Date: Friday, November 20, 2009, 4:38 PM
On 11/20/2009 at 10:34
AM, Marian Gasparovic mar...@yahoo.com
wrote:
Sorry, I was talking about SLES 11 which does not
support dasd= parameter and
does not use hwcfg files
Mark,
Like were most people ...
I like this one:
- or add a dasd=dasd-list in their kernel parameters
because then you can go to /etc/zipl.conf to see which disks (or disks and
slots) the system is supposed to have. And if you do leave slots open,
you can add DASD more easily.
Mike
What I was really interested in was the Linux side configuration to add the
disk permanently so that it would be online during boot up.
Like were most people ...
- just running a big script calling dasd_configure as Mark Post had
suggested
- or do most just do chccwdev and then run mkinitrd and
On 11/13/2009 at 4:41 PM, Mark Ver mark...@us.ibm.com wrote:
What I was really interested in was the Linux side configuration to add the
disk permanently so that it would be online during boot up.
Like were most people ...
- just running a big script calling dasd_configure as Mark Post
Add the disk to the directory
link the disk, format and convert to linux format
detach the disk
use secuser to linux server to link the disk and bring it online.
That assums that you have root logged on the console. I do.
Wrap it all up in an exec and you can do as many as you want.
You could also
Just out of curiosity, since SLES has many different ways to let you add
DASD, what method have most folks been using to add a lot of DASD at once
(like say 40 to 80 volumes) ?
Thanks,
- Mark Ver
office: Building 710 / Room 2-RF-10
phone: (845) 435-7794 [tie 8 295-7794]
On 11/11/2009 at 4:13 PM, Mark Ver mark...@us.ibm.com wrote:
Just out of curiosity, since SLES has many different ways to let you add
DASD, what method have most folks been using to add a lot of DASD at once
(like say 40 to 80 volumes) ?
If you're asking this because you want to script it,
1 - 100 of 257 matches
Mail list logo
