Datasheet

“main” (Installation and Administration) — 2004/6/25 — 13:29 — page 192 — #218
i
i
i
i
i
i
i
i
6.5.3 Mounting the Root Device
If the modules have loaded correctly, you should now be able to mount
the root device. Assuming that the root device is on the second partition of
the DASD device (/dev/dasda2) the corresponding command is mount
/dev/dasda2 /mnt.
Note
File System Consistency
If the installed system has not been shut down properly, it may
be advisable to check the file system consistency prior to mount-
ing. This prevents any accidental loss of data. Using this exam-
ple, issue the command fsck /dev/dasda2 to ensure that the
file system is in a consistent state.
Note
By just issuing the command mount, it is possible to check whether the file
system could be mounted correctly.
Example 6.3: Output of the Mount Command
SuSE Instsys suse:/ # mount
shmfs on /newroot type shm (rw,nr_inodes=10240)
devpts on /dev/pts type devpts (rw)
virtual-proc-filesystem on /proc type proc (rw)
/dev/dasda2 on /mnt type reiserfs (rw)
6.5.4 Changing to the Mounted File System
For the zipl command to read the configuration file from the root device
of the installed system and not from the rescue system, change the root de-
vice to the installed system with the chroot command:
Example 6.4: chroot to the Mounted File System
SuSE Instsys suse:/ # cd /mnt
SuSE Instsys suse:/mnt # chroot /mnt
192
6.5. S/390, zSeries: Using initrd as a Rescue System