From owner-freebsd-stable@FreeBSD.ORG Fri May 18 09:04:37 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F030216A400 for ; Fri, 18 May 2007 09:04:37 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.freebsd.org (Postfix) with ESMTP id 7188313C455 for ; Fri, 18 May 2007 09:04:37 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id l4I94aqJ013976 for ; Fri, 18 May 2007 11:04:36 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id l4I94ZZT018416 for ; Fri, 18 May 2007 11:04:36 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id l4I94ZTN018415 for freebsd-stable@freebsd.org; Fri, 18 May 2007 11:04:35 +0200 (CEST) (envelope-from ry93) Date: Fri, 18 May 2007 11:04:35 +0200 From: "Patrick M. Hausen" To: freebsd-stable@freebsd.org Message-ID: <20070518090435.GB17241@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.15 (2007-04-06) Subject: Native SATA vs. PATA-emulation - difference? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2007 09:04:38 -0000 Hi, all! I have a Tyan barebone on my desk that is based on the ServerWorks HT1000 chipset. It features 4 SATA connectors and 4 hot plug drive bays. I installed FreeBSD on the system with the BIOS settings as set by the manufacturer. This includes setting the "SATA mode" to "P-ATA emulation". The devices are probed by FreeBSD like this: server# dmesg | grep ata atapci0: port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3fffff irq 11 at device 14.0 on pci1 ata2: on atapci0 ata3: on atapci0 atapci1: port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f irq 11 at device 14.1 on pci1 ata4: on atapci1 ata5: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: on atapci2 ata1: on atapci2 acd0: CDROM at ata0-slave UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 157066MB at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 157066MB at ata3-master UDMA33 ad8: DMA limited to UDMA33, device found non-ATA66 cable ad8: 157066MB at ata4-master UDMA33 ad10: DMA limited to UDMA33, device found non-ATA66 cable ad10: 157066MB at ata5-master UDMA33 Everything's working fine, besides the messages about DMA limited to UDMA33. I figure, they can safely be ignored? I set up a GEOM mirror on my boot disk, again, everythings working as expected: server# cat /boot/loader.conf geom_mirror_load="YES" server# gmirror list Geom name: gm0s1 State: COMPLETE Components: 2 Balance: round-robin Slice: 4096 Flags: NONE GenID: 2 SyncID: 1 ID: 2124128128 Providers: 1. Name: mirror/gm0s1 Mediasize: 164694458368 (153G) Sectorsize: 512 Mode: r4w4e4 Consumers: 1. Name: ad4s1 Mediasize: 164694458880 (153G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 2 SyncID: 1 ID: 1671205054 2. Name: ad6s1 Mediasize: 164694458880 (153G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: NONE GenID: 2 SyncID: 1 ID: 1645626982 Now for the part that I do not understand ;-) Out of curiosity I changed the BIOS setup setting for the SATA controller to "native SATA". When booting, the controller and all disks are probed OK. The output shows "SATA150" for the devices. Yet, the root filesystem on /dev/mirror/gm0s1 cannot be found. Hitting "?" at the prompt that asks for manual root dev specification, I get "ad4, ad4s1, ad4s1a ... ad6, ad6s1, ad6s1a ...". I can even boot ad4s1 to single user mode, so all data on the disk can be read just like when in "P-ATA emulation" mode. Why does gmirror fail to load? An answer to this question could prove critical in the future if one of theses servers fails an I need to put the disks in a different chassis/mainboard combination. I used to think that in LBA mode all disks and disk access methods were created equal. Thanks in advance, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285