Jump to content
14 posts in this topic

Recommended Posts

If I boot OS X I get this message: "The disk you inserted was not readable by this computer." . This message is referring to the second disk in my system which contains two Linux partitions which OS X apparently cannot read. This is perfectly acceptable for me since I will not be using those anyway. However, the system is giving me the option to (god forbid) erase the disk and it is only a matter of time before I will accidently push the wrong button. So: how do I make OS X understand not to make an attempt to auto-mount the disk alltogether ? Or is there a way to just make the warning dissapear ?

Hi Ramjet,

 

thanks for your response, but this solution does not work. Since OS X cannot read the partitions they do not have a label or uuid, so there is no way to identify them in fstab (I assume you were referring to that howto). And I am sure I gave them a label in Linux ...

 

diskutil list

/dev/disk0

#: type name size identifier

0: FDisk_partition_scheme *76.7 GB disk0

1: Linux 63.0 GB disk0s1

2: Linux 11.0 GB disk0s2

3: Linux_Swap 2.7 GB disk0s3

/dev/disk1

#: type name size identifier

0: FDisk_partition_scheme *37.3 GB disk1

1: Apple_HFS Apple MacOS X 37.3 GB disk1s1

First link, 3rd solution using rc.local

 

Change command to unmount device id of partition: diskutil unmount /dev/disk0s1 <== partition ident

Repeat that command in rc.local for s2 and s3, but if you are going to unmount all 3 partitions, might as well unmount the whole disk: diskutil unmountDisk /dev/disk0 <== disk ident

 

One caveat: if you add another hard drive or if you change the boot order in BIOS, "/dev/disk0" (disk) or "/dev/disk0s1" (partition) might become "/dev/disk1" (disk) or "/dev/disk1s1" (partition). This could then unmount the wrong device.

 

If it happens, probably can fix it by booting in single user mode and renaming the rc.local file and then rebooting. Afterwards can fix rc.local to new idents.

Unfortunately that did not work either ... The problem is that the warning occurs at the moment OS tries to mount the partitions, so unmounting them afterwards does not prevent it. A solution could be to 1) make OS X be able to mount EXT3 partitions and 2) unmount them. But there must be an easier way :( .

 

Do you perhaps know which process/job/program is responsible for auto-mounting attempts at startup? Maybe something can be configured there...

 

Edit: I found something interesting in /System/Library/StartupItems/Disks. Will investigate tomorrow ...

Edited by Pietus

Rammjet,

 

I have similar error message "The disk you inserted was not readable by this computer." on OSX bootup with red exclamation mark.

 

diskutil list

 

blascos-computer:~ blasco$ diskutil list

/dev/disk0

#: type name size identifier

0: FDisk_partition_scheme *232.9 GB disk0

1: Apple_HFS OSX1048 78.0 GB disk0s1

2: Apple_HFS MacPrograms 119.4 GB disk0s2

3: DOS_FAT_32 MAC-XP 35.4 GB disk0s3

/dev/disk1

#: type name size identifier

0: FDisk_partition_scheme *279.5 GB disk1

1: Windows_NTFS Blasco-C 30.3 GB disk1s1

2: Windows_NTFS Blasco-D 48.8 GB disk1s5

3: Windows_NTFS Blasco-E 200.3 GB disk1s6

/dev/disk2

#: type name size identifier

0: *320.0 KB disk2

 

Tried your suggestion to unmount disk2 (I am not sure about the disk that is giving error message and was wondering with this disk2, that refers as "320 kb config disk" in diskutil, might be culprit) by adding "diskutil unmountDisk /dev/disk2" in rc.local, but still the error message pops up on reboot.

To add more on the subject, I have already added /etc/fstab with following two commands:

LABEL=Blasco-C /private/mnt/Blasco-C ntfs ro,noauto

LABEL=Blasco-D /private/mnt/Blasco-D ntfs ro,noauto

This unmounts two NTFS partitions on boot.

 

Any suggestion is highly appreciated.

 

Thanks

yeah, if you set it to use AHCI instead the other modes, it wont give you that warning in OSX. however, windows wont boot up if you already installed it before you set your ide/sata configuration to use AHCI, osx doesnt care (you can switch back and forth).

 

one of the other fixes was to connect your SATA drive to one of the specific ports (however i'm not sure which one it is).

 

i installed winxp without AHCI, so whenever i decide to boot winxp, i turn AHCI in the bios, i should probably just stop being lazy and reinstall winxp with AHCI support.

sg,

 

Have you tried installing XP with AHCI?. When we install XP with AHCI setting in BIOS, do we have to supplement SATA driver during installation (pressing F6 and then insert floppy)?

 

Thanks

 

from what i've read, i think you do (havent done it yet, still too lazy since i barely use winxp). it should be on your asus p5w-dh cdrom.

 

i've also read that you can install drivers before you switch to AHCI on a live winxp system, then boot off winxp cd and do a repair or something.

 

if you google for it, you should find how to do it.

  • 2 weeks later...
×
×
  • Create New...