Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!husc6!cs.utexas.edu!bunda From: bunda@cs.utexas.edu (John Bunda) Newsgroups: comp.os.minix Subject: Hard disk with 1.2 (problems) Keywords: Seagate ST-225, WD WX-1, IBM PC Message-ID: <2900@cs.utexas.edu> Date: 22 Jun 88 04:40:09 GMT Organization: U. Texas CS Dept., Austin, Texas Lines: 35 I thought I finally had it. I changed the AUT O_BIOS in xt_wini.c, and put in the com_out replacement from the archives, made the kernel, and booted. "h" seemed to initialize things ok, though it did report bad superblock..., which I guess is expected. Anyhow, once up and running, the dd if=/dev/hd0.... test ran to completion, my hard disk merrily whirring away, dumping its 1000 blocks to /dev/null. I then backed up the disk, reformatted (low-level with the WD BIOS formatter using debug), and used DOS (3.3 by the way) FDISK to partition the drive. I created a DOS partition and another "extended DOS partition" for Minix. I formatted C:, restored my DOS system to its partition, and it works great (don't forget to activate the primary partition, or it won't boot). I then brs'd and booted Minix. fsck of either hard partition from the boot menu gives "bad superblock, fatal", again, I guess expected since mkfs hasn't been done yet. The light on the drive winks though, so I do know it's awake. Put in the root diskette and "=", the ram disk begins loading, meanwhile the hard drive begins what sounds like a major seek. The whole show then comes to a screeching halt with the message "kernel panic - can't read partition table on drive 0" I tried making the minix partition a virtual drive for DOS (D:), then high-level formatted. Waste of time, no effect whatsoever. Any coaching would be welcome.... thanks john -- ................................................................ John Bunda UT CS Dept. The proof is trivial, and bunda@cs.utexas.edu Austin, Texas left as an exercise.