Re: "cannot create /boot/grub/grub.cfg.new: Read-only file system" on a Power Mac G5
Hi Adrian,
Thanks for the suggestion but regarding:
>You must install the package “hfsprogs”, then run:
>
># umount /boot/grub
># fsck.hfs -y /dev/sda2
># mount -a
># dpkg-configure -a
Unfortunately that doesn't work because I can't install absolutely anything, it always fails with the same error as stated in OP:
sudo apt-get install hfsprogs
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
linux-image-6.1.0-9-powerpc64
The following NEW packages will be installed:
hfsprogs
0 upgraded, 1 newly installed, 1 to remove and 991 not upgraded.
3 not fully installed or removed.
Need to get 0 B/163 kB of archives.
After this operation, 301 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 131680 files and directories currently installed.)
Removing linux-image-6.1.0-9-powerpc64 (6.1.27-1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.1.0-9-powerpc64
/etc/kernel/postrm.d/zz-update-grub:
/usr/sbin/grub-mkconfig: 270: cannot create /boot/grub/grub.cfg.new: Read-only file system
run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 2
dpkg: error processing package linux-image-6.1.0-9-powerpc64 (--remove):
installed linux-image-6.1.0-9-powerpc64 package post-removal script subprocess returned error exit status 1
dpkg: too many errors, stopping
Errors were encountered while processing:
linux-image-6.1.0-9-powerpc64
Processing was halted because there were too many errors.
E: Sub-process /usr/bin/dpkg returned an error code (1)
> On Aug 12, 2024, at 12:48 PM, ilko Iliev <ilko@gyuvetch.bg> wrote:
>
>
> >You could try doing: mount -o remount,rw /boot/grub
> >
> >Maybe that will make it read write and hence able to allow grub to update.
>
> Thanks for the suggestion but issuing that command didn't change it to 'rw'.
> Maybe it's not worth it pursuing it furthers.
Errm, I gave you the exact instructions how to fix your issue. While I appreciate others trying to help, the off-topic texts seem to have buried my answer.
Adrian
Reply to: