Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 191 — #217
i
i
i
i
i
i
i
i
6
System Repair
netsetup
To continue the installation, enter:
./inst_source
bash: no job control in this shell
SuSE Instsys suse:/ #
This opens a root shell from which to issue all necessary commands di-
rectly.
6.5.2 Loading DASD Modules
To access the root device, load the required kernel modules. First, load the
DASD modules. They consist of a middle layer module, dasd_mod, and a
low-level module depending on the DASD type. Here, ECKD devices are
assumed, so the module is called dasd_eckd_mod. The dasd_mod mod-
ule requires the channel ranges of the DASDs to access (e.g., 0150) as an
argument. The modules are loaded with the commands:
Example 6.2: Loading DASD Modules
SuSE Instsys suse:/ # insmod dasd_mod dasd=0150
Using /lib/modules/version/kernel/drivers/s390/block/dasd_mod.o
dasd: initializing...
debug: dasd: new level 3
dasd: Registered successfully to major no 94
dasd: initialization finished
SuSE Instsys suse:/ # insmod dasd_eckd_mod
Using /lib/modules/version/kernel/drivers/s390/block/dasd_eckd_mod.o
dasd(eckd): ECKD discipline initializing
[ ... ]
Partition check:
dasda:VOL1/ 0X0150: dasda1 dasda2
dasd(eckd): We are interested in: CU 3880/00
dasd(eckd): We are interested in: CU 3990/00
dasd(eckd): We are interested in: CU 2105/00
dasd(eckd): We are interested in: CU 9343/00
If the line Partition check is printed, all modules have been loaded
properly and the DASD device is now available for mounting.
191
SUSE LINUX Enterprise Server