Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Dec 1999 12:19:52 +0100
From:      Andreas Braukmann <braukmann@tse-online.de>
To:        Mike Smith <msmith@freebsd.org>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: No disks found msg in /stand/sysinstall, how come?
Message-ID:  <19991219121952.C15806@cage.tse-online.de>
In-Reply-To: <199912190201.SAA01698@mass.cdrom.com>; from msmith@freebsd.org on Sat, Dec 18, 1999 at 06:01:21PM -0800
References:  <19991219021222.B15806@cage.tse-online.de> <199912190201.SAA01698@mass.cdrom.com>

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

On Sat, Dec 18, 1999 at 06:01:21PM -0800, Mike Smith wrote:
> > On Sat, Dec 18, 1999 at 04:21:19PM +0200, Vallo Kallaste wrote:
> > > > Is is not possible to configure and add a second disk via the
> > > > /stand/sysinstall Label and Fdisk menu's?
> > ... I got this, too, ... but
> > >
> > > Hmm, yes I got it too. Me thinks it's related to change from block
> > > devices to char and to the MAKEDEV. Anybody out there please
> > > correct me if I'm wrong. I had to do standard disklabel -rw ad1
> > > auto and after that edit the disklabel by hand. It's certainly not
 
> Sysinstall is not build with 'make world', and should not be used on a 
> system that's been updated that way.
... but my /stand/sysinstall came from a freshly installed snapshot
(19991208). 

In principle I'm (or was) rather used to using disklabel
for labeling new disks.
But recently (I would say for the last 12 months) I had various
difficulties in disklabeling new drives. (on -stable and on -current)
I found a solution in each of the cases eventually, but it made me not
really happy. Once I just 'dd-ed' an existing label from another disk.
This time I tried this strategy, too, but to no avail, since writing
back the afterwards edited disklabel seemed not to be possible.
(the "no space left on device"-message appeared ... )

> > ... just after having the standard disklabel -rw ad0 auto (my boot disk is
> > da0) complained about 'no space left on device'. Yes, ... I did the
> > disklabel -W ad0 ...
 
> You forgot to overwrite the beginning of the disk.
... and yes I did (before doing the 'fdisk') a nice little
dd if=/dev/zero of=/dev/rad0 count=10000 

Do you have any further hints?

Kind regards,
    Andreas


Sidemark: Yes, ... I'm running -current on a few machines (and yes I
        know, that I get what I pay for ;). I'm used to live with
        -current since I switched my cvsup-Tag from stable to current on a
        'brand new' dual PPro/200.

standard disclaimer: I really don't want to sound insulting or arrogating 
                     or whatsoever.
                     If anybody really might read such an undertone from my
                     message(s), please ignore it and blame it on my rather 
                     ugly written English.


-- 
Andreas Braukmann - TSE GmbH - Neue Medien - http://www.tse-online.de



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




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