Re: error with /usr/sbin/grub-mkconfig Read-only file system??
On 6/22/21 22:34, Dennis Clarke wrote:
> On 6/22/21 22:08, John Paul Adrian Glaubitz wrote:
>> Hello!
>>
>> See this discussion: https://lists.debian.org/debian-powerpc/2021/06/msg00006.html
>>
>> Adrian
>
> That was a fast reply !
>
> Thank you ... however what am I doing wrong here ??
>
> enceladus#
> enceladus# apt show hfsprogs
> Package: hfsprogs
> Version: 540.1.linux3-4
> Priority: optional
> Section: non-free/otherosfs
> Maintainer: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> Installed-Size: 555 kB
> Depends: libc6 (>= 2.28), libssl1.1 (>= 1.1.0)
> Homepage: https://opensource.apple.com/source/diskdev_cmds/
> Download-Size: 162 kB
> APT-Sources: http://deb.debian.org/debian-ports unreleased/main ppc64
> Packages
> Description: mkfs and fsck for HFS and HFS+ file systems
> The HFS+ file system used by Apple Computer for their Mac OS is
> supported by the Linux kernel. Apple provides mkfs and fsck for
> HFS+ with the Unix core of their operating system, Darwin.
> .
> This package is a port of Apple's tools for HFS+ filesystems.
> .
> For users, HFS+ seems to be a good compromise to carry files between
> MacOS X and Linux Machines, as HFS+ doesn't suffer the problems of
> FAT32 like:
> .
> * huge space waste (in slack space as devices grow faster);
> * ability to create files that are more than 4GB in size (especially
> good for those working with multimedia and that need to carry large
> ISO files);
> * ability to use case preserving (and even sensitivity!);
> * ability to use uid's and gid's on the filesystem.
> .
> Users in general can enjoy such benefits since it is expected to have
> more HFS+ filesystems in use, as Apple has announced Macintoshes for
> ix86-64, besides the filesystem being already supported by PowerPC
> systems since the beginning.
>
> enceladus# apt-get install hfsprogs
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> The following NEW packages will be installed:
> hfsprogs
> 0 upgraded, 1 newly installed, 0 to remove and 7 not upgraded.
> Need to get 162 kB of archives.
> After this operation, 555 kB of additional disk space will be used.
> Get:1 http://deb.debian.org/debian-ports unreleased/main ppc64 hfsprogs
> ppc64 540.1.linux3-4 [162 kB]
> Fetched 162 kB in 1s (273 kB/s)
> Selecting previously unselected package hfsprogs.
> (Reading database ... 57475 files and directories currently installed.)
> Preparing to unpack .../hfsprogs_540.1.linux3-4_ppc64.deb ...
> Unpacking hfsprogs (540.1.linux3-4) ...
> Setting up hfsprogs (540.1.linux3-4) ...
> Processing triggers for man-db (2.9.4-2) ...
> enceladus#
>
>
> Is /dev/sda2 read only ?
>
> enceladus# cat /proc/mounts | grep 'grub'
> /dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
>
> YES .. that is read only.
>
> enceladus# mount -o remount,rw /boot/grub
> enceladus# cat /proc/mounts | grep 'grub'
> /dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
>
> That seems to fail silently.
>
> enceladus# mount -o remount,rw /boot/grub
> enceladus# echo $?
> 0
> enceladus#
>
> No error at all but we see :
>
> enceladus# cat /proc/mounts | grep 'grub'
> /dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
> enceladus#
>
> Do I have to specify -t hfs here ?
>
> enceladus# mount -v -t hfs -o remount,rw /boot/grub
> mount: /dev/sda2 mounted on /boot/grub.
> enceladus# cat /proc/mounts | grep 'grub'
> /dev/sda2 /boot/grub hfs ro,relatime,uid=0,gid=0 0 0
> enceladus#
>
> So am I missing something here ?
>
>
* * * The magic self reply here * * *
dmesg says :
[531474.917470] hfs: filesystem was not cleanly unmounted, running
fsck.hfs is recommended. leaving read-only.
Which makes no sense given that this is on UPS and never merely crashes
but whatever.
enceladus# umount /dev/sda2
enceladus# mount -v | grep 'sda2'
enceladus# fsck.hfs -d -q /dev/sda2
** /dev/sda2 (NO WRITE)
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
Executing fsck_hfs (version 540.1-Linux).
volume type is HFS
primary MDB is at block 2 0x02
alternate MDB is at block 499999 0x7a11f
primary VHB is at block 0 0x00
alternate VHB is at block 0 0x00
sector size = 512 0x200
VolumeObject flags = 0x19
total sectors for volume = 500001 0x7a121
total sectors for embedded volume = 0 0x00
QUICKCHECK ONLY; FILESYSTEM DIRTY
enceladus#
OKay well there we see it.
enceladus#
enceladus# fsck.hfs -d /dev/sda2
** /dev/sda2
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
Executing fsck_hfs (version 540.1-Linux).
** Checking HFS volume.
The volume name is untitled
** Checking extents overflow file.
** Checking catalog file.
Unused node is not erased (node = 179)
Unused node is not erased (node = 226)
Unused node is not erased (node = 235)
.
.
. a whole whack of those :)
.
Unused node is not erased (node = 375)
Unused node is not erased (node = 376)
Unused node is not erased (node = 378)
Unused node is not erased (node = 383)
** Checking catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
Verify Status: VIStat = 0x0000, ABTStat = 0x0000 EBTStat = 0x0000
CBTStat = 0x0004 CatStat = 0x00000000
** Repairing volume.
** Rechecking volume.
** Checking HFS volume.
The volume name is untitled
** Checking extents overflow file.
** Checking catalog file.
** Checking catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
** The volume untitled was repaired successfully.
enceladus#
enceladus# grep 'grub' /etc/fstab
# /boot/grub was on /dev/sda2 during installation
UUID=221a37cd-0cfb-3f7a-91da-78edee6f1382 /boot/grub hfs
defaults 0 2
enceladus# mount -v /boot/grub
mount: /dev/sda2 mounted on /boot/grub.
enceladus#
enceladus# cat /proc/mounts | grep 'grub'
/dev/sda2 /boot/grub hfs rw,relatime,uid=0,gid=0 0 0
enceladus#
Neato. Thank you Sir Adrian !
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
Reply to: