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 gets updated for each of the options in the zipl
Robert P. Nix Mayo Foundation .~.
RO-OC-1-18 200 First Street SW /V\
507-284-0844 Rochester, MN 55905 /( )\
"In theory, theory and practice are the same, but
in practice, theory and practice are different."
> Do you need to run 'mkinitrd' with the new modprobe info.
> Nix.Robert@mayo... >
> Re: Missing DASD after reboot
> 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
> because it hasn't been told to scan that address.