[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: read_intr / DriveStatusError errors with Promise FT 100



Here's another idea. Try including "Enable multimode by default" for your
hard disks while you compile your kernel. If your machine has only one
processor, you can also try enabling Local APIC and IO-APIC when you
compile your kernel. Let me know if either works for you

On Tue, 7 Jan 2003, Eric Christensen wrote:

> All:
> Ignore this as a new post as it was originally posted last week from my
> other, registered email address. The moderator must have just cleared this
> from a non-registered post that I inadvertently let go. This problem (after
> the first time it appeared) was responded to. The suggestion did not work,
> unfortunately, so if anyone wants to throw in another idea, I will welcome
> it.
> Regards,
> esc
> 
> -----Original Message-----
> From: ataraid-list-admin redhat com
> [mailto:ataraid-list-admin redhat com]On Behalf Of Eric Christensen
> Sent: Sunday, December 29, 2002 12:20 AM
> To: ataraid-list redhat com
> Subject: read_intr / DriveStatusError errors with Promise FT 100
> 
> 
> Hello,
> 
> I am following Murty's helpful HOW-TO to install a SMP system over a
> FastTrak 100 Lite on-board RAID. Rather than a mirror, though, I am trying a
> stripe set with 2 drives. These are the only drives on the system other than
> a CD-ROM on the second regular IDE channel.
> 
> Everything goes well to start:
> 7.3 base installation goes well and I can boot with the FastTrak module and
> ramdisk.
> Build of a 2.4.19 kernel is fine, I based mine on the config provided by
> Murty.
> New .19 kernel is self contained using the ataraid and Promise support, no
> need for ramdisk or Promise module. It boots and seems to function ok but a
> slew of drive errors occur on boot..
> 
> >>
> Dec 28 22:22:12 localhost kernel: ead_intr: error=0x04 { DriveStatusError }
> Dec 28 22:22:12 localhost kernel: hde: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Dec 28 22:22:12 localhost kernel: hde: read_intr: error=0x04 {
> DriveStatusError }
> Dec 28 22:22:12 localhost kernel: hde: read_intr: status=0x59 { DriveReady
> SeekComplete DataRequest Error }
> Dec 28 22:22:12 localhost kernel: hde: read_intr: error=0x04 {
> DriveStatusError }
> Dec 28 22:22:12 localhost kernel: ide2: reset: success
> <<
> etc. etc. etc.
> 
> Using Murty's formula and after looking at the /proc/pci, I had to config my
> lilo as follows:
> >>
> image=/boot/vmlinuz-2.4.19
> 	label=my19
> 	read-only
> 	root=/dev/ataraid/d0p2
> 	append="ide2=0xa400,0xa802,10 ide3=0xac00,0xb002,10"
> (BTW, I also tried ide0 and ide1 and errors reflect hda rather than hde)
> <<
> 
> I have not yet updated my lilo binaries as Murty prescribes. I want to first
> make sure I am not doing something wrong or heading into trouble. When I
> boot with my old .18-3 kernel with the FastTrak module, I get no errors.
> These are new IBM drives and even though the error messages above often
> indicate impending doom, I think they are fine.
> 
> Thanks for any help. Happy New Year.
> 
> -esc
> 
> 
> 
> _______________________________________________
> Ataraid-list mailing list
> Ataraid-list redhat com
> https://listman.redhat.com/mailman/listinfo/ataraid-list
> 
> 
> 
> _______________________________________________
> Ataraid-list mailing list
> Ataraid-list redhat com
> https://listman.redhat.com/mailman/listinfo/ataraid-list
> 





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]