I am currently playing with SLES 8 in our z/VM environment.  Today I
attempted to build a system that had assigned to it 5 MOD3 devices, 200 -
204.  Going through the process of formating each device from z/VM and then
proceeding into the install all works fine.  I a
sk that the install process format my drives with ext3.  I have also
attempted /boot with ext3 and the remaining drives being assigned to a VG
under LVM.  In both cases, once the install completes and the guest
shutsdown I receive an error at z/VM.

DMSACP112S C(200) device error
DMSACP112S E(201) device error
DMSACP112S F(202) device error
DMSACP112S G(203) device error
DMSACP112S H(204) device error

The drives at this point are no longer accessible.  I have even ignored the
errors and attempted ipl 200 clear and received the following error:

/lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_eckd_mod.o:
unresol
ved symbol dasd_default_erp_postaction
/lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_eckd_mod.o:
unresol
ved symbol dasd_discipline_add
/lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_eckd_mod.o:
unresol
ved symbol dasd_int_handler
/lib/modules/2.4.19-3suse-SMP/kernel/drivers/s390/block/dasd_eckd_mod.o:
unresol
ved symbol dasd_start_IO
kmod: failed to exec /sbin/modprobe -s -k block-major-94, errno = 2
VFS: Cannot open root device "dasdb1" or 5e:05
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 5e:05
HCPGIR450W CP entered; disabled wait PSW 000A0000 8020ECF8

Can anyone help me out with this?  I have installed SLES 8 previously using
2 MOD3, but I don't see how installing to 5 MOD3 would differ from 2.

Thank you!
Eric Sammons
(804)697-3925

Reply via email to