baugh@hal.CSS.GOV (Nam Myoho Renge Kyo) (10/04/89)
'Folks, Well the disk problem continues. First a few corrections, in my last posting I said /dev/hd2, when I really meant /dev/hd5. Woops. Also yes I did realize that it wouldn't be exactly 20000, I hadn't calculated it out exactly. Thanks to everybody who pointed this out. That's what I get for not having the READ_ME file with me. Ok, so I also got directed to "...copy at_wini.c to wini.c in the kernel directory and then rebuild kernel." which I have done. SIDE NOTE: My system only has 1 floppy [1.2 mb] with it's 2 hard disks, since it came in a baby-AT case. I'll be getting a tower case and I have a 3.5 inch floppy left over from my ol'PC, so all I've have to do is get a 360kb drive when I buy the tower case. (However that's in the future) Ok, so thorough a lot of floppy swappings, I get the kernel rebuilt with at_wini.c in place, make a new bootdisk, re-boot, notice the difference in MINIX size and a slightly smaller amount of ram available (all expected of course...) 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've looked at them with fdisk (MSDOS 3.3) and they seem to be partitioned ok. The Seagate 251 (40mb) is divided in half, one dos partition, the other is non-DOS according to fdisk, the Seagate 225 (20mb) is a single partition, non-DOS according to fdisk. Now, when I have installed the device driver the 40mb looks like C: & D:, the 20mb E: . Without the driver, I couldn't get to D or E, but C looks fine. One other time tried this, I could get to the first partition of the 40mb (C) and the 20mb, but the 20mb was accessed as D not E and the second partition of the 40mb was unavailable. The disk drive controller is a genunine IBM controller (from an 6mhz PC-AT) and works fine under dos. Am I experiencing a MINIX 1.1 at_wini problem, or does it look like hardware?? -- Earl D. Baugh Jr. ENSCO INC. Internet : baugh@hal.CSS.GOV "Open the pod bay doors...."
paula@bcsaic.UUCP (Paul Allen) (10/06/89)
In article <181@hal.CSS.GOV> baugh@hal.css.gov writes: > [ about problems mkfs'ing on his disk partitioned with 3.3 fdisk ] I had trouble like you describe until I switched back to 3.10. I was seeing weird stuff like: Low-level format the drive. Create a small DOS partition with 3.3 fdisk. Create three more non-DOS partitions with Minix fdisk (1.3). Go back to DOS, run fdisk and it hangs! Reset the machine! I'd like to run 3.3 at some point, but it's not causing me a lot of grief right now. If anybody knows how the partition table changed between DOS revs 3.10 and 3.30, please post! The only trouble I have with my hard disk now is that I must touch the disk with the boot-menu fsck before it is usable under Minix. (I have a DTC RLL controller.) Paul Allen -- ------------------------------------------------------------------------ Paul L. Allen | pallen@atc.boeing.com Boeing Advanced Technology Center | ...!uw-beaver!bcsaic!pallen
cagney@chook.ua.oz (Andrew Cagney - aka Noid,285,5585,3362395) (10/10/89)
From article <15544@bcsaic.UUCP>, by paula@bcsaic.UUCP (Paul Allen): > Low-level format the drive. > Create a small DOS partition with 3.3 fdisk. > Create three more non-DOS partitions with Minix fdisk (1.3). > Go back to DOS, run fdisk and it hangs! Reset the machine! I also got this, the solution was get someone's minix fdisk that actually put numbers into the partition type field of the partition table. (eg 0x40). If the number was present fdisk did not hang.