Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!ll-xn!cullvax!boh From: boh@cullvax.UUCP (Brian P. O'Halloran) Newsgroups: comp.os.minix Subject: Hard Disk Message-ID: <1340@cullvax.UUCP> Date: Sun, 5-Jul-87 20:22:12 EDT Article-I.D.: cullvax.1340 Posted: Sun Jul 5 20:22:12 1987 Date-Received: Mon, 6-Jul-87 00:38:36 EDT Organization: Cullinet Software, Westwood, MA, USA Lines: 53 Summary: IBM PC/AT Hard Disk Problem I am attempting to get MINIX 1.1 up on my hard disk. I have made quite a bit of progress however there is still a problem w/ at_wini.c reading the partition table (I think). I should also make you all aware that I am not a professional developer. However I am very interested in learing MINIX so please if bear with me as I try to explain my problem. I am running an IBM PC/AT (6MHz) w/ 32MByte hard disk (? on the hard disk make, I think Seagate), one 360K floppy, one 1.2MByte floppy, 640K RAM. I have diffs that Matt Weinstein posted for at_wini.c. As a result of these changes I have successfully partitioned my 32MByte hard disk into two partitions cylinders 0 to 600 for DOS and cylinders 601 to 732 for MINIX (approx. 5.7MBytes). I am no longer experiencing the winchester won't reset problem and I can reliably use my hard disk for MINIX development. I have tested the hard disk file system by multiple cat's of two rather large files until I got a disk full error message which met my prediction of where it would fail. However, the symptoms of my problem are; o fsck at boot time for my hard disk partition returns the following errors: "error 0x8000 reading block 1, retry" "error 0x8000 reading block 1, retry" "error 0x20C0 reading block 1, retry" "fsck: can't read block 1 (error = 0x8000)" "fatal" Then goes back to boot menu. I suspect that there is a primitive form (BIOS call to DOS?) of winchester driver in fsck and that this needs to be modfied. I am looking at fsck.c now for some clues. Any hints as to what might be happening here? Of much more importance to me is the following; o I can't # /etc/mount /dev/hd2 /user unless I first select "h" off of the boot menu and get the above error conditions. It's almost as if I have to "jump start" my hard disk. If I don't select "h" as above and just do "=" when I issue # /etc/mount /dev/hd2 /user I get the following message "unrecoverable disk error on device 3/2, block 1" "mount: /dev/hd2 is not a valid file system" I tried changing PART_TABLE from 0x1C6 to 0x1C2 but this did not help. Does anyone have any ideas about what I might be doing wrong? Thanks in advance. Brian O'Halloran boh@cullvax