Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!kettle.magna.com.au!news.cs.su.oz.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!newsfeed.internetmci.com!howland.reston.ans.net!agate!soda.CSUA.Berkeley.EDU!mconst
From: mconst@soda.CSUA.Berkeley.EDU (Michael Constant)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 100595-SNAP problems: msdosfs, floppy install
Date: 19 Oct 1995 07:38:01 GMT
Organization: Society for the Prevention of Cruelty to Vegetables, UC Berkeley
Lines: 31
Message-ID: <464v8p$t2d@agate.berkeley.edu>
NNTP-Posting-Host: soda.csua.berkeley.edu
I'm installing 2.1.0-100595-SNAP, and it's getting errors reading my
msdos filesystem. mount_msdosfs() gives a warning that my root directory
size is not a multiple of the cluster size; I assume this is because I
repartitioned my drive with FIPS and mount_msdosfs() expects a different
cluster size based on the partition size. However -- correct me if I'm
wrong -- this shouldn't cause errors reading the disk, should it? When
I use the emergency holographic shell and run mount_msdos manually, I can
access a lot of the files on the disk, but sometimes I will get garbage
in directory listings. When I try to install from the msdos partition,
gunzip starts complaining about bad input data, and finally sysinstall
gives up and returns error. According to Norton Disk Doctor and Scandisk,
there are no actual errors on the dos partition. Besides, a directory
that looks fine when I look at it once (from the holographic shell) will
sometimes look garbled the next, and it won't go back to looking fine
until I reboot.
The only things I can think of that are even slightly abnormal are the
following: first, my dos partition starts at sector 63. Would msdosfs
be happier if it was better aligned? Second, when I install the root
floppy (either from the image on disk or from the actual floppy) I get
a message that trailing garbage was ignored (the message appears right
after it installs /stand/ls). All the tools in /stand seem to work,
though. Also, I have heard people say that msdosfs is broken; is my
problem a symptom of that? If so, is there a workaround?
Anyway, I tried installing from floppies as well, and here I got an error
that just seems silly: it reads the first disk (bin.aa - bin.af) fine,
then it tries to read bin.ag, fails, and aborts the installation. That
*shouldn't* happen, should it? :-)
--
Michael Constant (mconst@soda.csua.berkeley.edu)