Strange disk problems make the system lock up

[Scot Hetzel]

On Wed, 16 Feb 2005 23:31:25 +0100, Godwin Stewart <gstewart at bonivet.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wed, 16 Feb 2005 21:58:37 +0100, Charles Erik McDonald
> <charles-erik at mcdonald.no> wrote:
> 
> > bastion(root):#mount -t ufs /dev/ad3s1 /mnt/wd2500pb/
> > mount: /dev/ad3s1 on /mnt/wd2500pb: incorrect super block
> > bastion(root):#mount -t ufs /dev/ad3s1c /mnt/wd2500pb/
> > mount: /dev/ad3s1c on /mnt/wd2500pb: incorrect super block
> > bastion(root):#mount -t ufs /dev/ad3 /mnt/wd2500pb/
> > bastion(root):#
> 
> Well, I don't know anything near enough about UFS to be able to speculate
> on why a valid disklabel is found while the entire physical disk is mounted.
> What I would say is that the system freezing when trying to umount the
> filesystems could have something to do with this oddity.
> 
> However, one thing I'd do ASAP is back up the data (I know 300+ GB is a lot
> of data) and boot into single user mode so that the 2 disks aren't mounted.
> I'd then newfs ad{2,3}s1c and modify my fstab to reflect the fact that I'm
> now using filesystems here rather than just ad{2,3}, boot normally and
> restore the data.
> 
The problem is that he only has the "c" partition, which is reserved
to specifying the entire disk.  He needs to use disklabel to create a
partion using one of a,b,d-h.

see "man disklabel"

Scot