Arjan, I appreciate your reply. OK know I know about the lilo. BTW, I was
aware that I needed to use /dev/ataraid/p0, NOT hde/hdg, but thanks for
reminding me anyway.
I now have my "fdisk" results.
fdisk (from 2.4.8-ac7):
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Warning: invalid flag 0x0000 of partition table 5 will be corrected by
w(rite)
Disk /dev/hdg doesn't contain a valid partition table
Disk /dev/hde: 255 heads, 63 sectors, 7476 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hde1 * 6 925 7389900 7 HPFS/NTFS
/dev/hde2 926 14952 112671877+ f Win95 Ext'd (LBA)
/dev/hde3 1 5 40131 16 Hidden FAT16
/dev/hde5 ? 260095 102535 881886022+ 86 NTFS volume set
Disk /dev/hdg: 16 heads, 63 sectors, 53614 cylinders
Units = cylinders of 1008 * 512 bytes
Disk /dev/hdh: 255 heads, 63 sectors, 7476 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdh1 1 7300 58637218+ c Win95 FAT32 (LBA)
/dev/hdh2 7301 7476 1413720 f Win95 Ext'd (LBA)
/dev/hdh5 7301 7476 1413688+ 82 Linux swap
fdisk (from 2.2.19 using Promise's Fasttrak100 ft.o module - this works):
Disk /dev/sda: 255 heads, 63 sectors, 14952 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 6 925 7389900 7 HPFS/NTFS
/dev/sda2 926 14952 112671877+ f Win95 Ext'd (LBA)
/dev/sda3 1 5 40131 16 Hidden FAT16
/dev/sda5 926 14952 112671846 83 Linux native
Disk /dev/sdb: 255 heads, 63 sectors, 7476 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 7300 58637218+ c Win95 FAT32 (LBA)
/dev/sdb2 7301 7476 1413720 f Win95 Ext'd (LBA)
/dev/sdb5 7301 7476 1413688+ 82 Linux swap
This is why I am confused as to what to do now.
Also included is the results from dmesg 2>dmesg.txt 1>&2 using the 2.4.8-ac7
kernel.
, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
CPU: Before vendor init, caps: 0183fbff c1c7fbff 00000000, vendor = 2
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@xxxxxxxxxxxxx)
mtrr: detected mtrr type: Intel
CPU: Before vendor init, caps: 0183fbff c1c7fbff 00000000, vendor = 2
Intel machine check reporting enabled on CPU#0.
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
CPU: After vendor init, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: After generic, caps: 0183fbff c1c7fbff 00000000 00000000
CPU: Common caps: 0183fbff c1c7fbff 00000000 00000000
CPU0: AMD Athlon(tm) Processor stepping 02
per-CPU timeslice cutoff: 731.42 usecs.
SMP motherboard not detected.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1109.8870 MHz.
..... host bus clock speed is 201.7977 MHz.
cpu: 0, clocks: 2017977, slice: 1008988
CPU0<T0:2017968,T1:1008976,D:4,S:1008988,C:2017977>
PCI: PCI BIOS revision 2.10 entry at 0xf1150, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/0686] at 00:04.0
PCI: Found IRQ 3 for device 00:09.0
PCI: Sharing IRQ 3 with 00:04.2
PCI: Sharing IRQ 3 with 00:04.3
PCI: Sharing IRQ 3 with 00:0d.0
PCI: Found IRQ 5 for device 00:0a.0
PCI: Found IRQ 10 for device 00:0b.0
PCI: Sharing IRQ 10 with 00:11.0
PCI: Disabling Via external APIC routing
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Simple Boot Flag extension found and enabled.
Starting kswapd v1.8
VFS: Diskquotas version dquot_6.5.0 initialized
devfs: v0.107 (20010709) Richard Gooch (rgooch@xxxxxxxxxxxxx)
devfs: boot_options: 0x0
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10d
block: queued sectors max/low 511184kB/380112kB, 1536 slots per queue
RAMDISK driver initialized: 16 RAM disks of 94152K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 21
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:04.1
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio
PDC20267: IDE controller on PCI bus 00 dev 68
PCI: Found IRQ 3 for device 00:0d.0
PCI: Sharing IRQ 3 with 00:04.2
PCI: Sharing IRQ 3 with 00:04.3
PCI: Sharing IRQ 3 with 00:09.0
PDC20267: chipset revision 2
PDC20267: not 100% native mode: will probe irqs later
PDC20267: (U)DMA Burst Bit ENABLED Primary MASTER Mode Secondary MASTER
Mode.
ide2: BM-DMA at 0x6800-0x6807, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x6808-0x680f, BIOS settings: hdg:pio, hdh:pio
PDC20265: IDE controller on PCI bus 00 dev 88
PCI: Found IRQ 10 for device 00:11.0
PCI: Sharing IRQ 10 with 00:0b.0
PDC20265: chipset revision 2
PDC20265: not 100% native mode: will probe irqs later
PDC20265: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
ide4: BM-DMA at 0x5000-0x5007, BIOS settings: hdi:pio, hdj:pio
ide5: BM-DMA at 0x5008-0x500f, BIOS settings: hdk:pio, hdl:DMA
hda: Pioneer DVD-ROM ATAPIModel DVD-105S 012, ATAPI CD/DVD-ROM drive
hdc: PLEXTOR CD-R PX-W1210A, ATAPI CD/DVD-ROM drive
hde: IBM-DTLA-307060, ATA DISK drive
hdg: IBM-DTLA-307060, ATA DISK drive
hdh: IC35L060AVER07-0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide2 at 0x8000-0x8007,0x7802 on irq 3
ide3 at 0x7400-0x7407,0x7002 on irq 3
hde: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63,
UDMA(100)
hdg: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63,
UDMA(100)
hdh: 120103200 sectors (61493 MB) w/1916KiB Cache, CHS=119150/16/63,
UDMA(100)
hda: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
hdc: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
ide-floppy driver 0.97
Partition check:
/dev/ide/host2/bus0/target0/lun0:<7>LDM: DEBUG (ldm.c, 877):
validate_partition_table: Found basic MS-DOS partition, not a dynamic disk.
[PTBL] [7476/255/63] p1 p2 < > p3
/dev/ide/host2/bus1/target0/lun0:<7>LDM: DEBUG (ldm.c, 857):
validate_partition_table: No MS-DOS partition found.
unknown partition table
/dev/ide/host2/bus1/target1/lun0:<7>LDM: DEBUG (ldm.c, 877):
validate_partition_table: Found basic MS-DOS partition, not a dynamic disk.
[PTBL] [7476/255/63] p1 p2 < p5 >
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
ide-floppy driver 0.97
ataraid/d0:<7>LDM: DEBUG (ldm.c, 877): validate_partition_table: Found
basic MS-DOS partition, not a dynamic disk.
p1 p2 < >
Promise Fasttrak(tm) Softwareraid driver for linux version 0.02
Drive 0 is 58644 Mb
Drive 1 is 58644 Mb
Raid array consists of 2 drives.
Highpoint HPT370 Softwareraid driver for linux version 0.01
No raid array found
SCSI subsystem driver Revision: 1.00
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
md: linear personality registered
md: raid0 personality registered
md: raid1 personality registered
md: raid5 personality registered
raid5: measuring checksumming speed
8regs : 1697.200 MB/sec
32regs : 1405.600 MB/sec
pII_mmx : 2597.200 MB/sec
p5_mmx : 3320.800 MB/sec
raid5: using function: p5_mmx (3320.800 MB/sec)
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 0.9.1_beta3 by Heinz Mauelshagen (25/01/2001)
lvm -- Driver successfully initialized
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 8192 buckets, 64Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER
VFS: Disk change detected on device fd(2,60)
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 244k freed
8139too Fast Ethernet driver 0.9.18a
PCI: Enabling device 00:09.0 (0004 -> 0007)
PCI: Found IRQ 3 for device 00:09.0
PCI: Sharing IRQ 3 with 00:04.2
PCI: Sharing IRQ 3 with 00:04.3
PCI: Sharing IRQ 3 with 00:0d.0
eth0: D-Link DFE-538TX (RealTek RTL8139) at 0xf0806000, 00:50:ba:4d:b3:61,
IRQ 3
eth0: Identified 8139 chip type 'RTL-8139C'
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
NTFS version 1.1.16
Hopefully this isn't overkill, but the more info I give the easier it may be
to get a resolution. BTW, the fasttrak components of Alan Cox's patch is
compiled into the kernel.
Tried the 2.4.9-ac4 patched kernel, but this won't compile (something to do
with missing the "atomic_desc_and_lock" linkages). Moreover, I used the
MAKEDEV script to make the /dev/ataraid/d0* devices - made sure of that
(although until reading the messages from this news group, I wasn't aware of
the lilo issue.
Alan
-----Original Message-----
From: ataraid-list-admin@xxxxxxxxxx
[mailto:ataraid-list-admin@xxxxxxxxxx]On Behalf Of
ataraid-list-request@xxxxxxxxxx
Sent: Thursday, August 30, 2001 10:02 AM
To: ataraid-list@xxxxxxxxxx
Subject: Ataraid-list digest, Vol 1 #24 - 11 msgs
Send submissions to
ataraid-list@xxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://listman.redhat.com/mailman/listinfo/ataraid-list
or, via email, send a message with subject or body 'help' to
ataraid-list-request@xxxxxxxxxx
You can reach the person managing the list at
ataraid-list-admin@xxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ataraid-list digest..."
Today's Topics:
1. No raid array found (Andreas Thienemann)
2. Re: No raid array found (Arjan van de Ven)
3. Re: No raid array found (Andreas Thienemann)
4. Re: No raid array found (Arjan van de Ven)
5. Re: No raid array found (Andreas Thienemann)
6. Re: No raid array found (Ruediger Biernat)
7. Re: No raid array found (Andreas Thienemann)
8. Re: No raid array found (Arjan van de Ven)
9. Re: No raid array found (Andreas Thienemann)
10. Problems with the Promise Fastrak100 and 2.4.8-ac7 (Alan Miles)
11. Re: Problems with the Promise Fastrak100 and 2.4.8-ac7 (Arjan van de
Ven)
--__--__--
Message: 1
Date: Thu, 30 Aug 2001 13:34:20 +0200 (CEST)
From: Andreas Thienemann <andreas@xxxxxxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
Hi,
I'm trying to get a on-board PDC20265r "raid" controller to work with the
ataraid driver... Unfortunately I had no luck yet...
The problem seems to be that the disks of the raid-1 array are detected as
hde and hdg.
Next the promise fastrak driver tells me that "No raid array found", which
is strange because I rebuild the whole array and the controller says there
is one.
During Kernel compilation I selected CONFIG_BLK_DEV_PDC202XX,
CONFIG_PDC202XX_BURST, CONFIG_PDC202XX_FORCE, CONFIG_BLK_DEV_ATARAID,
CONFIG_BLK_DEV_ATARAID_PDC and CONFIG_BLK_DEV_ATARAID_HPT
thanks for any advice,
andreas
The Kernel messages are the following:
Aug 30 13:14:29 dyn119 kernel: PDC20265: IDE controller on PCI bus 00 dev 80
Aug 30 13:14:29 dyn119 kernel: PCI: Found IRQ 11 for device 00:10.0
Aug 30 13:14:29 dyn119 kernel: PDC20265: chipset revision 2
Aug 30 13:14:29 dyn119 kernel: ide: Found promise 20265 in RAID mode.
Aug 30 13:14:29 dyn119 kernel: PDC20265: not 100%% native mode: will probe
irqs later
Aug 30 13:14:29 dyn119 kernel: PDC20265: ROM enabled at 0xdffd0000
Aug 30 13:14:29 dyn119 kernel: PDC20265: (U)DMA Burst Bit ENABLED Primary
MASTER Mode Secondary MASTER Mode.
Aug 30 13:14:29 dyn119 kernel: ide2: BM-DMA at 0xcc00-0xcc07, BIOS
settings: hde:pio, hdf:pio
Aug 30 13:14:29 dyn119 kernel: ide3: BM-DMA at 0xcc08-0xcc0f, BIOS
settings: hdg:pio, hdh:pio
Aug 30 13:14:29 dyn119 kernel: hda: IC35L040AVER07-0, ATA DISK drive
Aug 30 13:14:29 dyn119 kernel: hdc: SR243T, ATAPI CD/DVD-ROM drive
Aug 30 13:14:29 dyn119 kernel: hde: IC35L040AVER07-0, ATA DISK drive
Aug 30 13:14:29 dyn119 kernel: hdg: IC35L040AVER07-0, ATA DISK drive
Aug 30 13:14:29 dyn119 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Aug 30 13:14:29 dyn119 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Aug 30 13:14:29 dyn119 kernel: ide2 at 0xdc00-0xdc07,0xd802 on irq 11
Aug 30 13:14:29 dyn119 kernel: ide3 at 0xd400-0xd407,0xd002 on irq 11
Aug 30 13:14:29 dyn119 kernel: hda: 80418240 sectors (41174 MB) w/1916KiB
Cache, CHS=5005/255/63, UDMA(33)
Aug 30 13:14:29 dyn119 kernel: hde: 80418240 sectors (41174 MB) w/1916KiB
Cache, CHS=79780/16/63, UDMA(100)
Aug 30 13:14:29 dyn119 kernel: hdg: 80418240 sectors (41174 MB) w/1916KiB
Cache, CHS=79780/16/63, UDMA(100)
Aug 30 13:14:29 dyn119 kernel: ide-floppy driver 0.97
Aug 30 13:14:29 dyn119 kernel: Partition check:
Aug 30 13:14:29 dyn119 kernel: hda: hda1 hda2 hda3
Aug 30 13:14:29 dyn119 kernel: hde:
Aug 30 13:14:29 dyn119 kernel: hdg:
Aug 30 13:14:29 dyn119 kernel: Floppy drive(s): fd0 is 1.44M
Aug 30 13:14:29 dyn119 kernel: FDC 0 is a post-1991 82077
Aug 30 13:14:29 dyn119 kernel: ide-floppy driver 0.97
Aug 30 13:14:29 dyn119 kernel: Promise Fasttrak(tm) Softwareraid driver for
linux version 0.02
Aug 30 13:14:29 dyn119 kernel: No raid array found
Aug 30 13:14:29 dyn119 kernel: Highpoint HPT370 Softwareraid driver for
linux version 0.01
Aug 30 13:14:29 dyn119 kernel: No raid array found
lspci -v gives the following information about the promise chipset:
00:10.0 RAID bus controller: Promise Technology, Inc. 20265 (rev 02)
Subsystem: Promise Technology, Inc.: Unknown device 4d39
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at dc00 [size=8]
I/O ports at d800 [size=4]
I/O ports at d400 [size=8]
I/O ports at d000 [size=4]
I/O ports at cc00 [size=64]
Memory at dffe0000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at dffd0000 [disabled] [size=64K]
Capabilities: [58] Power Management version 1
--__--__--
Message: 2
Date: Thu, 30 Aug 2001 07:39:06 -0400
From: Arjan van de Ven <arjanv@xxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
On Thu, Aug 30, 2001 at 01:34:20PM +0200, Andreas Thienemann wrote:
> Hi,
>
> I'm trying to get a on-board PDC20265r "raid" controller to work with the
> ataraid driver... Unfortunately I had no luck yet...
>
> The problem seems to be that the disks of the raid-1 array are detected as
> hde and hdg.
Ehhhh the driver currently only does raid-0 ....
--__--__--
Message: 3
Date: Thu, 30 Aug 2001 13:45:31 +0200 (CEST)
From: Andreas Thienemann <andreas@xxxxxxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
Hi,
On Thu, 30 Aug 2001, Arjan van de Ven wrote:
> Ehhhh the driver currently only does raid-0 ....
Eeeeeekkkkkkkkk!
Just to clear up things: raid-1 is mirroring, correct? raid-0 is spreading
out the data onto two disks?
Do you ahve any idea what the status of mirroring-support in your driver
is?
thanks,
andreas
--__--__--
Message: 4
Date: Thu, 30 Aug 2001 07:47:05 -0400
From: Arjan van de Ven <arjanv@xxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
On Thu, Aug 30, 2001 at 01:45:31PM +0200, Andreas Thienemann wrote:
> Hi,
>
> On Thu, 30 Aug 2001, Arjan van de Ven wrote:
>
> > Ehhhh the driver currently only does raid-0 ....
> Eeeeeekkkkkkkkk!
>
> Just to clear up things: raid-1 is mirroring, correct? raid-0 is spreading
> out the data onto two disks?
Yes.
> Do you ahve any idea what the status of mirroring-support in your driver
> is?
"I have to start writing it soon" :)
--__--__--
Message: 5
Date: Thu, 30 Aug 2001 13:52:30 +0200 (CEST)
From: Andreas Thienemann <andreas@xxxxxxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
Hello,
On Thu, 30 Aug 2001, Arjan van de Ven wrote:
> > Just to clear up things: raid-1 is mirroring, correct? raid-0 is
spreading
> > out the data onto two disks?
> Yes.
Okay, so we don't suffer from any misunderstandings. ;)
> > Do you ahve any idea what the status of mirroring-support in your driver
> > is?
> "I have to start writing it soon" :)
Hmmmm... Let me think. ;) How many pizza-vouchers will it take to speed
things up? ;)
bye,
andreas
--__--__--
Message: 6
From: "Ruediger Biernat" <info@xxxxxxxxxxx>
To: <ataraid-list@xxxxxxxxxx>
Subject: Re: No raid array found
Date: Thu, 30 Aug 2001 13:55:17 +0200
Reply-To: ataraid-list@xxxxxxxxxx
> > Ehhhh the driver currently only does raid-0 ....
> Eeeeeekkkkkkkkk!
That is exactly what I said as I realized that my brand
new TX2/100 is useless (slow) for my debian system without
driver support from Promise.
Next time it's a hardware raid so noone will see how this
"disk" is configured.
Sincerely
Ruediger Biernat
--__--__--
Message: 7
Date: Thu, 30 Aug 2001 14:07:18 +0200 (CEST)
From: Andreas Thienemann <andreas@xxxxxxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
Hi Ruediger,
On Thu, 30 Aug 2001, Ruediger Biernat wrote:
> > > Ehhhh the driver currently only does raid-0 ....
> > Eeeeeekkkkkkkkk!
> That is exactly what I said as I realized that my brand
> new TX2/100 is useless (slow) for my debian system without
> driver support from Promise.
Exactly. Problem is, Customer just got 5 of these shiny new 1U rack
servers which are ohh so cool because they got RAID and everything...
Exactly the right thing for their e-whatever-solution we are programming
for them...
When I saw that these things were not SCSI as promised but IDE I thought
"WTF?".
After I saw the IDE chipset it was "sheeeeshhh". Because unfortunately
I've got the Fastrak (thank $DEITY with 20267 chipset - less bugs) at home
and was already "well aware" of their shortcomings...
Now, after I heard the ataraid (Help me Arjan Van de Ven, you are my only
chance - Guess the movie!) driver does only raid-0 it was
"Eeeeeekkkkkkkkk!"
Anyway, we just told the customer, result: "What?"
> Next time it's a hardware raid so noone will see how this
> "disk" is configured.
It's either that or waiting till ataraid supports mirroring... :-/
bye,
andreas
--__--__--
Message: 8
Date: Thu, 30 Aug 2001 08:11:28 -0400
From: Arjan van de Ven <arjanv@xxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
On Thu, Aug 30, 2001 at 02:07:18PM +0200, Andreas Thienemann wrote:
> Anyway, we just told the customer, result: "What?"
>
> > Next time it's a hardware raid so noone will see how this
> > "disk" is configured.
> It's either that or waiting till ataraid supports mirroring... :-/
>
that or use linux softwareraid...
It's SOFTWARE RAID you bought..... the drivers are software raid, even the
binary only ones from Promise.
--__--__--
Message: 9
Date: Thu, 30 Aug 2001 14:18:06 +0200 (CEST)
From: Andreas Thienemann <andreas@xxxxxxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: No raid array found
Reply-To: ataraid-list@xxxxxxxxxx
Hi,
On Thu, 30 Aug 2001, Arjan van de Ven wrote:
> > It's either that or waiting till ataraid supports mirroring... :-/
> that or use linux softwareraid...
Jeppp. Another possibility...
> It's SOFTWARE RAID you bought..... the drivers are software raid, even the
> binary only ones from Promise.
Don't tell me... I know this already... Anyway... Thanks for the quick
reply...
bye,
andreas
--__--__--
Message: 10
From: "Alan Miles" <alan.miles1@xxxxxxxx>
To: <ataraid-list@xxxxxxxxxx>
Subject: Problems with the Promise Fastrak100 and 2.4.8-ac7
Date: Thu, 30 Aug 2001 07:26:21 -0600
Reply-To: ataraid-list@xxxxxxxxxx
I have done the following:
1/ Applied the ac7 patch to the 2.4.8 kernel source and then compiled - that
worked fine.
2/ Made the devices, i.e., /dev/ataraid/*
Originally I had 3 [identical] drives connected as Stripe/Raid 0. Due to
some hardware problems, I had to have one of the hard drives replaced and
the
vendor configured the machine as:
(a) Stripe/Raid 0 for the remaining identical drives
(b) Stripe/Raid 0 for the new drive
The vendor did this, as the machine is about 6.5 months old and is under
warranty. IBM, the hard drive manufacturing no longer makes this version of
the hard drive - hence the need for different configuration.
Now when I try the kernel:
Drive 0 58644 MB
Drive 1 58644 MB
I can see the new drive partitions OK. However, for the big drive (the 2
identical drives) the partition information doesn't make sense. Linux "sees"
this as /dev/hde and /dev/hdg. The first couple of partitions on /dev/hde
look fine, but the linux ext2 partition bridges both drives. Where the ext2
partition starts on /dev/hde it cannot figure out what type of partition it
is. As for /dev/hdg, the Linux fdisk cannot even tell what kind of partition
info there is.
looking in /proc/partitions, I see:
Major:114 Minor:1 ataraid/disc0/part1
Major:114 Minor:2 ataraid/disc0/part2
I guess it would help if I had managed to get the fdisk -l output and put in
this message - unfortunately I don't have it.
What am I missing or doing wrong?
BTW, what is this about patching lilo?
Alan Miles
Programmer/Analyst
email: alan.miles1@xxxxxxxx
--__--__--
Message: 11
Date: Thu, 30 Aug 2001 09:39:17 -0400
From: Arjan van de Ven <arjanv@xxxxxxxxxx>
To: ataraid-list@xxxxxxxxxx
Subject: Re: Problems with the Promise Fastrak100 and 2.4.8-ac7
Reply-To: ataraid-list@xxxxxxxxxx
On Thu, Aug 30, 2001 at 07:26:21AM -0600, Alan Miles wrote:
> I have done the following:
> I can see the new drive partitions OK. However, for the big drive (the 2
> identical drives) the partition information doesn't make sense. Linux
"sees"
> this as /dev/hde and /dev/hdg. The first couple of partitions on /dev/hde
> look fine, but the linux ext2 partition bridges both drives.
Do not look at /dev/hde and /dev/hdg!
only look at /dev/ataraid/d0 and the like!
> BTW, what is this about patching lilo?
lilo needs a patch in order to boot of the raid0 array; grub should be able
to run without one.
Greetings,
Arjan van de Ven
--__--__--
_______________________________________________
Ataraid-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/ataraid-list
End of Ataraid-list Digest
