Date: Thu, 30 Jul 1998 10:24:21 +0200 (CEST) From: Malte Lance <malte@webmore.com> To: Jim Van Baalen <vansax@mail.websidestory.com> Cc: malte.lance@gmx.net, questions@FreeBSD.ORG Subject: Re: Can't Newfs Disk Message-ID: <13760.11286.624337.23002@neuron.webmore.de> In-Reply-To: <Pine.BSI.3.96.980729095851.4174A-100000@mail.websidestory.com> References: <13758.65215.76314.466555@neuron.webmore.de> <Pine.BSI.3.96.980729095851.4174A-100000@mail.websidestory.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jim,
there are two preconditions to use a harddisk-device:
1. The kernel must be configured to use it
Example:
disk sd0 at scbus0 target 0 unit 0
disk sd1 at scbus0 target 1 unit 0
disk sd2 at scbus0 target 2 unit 0
disk sd3 at scbus0 target 5 unit 0
Edit your kernel-configfile if you need to.
2. There must be a special file present in /dev
There is a convention about the naming of this special
files. Have a look at /dev/MAKEDEV.
For "how to create that special file i am interested in",
see Dave's post.
Malte.
Jim Van Baalen writes:
> This does not seem to work
>
> su-2.01# newfs -N /dev/rsd1s4c
> newfs: /dev/rsd1s4c: No such file or directory
>
> The existing rsd1 devices are
>
> u-2.01# ls -l /dev/rsd1*
> crw-r----- 1 root wheel 13, 0x0001000a Mar 30 1997 /dev/rsd1
> crw------- 1 root wheel 13, 0x20000008 Mar 11 1997 /dev/rsd1.ctl
> crw-r----- 1 root operator 13, 8 Mar 11 1997 /dev/rsd1a
> crw-r----- 1 root operator 13, 9 Mar 11 1997 /dev/rsd1b
> crw-r----- 1 root operator 13, 10 Jul 28 18:21 /dev/rsd1c
> crw-r----- 1 root operator 13, 11 Mar 11 1997 /dev/rsd1d
> crw-r----- 1 root operator 13, 12 Mar 11 1997 /dev/rsd1e
> crw-r----- 1 root operator 13, 13 Mar 11 1997 /dev/rsd1f
> crw-r----- 1 root operator 13, 14 Mar 11 1997 /dev/rsd1g
> crw-r----- 1 root operator 13, 15 Mar 11 1997 /dev/rsd1h
> crw-r----- 1 root wheel 13, 0x0002000a Mar 30 1997 /dev/rsd1s1
> crw-r----- 1 root wheel 13, 0x00020008 Mar 30 1997 /dev/rsd1s1a
> crw-r----- 1 root wheel 13, 0x0002000a Mar 30 1997 /dev/rsd1s1c
> crw-r----- 1 root operator 13, 0x0003000a Mar 11 1997 /dev/rsd1s2
> crw-r----- 1 root operator 13, 0x0004000a Mar 11 1997 /dev/rsd1s3
> crw-r----- 1 root operator 13, 0x0005000a Mar 11 1997 /dev/rsd1s4
>
> It looks like rsd1c is supported??
>
> I went through this process on a 2.2.7 machine the other day and
> /dev/rsd1c worked.
>
> I tried
>
> su-2.01# newfs -N /dev/rsd1s1c
> newfs: /dev/rsd1s1c: Device not configured
>
> Oh well, this seemed like it made sense.
>
> Should I create /dev/rsd1s4c? It doesn't make much sense to me that
> the necessary devices to add a second drive are not part of the standard
> OS. Is their a document somewhere that explains which devices should be
> associated with standard partitions when secondary disks are used? Thanks.
>
> Jim
>
>
> On Wed, 29 Jul 1998, Malte Lance wrote:
>
> > Jim Van Baalen writes:
> >
> > 2.2.6 does not use the compatibility-slices anymore.
> >
> > > newfs -N /dev/rsd1c
> >
> > Try newfs -N /dev/rsd1s4c
> >
> > Malte.
> >
> > > I have just added a second disk to a machine and I can't newfs a
> > > filesystem on this disk. I have been through this process several
> > > times in the last week on different machines and have not had this
> > > problem. The machine is running 2.2.6-RELEASE. It sees the second
> > > disk at boot time
> > >
> > > Jul 28 13:49:07 host2 /kernel: sd1(ahc0:2:0): Direct-Access 4340MB (8888924 512 byte sectors)
> > >
> > > It seems to accept a disklabel. I added
> > >
> > > st34572w|Seagate ST34572W SCSI: \
> > > :dt=SCSI:ty=winchester:se#512:nt#8:ns#176:nc#6300: \
> > > :pc#8870400:oc#0:
> > >
> > > to /etc/disktab.
> > >
> > > disklabel -r -w sd1 st34572w
> > >
> > > returns no errors, but newfs fails.
> > >
> > > newfs -N /dev/rsd1c
> > > newfs: ioctl (GDINFO): Invalid argument
> > > newfs: /dev/rsd1c: can't read disk label; disk type must be specified
> > >
> > > An fdisk looks the same as on other systems to which I have added the
> > > same model disk.
> > >
> > > fdisk sd1
> > > ******* Working on device /dev/rsd1 *******
> > > parameters extracted from in-core disklabel are:
> > > cylinders=6300 heads=8 sectors/track=176 (1408 blks/cyl)
> > >
> > > Figures below won't work with BIOS for partitions not in cyl 1
> > > parameters to be used for BIOS calculations are:
> > > cylinders=6300 heads=8 sectors/track=176 (1408 blks/cyl)
> > >
> > > fdisk: Invalid fdisk partition table found
> > > Media sector size is 512
> > > Warning: BIOS sector numbering starts with sector 1
> > > Information from DOS bootblock is:
> > > The data for partition 1 is:
> > > sysid 108,(unknown)
> > > start 1819044972, size 1819044972 (888205 Meg), flag 6c
> > > beg: cyl 364/ sector 44/ head 108;
> > > end: cyl 364/ sector 44/ head 108
> > > The data for partition 2 is:
> > > sysid 108,(unknown)
> > > start 1819044972, size 1819044972 (888205 Meg), flag 6c
> > > beg: cyl 364/ sector 44/ head 108;
> > > end: cyl 364/ sector 44/ head 108
> > > The data for partition 3 is:
> > > sysid 108,(unknown)
> > > start 1819044972, size 1819044972 (888205 Meg), flag 6c
> > > beg: cyl 364/ sector 44/ head 108;
> > > end: cyl 364/ sector 44/ head 108
> > > The data for partition 4 is:
> > > sysid 165,(FreeBSD/NetBSD/386BSD)
> > > start 1, size 8870399 (4331 Meg), flag 80
> > > beg: cyl 0/ sector 2/ head 0;
> > > end: cyl 155/ sector 48/ head 7
> > >
> > > Hints??
> > >
> > > Jim
> > >
> > >
> > > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > > with "unsubscribe freebsd-questions" in the body of the message
> >
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?13760.11286.624337.23002>