From owner-freebsd-questions@FreeBSD.ORG Sun May 27 21:31:08 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 350DE16A4FC for ; Sun, 27 May 2007 21:31:08 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.freebsd.org (Postfix) with ESMTP id CE53E13C468 for ; Sun, 27 May 2007 21:31:07 +0000 (UTC) (envelope-from tedm@toybox.placo.com) Received: from TEDSDESK (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) by mail.freebsd-corp-net-guide.com (8.13.8/8.13.8) with SMTP id l4RLUtNF080927; Sun, 27 May 2007 14:31:00 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Date: Sun, 27 May 2007 14:32:24 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <51745.74.64.6.149.1180267419.squirrel@mail.el.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896 Importance: Normal X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (mail.freebsd-corp-net-guide.com [65.75.192.90]); Sun, 27 May 2007 14:31:01 -0700 (PDT) Cc: rsmith@xs4all.nl, freebsd-questions@freebsd.org Subject: RE: raid or not raid X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 May 2007 21:31:08 -0000 > -----Original Message----- > From: kalin mintchev [mailto:kalin@el.net] > Sent: Sunday, May 27, 2007 5:04 AM > To: Ted Mittelstaedt > Cc: kalin@el.net; freebsd-questions@freebsd.org; rsmith@xs4all.nl > Subject: RE: raid or not raid > > > > > > > >> -----Original Message----- > >> From: owner-freebsd-questions@freebsd.org > >> [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of kalin mintchev > >> Sent: Thursday, May 24, 2007 4:11 PM > >> To: freebsd-questions@freebsd.org > >> Cc: rsmith@xs4all.nl > >> Subject: Re: raid or not raid > >> > >> > >> > On Thu, May 24, 2007 at 06:30:06AM -0400, kalin mintchev wrote: > >> >> > >> >> so nobody on this list knows anything about raid? > >> >> wrong list? > >> >> > >> >> > hi all.. > >> >> > > >> >> > i have a box in a remote hosting facility that claims that > >> the machine > >> >> has > >> >> > two discs raided in it but df and fstab show only one disc with a > >> >> bunch of > >> >> > slices. > >> >> > under devices there is another name - ad6 - but it's not mounted > >> >> anywhere. > >> >> > the one i see both in df and the fstab is ad4 with one big slice > >> and > >> >> > different partitions.... > >> > > >> > My (VIA Tech V-RAID) raid disk shows up as ar0, although the ad4 and > >> ad6 > >> > device nodes exist as well. > >> > > >> > Do you have the ataraid device in the kernel? > >> > >> yes. but isn;t that in by default in 5.4 GENERIC?! > >> > >> >> > they insist there are 2 raided discs in tha machine. the os > >> is 5.4 and > >> >> i > >> >> > think at that point the raid drivers were still considered > >> >> > 'experimental'. > >> > > >> > Then ask them how it's done. > >> > > >> >> > it makes sense to me that if i don't see a second drive in the > >> fstab > >> >> there > >> >> > isn;t any mounting which means that there is no raid going on... > >> > > >> > If you're seeing an ad device, it's not RAID-ed, AFAIK. > >> > > >> >> > is there any other way i can make sure if raid is actually on? > >> >> > would there will be any logs somewhere? > >> >> > the machine has been up for about 2 years and the dmesg is long > >> >> gone... > >> > > >> > It should be in /var/run/dmesg.boot. > >> > >> thanks. i guess that solves the ad6 mistery: > >> > >> atapci0: port > >> 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device > 31.1 on pci0 > >> ata0: channel #0 on atapci0 > >> ata1: channel #1 on atapci0 > >> atapci1: port > >> 0xcc80-0xcc8f,0xcc98-0xcc9b,0xcca0-0xcca7,0xccb0-0xccb3,0xccb8-0xccbf > >> irq > >> 18 at device 31.2 on pci0 > >> ata2: channel #0 on atapci1 > >> ata3: channel #1 on atapci1 > >> ..................................................... > >> ad4: 152587MB [310019/16/63] at > >> ata2-master > >> SATA150 > >> ad6: 152587MB [310019/16/63] at > >> ata3-master > >> SATA150 > >> Mounting root from ufs:/dev/ad4s1a > >> > >> unless "at device 31.2 on pci0" points to some RAID evidence - which i > >> think it's false - than i read this as the ad6 disk sits there unused. > >> am i right?! > >> > >> according to pciconf the atapci0 and atapci1 are differnt conrollers - > >> EIDE and SATA so they can both be on pci0 as 31.1 and 31.2?! still no > >> RAID > >> though... > >> > > > > I've come late to this thread but it's been interesting watching the > > speculation. > > > > Yes, they F'd up the installation. Badly. But you need to > back up every > > scrap of data before trying to fix it. And use FBSD 6.2 on the > next one. > > There's been lots of driver fixes in the ata driver that you want. > > > > ata raid should show all your data on AR not AD!! Here's an example > > from my mailserver: > > > > mail# cat /etc/fstab > > # Device Mountpoint FStype Options Dump > > Pass# > > /dev/ar0s1b none swap sw > 0 0 > > /dev/ar0s1a / ufs rw > 1 1 > > /dev/ar0s1e /usr ufs rw > 2 2 > > /dev/ar0s1d /var ufs rw > 2 2 > > /dev/acd0 /cdrom cd9660 ro,noauto > 0 0 > > mail# > > > > Also, note the following. VERY important! > > > > When you go to setup a RAID mirror on a system, using a UDMA or SATA > > controller, > > (ie: NOT using a RAID5 card or SCSI card or some such) here is what you > > do. > > > > Start by going into the system RAID BIOS on boot, setup your RAID, then > > boot the install disk. Disks ad4 and ad6 will always show. If disk ar0 > > also shows, you can select ar0 and install to that. > > > > IF DISK ar0 DOES NOT SHOW, then your BIOS "metadata" isn't compatible. > > STOP. > > Reboot system. GO into BIOS. DESELECT and DISABLE the RAID. > > > > Boot system with install CD. At the screen that displays ad4 and ad6, > > select > > ad4. Select Minimal install. Don't bother answering any post install > > questions. > > Finish install. Reboot and login to root. At command line, issue > > command: > > > > atacontrol create RAID1 ad4 ad6 > > > > Immediately reboot from the install CD. Now, at the disk > selection screen > > you will see ar0. Select this. Delete all existing partitions and > > recreate > > them, install the full system and your in business. > > nice... thank you. i love condensed instructions. saves so much time... > I should have mentioned that it also isn't necessary to put both disks on separate SATA or UDMA controllers, you can mirror a primary and secondary on the same controller, or a primary on one controller and a secondary on another, or two secondaries, etc. etc. Whatever you want. Also, SATA is hot swap, and the driver can deal with this too. Just make sure to document exactly how you set it up, because if you ever have to replace a failed disk, you will need to know what you did, how the disks were pinned, etc. Ted