Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!wuarchive!mailrus!cornell!uw-beaver!fluke!dcd
From: dcd@tc.fluke.COM (David Dyck)
Newsgroups: comp.os.minix
Subject: Re: Disk Drive Install & DM
Summary: DM incompatible with minix fdisk
Keywords: MINIX 1.1 SEAGATE OnTRACK Disk Manager DM
Message-ID: <11574@fluke.COM>
Date: 7 Oct 89 21:41:40 GMT
References: <181@hal.CSS.GOV>
Sender: news@tc.fluke.COM
Organization: John Fluke Mfg. Co., Inc., Everett, WA
Lines: 26

In article <181@hal.CSS.GOV> baugh@hal.css.gov writes:
>Then I create /dev/hd5 -> /dev/hd9 and try to build a file
>system on /dev/hd6.  BOOM.  (well not that drastic, but....)  I get 
>the following error :
>
>		Error: put_block couldn't write
>		Line 1 being processed when error detected.
>
>	Now, here are some other facts that may help or be part of the
>the problem.  First the disks were 'set-up' with SEAGATES OnTRACK Disk
>Manager -- DM.  

I had a 40M Seagate 251 added to my computer a month ago, and the
dealer installed DM.  I had trouble integrating DOS and minix, but
the problem seems to be in incompatible fdisks.  The key to the solution
was (as best as I can remember), that DM reserves a whole TRACK for
bootstrap and partition information, which is incompatible with the way
minix uses the partition table.  I think I used MSDOS DEBUG do read in the
boot track, patch it, and write it back out again.

I suggest that at least you examine the boot sector and compare the information
in it with the code in minix.  I remember putting lot's of printfs in
the disk driver before I realized what was going on.

            David Dyck
    Domain: dcd@tc.fluke.COM