Missing disk after I trashed it

tomgradwell

Registered
I have 2 hard drives in my G4. One has the boot system OSX 10.2.2, and the Classic system 9.2.2. The other is disk with 9.2.2 on it for the purposes of running a System 9 startup disk which is config'd the way I need it to run old Sys9 applications... ie those apps that need all sorts of extensions that Classic doesn't like. The 2nd drive was partitioned in two just for storage purposes.
Now this is fine and has worked well, UNTIL... I "ejected" the disk (ie both volumes of the partitioned drive) while running OSX. I simply dragged both volume icons to the TRASH and they dutifully disappeared from the desktop - forever!
Restarting under OSX will not make them reappear. BUT they are visible and useable under OS9. Using Disk Utility under OSX will allow me to "see" and verify them, but I cannot erase, re-partition, or mount them. The "Mount' option is available under the "Options" menu, but does nothing. Likewise "erase" leads to disk activity, but after the operation is complete the disk returns to it's former condition in the Disk Utility Info window, ie partitioned, and "greyed out".
Attempting to erase the disks under OS9 tools (ie Disk Setup) again does nothing, the disk partitions and their content remaining untouched.
Repairing disk permissions on the startup disk doesn't help.
In OSX I am the system administrator - I have no other users set up.
How do I regain access to the 2nd hard drive under OSX?
 
Sorry so you mean both disks don't appear on your desktop in OS X?

Perhaps Jaguar has some preference feature that disables viewing them on the desktop if yo trash them. In the Finder go to Finder (app mennu) -> Preferences and make sure Hard Disks is checked. If it is, uncheck it, click ok, then go back and re-check it.

Just a hunch...
 
The startup disk appears, but both partitions of the 2nd disk are missing from the desktop. Can be "seen" by Disk Ute, but can't "do" anything to them.
Tried your hunch, thanks, but no luck
 
The problem persists

following is the console log that appears when I attempt to mount either partition (Overflow Partition or OS9 Partition) using Disk Utility

<
&#65279;Dec 14 15:27:35 Tom-Gradwells-Computer /sbin/autodiskmount[340]: (autodiskmount.tproj/DiskArbitrationServerMain.c:1796) UpdateAckValue(0x000836f0, pid=432, errorCode=0): error: state != kWaitingForAck

Dec 14 15:27:39 Tom-Gradwells-Computer /sbin/autodiskmount[340]: DiskVolume_mount_foreign: unrecognized return code from foreignMountDevice: -4

Dec 14 15:27:39 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s10 hfs yes yes OS 9 partition [not mounted]

Dec 14 15:27:39 Tom-Gradwells-Computer /sbin/autodiskmount[340]: DiskVolume_mount_foreign: unrecognized return code from foreignMountDevice: -4

Dec 14 15:27:39 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s9 hfs yes yes Overflow partition [not mounted]

Dec 14 15:27:47 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s9 hfs yes yes Overflow partition [not mounted]

Dec 14 15:27:48 Tom-Gradwells-Computer /sbin/autodiskmount[340]: DiskVolume_mount_foreign: unrecognized return code from foreignMountDevice: -4

Dec 14 15:27:48 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s9 hfs yes yes Overflow partition [not mounted]

Overflow partitionOS 9 partitionDec 14 15:28:00 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s10 hfs yes yes OS 9 partition [not mounted]

Dec 14 15:28:04 Tom-Gradwells-Computer /sbin/autodiskmount[340]: DiskVolume_mount_foreign: unrecognized return code from foreignMountDevice: -4

Dec 14 15:28:04 Tom-Gradwells-Computer /sbin/autodiskmount[340]: disk1s10 hfs yes yes OS 9 partition [not mounted]
>

Any suggestions?
 
I'm having the same problem. I just ejected one of my hard disk. did you ever find a solution to your problem?
 
Go to the Terminal, and type mkdir /Volumes/OS9

Then, what happens if you type /sbin/mount -t hfs /dev/disk1s10 /Volumes/OS9 in the Terminal?

(after you're done, delete the folder OS9 that you made - rm -rf /Volumes/OS9)

(Note: that is from your previous post - if you rebooted since then, it may not be /dev/disk1s10 anymore)
 
Back
Top