My file system is (kind of) stuck as read-only reddit / freebsd ---------------------------------------------------------------------- wazzup7603 · 2023-03-11 02:02 Usually I try to look on online forums and wikis (especially since I also use arch) but I searched for this issue and all that came up were linux forums. Here is the situation: I have 2 USB drives: the first one is a generic USB drive which only holds the bootable installer. The other one is a SanDisk USB-C drive which holds the actual installation of FreeBSD and its file system and all that stuff. When I only have the USB-C SanDisk drive in, it boots into FreeBSD with the file system as read-only. However, when I boot into FreeBSD with BOTH the USB-C SanDisk and the Generic USB installer drive, the file system is read-write. Is this an issue involving mounting the hard disk incorrectly??? ---------------------------------------------------------------------- NerdVsGeek · 2023-03-11 05:31 Without logs, it's hard to say. Do you get all the way to a login screen when booting with both the USB-C and Generic USB? If yes, can you provide the output of the mount command and the contents of /etc/fstab? ---------------------------------------------------------------------- crest_ · 2023-03-11 14:56 Please share the output from `mount`, `gpart show -l` and `cat /etc/fstab`. ---------------------------------------------------------------------- wazzup7603 · 2023-03-11 17:40 Do you wanna see the output of those commands with just the USB-C drive or both the USB-C and the Generic USB drive? ---------------------------------------------------------------------- grahamperrin · 2023-03-11 17:44 Which version of FreeBSD, exactly? ---------------------------------------------------------------------- crest_ · 2023-03-11 17:46 If possible both. I **suspect** your `/etc/fstab` references the USB mass storage devices as /dev/da${NUMBER}. The number is just the order the kernel detected the devices in. In that case I would recommend assigning labels to your partitions (or file systems) and referencing them by those in `/etc/fstab`. The `bsdinstall` UFS install script still produces this fragile configuration, because it works most of the time, dealing with potentially conflicting names in hard for a shell script, and experienced greybeards just roll their eyes and fix the fstab or write their custom install script -> the low hanging fruit doesn't get fixed. ---------------------------------------------------------------------- wazzup7603 · 2023-03-11 20:38 Sorry, when I do that it no longer boots freebsd, it boots the installer. Would you be able to help me out still if I provided the /etc/fstab info when only thr USB-C drive is in? I can now only boot when only the USB-C drive is in ---------------------------------------------------------------------- wazzup7603 · 2023-03-11 20:39 Well something just changed I guess bc now when I use both USB drives it boots the installer instead. Would you like to see the /etc/fstab data with just the USB-C drive in? ---------------------------------------------------------------------- wazzup7603 · 2023-03-11 20:44 13.1-RELEASE ---------------------------------------------------------------------- NerdVsGeek · 2023-03-12 02:05 Can you boot the installer and then drop into a shell and run like u/crest_ suggested: gpart show -l Once this is know, we can look at next steps to get the other information.