Re: Request for testers of ATA RAID support

2002-03-11 Thread NAKAJI Hiroyuki

> In <[EMAIL PROTECTED]> 
>   Soren Schmidt <[EMAIL PROTECTED]> wrote:

SS> As some might have noticed I've done some significant work on
SS> the ATA RAID support (for Promise & Highpoint controllers)
SS> all thanks to Advanis which has made this possible.

SS> The code as it is now in -current allows for RAID1's (mirrors)
SS> to be properly handled when a disk dies, that means the
SS> system continues on the good disk and logs the loss of mirror
SS> to the console.

After this commit, I'm not sure, current kernel cannot detect ata buses on
my .

Any hint is appreciated.

With new kernel on Thu Feb 28 14:07:18 JST 2002, I got following boot
message. And yesterday's kernel also has same problem, that is, atapci0
cannot be detected properly and ar disk is not available.

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #3: Thu Feb 28 14:07:18 JST 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NAKAJI
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0469000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc04690a8.
Preloaded elf module "/boot/kernel/linux.ko" at 0xc04690f8.
Preloaded elf module "/boot/kernel/agp.ko" at 0xc04691a4.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc046924c.
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium 4 (1399.85-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf0a  Stepping = 10
  
Features=0x3febf9ff
real memory  = 671023104 (655296K bytes)
avail memory = 647380992 (632208K bytes)
Using $PIR table, 10 entries at 0xc00fdec0
ACPI-0161: *** Error: AcpiLoadTables: Could not get RSDP, AE_NO_ACPI_TABLES
ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_NO_ACPI_TABLES
ACPI: table load failed: AE_NO_ACPI_TABLES
apm0:  on motherboard
apm0: found APM BIOS v1.2, connected at v1.2
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
agp0:  mem 0xe000-0xe3ff at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
pcib2:  at device 30.0 on pci0
pci2:  on pcib2
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0x9000-0x907f mem 0xe900-0xe97f 
irq 9 at device 1.0 on pci2
xl0: Ethernet address: 00:01:02:c2:15:af
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ahc0:  port 0x9400-0x94ff mem 
0xe9001000-0xe9001fff irq 11 at device 2.0 on pci2
aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs
atapci0:  port 
0xa800-0xa8ff,0xa400-0xa403,0xa000-0xa007,0x9c00-0x9c03,0x9800-0x9807 irq 5 at device 
5.0 on pci2
pcib2: device atapci0 requested unsupported I/O range 0x0-0x9c00 (decoding 
0x9000-0xafff)
pcib2: device atapci0 requested unsupported I/O range 0x0-0xa400 (decoding 
0x9000-0xafff)
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci1:  port 0xf000-0xf00f at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
pci0:  at device 31.2 (no driver attached)
pci0:  at device 31.3 (no driver attached)
pci0:  at device 31.4 (no driver attached)
pcm0:  port 0xc000-0xc03f,0xbc00-0xbcff irq 11 at device 31.5 on 
pci0
orm0:  at iomem 0xd-0xd57ff,0xc-0xc on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: failed to get data.
psm0:  irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
fdc0:  at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: IEEE1284 device found /NIBBLE/ECP/ECP_RLE
Probing for PnP devices on ppbus0:
ppbus0:  PRINTER POSTSCRIPT
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
ppc1: cannot reserve I/O port range
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
ad0: 2441MB  [4960/16/63] at ata0-master WDMA2
ad1: 14655MB  [29777/16/63] at ata0-slave UDMA66
ad3: 9765MB  [19841/16/63] at ata1-slave UDMA33
acd0: CDROM  at ata1-master PIO3
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/da0s1a
da0 at ahc0 bus 0 target 0 lun 0
da0:  Fixed Direct Access SCSI-2 device 
da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled
da0: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C)
da1 at ahc0 bus 0 target 4 lun 0
da1:  Fixed Direct Access SCSI-3 device 
da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
da2 at ahc0 bus

Request for testers of ATA RAID support

2002-03-03 Thread Søren Schmidt


As some might have noticed I've done some significant work on
the ATA RAID support (for Promise & Highpoint controllers)
all thanks to Advanis which has made this possible.

The code as it is now in -current allows for RAID1's (mirrors)
to be properly handled when a disk dies, that means the
system continues on the good disk and logs the loss of mirror
to the console.

The hotswap part of the ATA driver has been extended with 
functions to enable the bad disk to be detached with atacontrol
and if it is in a removeable enclosure, it can be swapped with
a new good disk even while the system is running.
When the new disk is attached again with atacontrol, the 
ATA driver will mark it as a SPARE disk if its located 
where the failed disk was before.

Now the really interesting part is the new rebuild command
in atacontrol, that will bring the SPARE disk up to date,
and when done will set the RAID to fully functional again.

All the above is properly written to the config sectors on
the disks, so that the BIOS will pick up any changes that
happend when the ATA driver was in control.

If you have Promise SuperSwap enclosures, the state of the
disks will be shown by the LEDs, red for broken disk, orange
for rebuilding and green for online.

All this said I need testers to really give this new functionality
a run for its money, so please, if you have the HW needed for
this (Promise Fasttrak or a Highpoint controller with ATA disks)
please give it a whirl and let me know how it works out.

Thanks!

-Søren

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message