Well, that fixed my problem! I guess there's a flag that can get corrupted and attempting to mount it with hpmount probably fixes it (I'm guessing).
Anyway, the offending partition was on /dev/hdc7 (in my case), mounted at /mnt/macosx. So, to unmount it (since it's auto-mounted at boot): umount /mnt/macosx hpmount /dev/hdc7 mount /dev/hdc7 /mnt/macosx -t hfsplus Read-write is back! Thanks for being my sounding board. Eric. On 11/25/05, Eric Dunbar <eric.dunbar at gmail dot com> wrote: > Well, I did a little Googling and found my answer. > > It seems fsck.hfsplus does not exist for Linux (at least, that was as > of beginning of 2004... doubt that's changed in the interrim). Instead > a work-around was reported here: > <http://lists.debian.org/debian-powerpc/2004/01/msg00984.html> that I'll try: > > From: Sebastian Henschel <debian at kodeaffe dot de> > Date: Mon, 26 Jan 2004 16:01:15 +0100 > "well, i have exactly the same problem. but i found a work around for that: > mount the hfs+ partition via hpmount from the package hfsplus > (http://www.penguinppc.org/usr/ftp/pub/hfsplus/hfsplus.src.tar.gz). > > this by itself does not mount the partition at all, but stops with an > error message (v1.0.4). though something is done with that partition, > because afterwards, i can mount it for writing again in the regular > way with "mount -t hfsplus" (recent benh-2.6 kernel)." > > Eric. > > On 11/25/05, Eric Dunbar <eric.dunbar at gmail dot com> wrote: > > Thanks for your response. > > > > Found the error message in /var/log/messages: > > HFS+-fs warning: Filesystem was not cleanly unmounted, running > > fsck.hfsplus is recommended. mounting read-only. > > > > One problem. fsck.hfsplus seems to be missing :-( (fsck reports: > > fsck 1.35 (28-Feb-2004) > > fsck: fsck.hfsplus: not found > > ./fsck: Error 2 while executing fsck.hfsplus for /dev/hdc7 > > ) > > > > How do I get fsck.hfsplus? > > > > All my system has in /sbin are: > > dosfsck > > e2fsck > > fsck > > fsck.cramfs > > fsck.ext2 > > fsck.ext3 > > fsck.msdos > > fsck.vfat > > > > Thanks, Eric. > > > > On 11/25/05, peter.g.harper at magnox.co.uk <peter.g.harper at > > magnox.co.uk> wrote: > > > > > > Sometimes the system will mount filesystems ro if it problems when > > > mounting > > > it > > > at boot time. Look in /var/log/messages? Unmount the disk, fsck it them > > > remount it? > > > > > > Peter > > > > > Subject: [ydl-gen] HFS+ mount is read only -- how to make RW? (YDL > > > 4.0.1) > > > Hello, I have an HFS+ partition that I always mount on boot. It has > > > now become read-only and I would like to be able to write to it as > > > well. > > > > > > Until recently I was able to use it to store files on this partition. > > > Now it's become read-only (after a power failure, I suspect). > > > > > > This happened once to me under YDL 3.0.1 when I caused YDL 3 to kernel > > > panic using df (or was that du) on the HFS+ partition (solution: > > > reformat the partition in OS X). > > > > > > That problem with du (or df) was fixed in YDL 4. > > > > > > Now, it seems that somehow my HFS+ partition has been "damaged" again, > > > and I can't write to it even though mount says it's rw: > > > > > > /dev/hdc8 on / type ext3 (rw) > > > none on /proc type proc (rw) > > > none on /sys type sysfs (rw) > > > none on /dev/pts type devpts (rw,gid=5,mode=620) > > > none on /dev/shm type tmpfs (rw) > > > /dev/hdc10 on /home type ext3 (rw) > > > /dev/hdc7 on /mnt/macosx type hfsplus (rw) > > > > > > > > > Does anyone know what the problem is and/or how to fix it (i.e. make > > > it read-write again)? > > > > > > Eric. > _______________________________________________ yellowdog-general mailing list [email protected] http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
