upstream/opnsense-src
1
0
Fork 0
mirror of https://github.com/opnsense/src.git synced 2026-06-14 19:20:18 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

crash.8: update a little

Browse source 
Replace "cannot mount root" (which is no longer a panic) with a brief
description of the mountroot> prompt, and recommend using "system
install media" rather than the fixit floppy.

Remove "timeout table full" entirely since this panic no longer exists.

MFC after:	3 days
Reviewed by:	ziaee
Differential Revision:	https://reviews.freebsd.org/D51512
This commit is contained in:
Lexi Winter 2025-07-25 14:59:58 +01:00
parent 5c3081bda9
commit c9868af774
1 changed files with 14 additions and 18 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
share/man/man8/crash.8
View file

@ -30,7 +30,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.Dd July 23, 2011
.Dd July 25, 2025
.Dt CRASH 8
.Os
.Sh NAME
@ -71,18 +71,19 @@ Left unstated in all cases is the possibility that hardware or software
error produced the message in some unexpected way.
.Pp
.Bl -diag -compact
.It "cannot mount root"
This panic message results from a failure to mount the root file system
during the bootstrap process.
Either the root file system has been corrupted,
or the system is attempting to use the wrong device as root file system.
Usually, an alternate copy of the system binary or an alternate root
file system can be used to bring up the system to investigate.
Most often
this is done by the use of the boot floppy you used to install the system,
and then using the
.Dq fixit
floppy.
.It Mounting from <device> failed with error <err>
The system was unable to mount the configured root filesystem.
Either the root filesystem has been corrupted,
or the system is attempting to use the wrong device as root filesystem.
.Pp
This is not a panic message; rather it is followed by an interactive
.Sy mountroot>
prompt where the operator can list detected devices and filesystems,
and select an alternative root filesystem to mount.
Alternatively, the system can be booted from recovery media to repair
the situation.
The system install media provides a live environment which is suitable
for this task.
.Pp
.It "init: not found"
This is not a panic message, as reboots are likely to be futile.
@ -108,11 +109,6 @@ after a crash, hardware failures, or other condition that should not
normally occur.
A file system check will normally correct the problem.
.Pp
.It "timeout table full"
This really should not be a panic, but until the data structure
involved is made to be extensible, running out of entries causes a crash.
If this happens, make the timeout table bigger.
.Pp
.\" .It "trap type %d, code = %x, v = %x"
.\" An unexpected trap has occurred within the system; the trap types are:
.\" .Bl -column xxxx -offset indent