I would suggest you run an fsck on the filesystem and see if there are
any problems.
Filesystems may be considered "required" for the system to function and
be mounted read-only when problems are detected, to prevent further
problems from developing while allowing the system to run.
Bob
On 5/7/23 05:54 PM, Ben Westover wrote:
Hello,
When I ran apt upgrade on my iMac G3, the kernel and GRUB packages
failed to configure. The step that failed in each case was update-grub
or grub-install, which failed when trying to write to the /boot/grub
HFS partition because it's a "Read-only filesystem."
Investigating /etc/fstab, even though it doesn't say to mount that
partition read-only, it was mounted as "ro,relatime,uid=0,gid=0". I
tried running `mount -o remount,rw`, but it still mounted as
read-only. I also tried mounting it in a non-Debian live environment
[1], using the rw option explicitly, but it was still mounted with
those same options.
It now makes sense why writing to the disk fails, as it seems any HFS
mount is automatically read-only, but why is this only now breaking
kernel upgrades? It can't have been a recent change to HFS mounting,
since my live environment's ISO was from December 2022. Does anyone
know what the problem here could be?
Thanks,
--
Ben Westover
[1] https://archlinuxpower.org
