>> What makes the drive special? mac68k has been installed on just
>> about every kind of drive I can think of.
>
> The SCSI-to-IDE adapters may or may not map all of the SCSI disk command set 
> in a reasonable manner, and they may or may not take into account peculiar 
> implementations on ~twenty-year-old machines. Thomas is the first to report a 
> NetBSD/mac68k installation on a bridged IDE drive, for all I know.

But how could that explain improper magic numbers?

Also, I've been using SCSI-IDE adapters for years in many machines, 
including production machines, VAXen, mac68k, SPARC, Amigas, et cetera. If 
any code did strange SCSI stuff, it'd be the code in MacOS because Apple 
knew the hardware much more intimately than anyone else.

I have three mac68k machines using them, two of which are colocated - 
Quadra 605s make for very tidy 1U servers. Here's a low power 160 gig 
drive in one of them:

sd0 at scsibus0 target 0 lun 0: <Hitachi, HDS721616PLAT80, P22O> disk fixed
sd0: 149 GB, 77525 cyl, 64 head, 63 sec, 512 bytes/sect x 312581808 sectors
sd0: sync (248.00ns offset 15), 8-bit (4.032MB/s) transfers, tagged queueing

My adapters are Acard. What kind are yours?

> To me this all sounds like MacOS and NetBSD disagree about your 
> partitions.

This is possible, and has happened on many kinds of drives for me, be they 
500 meg SCSI or 500 gig IDE on SCSI-IDE bridges. What I have found that 
works well (if a bit slowly) is using the Apple HD SC utility to 
auto-partition a drive (just select any of the defaults), then making 
changes. For some reason, Apple HD SC and Drive Setup both leave little 
spaces between the driver sections and partitions. When didn't leave 
spaces, strage things would happen; I'd mount a partition, then see no 
files in it (including . and ..), or I'd start to use it, then panic the 
machine because of filesystem corruption.

The spaces created by Apple HD SC appear to be only 16k or so, so you're 
not losing much by trying.

John Klos