jca@hou2f.UUCP (J.ANTROSIGLIO) (09/15/87)
Thanks to Jim Lyons I now have Minix 1.1 accessing the
winchester on my AT&T 6300. I ran mkfs to created a empty
file system with 10,000 blocks and copied the /usr disk
to the wini. Everything seemed to work fine until the
next time I booted the system I decided to run a fsck
on the winchester (/dev/hd6).
The first thing it complained about was the INODE NLINK COUNT.
I answered yes when it ask if I wanted to correct it printed the
message "internal error (counterror)" and quit.
I restarted fsck and answered no the next time it complained about the
count and it started complaining about inodes not being clear.
I answered yes when it ask if it should clear each inode.
This happened for about 1000 inodes. After fsck finished I continued
to boot the system and mount the winchester in /user.
The disk mounted fine but when I issued a ls command in /user
it complained that it couldn't access ".". Seems like I blew
away my file system. I tried reformatting the winchester under DOS and
remaking the file system but fsck still complained.
Everything seems to work fine as long as I don't request a fsck.
However, I sure this is not the answer! Has anyone every seen this
problem before? If so, could you provide any pointers to the
solution.
Thanks In Advance,
John Antrosiglio
AT&T Bell Labs
ihnp4!{hou2f,hotld}!jca