[comp.unix.microport] UNIX/DOS Slice table and fs problems

val@swamps.UUCP (Val Christian) (09/23/89)

After quite a bit of aggravation, I've finally decided to put this to the
net, in hopes that some of you may be able to help out.

Configuration:

AT-type PC with a "Type 2" drive (20Mb) and a ST4096 disk.  Microport
2.3, with 2.4 winchester drivers.

Problem:

1) Apparent inability to establish a DOS partition on the second (ST4096)
drive which does not clobber a UNIX file system (/dev/dsk/1s1).

2) Also, the apparent inability to properly address a DOS partition via
dosdir and doscp commands on the first drive.

3) UNIX file system (/dev/dsk/1s1) is broke somewhere between block 12900
and 17900; subsequent writes cause the available inodes to reduce to 0.
fsck appears to fix.

Discussion:

1.)  Apparently, a mkfs on /dev/dsk/1s1, and subsequent use of that
file system acts on the DOS partition, as shown in the fdisk and
divvy -d excerpts below.  If the DOS partition is formatted, filesystem
/dev/dsk/1s1 gets clobbered.  If the filesystem is mkfs, then the DOS
partition gets clobbered.  It is necessary to have the DOS partition be
the first partition on the ST4096, as DOS (3.1) doesn't know how to handle
the larger number of heads and tracks of the 4096.  I tried Disk Manager,
but apparently it is incompatable with Microport, as it uses the boot
track (0).  Disk Manager works fine with DOS solo, but not with Microport.

2.)  This may be for reasons stated above, as well as a outrageous entry
in the DOS partition entry in the Slice talbe for Drive 0.  How can I patch  
the Slice Table?

3.)	 This one puzzles me, except that the end of the DOS partition is at
about the point where things break.  I want (need!) two separate UNIX
file systems on the second drive.

Bottom Line:

I am open to information and suggestions.  The ability to have three 
UNIX file systems, and two DOS partitions is an interest.  I have
done some experimentation to help analyze the situation, but have
not formulated any solutions.  



APPENDIX:  fdisk information and divvy -d excerpts


FDISK assignments

Drive 0 (Type 2)

	Part #		Status	Type	Start	End		Size	Blocks
	4			A		System5	1		510		510		34680
	3			N		DOS		511		613		103		7004

Drive 1 (ST4096)

	4			N		DOS		3		170		168		25704
	3			A		System5	176		1021	846		129438

divvy -d excerpts:


 CONTENTS OF PARTITION END RECORD FOR UNIT #0

                 Drive Table
                 ----- -----
         Number of cylinders:  615
         Number of heads/cylinder:  4
         Landing zone:  615
         Write precomp:  300
         Sectors/track:  17
         Sector size:  512
         Number of alternate cylinders:  0
         Actual sectors/cylinder:  68
...
                 Slice Table
                 ----- -----
Slice 0 ROOT -- first sector:  68, number of sectors:  12000
Slice 1 SWAP -- first sector:  12068, number of sectors:  10000
Slice 2 USR -- first sector:  22068, number of sectors:  11660
Slice 3 TMP -- first sector:  22068, number of sectors:  0
Slice 4 Reserved -- first sector:  0, number of sectors:  0
Slice 5 DOS partition -- first sector: 1869182064, number of sectors: 757932142
Slice 6 UNIX partition #1 -- first sector: 0, number of sectors: 0
Slice 7 UNIX partition #2 -- first sector: 0, number of sectors: 0
Slice 8 UNIX partition #3 -- first sector: 34748, number of sectors: 7004
Slice 9 UNIX partition #4 -- first sector: 68, number of sectors: 34680
Slice 10 Entire disk -- first sector: 0, number of sectors: 41820
Slice 11 Last track active pt -- first sector: 34731, number of sectors: 17

...

 CONTENTS OF PARTITION END RECORD FOR UNIT #1

                 Drive Table
                 ----- -----
         Number of cylinders:  1023
         Number of heads/cylinder:  9
         Landing zone:  1023
         Write precomp:  -1
         Sectors/track:  17
         Sector size:  512
         Number of alternate cylinders:  0
         Actual sectors/cylinder:  153
...
                 Slice Table
                 ----- -----
Slice 0 ROOT -- first sector:  26928, number of sectors:  0
Slice 1 SWAP -- first sector:  26928, number of sectors:  0
Slice 2 USR -- first sector:  26928, number of sectors:  128418
Slice 3 TMP -- first sector:  26928, number of sectors:  0
Slice 4 Reserved -- first sector:  26928, number of sectors:  0
Slice 5 DOS partition -- first sector: 26928, number of sectors: 60000
Slice 6 UNIX partition #1 -- first sector: 86928, number of sectors: 68418
Slice 7 UNIX partition #2 -- first sector: 86928, number of sectors: 0
Slice 8 UNIX partition #3 -- first sector: 26928, number of sectors: 129438
Slice 9 UNIX partition #4 -- first sector: 459, number of sectors: 25704
Slice 10 Entire disk -- first sector: 0, number of sectors: 156519
Slice 11 Last track active pt -- first sector: 156349, number of sectors: 17

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Val Christian
UUCP: ...attctc!swamps!val
	  ...rochester!kodak!swamps!val

nvk@ddsw1.MCS.COM (Norman Kohn) (09/25/89)

In article <63@swamps.UUCP> val@swamps.UUCP (Val Christian) writes:
>I am open to information and suggestions.  The ability to have three 
>UNIX file systems, and two DOS partitions is an interest.

I can't solve the problem you posed, and no longer have SVAT
up (I've migrated to unix386).

When I ran SVAT I used 3 unix partitions on drive 0: this
is readily done by using the designators for other partitions
(e.g., /dev/rdsk/0s7).  You might want to try some such...
I suspect that the sub-partitions of the active partition
on drive 1 never got tested very thoroughly.

-- 
Norman Kohn   		| ...ddsw1!nvk
Chicago, Il.		| days/ans svc: (312) 650-6840
			| eves: (312) 373-0564