Mark Post wrote:
On Fri, May 4, 2007 at 2:00 PM, in message <[EMAIL PROTECTED]>, Matt
Gourley <[EMAIL PROTECTED]> wrote:
-snip-
2) If I add the LUN to the guestvol system through YaST and reboot, the
LUN information is lost. Obviously, this isn't good. :)
-snip-
Sounds like you need to re-run mkinitrd and zipl.
There's where I'm running into issues. I can't run mkinitrd and zipl
from the guestvol system, as it's seeing /sys and /boot as read-only. I
have added the following line to /etc/sysconfig/kernel on the basevol:
INITRD_MODULES="dasd_fba_mod zfcp"
and have run mkinitrd and zipl on the basevol. Without this, I would
not have been able to see the LUN.
When we setup the DASD beyond the 202 disk on the other guests, we had a
similar problem. The solution was to write a script to mount any
ext[23] filesystem in /etc/fstab that wasn't already mounted or
/guestvol, and put that in /etc/init.d/rc3.d between the system scripts
and the application scripts.
-Matt
--
Matt Gourley
Systems Administrator
Pennsylvania State University
Administrative Information Services - Infrastructure/Sysarc
Rm 25 Shields Bldg., University Park, PA 16802
(814) 865-8726
[EMAIL PROTECTED]
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
