Re: Native SATA vs. PATA-emulation - difference?
Patrick M. Hausen [EMAIL PROTECTED] wrote: 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: [...] I set up a GEOM mirror on my boot disk, again, everythings working as expected: [...] 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? Are the disk sizes exactly the same in both cases? Please provide dmesg output from the 2nd case (native SATA). Most GEOM modules (gmirror, gjournal etc.) store their meta data in the last sector of the device. If the size of the devices change when you change the emulation mode, gmirror won't be able to locate the sector that contains the meta data anymore. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd anyone new to programming should be kept as far from C++ as possible; actually showing the stuff should be considered a criminal offence -- Jacek Generowicz ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
Hi, all! On Mon, May 21, 2007 at 02:36:48PM +0200, Oliver Fromme wrote: Are the disk sizes exactly the same in both cases? Please provide dmesg output from the 2nd case (native SATA). Good point ;-) But ... P-ATA emulation: atapci0: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master UDMA33 Native S-ATA: atapci0: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master SATA150 ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master SATA150 I don't see a difference here that could be the root cause of the problem. Besides, I'm using ad4s1 and ad6s1 as the providers for gmirror, so a few sectors plus/minus at the very end of the raw disk should not matter. Thanks, Patrick -- punkt.de GmbH * Vorholzstr. 25 * 76137 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 [EMAIL PROTECTED] http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
Patrick M. Hausen wrote this message on Mon, May 21, 2007 at 15:18 +0200: Hi, all! On Mon, May 21, 2007 at 02:36:48PM +0200, Oliver Fromme wrote: Are the disk sizes exactly the same in both cases? Please provide dmesg output from the 2nd case (native SATA). Good point ;-) But ... P-ATA emulation: atapci0: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master UDMA33 Native S-ATA: atapci0: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master SATA150 ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master SATA150 I don't see a difference here that could be the root cause of the problem. Besides, I'm using ad4s1 and ad6s1 as the providers for gmirror, so a few sectors plus/minus at the very end of the raw disk should not matter. That doesn't show the exact size... run diskinfo on each of them and that will tell you the reported to geom size.. -- John-Mark Gurney Voice: +1 415 225 5579 All that I will do, has been done, All that I have, has not. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Native SATA vs. PATA-emulation - difference?
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: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ServerWorks HT1000 SATA150 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f irq 11 at device 14.1 on pci1 ata4: ATA channel 0 on atapci1 ata5: ATA channel 1 on atapci1 atapci2: ServerWorks HT1000 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: ATA channel 0 on atapci2 ata1: ATA channel 1 on atapci2 acd0: CDROM CD-224E-N/1.AA at ata0-slave UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master UDMA33 ad8: DMA limited to UDMA33, device found non-ATA66 cable ad8: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata4-master UDMA33 ad10: DMA limited to UDMA33, device found non-ATA66 cable ad10: 157066MB WDC WD1600YS-01SHB1 20.06C06 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 [EMAIL PROTECTED] http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
On Fri, 2007-05-18 at 11:04 +0200, Patrick M. Hausen wrote: to UDMA33. I figure, they can safely be ignored? Only if there isn't some massive performance degradation. ports/benchmarks/bonie++ can tell you that. As for the boot loader and your gmirror volumes; it's hard to say. It's possible that there is some absolute or non-relative data in there related to the device and the bus. Also: Maybe the geometry of the devices changes between modes? Send us the comparable dmesg(8) in both modes? ~BAS -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
On Fri, 2007-05-18 at 10:57 -0400, Brian A. Seklecki wrote: On Fri, 2007-05-18 at 11:04 +0200, Patrick M. Hausen wrote: to UDMA33. I figure, they can safely be ignored? Only if there isn't some massive performance degradation. ports/benchmarks/bonie++ can tell you that. As for the boot loader and your gmirror volumes; it's hard to say. It's possible that there is some absolute or non-relative data in there related to the device and the bus. Also: Maybe the geometry of the devices changes between modes? Send us the comparable dmesg(8) in both modes? ~BAS On my Intel ICH7 based laptop, switching from SATA/PATA emulation to SATA native mode changes the device of my HD from ad0 to ad4. YMMV signature.asc Description: This is a digitally signed message part
Re: Native SATA vs. PATA-emulation - difference?
right which I never understood absolute device number. you can choose to do that in obsd/nbsd, but fbsd seems to psuedo magically do it. reminds me Solaris. ~BAS On Fri, 2007-05-18 at 16:25 +0100, Tom Evans wrote: On Fri, 2007-05-18 at 10:57 -0400, Brian A. Seklecki wrote: On Fri, 2007-05-18 at 11:04 +0200, Patrick M. Hausen wrote: to UDMA33. I figure, they can safely be ignored? Only if there isn't some massive performance degradation. ports/benchmarks/bonie++ can tell you that. As for the boot loader and your gmirror volumes; it's hard to say. It's possible that there is some absolute or non-relative data in there related to the device and the bus. Also: Maybe the geometry of the devices changes between modes? Send us the comparable dmesg(8) in both modes? ~BAS On my Intel ICH7 based laptop, switching from SATA/PATA emulation to SATA native mode changes the device of my HD from ad0 to ad4. YMMV -- Brian A. Seklecki [EMAIL PROTECTED] Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
On Friday 18 May 2007 11:34:52 am Brian A. Seklecki wrote: On Fri, 2007-05-18 at 16:25 +0100, Tom Evans wrote: On Fri, 2007-05-18 at 10:57 -0400, Brian A. Seklecki wrote: On Fri, 2007-05-18 at 11:04 +0200, Patrick M. Hausen wrote: to UDMA33. I figure, they can safely be ignored? Only if there isn't some massive performance degradation. ports/benchmarks/bonie++ can tell you that. As for the boot loader and your gmirror volumes; it's hard to say. It's possible that there is some absolute or non-relative data in there related to the device and the bus. Also: Maybe the geometry of the devices changes between modes? Send us the comparable dmesg(8) in both modes? ~BAS On my Intel ICH7 based laptop, switching from SATA/PATA emulation to SATA native mode changes the device of my HD from ad0 to ad4. YMMV right which I never understood absolute device number. you can choose to do that in obsd/nbsd, but fbsd seems to psuedo magically do it. reminds me Solaris. ~BAS If you don't want this behavior then remove options ATA_STATIC_ID from your kernel config. JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Native SATA vs. PATA-emulation - difference?
Patrick M. Hausen wrote: The devices are probed by FreeBSD like this: server# dmesg | grep ata atapci0: ServerWorks HT1000 SATA150 controller port 0xc080-0xc087,0xc000-0xc003,0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb80f mem 0xff3fe000-0xff3f irq 11 at device 14.0 on pci1 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ServerWorks HT1000 SATA150 controller port 0xcc00-0xcc07,0xc880-0xc883,0xc800-0xc807,0xc480-0xc483,0xc400-0xc40f irq 11 at device 14.1 on pci1 ata4: ATA channel 0 on atapci1 ata5: ATA channel 1 on atapci1 atapci2: ServerWorks HT1000 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 2.1 on pci0 ata0: ATA channel 0 on atapci2 ata1: ATA channel 1 on atapci2 acd0: CDROM CD-224E-N/1.AA at ata0-slave UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata3-master UDMA33 ad8: DMA limited to UDMA33, device found non-ATA66 cable ad8: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata4-master UDMA33 ad10: DMA limited to UDMA33, device found non-ATA66 cable ad10: 157066MB WDC WD1600YS-01SHB1 20.06C06 at ata5-master UDMA33 Everything's working fine, besides the messages about DMA limited to UDMA33. I figure, they can safely be ignored? Yes it can be ignored, it just shows the wrong settings. I think its fixed in STABLE. greetings, philipp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
