1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.POWERP

  • =?UTF-8?Q?Re:_Bug#989645:_/usr/sbin/grub-mkconfig:_dpkg:_error_processi

    From Rick Thomas@21:1/5 to John Paul Adrian Glaubitz on Thu Jun 10 00:00:02 2021
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rick Thomas@21:1/5 to Rick Thomas on Thu Jun 10 00:40:01 2021
    On Wed, Jun 9, 2021, at 2:58 PM, Rick Thomas wrote:


    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

    Yep, I was missing hfsprogs. I installed that and was able to do the fsck.hfs, then remounted /boot/grub and all was well.

    So the only remaining question is "why was hfsprogs not automatically install on a G5 PowerMac?"

    Thanks to all for your help in fixing this!

    Rick

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Rick Thomas@21:1/5 to John Paul Adrian Glaubitz on Fri Jun 11 03:40:02 2021
    On Wed, Jun 9, 2021, at 9:42 PM, John Paul Adrian Glaubitz wrote:
    On 6/10/21 12:14 AM, Rick Thomas wrote:
    So the only remaining question is "why was hfsprogs not automatically install on a G5 PowerMac?"

    See: https://lists.debian.org/debian-powerpc/2021/04/msg00129.html

    and: https://lists.debian.org/debian-powerpc/2021/05/msg00012.html


    Thanks. Now I understand the situation. I'll just add "install hfsprogs" to my list of things I have to do after installing on a PowerPC Mac.

    Enjoy!
    Rick

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)