Date: Wed, 16 Feb 2005 21:58:37 +0100 From: Charles Erik McDonald <charles-erik@mcdonald.no> To: Godwin Stewart <gstewart@bonivet.net> Cc: freebsd-stable@freebsd.org Subject: Re: Strange disk problems make the system lock up Message-ID: <4213B3FD.6060400@mcdonald.no> In-Reply-To: <20050216175920.4f60007c.gstewart@bonivet.net> References: <42134454.7030306@mcdonald.no> <790a9fff05021607456ec0406d@mail.gmail.com> <20050216175920.4f60007c.gstewart@bonivet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> >> 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.
Disk name: ad2 FDISK Partition
Editor
DISK Geometry: 19457 cyls/255 heads/63 sectors = 312576705 sectors
(152625MB)
Offset Size(ST) End Name PType Desc Subtype
Flags
0 63 62 - 12 unused 0
63 312576642 312576704 ad2s1 8 freebsd 165
312576705 5103 312581807 - 12 unused
0
and
Disk name: ad3 FDISK Partition
Editor
DISK Geometry: 30401 cyls/255 heads/63 sectors = 488392065 sectors
(238472MB)
Offset Size(ST) End Name PType Desc Subtype
Flags
0 63 62 - 12 unused 0
63 488392002 488392064 ad3s1 8 freebsd 165
488392065 5103 488397167 - 12 unused
0
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#
.. it doesn't have valid disklabels on /dev/ad?
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):#
.. still /dev/ad3 mounts just fine. I can probably use it and it'll be
rock steady for a week now before suddenly it'll go offline. If I then
try to umount it the system will freeze up.
So what I am doing wrong is I've used /dev/ad2 instead of /dev/ad2s1 for
my partition?
Will I have to reformat the drives and use standard partitions? (why? :-)
Thanks for your time,
Erik
ps. If I am wasting your time please point me in the right direction and
I'll do some research on my own.
Right now I'm kinda stuck.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.8 - Release Date: 14.02.2005
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4213B3FD.6060400>