• No se han encontrado resultados

La memoria colectiva: reinas y santas de la Europa medieval

XVI XVII XVIII XIX Siglos

2. LA REINA, EL REINO Y EL GOBIERNO

2.3. La memoria colectiva: reinas y santas de la Europa medieval

This subsection describes how to perform a new installation of HDLM in a single-path boot disk environment that uses a SCSI device and how to set up the environment. Note that if the settings are incorrect, the OS might not start. For details about what action to take if the OS cannot be started from an HDLM device, see 3.7.7.

To install HDLM in a boot disk environment that uses a SCSI device, and set up the environment:

1. Log in to Linux as a user with root privileges.

In an HDLM environment, a SCSI device cannot be identified from the value set in LABEL. Before installing HDLM, therefore, you must remove the LABEL setting. Perform steps 2 and 3 to check whether LABEL is set.

2. Check whether the definition in the /etc/fstab file contains LABEL. Check the contents of the /etc/fstab file.

– When the boot loader is LILO or GRUB

Figure 3.12 shows example content of /etc/fstab file.

Figure 3.12 Example Content of /etc/fstab file When the Boot Loader Is LILO or GRUB

LABEL is set in the shaded portion.

If Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 is being used, you must also check the following line:

LABEL=SWAP-sda3 swap swap defaults 0 0

– When the boot loader is ELILO installed on an IPF host Figure 3.13 shows example content of /etc/fstab file.

Figure 3.13 Example Content of /etc/fstab file When the Boot Loader Is ELILO

LABEL is set in the shaded portion.

If Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 is being used, you must also check the following line:

LABEL=SWAP-sda3 swap swap defaults 0 0

3. Check whether the definition in the boot loader configuration file contains LABEL.

Separate examples are provided for when the boot loader is LILO, GRUB, or ELILO running on an IPF host.

– When the boot loader is LILO

Figure 3.14 shows example content of the configuration file.

Figure 3.14 Example Content of /etc/lilo.conf file

LABEL is set in the shaded portion.

– When the boot loader is GRUB

Figure 3.15 shows example content of the configuration file.

Figure 3.15 Example Content of /etc/grub.conf file

LABEL is set in the shaded portion.

– When the boot loader is ELILO running on an IPF host

Figure 3.16 shows example content of the configuration file.

Figure 3.16 Example Content of /etc/elilo.conf file

LABEL is set in the shaded portion.

In steps 2 and 3, you checked the /etc/fstab file and the boot loader configuration file. If

LABEL is not set in these files, go to step 15 and perform a new installation of HDLM. If LABEL

is set in either or both of these files, perform steps 4 to 14 to check the mounted file system, and then to remove the LABEL setting.

4. Execute the mount command to check the mounted file system.

Check the correspondence between the SCSI device and LABEL that you checked in steps 2 and 3. You will need this information to remove the LABEL setting.

– When the boot loader is LILO or GRUB

Figure 3.17 shows an example of executing the mount command.

Figure 3.17 Example of Executing the mount Command When the Boot Loader Is LILO or GRUB

The shaded portion indicates the SCSI device for which LABEL is set.

– When the boot loader is ELILO running on an IPF host

Figure 3.18 shows an example of executing the mount command.

Figure 3.18 Example of Executing the mount Command When the Boot Loader Is ELILO The shaded portion indicates the SCSI device for which LABEL is set.

Remove the LABEL setting in the /etc/fstab file and the boot loader configuration file according to the information for the mounted file system. First perform steps 5 to 7 to remove the LABEL setting in the /etc/fstab file.

If Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 is being used, check the SCSI device name by referring to the /proc/swaps file.

Figure 3.19 Example Content of /proc/swaps file

5. Edit the /etc/fstab file to remove the LABEL setting.

The detailed procedure is explained in steps 6 and 7.

– When the boot loader is LILO or GRUB

Figure 3.20 shows an example of editing the /etc/fstab file.

Figure 3.20 Example of Editing /etc/fstab file When the Boot Loader Is LILO or GRUB Comment out the LABEL line, and then add the shaded line.

If Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 is being used, you must also comment out the following LABEL line, and then add the line specified by the SCSI device.

# LABEL=SWAP-sda3 swap swap defaults 0 0 /dev/sda3 swap swap defaults 0 0

– When the boot loader is ELILO running on an IPF host Figure 3.21 shows an example of editing the /etc/fstab file.

Figure 3.21 Example of Editing /etc/fstab file When the Boot Loader Is ELILO Comment out the LABEL line, and then add the shaded line.

If Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5 is being used, you must also comment out the following LABEL line, and then add the line specified by the SCSI device.

If Red Hat Enterprise Linux AS4/ES4 is being used, you must also comment out the following line:

# LABEL=SWAP-sda3 swap swap defaults 0 0 /dev/sda3 swap swap defaults 0 0

6. If necessary, back up the /etc/fstab file.

7. Edit the /etc/fstab file.

Refer to the correspondence between LABEL and the SCSI device that you checked in step 4.

Copy the registration of the LABEL specification.

Comment out the existing settings.

Edit the file to disable the LABEL specification and enable the SCSI device specification.

After editing the /etc/fstab file, perform steps 8 to 13 to remove the LABEL setting contained in the boot loader configuration file.

8. Edit the boot loader configuration file to remove the LABEL setting.

Edit the boot loader configuration file as shown in Figure 3.22, Figure 3.23, and Figure 3.24.

The detailed procedure is explained in steps 9 to 13.

Separate examples are provided for when the boot loader is LILO, GRUB, or ELILO running on an IPF host.

– When the boot loader is LILO

Figure 3.22 shows an example of editing the configuration file. After changing the configuration file, execute /sbin/lilo command to activate the new setting.

Figure 3.22 Example of Editing /etc/lilo.conf file Edit the shaded portion.

– When the boot loader is GRUB

Figure 3.23 shows an example of editing the configuration file.

Figure 3.23 Example of Editing /etc/grub/grub.conf file Edit the shaded portion.

– When the boot loader is ELILO running on an IPF host

Figure 3.24 shows an example of editing the configuration file.

Figure 3.24 Example of Editing /etc/elilo.conf file Edit the shaded portion.

9. If necessary, back up the boot loader configuration file.

10. Copy the startup configuration that has the LABEL specification.

11. Assign a name to the copied configuration.

You can assign any name that indicates that the configuration is used for specifying the SCSI device.

– If the boot loader is LILO, or ELILO running on an IPF host Change label.

– If you will use GRUB as the boot loader Change title.

12. Convert the copied configuration from the LABEL specification to the SCSI device

specification according to the correspondence between LABEL and the SCSI device that you checked in step 4.

Edit the file to disable the LABEL specification and enable the SCSI device specification.

When editing the file, be careful of the following:

– When an option that depends on the user environment is specified:

Be careful not to delete the option.

– When the boot loader is LILO, or ELILO running on an IPF host, and an option that depends on the user environment is not specified:

Comment out or delete append.

13. Specify the configuration to be used for booting the system.

– When the boot loader is LILO, or ELILO running on an IPF host

Specify label for default. If LILO is the boot loader, you must then execute /sbin/lilo

command to activate the new setting.

– When GRUB is the boot loader

Specify the position of the valid title for default.

14. Restart the host to make sure that booting from the SCSI device is possible.

This completes the removal of the LABEL setting.

15. Install HDLM.

To install HDLM, see section 3.6.2 perform steps 2 and 3 to 12 to create an HDLM device.

You will also need to perform step 13 if you are only restarting the host. Note that the procedure differs depending on whether the host is restarted after installation.

In steps 16 to 35 that follow, you will edit the configuration file to change the definition so that the OS starts with HDLM specified.

16. Execute the HDLM-configuration definition utility (dlmcfgmgr) with the -v parameter specified to check the correspondence between the SCSI device and the HDLM device.

Figure 3.25 shows an example of executing the dlmcfgmgr utility with the -v parameter specified.

Figure 3.25 Example of Executing the dlmcfgmgr Utility with the -v Parameter Specified

Check the shaded portion, which shows the correspondence between the SCSI device and the HDLM device.

17. Check the umask value.

Execute the following command to check the specified umask value:

# umask 0177

In the above example, the specified umask value is 0177.

If the umask value is not 0022, execute the command below to change the value. Note that after you create an initial RAM disk image in step 18, you need to reset the umask value to the original value. Therefore, make a note of the original umask value.

# umask 0022

18. Execute the dlmmkinitrd utility for supporting a boot disk to create an initial RAM disk image for HDLM.

For the initial RAM disk image file specified in the parameter, assign a name that is different from all currently used names.

For details on the dlmmkinitrd utility, see section 7.4.

– When using Red Hat Enterprise Linux AS3/ES3

When the dlmmkinitrd utility terminates normally, a message indicating the RAM disk size required for the created initial RAM disk image file appears. Write down the displayed value, since you will need it when you edit the boot loader configuration file. Figure 3.26 and Figure 3.27 show examples of executing the dlmmkinitrd utility.

Figure 3.26 Example of Executing the dlmmkinitrd Utility When Using Red Hat Enterprise Linux AS3/ES3 (IA32)

Figure 3.27 Example of Executing the dlmmkinitrd Utility When Using Red Hat Enterprise Linux AS3/ES3 (IPF)

The shaded portion indicates the RAM disk size.

– When using Red Hat Enterprise Linux AS4/ES4 or Red Hat Enterprise Linux 5

The execution result in Red Hat Enterprise Linux AS4/ES4 does not differ from the execution result in Red Hat Enterprise Linux 5.Figure 3.28 and Figure 3.29 show examples of executing the dlmmkinitrd utility in Red Hat Enterprise Linux AS4/ES4.

Figure 3.28 Example of Executing the dlmmkinitrd Utility When Using Red Hat Enterprise Linux AS4/ES4 (IA32)

Figure 3.29 Example of Executing the dlmmkinitrd Utility When Using Red Hat Enterprise Linux AS4/ES4 (IPF)

19. If you changed the umask value in step 17, reset the value to the original value. If you have not changed the umask value, proceed to step 20.

In the following example, the value originally specified was 0177.

# umask 0177

20. Edit the /etc/fstab file.

Change the definition in the mount point for HDLM management-target devices other than

/boot directory or /boot/efi directory so that the HDLM device will be mounted rather than the SCSI device. Do not specify the /boot or /boot/efi directory as the mount point for the HDLM device. Also, change the definition so that the swap partition uses the HDLM device.

Edit the /etc/fstab file as shown in Figure 3.30 or Figure 3.31.

The detailed procedure is explained in steps 21 to 24.

– When the boot loader is LILO or GRUB

Figure 3.30 shows an example of editing the /etc/fstab file.

Figure 3.30 Example of Editing /etc/fstab When the Boot Loader Is LILO or GRUB Edit the shaded portion.

– When the boot loader is ELILO running on an IPF host Figure 3.31 shows an example of editing the /etc/fstab file.

Figure 3.31 Example of Editing /etc/fstab When the Boot Loader Is ELILO Edit the shaded portion.

21. If necessary, back up the file.

22. Copy the registration of the SCSI device specification.

23. Comment out the existing SCSI device specification by placing a hash mark (#) at the beginning of each line.

24. Convert the copied registration from a SCSI device specification to an HDLM device specification according to the correspondence between the SCSI device and the HDLM device that you checked in step 16.

25. Edit the boot loader configuration file so that the OS will start with HDLM specified.

Edit the boot loader configuration file as shown in Figure 3.32, Figure 3.33, and Figure 3.34.

The detailed procedure is explained in steps 26 to 31.

Separate examples are provided for when the boot loader is LILO, when the boot loader is GRUB, and when the boot loader is ELILO running on an IPF host.

– When the boot loader is LILO

Figure 3.32 shows an example of editing the configuration file. After changing the configuration file, execute /sbin/lilo command to activate the new setting.

Figure 3.32 Example of Editing /etc/lilo.conf file Edit the shaded portion.

– When the boot loader is GRUB

Figure 3.33 shows an example of editing the configuration file.

Figure 3.33 Example of Editing /etc/grub.conf file Edit the shaded portion.

– When the boot loader is ELILO running on an IPF host

Figure 3.34 shows an example of editing the configuration file.

Figure 3.34 Example of Editing /etc/elilo.conf file Edit the shaded portion.

26. If necessary, back up the file.

27. Copy the configuration that was used for startup from the SCSI device.

28. Assign a name to the copied configuration that indicates that the configuration is used for specifying the HDLM device.

– If the boot loader is LILO, or ELILO running on an IPF host Change label.

– If you will use GRUB as the boot loader Change title.

29. Delete the root specification.

30. In initrd, specify the initial RAM disk image file you created in step 18, and specify the RAM disk size in ramdisk_size if Red Hat Enterprise Linux AS3/ES3 is being used.

Note: how you specify initrd and ramdisk_size differs depending on the boot loader.

When editing the file, be careful of the following:

– When an option that depends on the user environment is specified:

Be careful not to delete the option.

– When the boot loader is LILO, or ELILO running on an IPF host, and append is deleted or commented out:

Add append and specify ramdisk_size.

31. Specify the configuration that will be used for booting.

– When the boot loader is LILO, or ELILO running on an IPF host

Specify label for default. If LILO is the boot loader, you must then execute /sbin/lilo

command to activate the new setting.

– When GRUB is the boot loader

Specify the position of the valid title for default. 32. Shut down the host.

Execute the following command to shut down the host:

# shutdown -h now

33. Change the configuration from a single-path configuration to a multi-path configuration.

34. Start the host.

35. Make sure that the HDLM device is used by the file system and the swap partition.

Make sure that the HDLM device is mounted and the HDLM device is assigned to the swap partition.

– When the boot loader is LILO or GRUB

Figure 3.35 shows an example of executing the mount command.

Figure 3.35 Example of Executing the mount Command When the Boot Loader Is LILO or GRUB Check the shaded portion.

– When the boot loader is ELILO running on an IPF host

Figure 3.36 shows an example of executing the mount command.

Figure 3.36 Example of Executing the mount Command When the Boot Loader Is ELILO

Check the shaded portion.

Refer to the /proc/swaps file to make sure that the specified HDLM device name is displayed in the Filename column.

Figure 3.37 Example Content of /proc/swaps file