Bug 172849 - Missing fstab in rootfs leads to problems
Summary: Missing fstab in rootfs leads to problems
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: 10.0-CURRENT
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-18 12:40 UTC by yerenkow
Modified: 2018-01-03 05:13 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description yerenkow 2012-10-18 12:40:00 UTC
If you have single media, with missing fstab file (e.g. - no such file /etc/fstab)

Then boot will throw you forcedly to single user mode, and you will need interactively enter rootfs device, like

ufs:ada0s1 rw

More of that, options are really ignored, rootfs is always in RO, and 
mount -u / not working, so you can't set rootfs writeable, to create fstab.

This is very obscure situation, which required from you some external media to boot from just to mount your disk and create fstab with / record.

Currently even
mount -o rw -u /dev/ada0s1a /
NOT working.

Fix: 

1. Fix options in mountroot prompt, e.g.
ufs:ada0s1 rw
will mount in RW, not in RO, so you'll be able to create fstab. (Or if UFS root can not be mounted in rw, change help, it's lying to me)

2. Deal with mount -u / when there's no fstab exists (make it work).
How-To-Repeat: Get some FreeBSD, erase fstab, boot.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:23 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped