Date: Mon, 1 Sep 2008 15:57:09 +0300 From: "Max E. Kuznecov" <syhpoon@syhpoon.name> To: freebsd-geom@freebsd.org Subject: raid & label issues Message-ID: <20080901125709.GA26304@syhpoon-portaone.portaone.com>
next in thread | raw e-mail | index | archive | help
Hi,
I have a RAID1 created with atacontrol.
After installation I create a label, say: tunefs -L root /dev/ar0s1a
and put /def/ufs/root as rootfs into fstab.
So I expect the system will boot from raid (ar0s1a) device, but it
won't.
It occurs that tunefs create label not only on ar0 device itself but on
the raid components as well, in my case they are ad4 and ad6.
And after reboot I've got my system booted from ad4, i.e. the first
device with 'root' label on it. I've skimmed through the geom_label
sources and, indeed, it creates /dev/ufs/<label> entry for the first
device it tastes, and all the subsequent are ignored.
So the question is - is it possible to overcome this situtation and
force system to boot from right device?
My setup:
# uname -sr
FreeBSD 6.3-RELEASE
# pciconf -lv
atapci0@pci0:31:1: class=0x01018a card=0x24d08086 chip=0x24db8086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB/ER (ICH5/ICH5R) EIDE Controller'
class = mass storage
subclass = ATA
atapci1@pci0:31:2: class=0x01018f card=0x24d18086 chip=0x24d18086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801EB (ICH5) SATA Controller'
class = mass storage
subclass = ATA
# dmesg | grep RAID
hptrr: HPT RocketRAID controller driver v1.1 (Jan 16 2008 04:16:19)
ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
ar0: 76319MB <Intel MatrixRAID RAID1> status: DEGRADED
Thanks
--
~syhpoon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080901125709.GA26304>