Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Oct 2000 16:51:10 -0400
From:      media@ct1.nai.net
To:        questions@FreeBSD.ORG
Cc:        john253@crosswinds.net
Subject:   Re: install from 4.1 CDROM failed
Message-ID:  <v03130304b5fe63bee23d@[209.150.38.76]>
In-Reply-To: <onnctso6q4eta52c7n9dqnjt75nrhdh3r3@4ax.com>
References:  <v03130301b5fba6258620@[209.150.34.18]> <NCBBIPDEFKONHLOLAMEOEEDJCDAA.emag2@emag1.com> <v03130301b5fba6258620@[209.150.34.18]>

next in thread | previous in thread | raw e-mail | index | archive | help
At 1:06 AM +0100 10/01/00, John Murphy wrote:
>
>That sounds very recent for a CD, so there shouldn't be a problem.

Thank you very much for your response.  A recent master can still be bad,
and a good master can still create a bad replicant.  However, I want to
explore other possible causes before I return the CD-ROM to Walnut Creek.

>None of which should have been necessary.
>Newfs'ing the slice should've sufficed.

That's what I thought, but I decided to erase it under DOS just to make
sure.  At this point the disk has been erased and reformatted several times.

>Was the '3.4 install on an Extended DOS partition?

It wasn't on an Extended DOS partition because I had not previously
formatted it as such, but it was on the same physical space on the drive.
I'm thinking if 3.4 installed, then 4.1 should install.

>Slightly less likely to have problems with primary partitions, though '4.1
>seems to interpret them ok.  I keep thinking there may be a problem with
>your BIOS and a large drive, but then '3.4 worked so it can't be that.

It's only a 3G drive.

>>The 4.1 installer seems a bit different from the 3.4.  Where did the bad
>>block scan go??  The flag is described on the help page (F1), but the
>>command is not listed.
>
>I don't remember seeing or needing that.  Perhaps these bad blocks are the
>problem.

Perhaps, although I don't remember the 3.4 install finding any bad blocks.
I wonder why they removed the bad block scan for 4.1.

>Providing "/" is at ad0s2a ('ad' is the FreeBSD-4.x IDE driver, superseding
>the old wd (Western Digital) driver of FreeBSD-3.x fame; '0' is the master
>>of the first IDE port; 's2' is the second slice and 'a' is the first
>partition where "/" should be.  I think I would always put "/" first >though.

It failed no matter what I put first.  Regardless the installer always
seems to make "/" ad0s2a.

>You need Newfs if you want to replace the old file system.  I guess...

Right, I had it set active.

>It may be that re-formatting was un-necessary until you DOS formatted it.
>The process is probably quicker with '4.1: Memory of the relative speed of
>something is an insignificant symptom.

Good point!!

>Sorry to not have pin-pointed the problem but I need more facts.
>How big is it ferinstance.

It is 3G.  I think finding out what "panic: lockmgr: non-zero exclusive
count" means may be the at the heart of a solution.  I will post a separate
question.

>PS: You said "FreeBSD CD-ROM" singular.  The last I bought was '3.2 and it
>was four disks.  Has this changed?

You are correct.  If you buy FreeBSD on it's own or with _The Complete
FreeBSD_ you receive 4 CD-ROMS.  If you opt to buy the CD that comes with
_The FreeBSD Hanbook_, you only get one CD-ROM.

Thanks again for your help.





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




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