On 1/8/19 14:15, Mark Cave-Ayland wrote:
Do you see the fsck error on all filesystems or just /dev/sda4?
I only have one HFS (actually /dev/sda2) on the used disk. And the
`fsck.hfs` errors happen with both clean and damaged HFSes.
I'd be interested to
do a side-by-side comparison with the same filesystem image on my local G4 mini
vs.
your G5 to help work out what is happening, if it's something you can make
available?
I already tried that, `fsck.hfs` works on a G4 (Mac mini G4 here, too)
and can both check and repair clean/damaged HFSes on the very same disk.
See [1] for the process, where I first made sure that the HFS is ok on a
Mac mini G4 and then tried to check it on a G5 with (1) a 64 bit version
of fsck.hfs - which segfaulted - and (2) a 32 bit version of fsck.hfs -
which worked the same way as it did on the G4.
[1]: https://lists.debian.org/debian-powerpc/2019/01/msg00023.html
Therefore think the problem is not the state of the HFS, as I got the
segfaults for both damaged and undamaged HFSes. Quick test: Just create
a HFS on a G4 (e.g. using `parted` and `mkfs.hfs`) and try to check it
on a G5 with the 64 bit version of `fsck.hfs`.
See:
```
root@mac-mini:/# partx /dev/sdb
NR START END SECTORS SIZE NAME UUID
1 1 63 63 31.5K Apple
2 64 251953 251890 123M hfs
3 251954 488281249 488029296 232.7G Extra
root@mac-mini:/# mkfs.hfs -h /dev/sdb2
Initialized /dev/sdb2 as a 122 MB HFS volume
root@mac-mini:/# fsck.hfs -d /dev/sdb2
** /dev/sdb2
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
** Checking HFS volume.
** Checking Extents Overflow file.
** Checking Catalog file.
** Checking Catalog hierarchy.
** Checking volume bitmap.
** Checking volume information.
** The volume untitled appears to be OK.
root@powermac-g5:~# partx /dev/sdb
NR START END SECTORS SIZE NAME UUID
1 1 63 63 31.5K Apple
2 64 251953 251890 123M hfs
3 251954 488281249 488029296 232.7G Extra
root@powermac-g5:~# fsck.hfs -d /dev/sdb2
** /dev/sdb2
Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K.
** Checking HFS volume.
Segmentation fault
```
Cheers,
Frank
