Mac-on-Linux: Mac OSX partition locked? How do I unlock?

Chris Kastorff yellowdog-general@lists.terrasoftsolutions.com
Sun, 22 Aug 2004 22:53:28 -0400


	-Chris K.
On Aug 21, 2004, at 9:05 PM, Roger Scow wrote:

> Okay, I have two mol logs in /var/log.  I'm not sure I'm supposed to.
> The interesting thing is that it shows dev/hda9 as locked.  It doesn't
> show being mounted in linux.  How do I unlock it?
>
> I think the mol.0.log is from the initial load of YDL.  I removed and
> reloaded, and made changes that are reflected in mol.1.0.  xvideo isn't
> running, console is, which is good.  The change in RAM is there.  The
> problems with the console.kbd, etc. are gone.  The video modes are
> modified to reflect the one that I have.
>
> Sound card is still not recognized ... I get startup chimes, system
> sounds, etc., but a CD in the CDROM drive plays without sound.  I can
> get the system to recognize the card when I run Soundcard Detection, 
> but
> it doesn't show up in Info System.
>
> Anyway:
>
> Here is cat /var/log/mol.1.log:
>
>
>> # cat mol.1.log
>> --snip--
>> MOL SCSI controller registered
>>
>>     /dev/sg0 SCSI-<0:0:0> CD/DVD TOSHIBA  DVD-ROM SD-R2212 1P19
>>
>>     HFS+ /dev/hda9                       <rw> 66083 MB
>> ------> The volume '/dev/hda9' is locked
>> No volumes found in '/dev/hdb'
>> No volumes found in '/dev/sda'
>> No volumes found in '/dev/sdb'
>>
>>
>>>> ==================================================
>>>> MacOS X Boot Loader 1.1.18
>>>> Candidate boot volume: /mol-blk@0/disk@0:0
>>>> /mol-blk@0/disk@0:0,\mach_kernel (3859004 bytes)
>>>> /mol-blk@0/disk@0:0,\System\Library\Extensions.mkext
>>>> ==================================================
>>
>> <*> SCSI driver v1.03
>> <*> Block Driver v1.1
>
> Here is mol.0.log:
>
>
>> cat /var/log/mol.0.log
>> --snip--
>> No video mode match the default one.
>> HACK: Mapping framebuffer to 81000000
>> Failed to register sound card
>>
>>
>> VideoMode: 640 x 480, Depth: 8
>> cleaning up...
>
> On Sat, 2004-08-21 at 13:30, David C. Hacker, DVM wrote:
>> Try taking a look at the files in /var/log/ and see what you find.
>> There should be a mol log from the last attempt to run mol.
>> David C. Hacker, DVM
>>

MOL won't use a drive that's already in use by linux because there 
could be write issues. It won't even let linux read the drive while the 
Mac OS is running (in my case). Try unmounting it and run mol again. If 
you don't have it mounted, I am clueless.

	-Chris K.