Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 11 Nov 2001 20:31:03 +0100 (CET)
From:      Cyrille Lefevre <clefevre@citeweb.net>
To:        John De Boskey <jwd@FreeBSD.org>
Cc:        Stable List <freebsd-stable@FreeBSD.org>
Subject:   Re: "disklabel -rw ar0 auto"  breaks HPT raid0+1
Message-ID:  <200111111931.fABJV3j10940@gits.dyndns.org>
In-Reply-To: <20011111063730.A3860@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
John De Boskey wrote:
> Hi,
> 
>    I have an ABIT KT7A-RAID motherboard with the builtin
> HPT370 controller:
> 
> atapci1: <HighPoint HPT370 ATA100 controller> port 0xe800-0xe8ff,0xe400-0xe403,0
> 
> ar0: 190792MB <ATA RAID0+1 array> [24322/255/63] subdisks:
>   ad6: 95396MB <WDC WD1000BB-00CCB0> [193821/16/63] at ata3-master UDMA100
>   ad5: 95396MB <WDC WD1000BB-00CCB0> [193821/16/63] at ata2-slave UDMA100
>   ad4: 95396MB <WDC WD1000BB-00CCB0> [193821/16/63] at ata2-master UDMA100
>   ad7: 95396MB <WDC WD1000BB-00CCB0> [193821/16/63] at ata3-slave UDMA100
> 
> 
>    After setting up the raid (stripes are quick, mirror takes 4+ hours)
> and booting the machine I get the above.
> 
>    The disklabel command:
> 
> disklabel -rw ar0 auto
> 
>    creates and writes a label.
> 
> newfs -c 22 /dev/ar0c
> 
>    writes a filesystem on to the disk which can then be mounted and used.
> However, when the system is rebooted, the HPT controller says the stripe
> has been broken and needs to be re-synced. After re-syncing the array comes
> up fine and continues to work correctly across reboots with no problems.
> 
>    Having debugged this a few times, it appears that disklabel is writing
> data over the control information at the head of the disks. Looking at the
> ata-raid.c source code, it appears to be reserving 10 blocks. Am I stuck
> simply increasing this number until the problem goes away or is there
> any real information on the control structures being written out?

as I understand it, you are partitionning your drive in "dangerously
dedicated mode" which is the wrong way to go. to avoid this problem
you have to partition your drive using fdisk and to create your BSD
slices w/in MSDOS partitions. maybe I'm wrong, but I'm almost sure
I'm not.

Cyrille.
-- 
Cyrille Lefevre                 mailto:clefevre@citeweb.net

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111111931.fABJV3j10940>