On Wed, Jun 9, 2021, at 2:41 PM, John Paul Adrian Glaubitz wrote:
> Hello Rick!
>
> On 6/9/21 11:34 PM, Rick Thomas wrote:
> > You're right that /boot/grub somehow has gotten read-only. I didn't do that
> > myself, so something else must have done that. Have you any clue you can
> > share
> > with me as to which package I should re-file this report against?
> You are too quick in assuming that there might be a bug somewhere. We don't
> know
> yet how and why the filesystem was re-mounted read-only. You should check your
> log files for any error messages or warnings.
>
> Normally the kernel warns you when a filesystem gets remounted read-only.
>
> Adrian
For what it's worth, the original install was not from February. It was the
April 17th iso images instead.
Searching "journalctl -b" I find:
> Jun 09 01:42:55 kmac kernel: hfs: filesystem was not cleanly unmounted,
> running fsck.hfs is recommended. mounting read-only.
I did have a brief power outage recently. Maybe that's what caused the "not
cleanly unmounted".
I'll try unmounting it and running fsck.hfs...
Hmmm...
> root@kmac:~# fsck.hfs -f -C0 /boot/grub
> -bash: fsck.hfs: command not found
Am I missing a package somewhere?
Rick
