Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 May 1996 23:38:00 +0930 (CST)
From:      Michael Smith <msmith@atrad.adelaide.edu.au>
To:        genj1@aptpcs.com (Jeff Genender)
Cc:        questions@FreeBSD.ORG
Subject:   Re: Big problems
Message-ID:  <199605111408.XAA13213@genesis.atrad.adelaide.edu.au>
In-Reply-To: <319343C2.3D43@aptpcs.com> from "Jeff Genender" at May 10, 96 08:25:22 am

next in thread | previous in thread | raw e-mail | index | archive | help

Jeff Genender stands accused of saying:
> 
> Be prepared... this is a long question with many sub-parts.

No sweat.  Beats the hell out of unintelligble one-liners 8)

> Gateway 2000 Pentium 90Mhz
> 40M Ram
> 1 Gig EIDE Drive as C: Drive with DOS/Windows NT/WIndows 95 - Primary DOS
> ATAPI EIDE CD-ROM
> Adaptec 1542CF SCSI Adapter
> (sd0) 1 Gig Conner SCSI drive as drive D: with Extended DOS
> (sd1) 1 Gig Seagate SCSI drive partitioned the first 600M as NTFS and the remaining 405 as FreeBSD.
> 
> Problem 1
> ---------
> I would like to install XWindows but can't because I cannot get the
> CD Rom to mount.  I rebuilt the kernel and removed the comments for
> ATAPI and the wcd0.  When I try to mount the CD, I get a 'Device not
> Configured' (Yes, I did have a CD in the CD ROM).  No luck.  Any
> ideas?

Is the CD found at startup?  If yes, then it _should_ be mountable.  If no,
then you may want to experiment with moving it to the second IDE controller
and running it as master by itself there.

Note that ATAPI CDroms are spawn of the devil, and getting them to work
properly is very difficult 8(

> Problem 2
> ---------

> Related to problem 1.  Since I could not install off the CD Rom, I
> decided to copy the files to my C Drive in the \freeBSD\X86312\
> directory (oh and I tried several other directory combinations as
> well \X86312, \FreeBSD\DISTS\X86312, trust me, I tried them all) and
> ran the sysinstall program to install X.  Nope.  It couldn't install
> from DOS.  Why?

Um, I think that should have been \freebsd\XF86312, but no matter.
Did you get a reason from sysinstall?  Regardless, it's not too hard to 
install by hand.

> Problem 3
> ---------
> Related to problem 2.  Since I could not install by the sysinstall
> program, I decided to try it manually.  So, I decided to mount the
> MSDOS drive.  When I did it gave me some sort of error that cluster
> size did not match something or other.  However, it still mounted.
> I went to look at the drive and when I did an 'ls', it listed the
> files and a lot of other files kind of like : ??????.EXE.  At any
> rate, I started to tar the files and ... BOOM! Panic - UFS_LOCK:
> Recursive something or other.  Reboot.

The 'root directory is not a multiple of cluster size' error tends to
indicate that you shrunk one or more of your filesystems with FIPS.
The current MSDOSFS code is pretty shaky, and FIPS leaves the
filesystem in a fairly inconsistent state that tends to make it more
so.

Nonetheless, it should work for what you were doing.  Were you
extracting the files on the DOS filesystem, or directly into /usr?
The former may have lead to serious grief.

> Problem 4
> ---------
> You guessed it.  Related to problem 3. I let the computer come up in
> DOS and decided, well maybe its and IDE-BIOS-FreeBSD-Geometry
> problem.  So, I copied the filed to my D drive (sd0).  Did the
> usual, tried to install by the sysinstall - didn't work of course.
> So I tried it the manual method on this drive.  I tried to mount sd0
> and as soon as I did... BOOM... Panic.  I forgot the error on this
> one..  I think it was the UFS_LOCK one again. What happened?  Why
> couldn't I mount the scsi extended Dos drive?

There is something distinctly funny about your DOS partitions.  What
did you create them with?  Did you try to mount the correct slice?
(It sounds like you know what to try to mount; just trying to work
this one out)

> Problem 5
> ---------
> Related to number 4.  The computer reboot itself and began its boot
> process.  When it got to mounting /rds1a (I think this is what it
> tried to mount - or something to that effect), it hung.  I had to
> press the reset key.  I tried it again.  It hung.  I now cannot get
> into FreeBSD.  Can I fix this?  Can I do it with a fixit disk?  or
> do I need a full reinstall?

Try booting with the '-s' flag at the boot prompt, then go with this :

# fsck /dev/rsd1a
# reboot

The former may tell you your root filesystem is toasted, in which case a
reinstall is definitely the way to go.  If it works OK, try booting again/

It sounds like you have some serious filesystem corruption happening.  Do
you mount your FAT filesystems by default at startup?

> Jeff Genender

-- 
]] Mike Smith, Software Engineer        msmith@atrad.adelaide.edu.au    [[
]] Genesis Software                     genesis@atrad.adelaide.edu.au   [[
]] High-speed data acquisition and      (GSM mobile) 0411-222-496       [[
]] realtime instrument control          (ph/fax)  +61-8-267-3039        [[
]] Collector of old Unix hardware.      "Where are your PEZ?" The Tick  [[



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605111408.XAA13213>