Subject: Re: Hard drive formatting problem
To: None <PORT-MAC68K@NetBSD.ORG>
From: Bruce Anderson <brucea@wavefront.com>
List: port-mac68k
Date: 07/06/1997 21:30:00
--Cyberdog-MixedBoundary-0006B2CF
Content-Type: text/enriched; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<<html>

Try this instead. From the FAQ-O-Matic :

<<a <FONTFAMILY><PARAM>Geneva</PARAM>http://cobweb.dartmouth.edu/cgi-bi=
n/cgiwrap/jonh/faqomatic/sysconfig/disks/faq.pl</FONTFAMILY>>FAQ-O-Mati=
c /sysconfig/disks/<</a>


<FONTFAMILY><PARAM>Geneva</PARAM><<a http://cobweb.dartmouth.edu/cgi-bi=
n/cgiwrap/jonh/faqomatic/sysconfig/disks/faq.pl?question=3D6> 6. How
can I use Apple's free HD SC Setup 7.3.5 to partition my drive for
MkLinux? <</a>


Note that- HD SC will refuse to partition your drive until you do a
low-level format and install the driver. 

</FONTFAMILY>And you can use pdisk from the MacOS side on your 8500 to
view and change the partition table.  I recomend you use HD SC to do
the partitioning.

Then remember that only the devices (two  only ) on each end of the
SCSI chain is to be terminated. The extenal drive should be configured
with termination removed from the drive. Termination is done by the
enclosuer or with external temination.

<</html>

--------------Here is what  pdisk shows for my system-------------


This app uses the SIOUX console library

Choose 'Quit' from the file menu to quit.


Use MkLinux style disk names (i.e. /dev/sda, /dev/sdb, etc.).


Top level command (? for help): L

/dev/sda

   #:                 type name                length   base    ( size
)

   1:  Apple_partition_map Apple                   63 @ 1      

   2:       Apple_Driver43 Macintosh               64 @ 64     

   3:       Apple_Driver43 Macintosh               64 @ 128    

   4:        Apple_Patches Patch Partition        512 @ 192    

   5:            Apple_HFS MacOS              1064521 @ 704    
(519.8M)

   6:           Apple_Free Extra                   10 @ 1065225


Block size=3D512, Number of Blocks=3D1065234

DeviceType=3D0x0, DeviceId=3D0x0

Drivers-

1: @ 64 for 18, type=3D0x1

2: @ 128 for 32, type=3D0xffff


pdisk: can't open file '/dev/sdb'

/dev/sdc

   #:                 type name                length   base    ( size
)

   1:  Apple_partition_map Apple                   63 @ 1      

   2:       Apple_Driver43 Macintosh               32 @ 64     

   3:      Apple_UNIX_SVR2 Root file system    198000 @ 96      (
96.7M)

   4:      Apple_UNIX_SVR2 Swap                258000 @ 198096 
(126.0M)

   5:      Apple_UNIX_SVR2 Usr file system     638544 @ 456096 
(311.8M)

   6:      Apple_UNIX_SVR2 Unreserved 1       1011028 @ 1094640
(493.7M)

   7:      Apple_UNIX_SVR2 Unreserved 2       1090887 @ 2105668
(532.7M)

   8:      Apple_UNIX_SVR2 Unreserved 3       1277136 @ 3196555
(623.6M)

   9:      Apple_UNIX_SVR2 A/UX Root          1064315 @ 4473691
(519.7M)

  10:            Apple_HFS MacOS               743850 @ 5538006
(363.2M)


Block size=3D512, Number of Blocks=3D6281856

DeviceType=3D0x1, DeviceId=3D0x1

Drivers-

1: @ 64 for 19, type=3D0x1


pdisk: can't open file '/dev/sdd'

pdisk: can't open file '/dev/sde'

pdisk: can't open file '/dev/sdf'

pdisk: can't open file '/dev/sdg'

Top level command (? for help): 


-----------------------------------------------------------------------=
------------


     . .  I haven't lost my mind; it's backed up on tape *somewhere*!


Bruce Anderson       

Burnsville MN, USA

http://members.aol.com/brucea396/

send Mail mailto:Brucea@wavefront.com


>On Sun, Jul 6, 1997 7:25 AM, 
--Cyberdog-MixedBoundary-0006B2CF
Content-Type: application/X-url
Content-Transfer-Encoding: base64
Content-Description: T. Sean (Theo) Schulze

bWFpbHRvOjcxNDEwLjI1QENvbXB1U2VydmUuQ09N
--Cyberdog-MixedBoundary-0006B2CF
Content-Type: text/enriched; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

 wrote:

<FONTFAMILY><PARAM>Geneva</PARAM>> This isn't a NetBSD/mac68k specific
problem, but because I suspect that a 

> number of list members have a wealth of experience formatting and 

> preparing hard drives for use with NetBSD/mac68k, I hope someone
here

> can 

> help me.

> 

> I am having problems formatting a Quantum Empire 2100S to use with 

> NetBSD/mac68k on my Mac IIci or with MkLinux on my PPC 8500/120.  I 

> bought the drive at a computer fair in Sept. '95, and installed it
in an 

> external housing I had bought for it.  When I tried to format it
with 

> FWB's Hard Drive Toolkit, HDT correctly recognized the drive as an
Empire 

> 2100S, but showed its size as 0MB.  It would also not allow me to
select 

> the drive for formatting.  I took the drive to a Apple dealer, and
he 

> could also not get it to work.

> 

> I kept trying different things, including getting some pretty good 

> customer service and terminating resistors from Quantum.  Finally, 

> Quantum agreed to accept the drive for repair (for a price), and I
sent 

> it off to them.  Rather than repair the drive, they replaced it.  

> Unfortunately, I still have the same problem with the replacement
drive.  

> So, obviously, the problem must lie elsewhere. :-)

> 

> One other odd thing I have noticed about the drive is that I will
turn 

> the drive on before starting up the computer (MacOS boot), but as
the 

> computer starts up, the Empire 2100S will spin down and then spin
back up 

> again.

> 

> Can anyone give me an idea what the problem could be?  I have tried
a 

> number of formatting utilities to include HDT and a few formatters
on the 

> Apple Club CD.  No joy.  I know termination is an area where
problems 

> often crop up, but I am not really sure how to test for those type
of 

> problems.  I am close to buying a SCSIVue Active Terminator, because
I 

> read somewhere that active terminators often help clear up
termination 

> problems.  Is that worth a shot?

> 

> IIRC, Apple's earlier versions of HD Setup would not work with
drives 

> using a non-Apple driver.  Could something like this be part of the 

> problem?   I mean, if the drive were formatted for DOS or some other
OS, 

> would that cause this kind of behavior?  If that is the problem,
might I 

> be able to use the drive with a Pentium or 486 machine I am in the 

> beginning stages of building?  (I'd need a SCSI controller card,
though, 

> wouldn't I?)

> 

> TIA,

> 

> Sean.

> 

> 

>                  T. Sean (Theo) Schulze

> 71410.25@compuserve.com           TSSchulze@aol.com

> ***************************************************

> Your representative owes you, not his industry only, but

> his judgement; and he betrays, instead of serving you, if

> he sacrifices it to your opinion. -- Edmund Burke

> 

> 

> 

> 

> </FONTFAMILY>



--Cyberdog-MixedBoundary-0006B2CF--