Strange disk problems make the system lock up

[Scot Hetzel]

On Wed, 16 Feb 2005 21:58:37 +0100, Charles Erik McDonald
<charles-erik at mcdonald.no> wrote:
> > >> Do you have any error messages related to ad2 or ad3 in
> /var/log/messages?
> no.
> 
> > >>I have two large disks:
> > >>
> > >>/dev/ad2       144G    124G    9.2G    93%    /mnt/sp1604n
> > >>/dev/ad3       226G    202G    5.2G    98%    /mnt/wd2500pb
> >
> > >Did you use disklabel on these disks (/dev/ad2s1 and /dev/ad3s1) to
> > >create a partition on the slice?
> >
> > The above looks like an excerpt of `df`, meaning that not only was
> bsdlabel
> > not used, but neither was fdisk. That could be a problem for some things
> > that at least expect a partition table somewhere.
> 
> Correct, it is from 'df', but both disks were initialized from within
> the fdisk editor
> in the installer, where I used the "use entire disk" option.
> 

> So, for example:
> 
> bastion(root):/usr/src#disklabel /dev/ad2
> disklabel: /dev/ad2: no valid label found
> bastion(root):/usr/src#disklabel /dev/ad2s1
> # /dev/ad2s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>  c: 312576642        0    unused        0     0         # "raw" part,
> don't edit
> bastion(root):/usr/src#disklabel /dev/ad3
> disklabel: /dev/ad3: no valid label found
> bastion(root):/usr/src#disklabel /dev/ad3s1
> # /dev/ad3s1:
> 8 partitions:
> #        size   offset    fstype   [fsize bsize bps/cpg]
>  c: 488392002        0    unused        0     0         # "raw" part,
> don't edit
> bastion(root):/usr/src#
> 
you don't have any partitions on those disks.

You need to use disklabel to create an "a" partition.


a: 488392002        0    BSD        0     0         #
c: 488392002        0    unused        0     0         # "raw" part


Scot