Hi Listers,
After a reboot not all dasd is online and not all dasd is available for Oracle.
I guess it has to do with udev but I can't find the logic behind it.
We run a guest on SUSE 11 SP1, Oracle 11. Minidisks 213-285 are in use for
Oracle ASM.
The udev rule for disk 213 looks like:
#
Yes, the dasd is online and the minidisk is available on the guest. So
chccwdev -e 213 has put it online and then we could move on with it. We had
to rename the VM guest name and next started the guest again. So basically the
guest was already running and got a reboot.
Yes multiple LPARs,
I don't know if this is a problem with SuSE, but in RedHat, I usually do
this to myself by not remembering to put a disk into modprobe.conf.
If the disk is offline during the boot, chances are that it has nothing to
do with udev, and much more to do with the dasd driver not seeing the device
On 2/7/2012 at 01:27 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net
wrote:
After reboot all DASD is online except 213.
I have no idea what might be causing this, but perhaps this might stop the
problem. If you want to try to document the problem and open a service request
about it,
Do you need to run 'mkinitrd' with the new modprobe info.
nix.rob...@mayo.edu
Sent by: LINUX-390@VM.MARIST.EDU
02/07/2012 02:57 PM
Please respond to
LINUX-390@VM.MARIST.EDU
To
LINUX-390@VM.MARIST.EDU
cc
Subject
Re: Missing DASD after reboot
I don't know if this is a problem with
Edit modprobe.conf, mkinitrd, zipl. That's the pattern I use. It needs to be
available when the driver gets loaded, which, I think, is before the real
filesystem is available (which makes sense).
We have a script that re-reruns mkinitrd for each of the initrds that exist
on /boot, so everything
Hi Rob,
No, it's zVM 5.4, so this apar is not the issue.
In the mean time I have formatted the DASD but that was done on SLES10. Also
the fdasd had to be on SLES10. Next the pvcreate on SLES11 still fails.
So for some reason I can't use the new DASD on this SLES11 machine while I
could use
As far as I know the modprobe doesn't need to be changed. The DASD module is
loaded, all except one minidisk is found.
When we started with SLES11 we had (still) the old workinstruction of putting
the DASD into zipl.conf. I had found when more disks were added that they
should have been added
It works for me but. . . .Please double check this on a test system first.
vi /etc/modprobe.conf
cd /boot/; mv -v initrd-$(uname -r).img initrd-$(uname -r).img.old
cd /boot/;mkinitrd -v initrd-$(uname -r).img $(uname -r)
zipl -V
Emmett
nix.rob...@mayo.edu
Sent by: LINUX-390@VM.MARIST.EDU
On Tue, 7 Feb 2012 15:02:26 -0500, Emmett O'Grady ogra...@mbusa.com
wrote:
Do you need to run 'mkinitrd' with the new modprobe info.
Yes. Your modprobe.conf-derived behavior in the initrd is only refreshed
if you re-mkinitrd it.
If you ever want/need to check what's in the initrd you can do
On 2/7/2012 at 03:46 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net
wrote:
When we started with SLES11 we had (still) the old workinstruction of putting
the DASD into zipl.conf. I had found when more disks were added that they
should have been added in the /etc/udev/rules.d/ directory
Have you manually checked to see if the DASD is online? i.e. QUERY DASD volid
or QUERY dasd_addr
If they are not online, check your SYSTEM CONFIG file to be sure they either
are not coded as OFFLINE or use an ONLINE statement to put them on line at IPL.
If they are online check again to be
On 2/7/2012 at 03:50 PM, van Sleeuwen, Berry berry.vansleeu...@atos.net
wrote:
Do I understand it correctly that dasd_configure sets disks online or
offline and creates or deletes an entry in /etc/udev/rules.d/? Does it do
anything more?
No, that's all it does. It can also flag the
13 matches
Mail list logo
