[ydl-gen] Re: HFS+ mount is read only -- how to make RW? (YDL 4.0.1)

Danny Hembree danny-hembree at dynamical.org
Fri Dec 2 18:06:22 MST 2005


Jeffrey, just so you know your not crazy, I'm using YDL 4.0.1 on a dual
processor G5 and cannot mount the filesystem slice from an OSX 10.3.9
server disk.

here's my pdisk

Partition map (with 512 byte blocks) on '/dev/sdb'
 #:                type name                     length   base      (
size )
 1: Apple_partition_map Apple                        63 @ 1
 2:          Apple_Boot eXternal booter          262144 @ 64       
(128.0M)
 3:          Apple_HFSX Apple_HFSX_Untitled_2 319910832 @ 262208   
(152.5G)
 4:          Apple_Free Extra                        16 @ 320173040
 
Device block size=512, Number of Blocks=320173056 (152.7G)

# mount /dev/sdb3 /osx -thfsplus
mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
       or too many mounted file systems
DeviceType=0x0, DeviceId=0x0

curiously, the boot slice, sdb2 does mount. Perhaps it's something to do
with the journaling ?



On Fri, 2005-12-02 at 15:17, Jeffrey Paul Burger wrote:
> Thanks!... And I'm still in trouble. Here's what I get from pdisk:
> 
> Partition map (with 512 byte blocks) on '/dev/sda'
>  #:                type name        length   base      ( size )
>  1: Apple_partition_map Apple           63 @ 1
>  2:     Apple_Bootstrap untitled      2048 @ 64        (  1.0M)
>  3:     Apple_UNIX_SVR2 untitled 394009666 @ 2112      (187.9G)
>  4:     Apple_UNIX_SVR2 swap       4080510 @ 394011778 (  1.9G)
>  5:     Apple_UNIX_SVR2 untitled    204800 @ 398092288 (100.0M)
> 
> Device block size=512, Number of Blocks=398297088 (189.9G)
> DeviceType=0x0, DeviceId=0x0
> 
> pdisk: Bad data in block 2 from '/dev/sdb'
> pdisk: can't open file '/dev/hda'  (No medium found)
> 
> Somebody off-thread speculated that " it could be with the uid.  HFS doesn't
> have the same ownership/permissions structure and the default is that only
> root can write, but you can change this with mount options such as user,
> umask, uid, etc." Unfortunately, this doesn't mean much to me though. But
> since  to mount the errant disk still give me "Wrong fs type, bad option,
> bad superblock on /dev/sdb or too many mounted filesystems", I'm thinking
> that I somehow told it that the file system is not HFS+... in which case I'm
> hoping that there's some way to tell it that it is indeed HFS+ and access
> the data again. 
> 
> Any and all help is greatly appreciated!
> 
> Thanks!
> 
> Jeff
> 
> Date: Thu, 1 Dec 2005 23:47:52 -0500
> From: Eric Dunbar <eric.dunbar at gmail.com>
> Subject: Re: [ydl-gen] Re: HFS+ mount is read only -- how to make RW?
>     (YDL    4.0.1)
> To: Yellow Dog Linux General Discussion List
>     <yellowdog-general at lists.terrasoftsolutions.com>
> Message-ID:
>     <77520bee0512012047m2b611949oa17aa9b3adcb6954 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Hmm. Not good, but, maybe there's hope.
> 
> Ok, I ain't no expert on partitions but shouldn't you have a number to
> go along with your sdb?
> 
> In your case, you're on the SCSI bus (right?) and are on the second
> drive (ergo b). Take a look at your partition table using pdisk
> (/sbin/pdisk -l /dev/sdb). What does it say?
> 
> In my case my drive resides at hdc and the relevant HFS+ partition is
> #7. So my mount command would be:
> 
> mount /dev/hdc7 /mnt/macosx -t hfsplus
> 
> So for you it would be something like:
> mount /dev/sdb# /mnt/macos -t hfsplus
> 
> I would strongly recommend that you do things read-only until you've
> got the problem licked:
> 
> mount/dev/sdb# /mnt/macos -r -thfsplus (NOTE: the space doesn't make a
> difference)
> 
> Also, /mnt/whatever is merely your "mount point". You have a "real"
> directory (/mnt/whatever) on your drive and you reference another
> volume to that mount point when you mount the other volume.
> 
> Thus, doing hpmount /mnt/macos would do nothing.
> 
> PS I'm guessing that hpmount didn't like the fact that you referenced
> your _whole_ drive.
> 
> Good luck.
> 
> Eric.
> 
> On 12/1/05, Jeffrey Paul Burger <jeff at sedona.net> wrote:
> > Red Alert! Now I've lost access to my HFS+ drive from both Linux and OS X!!!
> > Help!!!
> >
> > Background: This is a dual boot G5 running YDL 4.0 and OS 10.4. I'm a Linux
> > newbie. A friend (who no longer lives where I do) gave me the magic to mount
> > the Mac OS disk from YDL at /dev/sdb, so that's the destination I've been
> > using. And I have a "macos" folder in my mnt directory. Until now, I've been
> > successfully mounting and reading from the HFS+ drive using "mount /dev/sdb
> > /mnt/macos -t hfsplus". (Strangely, until I corrected it today, the exec
> > file my friend wrote was missing a space:  "... -thfsplus" and it still
> > mounted and read.) Anyway, the problem came when trying to follow
> > instructions from this thread to enable writing to the HFS+ disk from YDL as
> > well.
> >
> > Pursuant to earlier messages in this thread, I found hfsplus on my system
> > and invoked in. The man page essentially says:
> >
> > hpmount [...] source-path
> >
> > Not knowing whether source-path meant /mnt/macos or /dev/sdb, I tried both.
> > I know that hpmount /dev/sdb gave me the following message (hpmount
> > /mnt/macos may have been identical but I can't be sure now):
> >
> > "Warning. You are about to open /dev/sdb for writing. Are you sure you want
> > to do this (y/n)?"
> >
> > I responded affirmatively and received:
> >
> > "hpmount: Neither wrapper nor native HFS+ volume header found (unknown error
> > 4294967295)"
> >
> > I went ahead anyway with the usual "mount /dev/sdb /mnt/macos -t hfsplus"
> > and received:
> >
> > "Wrong fs type, bad option, bad superblock on /dev/sdb or too many mounted
> > filesystems"
> >
> > After trying several variations on this theme (and getting the same error
> > messages), I decided to see if I could boot from that volume normally under
> > OS X. After the initial switch screen for Linux vs. OS X, followed by the
> > gray Apple logo on the white screen, the logo is replaced with a large gray
> > international symbol for "no" (circle with a slash across it). And the
> > circular progress meter below just spins forever.
> >
> > So I now have two problems: 1) how do I get my OS X boot drive back? 2) what
> > did I do wrong (or what do I need to do right) to access this drive from YDL
> > once it's resurrected?
> >
> > Any and all help is greatly, greatly appreciated. And please keep in mind
> > that I only know enough to make myself dangerous (obviously!) and clear
> > explanations are very helpful.
> >
> > Thank you!
> >
> > Jeffrey
> 
> 
> 
> 
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general at lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
> HINT: to Google archives, try  '<keywords> site:terrasoftsolutions.com'



More information about the yellowdog-general mailing list