*BSD News Article 78872


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!serv.hinet.net!news.uoregon.edu!arclight.uoregon.edu!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@awfulhak.demon.co.uk (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: New harddrive how to ?
Date: 23 Sep 1996 06:07:35 +0100
Organization: Coverform Ltd.
Lines: 43
Message-ID: <5255un$i8@anorak.coverform.lan>
References: <51s792$kb@Steinlager.tip.net> <51spjf$1a0@anorak.coverform.lan> <51tfgq$7at@Jupiter.Mcs.Net>
NNTP-Posting-Host: localhost.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
X-Newsreader: TIN [version 1.2 PL2]

Font (font@MCS.COM) wrote:
: brian@awfulhak.demon.co.uk (Brian Somers) writes:

: >[about installing a second disk]

: >Run /stand/sysinstall, go into the custom setup and fdisk & disklabel
: >the new drive.  You can then put your new partitions in /etc/fstab.
: >I can't remember if sysinstall newfs's the partitions - if it doesn't,
: >do it manually :)

: I tried this, and tried something along the lines of what was
: suggested in the FreeBSD FAQ.  What happened?  After quitting the
: disklabel editor menu...

:                        +------ Information Dialog ------+
:                        | Copying initial device files..Segmentation fault
: (core dumped)          +--------------------------------+

Funny you should say that, but this happens for me too !  It happens after
the drive is fdisk'd and before it's labeled.... oh well, you can always
do it manually.  After this happens, try running "disklabel -r -e sd1"
(I'm assuming scsi disks - otherwise replace "sd").  Bear in mind that
the 'c' partition is the whole thing - keep within these bounds.

: But I've had a /lot/ of problems with sysinstall (2.1.5) not detecting
: errors (checksum errors, unable to get back into network interface
: config, etc) and otherwise screwing up.  My hardware might be a bit
: dodgy (AHA1542CF, 1G Jaz drive) and be the cause of some difficulty,
: but sysinstall's ignoring certain kinds of errors is even worse.
: Luckily I was able to get the kernel sources that it mangled off of
: the "live file system" cd.  I'm avoiding using sysinstall whenever I
: can.

I've not examined the core for this error - but it's the only one I've
seen.

: Time for me to read the disklabel and newfs man pages, I guess.

'fraid so :(  Still, keeps ya off the streets :)

--
Brian <brian@awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour....