Source string Read only

(itstool) path: sect3/para
Context English State
At the prompt asking for a root file system to mount, any device that contains a valid root file system can be entered. If <filename>/etc/fstab</filename> is set up correctly, the default should be something like <literal>ufs:/dev/gvinum/root</literal>. A typical alternate choice would be something like <literal>ufs:da0d</literal> which could be a hypothetical partition containing the pre-<filename>vinum</filename> root file system. Care should be taken if one of the alias <literal>a</literal> partitions is entered here, that it actually references the subdisks of the <filename>vinum</filename> root device, because in a mirrored setup, this would only mount one piece of a mirrored root device. If this file system is to be mounted read-write later on, it is necessary to remove the other plex(es) of the <filename>vinum</filename> root volume since these plexes would otherwise carry inconsistent data.
Only Primary Bootstrap Loads
If <filename>/boot/loader</filename> fails to load, but the primary bootstrap still loads (visible by a single dash in the left column of the screen right after the boot process starts), an attempt can be made to interrupt the primary bootstrap by pressing <keycap>space</keycap>. This will make the bootstrap stop in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/boot.html#boot-boot1">stage two</link>. An attempt can be made here to boot off an alternate partition, like the partition containing the previous root file system that has been moved away from <literal>a</literal>.
Nothing Boots, the Bootstrap Panics
This situation will happen if the bootstrap had been destroyed by the <filename>vinum</filename> installation. Unfortunately, <filename>vinum</filename> accidentally leaves only 4 KB at the beginning of its partition free before starting to write its <filename>vinum</filename> header information. However, the stage one and two bootstraps plus the bsdlabel require 8 KB. So if a <filename>vinum</filename> partition was started at offset 0 within a slice or disk that was meant to be bootable, the <filename>vinum</filename> setup will trash the bootstrap.
Similarly, if the above situation has been recovered, by booting from a <quote>Fixit</quote> media, and the bootstrap has been re-installed using <command>bsdlabel -B</command> as described in <link xlink:href="@@URL_RELPREFIX@@/doc/en_US.ISO8859-1/books/handbook/boot.html#boot-boot1"/>, the bootstrap will trash the <filename>vinum</filename> header, and <filename>vinum</filename> will no longer find its disk(s). Though no actual <filename>vinum</filename> configuration data or data in <filename>vinum</filename> volumes will be trashed, and it would be possible to recover all the data by entering exactly the same <filename>vinum</filename> configuration data again, the situation is hard to fix. It is necessary to move the entire <filename>vinum</filename> partition by at least 4 KB, in order to have the <filename>vinum</filename> header and the system bootstrap no longer collide.


No matching activity found.

Browse all component changes

Things to check


The string is used as plural, but not using plural forms



English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect3/para
No labels currently set.
Source string location
Source string age
9 months ago
Translation file
, string 187