dead hard drive symptoms

[bigmessowires]

I picked up a dead (?) PowerMac 7100/80 today, and transplanted the hard drive to a Mac IIsi. It's a Seagate Barracuda, not sure of the capacity.

At power-up, the happy mac icon appears very briefly, but then the IIsi switches to the question-mark disk icon. If I boot it with a floppy, after booting the Mac says "the disk Untitled couldn't be used because an error of type -127 occurred". If I run Apple HD setup, it says no SCSI devices were detected.

Are these typical symptoms of a dead hard drive, or might it be something else? The fact that the happy mac icon appears briefly when attempting to boot from it suggests that it's at least partly working, and it sounds OK. But the -127 error and non-recognition by the Apple HD setup tool suggest otherwise. Is there some PowerPC to 68K hard drive transplant issue that might be happening, that I'm not aware of?

 

[Macdrone]

Does it let you initialize? Is it an apple rom drive if not you may need a third party driver (which the IIsi maybe cannot use)

 

[bibilit]

You should try better Lido 7, the fact that the happy mac is present is a good sign for me (moreover the disk is named... "Untitled")

I think the version of HD setup cannot manage and see HFS disks.

The fact that the disk is issued from a Power PC and you are trying to use it in a 68k probably triggers the -127 code error.

-127 is an internal file system error code

HFS Errors

-120  dirNFErr                Directory not found
-121  tmwdoErr                No free WDCB available
-122  badMovErr               Move into offspring error
-123  wrgVolTypErr            Not an HFS volume [wrong  volume type error or
                             (obsolete) operation  not supported for MFS]
-124  volGoneErr              Server volume has been disconnected.
-125  updPixMemErr            Insufficient memory to update a pixmap
-127  fsDSIntErr              Internal file system error

Let us know.

 

[bigmessowires]

Lido 7 recognized it as a 4 GB drive, and it's formatting now. It's been going for about 15 minutes... a progress bar sure would be nice. But the drive is still making noises, so I assume it's working ok.

Don't hard drives have their driver software stored on the disk itself? Maybe the driver code was PPC-only, which is why I couldn't mount the drive on a 68030-based IIsi? I've never tried moving a drive between a PPC and a 68K Mac before.

 

[volvo242gt]

The reason why it didn't work was because the drive was formatted with HFS+, which is PPC only. I ran into this when I forgot that 68k machines can't handle HFS+ and tried to install 8.1 on a 3GB Quantum Fireball in my 660av. Had to reformat the drive with two 1.5GB partitions. Then, it worked fine.

-J

 

[onlyonemac]

Bad system software on my Mac after a forced reboot caused the exact same symptoms.

Reinstall the system software. Or try booting from a floppy and see what's on the drive.

 

[bigmessowires]

I think Volvo is right. It took nearly an hour, but the format succeeded. I installed system 6.0.8, and the IIsi boots up just fine from the New drive. Hooray!

 

[NJRoadfan]

The reason why it didn't work was because the drive was formatted with HFS+, which is PPC only.

Can't 68040 machines boot off of HFS+ partitions if they have MacOS 8.1 installed? By default, HFS+ aware versions of Drive Setup create the partition in a HFS "wrapper" that loads the driver in machines that lack HFS+ support in ROM. It also includes that dummy partition that mounts with the text file called "Where are my files?" If the drive was setup with OS X's Disk Utility, it won't create the wrapper or install the required driver partition for classic MacOS.

 

[volvo242gt]

Learned that it won't happen. An '040 Mac can use it as a storage partition, but not as a boot partition. So, I reformatted it... No big deal. The data that was on the drive was inconsequential, since all of it is on my G4's 80GB drive. The 3GB drive was from my old 7100/80 and eventually got updated to 9.2.2 when it made its way into my 7500/100.

-J