ASX: thanks for your patient response. Bottom line: it worked.
As documentation for anyone else attempting this, I did this:
Code: Select all
root@ghostbsd:/home/ghostbsd # gpart show -p
=> 34 312581741 ada0 GPT (149G)
34 2048 ada0p1 bios-boot (1.0M)
2082 6 - free - (3.0K)
2088 308432896 ada0p2 freebsd-ufs (147G)
308434984 4136960 ada0p3 freebsd-swap (2.0G)
312571944 9831 - free - (4.8M)
=> 9 947047 cd0 MBR (1.8G)
9 947047 - free - (1.8G)
=> 9 947047 iso9660/GhostBSD MBR (1.8G)
9 947047 - free - (1.8G)
=> 63 15695808 da5 MBR (7.5G)
63 15695808 da5s1 !12 [active] (7.5G)
root@ghostbsd:/home/ghostbsd #
root@ghostbsd:/home/ghostbsd # mount /dev/ada0p2 /dev
mount: /dev/ada0p2: R/W mount of / denied. Filesystem is not clean - run fsck. Forced mount will invalidate journal contents: Operation not permitted
root@ghostbsd:/home/ghostbsd # fsck -y /dev/ada0p2
** /dev/ada0p2
USE JOURNAL? yes
** SU+J Recovering /dev/ada0p2
** Reading 33554432 byte journal from inode 4.
RECOVER? yes
** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.
WRITE CHANGES? yes
** 24 journal records in 1536 bytes for 50.00% utilization
** Freed 0 inodes (0 dirs) 0 blocks, and 0 frags.
***** FILE SYSTEM MARKED CLEAN *****
root@ghostbsd:/home/ghostbsd # mount -w /dev/adaop2 /home/ghostbsd
My problem was initiated by an attempt to change the slim login screen.
I cut out the file background.png, and replaced it with another labelled
background.jpg. When I attempted to reboot, slim would not run. But once
I mounted the drive as above, I was able to open Caja, cut and paste it
back in, and reboot perfectly.
I assume that any replacement image for slim MUST be labelled background.png,
and truly be a png image. If I bork the system again, I now know how to fix it.
Thanks again!