RH 7.1 HD thrashing

[Icculus]

i just installed RH 7.1
and my HD wont stop thrashin , i hear it spina lil , or like its trying to set it self

during install it gave a HD error saying it failed to probe the IRQ of my 2 ata100 HD 's

it didnt do this in mandrake , so naturaly im concerned , plus its rather annoying

everythign works fine though ...

[bdg1983]

I would start my reviewing /var/log/messages to see if there are any errors/conflicts with your hd or controller.

If you see anything, then post them here and we can try to help get the problem fixed.

[Icculus]

hmm
hit cntl_alt+ f2
boots me to console
and
it keeps repeating
hdd : status error status = 0x01 9error)
hdd : status error 0x04
hdd : status error status = 0x01 (error)
hdd : status error 0x04
hdd atapi reset complete
hdd : status error status = 0x01 (error)
hdd : status error 0x04
end_request : i/o error dev 16: 40 (hdd) sector 0

it only does it in X-Win
in shell mode its not doing it. ok let me go check that log file right now

[Icculus]

ok i went through that log

during booting it says this

Aug 13 23:58:45 242818hfc07 kernel: PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
Aug 13 23:58:45 242818hfc07 kernel: ide2: BM-DMA at 0x8800-0x8807, BIOS settings: hde :DMA, hdf :DMA
Aug 13 23:58:45 242818hfc07 kernel: ide3: BM-DMA at 0x8808-0x880f, BIOS settings: hdg :pio, hdh :pio
Aug 13 23:58:45 242818hfc07 kernel: hda: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hda: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hda: no response (status = 0x0a), resetting drive
Aug 13 23:58:45 242818hfc07 kernel: hda: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hda: no response (status = 0x0a)
Aug 13 23:58:45 242818hfc07 kernel: hdb: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hdb: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hdb: no response (status = 0x0a), resetting drive
Aug 13 23:58:45 242818hfc07 kernel: hdb: IRQ probe failed (0xfffffff8)
Aug 13 23:58:45 242818hfc07 kernel: hdb: no response (status = 0x0a)
Aug 13 23:58:45 242818hfc07 kernel: hdc: MAT****A CD-RW CW-7585, ATAPI CD/DVD-ROM drive
Aug 13 23:58:45 242818hfc07 kernel: hdd: MAT****A CD-RW CW-7585, ATAPI CD/DVD-ROM drive
Aug 13 23:58:45 242818hfc07 kernel: hdd: set_drive_speed_status: status=0x01 { Error }
Aug 13 23:58:45 242818hfc07 kernel: hdd: set_drive_speed_status: error=0x04
Aug 13 23:58:45 242818hfc07 kernel: ide1: Drive 1 didn't accept speed setting. Oh, well.
Aug 13 23:58:45 242818hfc07 kernel: hde: ST320420A, ATA DISK drive
Aug 13 23:58:45 242818hfc07 kernel: hdf: IBM-DPTA-372050, ATA DISK drive
Aug 13 23:58:45 242818hfc07 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Aug 13 23:58:45 242818hfc07 kernel: ide2 at 0xa000-0xa007,0x9802 on irq 10
Aug 13 23:58:45 242818hfc07 kernel: hde: 39851760 sectors (20404 MB) w/2048KiB Cache, CHS=39535/16/63, UDMA(66)
Aug 13 23:58:45 242818hfc07 kernel: hdf: 40088160 sectors (20525 MB) w/1961KiB Cache, CHS=39770/16/63, UDMA(66)

[Icculus]

Originally posted by Icculus:
<STRONG>hmm
hit cntl_alt+ f2
boots me to console
and
it keeps repeating
hdd : status error status = 0x01 9error)
hdd : status error 0x04
hdd : status error status = 0x01 (error)
hdd : status error 0x04
hdd atapi reset complete
hdd : status error status = 0x01 (error)
hdd : status error 0x04
end_request : i/o error dev 16: 40 (hdd) sector 0

it only does it in X-Win
in shell mode its not doing it. ok let me go check that log file right now</STRONG>


this is happening after boot , when im in X-Win


now the confusing part is , those ones that are failing , well my HD's are labeled e/f not a/b so those supposed HD's that are failing , are really none existent.

[bdg1983]

If it were happening to me, I would compile the latest kernel and pay specific attention to the IDE settings etc.

If this is not an option for you, then I would suggest you check Redhat's support site for anything on the Promise controller and 7.1 or else try searching for those errors at Google (http://www.google.com/linux).

There could be some parameters that need to be passed to the kernel when booting.

[xIcculusx]

one other tid bit

it doesnt do it in root in KDE