This nailed it. I ran the mkinitrd command tailored to my environment,
ran zipl, and IPL'd. /dev/sda mounted on boot.
Big thanks.
-Matt
P David Schaub wrote:
Matt Gourley wrote:
I've run into an interesting issue with SLES 9 64-bit and zfcp and was
hoping someone here had an idea to fi
It seems that your boot disks are eckd and you have the fcp devices mounted
during the startup process rather than boot. You said the zfcp driver was being
loaded so I'm not sure yuo need the fcp stuff there right at boot time. Does
syslog show any problems/warnings?
If you had needed the fcp
Yeah. Probably should have mentioned that. :)
Thanks,
-Matt
Neale Ferguson wrote:
Silly question but your /etc/fstab has an entry for that device?
-Original Message-
I've got a 50G FCP LUN on device F100 attached to a VM named LINUX2. If
I IPL SLES on LINUX2, zfcp discovers 0xF100
Matt Gourley wrote:
> I've run into an interesting issue with SLES 9 64-bit and zfcp and was
> hoping someone here had an idea to fix it. I've checked the archives
> but saw nothing matching this.
>
> I've got a 50G FCP LUN on device F100 attached to a VM named LINUX2. If
> I IPL SLES on LINUX2,
Silly question but your /etc/fstab has an entry for that device?
-Original Message-
I've got a 50G FCP LUN on device F100 attached to a VM named LINUX2. If
I IPL SLES on LINUX2, zfcp discovers 0xF100 after /etc/init.d runs
through all its startup scripts. I then need to log in as root to
Hi,
I've run into an interesting issue with SLES 9 64-bit and zfcp and was
hoping someone here had an idea to fix it. I've checked the archives
but saw nothing matching this.
I've got a 50G FCP LUN on device F100 attached to a VM named LINUX2. If
I IPL SLES on LINUX2, zfcp discovers 0xF100 aft
