Subject: Re: disklabel problem
To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Tony Povoas <tony@ing.iac.es>
List: port-hp300
Date: 04/08/1997 21:20:17
The actual version from dmesg is:
NetBSD 1.2 (GENERIC) #7: Sun Sep 15 16:15:20 PDT 1996
thorpej@basalt:/u3/NetBSD-1.2/src/sys/arch/hp300/compile/GENERIC
On Tue, 8 Apr 1997, Jason Thorpe wrote:
> On Tue, 8 Apr 1997 18:12:55 +0100 (BST)
> Tony Povoas <tony@ing.iac.es> wrote:
>
> > I'm now getting errors that the disk is read only which is news to me! Any
> > other ideas? ( I've tried disklabel -W)
>
> ...which revision are you running? -current?
>
> For the record, I'm NOT able to reproduce these problems. The proper
> way to initialize a disklabel for the first time is to create a label
> (you can do this by running disklabel sd1 > foo, editing foo, then
> running disklabel -W sd1; disklabel -r -R sd1 foo).
>
> > dd if=/dev/rsd0c of=/dev/rsd1c count=3
> > Dec 9 13:55:35 marat /netbsd: sd1: WARNING: no disk label, using old
> > default partitioning
> > dd: /dev/rsd1c: Read-only file system
> > 3+0 records in
> > 2+0 records out
> > 1024 bytes transferred in 1 secs (1024 bytes/sec)
> >
> > After that disklabel -r reports no label on the disk :-(
>
> ...right... it's not letting you write over the label area for some
> reason. However, I had fixed this, I thought...
>
> Please make sure you have arch/hp300/dev/sd.c revision:
>
> $NetBSD: sd.c,v 1.29 1997/01/30 09:14:20 thorpej Exp $
>
> Folks ... when reporting problems, it is _vitally_ important that you
> include all relevant information, including revisions of source
> files for relevant drivers, uname output, etc. It's almost impossible
> to determine what's actually going on otherwise.
>
> Jason R. Thorpe thorpej@nas.nasa.gov
> NASA Ames Research Center Home: 408.866.1912
> NAS: M/S 258-6 Work: 415.604.0935
> Moffett Field, CA 94035 Pager: 415.428.6939
>