Re: "cannot create /boot/grub/grub.cfg.new: Read-only file system" on a Power Mac G5
Lennart Sorensen <[email protected]>
| Newsgroups | gmane.linux.debian.ports.powerpc |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Aug 10, 2024 at 09:25:17PM +0300, ilko Iliev wrote: > Hello, > Whenever I'm trying to upgrade/install something I get the following errors. > I'd appreciate some pointers as to where to begin as I'm clueless on the matter. > > _______________________________________________________________________________________________________ apt-listchanges: Reading changelogs... > (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. > Error: Sub-process /usr/bin/dpkg returned an error code (1) So what do you have mounted as /boot and/or /boot/grub? I know some people in the past very incorrectly mounted their UEFI boot partion as /boot or /boot/grub and that can be a problem. Of course that doesn't apply to powerpc so I guess something else is the problem. If /boot/grub is readonly, then clearly something isn't mounted right.