How to force read-only after an update from 2.2.5 to 2.2.6 on NanoBSD image?

[vizi0n]

Hi all,

I have updated my Watchguard X750e from 2.2.5 to 2.2.6 today. It is running the NanoBSD version on a CompactFlash and now (since the update) the filesystem defaults to RW instead of RO. Where can I toggle it to be RO by default on boot? Changing it under Diagnostics / NanoBSD is only until the next reboot

Thanks!

Some info:

Bootup slice is currently: ada0s2

[2.2.6-RELEASE][admin@pfSense.localdomain]/root: cat /etc/fstab 
/dev/ufs/pfsense1 / ufs ro,sync,noatime 1 1
/dev/ufs/cf /cf ufs ro,sync,noatime 1 1

[phil.davis]

You should uncheck "Keep media mounted read/write at all times".
If that does not work after reboot, then there is some problem in the boot process - the file system should be switched to read only when the boot is finished doing its stuff.

[vizi0n]

@phil.davis:

You should uncheck "Keep media mounted read/write at all times".
If that does not work after reboot, then there is some problem in the boot process - the file system should be switched to read only when the boot is finished doing its stuff.

The problem is that the checkbox isn't checked. I'll keep fiddling around, but tomorrow! :)

[jimp]

The system must believe something is still attempting to write. You can try triggering the switch to RO multiple times until it switches back.

On the screen that Phil posted, does your "reference count" show a value greater than 0?

[vizi0n]

@jimp:

The system must believe something is still attempting to write. You can try triggering the switch to RO multiple times until it switches back.

On the screen that Phil posted, does your "reference count" show a value greater than 0?

Hi jimp,

There is no "reference count" on my router's page. If I click set to RO it does set it. Its just that after a reboot it is back to RW again.


[vizi0n]

Oh well… I did not find the root cause of it, but I backed up my settings, factory defaults, restore settings, and now its read-only after boot.

Go figure...

:o