Solaris引導(dǎo)管理器（全）－新手第一次譯東東，請多多指教

bosshoss_cn

III.1  Solaris boot manager
III.1  Solaris引導(dǎo)管理
Primary boot
主引導(dǎo)
Solaris boot process consists of two conceptually distinct phases, primary boot and secondary boot. The primary boot is implemented in the BIOS ROM on the system board and in BIOS extensions in ROMs on peripheral boards. The code is x86 real-mode code. This part of the boot process is common for all PC-compatible systems.
Solaris引導(dǎo)進程由二個概念明確的階斷組成，主引導(dǎo)和次引導(dǎo)。主引導(dǎo)被執(zhí)行在系統(tǒng)板BIOS ROM和位于外圍板上的ROM中的擴充BIOS。這些代碼是X86實模式代碼。這部分關(guān)于引導(dǎo)過程的說明對所有PC兼容系統(tǒng)都是一樣(共同)的。
A Solaris boot partition is a primary partition, and must be active in order to boot Solaris. It begins with one-cylinder boot slice, which contains the partition boot program pboot in the first sector, the standard Solaris disk label and the VTOC in the second and third sectors, and the bootblk program in the fourth and subsequent sectors (VTOC is discussed later).
一個Solaris引導(dǎo)分區(qū)是一個基本分區(qū)，并且必須是被激活的用來引導(dǎo)Solaris.起始于第一柱面的引導(dǎo)區(qū)，包含有：存在于第一個扇區(qū)的分區(qū)引導(dǎo)程序PBOOT，在第二和第三扇區(qū)的標(biāo)準(zhǔn)的Solaris放在盤標(biāo)簽和VTOC以及從第四扇區(qū)起的BOOTBLK程序。
When a system is booted from a hard disk drive, MBR of that disk is read into memory. If Solaris was the last operating system installed to this disk, its MBR contains mboot - master boot program. The program, though specific for Solaris, works as usual Master Boot Code, that is, it reads the first sector of the first active primary partition on the boot disk, and jumps to its first byte. If the active partition is Solaris boot partition, its VBS is read and pboot - partition boot program contained there is invoked. Then pboot in turn loads and runs bootblk program.
當(dāng)一個系統(tǒng)由一個硬盤引導(dǎo)時，這個盤的MBR(主引導(dǎo))被讀入內(nèi)存。如果SOLARIS是這個硬盤最后安裝的操作系統(tǒng)，它的MBR包含MBOOT(主引導(dǎo)程序)。雖然這個program是針對solaris的，但是和通常的主引導(dǎo)代碼的工作方式是一樣的，準(zhǔn)確的說，它讀這個硬盤的活動基本分區(qū)的第一個扇區(qū)并且跳轉(zhuǎn)到它的第一位。如果活動分區(qū)是SOLARIS引導(dǎo)分區(qū)，它的VBS被讀取和調(diào)用PBOOT(分區(qū)引導(dǎo)程序)。然后PBOOT轉(zhuǎn)去加載和運行 BOOTBLK程序。
In case Solaris is boot from floppy or CD-ROM, the first physical sector of the media read by BIOS, is a VBS not MBR. The pboot program contained there is responsible for loading the image of the boot manager strap.com.
   在SOLARIS是通過軟盤或光盤來引導(dǎo)的情況下，被BIOS讀取的媒介的第一個物理塊是VBS而不是MBR。Pboot程序負(fù)責(zé)加載引導(dǎo)管理STRAP.com的映像。
Note: From version 8 up, Solaris x86 installation CDs are boot-able.
注：從SOLARIS8起，SOLARIS X86安裝CD帶啟動功能。
Note: Some releases of Solaris 8 are affected by a bug which causes that Solaris Master Boot Code always loads Solaris VBS (PBR) from the first physical hard disk drive in the system. If Solaris is on second drive the error message "Bad PBR" is reported. See IV.4 Troubleshooting.
注：一些版本的SOLARIS8因一個BUG：solaris 主引導(dǎo)代碼總是從系統(tǒng)的第一個物理硬盤設(shè)備加載Solaris VBS(PBR)而受到影響。如果SOLARIS在第二個設(shè)備以及報告錯誤信息：”bad pbr”，請查閱IV.4 Troubleshooting.
Boot manager
引導(dǎo)管理器
Programs bootblk and strap.com, loaded in result of primary boot, are very similar. Both contain Solaris boot manager code, which reads current disk partition information, and in case there is more than one primary partition, displays the table with all available partitions. It gives an opportunity to reboot another partition, in other words, another operating system. The default one is Solaris. The default timeout to make selection is 30 seconds. The difference between bootblk and strap.com is that, the first one is placed on UFS file systems and can not be configured, while the second is placed on FAT file systems (floppy disk or x86 Boot partition) and the timeout may be set in /solaris/strap.rc file.
Bootblk和Strap.com程序加載到返回主引導(dǎo)是非常相似的。二者包含SOLARIS引導(dǎo)管理代碼，讀當(dāng)前盤分區(qū)信息，當(dāng)有多于一個基本分區(qū)和情況，顯示出所有可用的分區(qū)表。它給一個機會來重引導(dǎo)其它的分區(qū)，換句話說，就是另的操作系統(tǒng)。SOLARIS默認(rèn)一個。默認(rèn)選擇時間為30秒。 Bootblk和strap.com的差別在于：第一個是放置在UFS文件系統(tǒng)中并且不能被設(shè)置，第二是放置在FAT文件系統(tǒng)(軟盤或X86引導(dǎo)區(qū))并且可在/solaris/strap.rc文件中修改選擇時間長。
Secondary boot
二級引導(dǎo)
If Solaris partition is selected to boot off, the secondary boot - boot.bin - is loaded by the boot manager. The secondary boot is capable of reading and booting from a UFS file system on a hard disk or CD, or by way of LAN using NFS protocol. It switches the processor to 32-bit, paged, protected mode and performs some limited machine initialization. Then, it runs Device Configuration Assistant, which either, boots the system automatically, or let the user select boot device, depending on the state of auto-boot eeprom variable (see eeprom man page). After that, root file system specified in bootpath eeprom variable is mounted.
如果solaris分區(qū)被選擇引導(dǎo)完，二級引導(dǎo)-boot.bin-被引導(dǎo)管理器加載。二級引導(dǎo)能夠從UFS文件系統(tǒng)、硬盤、光盤或其它方法如局域網(wǎng)中使用NFS協(xié)議中讀取和導(dǎo)入。
Secondary boot is programmable, which makes it very flexible. If the root file system is successfully mounted, boot.bin invokes a command interpreter, that interprets /etc/bootrc script. The /etc/bootrc script lets the user to specify additional options for booting kernel, e.g. -r to reconfigure devices automatically.
二級引導(dǎo)是可以編輯的而構(gòu)成很大的靈活性。如果根文件系統(tǒng)成功裝上，boot.bin調(diào)用一個命令解釋器來解釋/etc/bootrc腳本。/etc/bootrc腳本使用戶為導(dǎo)入內(nèi)核指定額外選項。比方：-r 自動重新裝配設(shè)備。
Device Configuration Assistant
設(shè)備配置助手
Device Configuration Assistant, or shortly DCA, is used to add, remove and configure device drivers necessary to boot a machine up. Note that keyboard, display and mouse are configured with kdmconfig (see kdmconfig man page). DCA is run at the beginning of Solaris setup to determine what device drivers need to be load, and to select the device from which the installation software will be loaded. DCA is shipped with Solaris media kit on a floppy disk. Solaris 8 installation CD (Installation as well as Software 1 CD) is boot-able and contains DCA.
設(shè)備配置助手，簡寫為DCA，用來增加、刪除和配置必要的設(shè)備驅(qū)動來引導(dǎo)一臺機器。注意鍵盤、顯示器和鼠標(biāo)由kdmconfig(參照KDMCONFIG操作頁)配置。
DCA運行在安裝SOLARIS開始確定那些設(shè)備驅(qū)動是必須加載的以及選擇的設(shè)備的安裝程序?qū)⒈患虞d。DCA以SOLARIS存貯包裝載在一張軟盤上。SOLARIS8安裝CD(安裝CD之軟件一)是能引導(dǎo)和包含了DCA。
DCA is invoked by the secondary boot every time Solaris is boot up. In this situation DCA behavior is determined by the state of two eeprom variables: auto-boot and auto-boot-timeout. The first one, if true, causes DCA to boot Solaris kernel off the device and partition specified in bootpath variable, otherwise presents a list of all devices capable of doing that and waits for a user selection. The list usually contains all hard disk drives, CD-ROMs, and LAN adapters. The second variable auto-boot-timeout determines the amount of time DCA waits for pressing Esc (escape) key to enter into DCA utility.
在每次SOLARIS引導(dǎo)到二級引導(dǎo)時調(diào)用DCA。在二個EEPROM參數(shù)：auto-boot和auto-boot-timeout的狀況下，DCA的行為被中止。如果第一個參數(shù)為真，則使DCA脫離在BOOTPATH中定議的設(shè)備和分區(qū)參數(shù)引導(dǎo)SOLARIS內(nèi)核，并列出所有可能工作的設(shè)備來等待用戶選擇。列表通常包括所有的硬盤、光驅(qū)、網(wǎng)絡(luò)適配器。第二個參數(shù)auto-boot-timeout確定DCA等待按ESC鍵進入DCA應(yīng)用程序的總時間長。
By default auto-boot is set to true, and auto-boot-timeout to 5 seconds. With these settings DCA displays information that it waits for pressing Esc and delays boot process for 5 seconds. Both variables may be modified using either, DCA itself, or eeprom utility. To modify variables with DCA one needs to enter DCA utility pressing Esc key during Solaris boot time. First, DCA probes hardware, then presents the list of possible boot devices. New values may be assigned to variables under Boot Tasks option. If Solaris is already running, type as root:
根據(jù)默認(rèn)值：Auto-boot為真，auto-boot-timeout等于5秒，DCA顯示等待按ESC信息和延遲引導(dǎo)過程5秒。二個參數(shù)都可以通過 DCA或EEPROM來修改。當(dāng)用DCA來修改參數(shù)時，需要在SOLARIS引導(dǎo)時按ESC進入DCA應(yīng)用程序。首先，DCA探測硬件，再顯示可能的引導(dǎo)設(shè)備列表。引導(dǎo)任務(wù)參數(shù)變量可能賦與新的值。如果solairs已經(jīng)在運行，以ROOT身分輸入：
eeprom auto-boot?=true
to set auto-boot to true, or
設(shè)suto-boot為真。
eeprom auto-boot-timeout=0
to make DCA not to wait for Esc key.
使DCA不等待ESC鍵
Restoring Solaris boot manager
恢復(fù)SOLARIS引導(dǎo)管理器
Solaris Master Boot Code of the MBR might be overwritten during installation of other operating system or a third party boot manager after Solaris was installed. Solaris Master Boot Code is stored in the file /usr/lib/fs/ufs/mboot. It can be restored using Solaris fdisk utility (see fdisk man page) as follows:
在SOLARIS安裝后安裝其它操作系統(tǒng)或第三方引導(dǎo)管理器時MBR的Solaris 主引導(dǎo)代碼能被覆蓋。Solaris 主引導(dǎo)代碼存貯在文件：/usr/lib/fs/mboot中，它能夠用SOLARIS FDISK應(yīng)用程序來恢復(fù)。
fdisk -b /usr/lib/fs/ufs/mboot -n /dev/rdsk/c0d0p0
where /dev/rdsk/c0d0p0 stands for the raw device associated with the first (usually primary master) IDE/ATA hard disk drive on the system.
這里/dev/rdsk/c0d0p0代表原始設(shè)備所關(guān)聯(lián)的在這個系統(tǒng)中的第一個(通常是主控)IDE/ATA硬盤
Sometimes it is necessary to recover VBS of a Solaris boot partition or Solaris boot manager program. installboot utility is capable of doing that (see installboot man page). To refresh VBS of Solaris partition located on the first IDE/ATA drive type as root:
   有時，它是必須恢復(fù)一個SOLARIS引導(dǎo)或SOLARIS引導(dǎo)管理程序的VBS。INSTALLBOOT功能能夠?qū)崿F(xiàn)。刷新位于第一個IDE/ATA驅(qū)動器的solaris分區(qū)VBS，在ROOT用戶下輸入：
installboot /usr/platform/i86pc/lib/fs/ufs/pboot \
/usr/platform/i86pc/lib/fs/ufs/bootblk /dev/rdsk/c0d0s2
Since installboot can not verify the partition specified as its argument, it may write Solaris boot manager into any partition. Therefore care must be taken not to destroy other partitions. The same operation may be also done with fmthard utility discussed later.
因為installboot不檢驗分區(qū)指定的變量，它可能寫SOLARIS引導(dǎo)管理任何分區(qū)。因此，必須小心破壞另的分區(qū)。在后面討論FATHARD功能可以實現(xiàn)同樣的應(yīng)用。
The following files contain critical executable code for boot process:
接下來的文件包含引導(dǎo)過程的臨界[極限]試驗代碼。
        /usr/lib/fs/ufs/mboot - Master Boot Code, 主引導(dǎo)代碼
        /usr/platform/i86pc/lib/fs/ufs/pboot - Volume Boot Code, 巻引導(dǎo)代碼
        /usr/platform/i86pc/lib/fs/ufs/bootblk - Solaris boot manager. SOLARIS引導(dǎo)管理器。
x86 Boot partition
X86引導(dǎo)分區(qū)
x86 Boot partition was introduced in Solaris 8. Normally, it is a small primary partition, with FAT file system and DCA installed. It is necessary when Webstart installation is used in order to boot Solaris kernel from miniroot (temporary) file system. It provides also a user the way to load Solaris kernel from non-boot hard disk drive, select one of multiple Solaris installations, or boot Solaris across a network - all that DCA booted from floppy can do.
X86引導(dǎo)分區(qū)在SOLARIS8中提出。通常，它是一個小的主分區(qū)，F(xiàn)AT文件系統(tǒng)和安裝有DCA。在WEB開始安裝用來為了從MINIROOT(臨時的)文件系統(tǒng)引導(dǎo)SOLARIS內(nèi)核時它是必須的。它也同樣提供一個使用途徑去引導(dǎo)SOLARIS內(nèi)核從無引導(dǎo)的硬盤設(shè)備，從多種SOLARIS安裝中選擇一種，或通過網(wǎng)絡(luò)引導(dǎo)SOLARIS――從軟盤引導(dǎo)DCA能實現(xiàn)。
It is created by default during Solaris 8 installation. Practice shows, however, that x86 Boot partition is not necessary to run Solaris 8. DCA is still below /boot directory and can be run during boot time.
它在默認(rèn)安裝SOLARIS8期間創(chuàng)建�？墒菍嶋H上，X86引導(dǎo)分區(qū)不是運行SOLARIS8所必要。DCA一直存在/boot目錄下和在引導(dǎo)的時候運行。
x86 Boot partition can be created with Solaris fdisk program. At this stage it is simply a reserved portion of a hard disk with partition ID set to 0xBE. To make it functional FAT file system must be constructed, and Solaris boot manager installed. If x86 Boot partition is created and set active, on c0d0 (the first IDE drive), then command:
X86引導(dǎo)分區(qū)能被SOLARIS　FDISK程序創(chuàng)建。在這個過程它只不過是一個分區(qū)ID為0xBE的硬盤的一個保留部分。要構(gòu)造它，F(xiàn)AT文件系統(tǒng)功能必須被建立和安裝SOLARIS引導(dǎo)管理器
。如果在C0D0（第一個IDE設(shè)備）上已創(chuàng)建X86引導(dǎo)分區(qū)并且設(shè)置為活動的，那么使用下面的命令：
mkfs -F pcfs -o b=BOOT,B=/boot/mdbootbp,s,i=/boot/strap.com /dev/rdsk/c0d0p0:boot
will do the job. To install DCA mount the partition and copy necessary files:
來做這個工作。安裝DCA來掛接分區(qū)和拷貝必要的文件。
mount -F pcfs /dev/dsk/c0d0p0:boot /mnt
cp -r /boot/* /mnt
echo "/boot/ / p">; /mnt/solaris.map
/dev/dsk/c0d0p0:boot is always the right address for x86 Boot partition on c0d0 drive. solaris.map file is required when DCA is installed on a FAT file system to remap default UFS paths to FAT ones. It is present on DCA floppy disk, but redundant on UFS variant of DCA.
在C0D0設(shè)備上的X86引導(dǎo)分區(qū)的正確地址永遠(yuǎn)是/dev/dsk/c0d0p0:boot。SOLARIS.MAP文件是必要的當(dāng)DCA被安裝在一個FAT文件系統(tǒng)來重繪默認(rèn)的UFS對應(yīng)的FAT路徑。它出現(xiàn)在DCA軟盤，但是在DCA的UFS變量是多余的。
Reconfiguring boot device
重新配置引導(dǎo)設(shè)備
Solaris requires details on physical connection of all devices to function properly. It saves these data during installation. When disk controller or cables are changed the data gets outdated. The following needs to be updated to boot Solaris:
Solaris命令詳細(xì)說明了在物理連接到所有設(shè)備直到適當(dāng)?shù)墓δ�。它在安裝期間保存這些數(shù)據(jù)。當(dāng)磁盤控制器或數(shù)據(jù)線被改變時，這此數(shù)據(jù)變成過時的了。接下來需要更新來引導(dǎo)SOLARIS：
        bootpath in /boot/solaris/bootenv.rc,
        /etc/path_to_inst.save,
        device nodes in /devices,
        either, /etc/vfstab, or device links under /dev/dsk and /dev/rdsk.
The first and the last must be done manually while the rest can be fixed with devfsadm utility (Solaris 8 or later). This is how to achieve that:
最先和最后必須手工來做當(dāng)重設(shè)時用devfsadm功能（Solaris8及其后）來確定。這是如何完成那樣的：
Assume that the old boot path was:
假設(shè)舊的引導(dǎo)路徑是：
/pci@0,0/pci9004,7881@13/sd@0,0:a,
where:
在這里：
        pci@0,0 is the architecture of the disk controller and its address,
        PCI＠0，0表明磁盤控制器結(jié)構(gòu)及它的地址
        pci9004,7881 is a device PNP identification, consists of a vendor and part number,
        PCI9004,7881表明一個即插即用設(shè)備標(biāo)識，包括一個所有者和局部編號
        13 is an IRQ level,
        13是一個IRQ（中斷請求）級別
        sd means SCSI driver (you may have ata, cmdk or eisa here),
        SD意味著SCSI驅(qū)動器（在這你可能有ATA、CMDK或EISA驅(qū)動器）
        0,0:a is the address of the Solaris root file system (slice) on the Solaris fdisk partition.
        0,0：A是在SOLARIS分區(qū)上的SOLARIS根文件系統(tǒng)（片）的地址
The boot path represents a subdirectory in /devices, Particular parts of the boot path change depending on what has changed in physical connection. For instance, when the controller is moved from one slot to another on the same motherboard the IRQ may change only.
引導(dǎo)路徑描述這一個子目錄在/devices, 引導(dǎo)路徑的詳細(xì)部分的改變依靠在物理連接的改變。比方說：當(dāng)控制器在同一塊主板上從一個通道（接口、插槽）移到另一個，也公僅僅IRQ可能改變。
The first question that arises here is what is the current boot path? It can be found with DCA. When the boot device is selected, the suitable boot path is displayed. Yet better method is to mount the root slice and check the full path associated to the disk device node used (the one under /dev/dsk).
第一個問題發(fā)生在這里：什么是當(dāng)前引導(dǎo)路徑？它能被DCA發(fā)現(xiàn)。當(dāng)引導(dǎo)設(shè)備被選擇，顯示出適當(dāng)?shù)囊龑?dǎo)路徑。然而更好的方法是掛接根片和核對完全（絕對）路徑所關(guān)聯(lián)的使用了的磁盤設(shè)備節(jié)點（在/dev/dsk下）
The step by step procedure would look as follows:
一步一步的過程將在接下來的表示出來：
1.        Boot the system from the Solaris installation disk (in case of Solaris 8 use "Software 1 CD"

to single user mode, that is, at the prompt to select between Interactive and J installation enter b -s. A shell will follow after this.
　從SOLARIS安裝盤引導(dǎo)系統(tǒng)（假設(shè)SOLARIS8使用軟件光盤1）到單用戶模式，更確切地說，在提示符下在交互方式和ump Start安裝之間選擇，輸入　B�。璖。在這之后跟隨一個SHELL。
2.        Set terminal type to AT386 to avoid problems with vi editor. Type in:
設(shè)置終端類型為AT386來避免VI編輯器的問題，輸入：
TERM=AT386; export TERM
3.        Mount root / file system:
　　　掛接根/文件系統(tǒng)
mount /dev/dsk/c0t0d0s0 /a
The command is for the first disk on the first SCSI controller. It varies from system to system. Consult Disks, partitions and slices under Solaris for details.
命令對應(yīng)于第一個SCSI控制器的第一個磁盤。它隨系統(tǒng)的不同而不同，詳細(xì)資料請參考Disks, partitions and slices under Solaris
4.        Determine the slice number of /usr file system:
　確定/usr文件系統(tǒng)的片編碼
grep /usr /a/etc/vfstab
You will see a line:
你將看到一行：
/dev/dsk/c0t0d0s4   /dev/rdsk/c0t0d0s4    /usr   ufs   1   no   logging
which means that the number of the /usr slice is 4.
表明/usr片編碼是4。
5.        Mount /usr file system:
　　掛接/usr文件系統(tǒng)
mount /dev/dsk/c0t0d0s4 /a/usr
6.        Rebuild /a/devices and /a/dev:
　　　重建　/a/devices和/a/dev
/usr/sbin/chroot /a /usr/sbin/devfsadm -C -v
/usr/sbin/chroot /a /usr/sbin/devfsadm -v
The first command cleans up invalid entries, the second creates new ones. -v stands for verbose mode. If you prefer to see first what is going to be changed without actually changing anything add -s option.
第一個命令行消除有問題的條目，第二個命令建立一個新的條目。－V參數(shù)對應(yīng)于詳細(xì)模式。如果你寧愿看第一個被改變的是什么沒有實際任何改變請加－s選項。
7.        Either, modify /a/etc/vfstab, or recreate soft links under /a/dev/dsk and /a/dev/rdsk, so that vfstab entries match appropriate slices on appropriate disks on the system. The second is more risky, but all customizations that involve disk device names are retained. Make sure that /a/dev/dsk links match /a/dev/rdsk links. Note that all those soft links can be removed and recreate with devfsadm as above safely.
　在更改/a/etc/vfstab,或在/a/dev/dsk和/a/dev/rdsk下重建軟件連接之一，所以vfstab條目匹配在系統(tǒng)中適當(dāng)?shù)拇疟P上的適當(dāng)?shù)钠�。第二個是相當(dāng)危險的，但是所有的定制包括保留的磁盤設(shè)備名。確信/a/dev/dsk連接匹配/a/dev/rdsk連接。注意那些所有的軟件連接能被devfsadm安全地刪除和重建。
8.        Unmount the hard disk
　　　卸載硬盤
　　　　　　
sync
umount /a/usr
umount /a
9.        Try to reboot from hard disk.
　　　　　　從硬盤重啟：
init 6
Note: Backup all of your data prior any modification to the system hardware which have direct relation with the hard disk, i.e. motherboard, disk controller including IDE or SCSI adapter.
注：在對直連有硬盤的系統(tǒng)硬件進行任何修改前備份你的所有數(shù)據(jù)。比方：主板，磁盤控制器（包括IDE或SCSI適配器）。

本文來自ChinaUnix博客，如果查看原文請點：http://blog.chinaunix.net/u/8146/showart_88124.html

matata

學(xué)習(xí)了！

多謝分享、、、、

充滿光的瞳孔

看了半天，我要ufsdump了系統(tǒng)文件，ufsrestore到另一個磁盤后，不知道怎么設(shè)置引導(dǎo)塊！如何用我的另一塊磁盤啟動系統(tǒng)�。。縶:3_186:}