Critical issues with 2.3CE nanobsd amd64 4g on SD card
-
For those who are seeing "Device busy" or similar and unable to force the disk read-write, try the following (preferably from the console):
umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf
Not something we'd normally recommend but somehow it seems that just the /cf slice is getting wedged for some people at the OS level.
Once that is done, set the permanent RW flag on Diagnostics > NanoBSD.
Jimp, is this safe to do over SSH from a LAN computer that I am RDP'd into? (I am not onsite)
-
umount -f /cf; fsck -t ufs -y /cf; mount -f -o rw /cf
Jimp, is this safe to do over SSH from a LAN computer that I am RDP'd into? (I am not onsite)
We have done that exact thing remotely several times with no ill effects, but there is always a chance it could go sideways so I can't say it's completely safe.
