I got a hd issue with fedora. It loops around all the hard drive types
and then stops at HDC and loads for a while, resetting the ATAPI and
disabling the DMA. Now, my HD isnt the newest, and its got a little
brother of about 4 gigs next to it, and its obivously having some
problems. Any help?

mightybigbox@gmail.com wrote:
> I got a hd issue with fedora. It loops around all the hard drive types
> and then stops at HDC and loads for a while, resetting the ATAPI and
> disabling the DMA. Now, my HD isnt the newest, and its got a little
> brother of about 4 gigs next to it, and its obivously having some
> problems. Any help?

What's your problem? The above sounds like a description of a correct
automated procedure to me.

If you have some concrete error conditions observed as a result, show
them! (PS - what do you mean by "resetting the ATAPI"? ATAPI is a
standard).


Peter

"Peter T. Breuer" <ptb@oboe.it.uc3m.es> wrote in message
news:0f69u2-cr2.ln1@news.it.uc3m.es...
> mightybigbox@gmail.com wrote:
>> I got a hd issue with fedora. It loops around all the hard drive types
>> and then stops at HDC and loads for a while, resetting the ATAPI and
>> disabling the DMA. Now, my HD isnt the newest, and its got a little
>> brother of about 4 gigs next to it, and its obivously having some
>> problems. Any help?
>
> What's your problem? The above sounds like a description of a correct
> automated procedure to me.
>
> If you have some concrete error conditions observed as a result, show
> them! (PS - what do you mean by "resetting the ATAPI"? ATAPI is a
> standard).

I'm surprised. While snarky sounding, Peter didn't actually snap at a newbie
and call him ignorant. I wonder if Peter is feeling well?

Now, the Linux kernel does interesting things with setting up hard drives.
Some of them are weird and complex, to deal with the latest hard drives and
the very oldest hard drives and make them both operate. At boot time, there
is a command called "hdparm" that sets such characteristics for your hard
drive. The init scripts of different Linux releases do different things with
it, and Fedora Core uses a file called "/etc/sysconfig/harddisks" at boot
time to set any non-default settings for your hard drive. I'd check that for
weird settings, particular for default settings that are not appropriate for
your hard drives and which need to be reset to make that old hdc hard drive
available.

Are your first and second hard drive controllers, ide0 and ide1, the same
model? And is that hdc drive perhaps so old that anything? Are you able to
see the contents of the hard drives, and what does "/dev/hdparm /dev/hdc" or
"hdparm /dev/hd[whatever]" say?

yeah sorry for not posting the stuff its giving me.

it says at startup:

Primary IDE channel no 80 conductor cable installed
and
primary slave hard disk fail (I unplugged my secondary HD for a cleaner
install)
Then it says the regular fedora stuff and i press enter for graphical
install mode.

It boots the ivmlinuz, then detects hardeware
Then sats that the hda : Cashe flushes not supported
hdc : probing with status (0x50) instead of altstatus(0x08)
hdc : Probing with status (0x51) instead of Altstatus (0x0a)
hdc: fx240s Atapi Cd/dvd rom drieve
ide1 at 0x170-0x177 ,0x376 on irq 15
ide-cd:cmd 0x5a timed out
hdc: irq timeout: Status=0x58 { driveready SeekComplete Datarequest }
ide failed opcode was:Unknown
Hdc: DMA disables
HDC: ATAPI reset complete.

HOpe that helps you help me.

Im trying to install Fedora core and its giving me these issues, so i
cant see the hard drives anyhow, and yeah thanks for not laughing at
me, i just suck ass at linux installs...because im a windower most of
the time (thank God for VMware Though) and windows finally pushed me
too far with its shit fucking up vmware.

Anyhow, it starts the install kernel fine it just screws up detecting
hardware.

Im trying to install Fedora core and its giving me these issues, so i
cant see the hard drives anyhow, and yeah thanks for not laughing at
me, i just suck ass at linux installs...because im a windower most of
the time (thank God for VMware Though) and windows finally pushed me
too far with its shit fucking up vmware.

Anyhow, it starts the install kernel fine it just screws up detecting
hardware.
As for the twin hard drives, im fairly sure they are the same modle,
but i have the slave unplugged to allow a cleaner setup and install.
Perhaps the cables are in the wrong slot??

<mightybigbox@gmail.com> wrote in message
news:1125248517.544246.259860@g14g2000cwa.googlegr oups.com...
> yeah sorry for not posting the stuff its giving me.
>
> it says at startup:
>
> Primary IDE channel no 80 conductor cable installed
> and
> primary slave hard disk fail (I unplugged my secondary HD for a cleaner
> install)
> Then it says the regular fedora stuff and i press enter for graphical
> install mode.
>
> It boots the ivmlinuz, then detects hardeware
> Then sats that the hda : Cashe flushes not supported
> hdc : probing with status (0x50) instead of altstatus(0x08)
> hdc : Probing with status (0x51) instead of Altstatus (0x0a)
> hdc: fx240s Atapi Cd/dvd rom drieve
> ide1 at 0x170-0x177 ,0x376 on irq 15
> ide-cd:cmd 0x5a timed out
> hdc: irq timeout: Status=0x58 { driveready SeekComplete Datarequest }
> ide failed opcode was:Unknown
> Hdc: DMA disables
> HDC: ATAPI reset complete.

I'm confused. You have a CD drive on hdc, gotcha. You have a hard drive at
hda and no other hard drive? How big and how old is this hard drive? How
fast and how old is your motherboard?

On Sun, 28 Aug 2005 18:41:28 +0200, <mightybigbox@gmail.com> wrote:

> I got a hd issue with fedora. It loops around all the hard drive types
> and then stops at HDC and loads for a while, resetting the ATAPI and
> disabling the DMA. Now, my HD isnt the newest, and its got a little
> brother of about 4 gigs next to it, and its obivously having some
> problems. Any help?

Sure, we can try.

What does it look like when "it loops around all the hard drive types" ?

How many disks do you have? Do you have a chance to capture the messages
and post them?

What disks do you have? How are they connected? For instance, you
could have the older one as the primary master - that is, on the cable
connecting to "ide0" on the motherboard, and with a jumper selecting
"master" configuration, as opposed to "Slave" configuration. There
is also a "Cable Select" configuration, in which case you must look
for a missing (or non-missing) pin on the connector... If I recall
correctly.

The older.. just how old? I don't need the seconds, but five years?
ten years?

The newer one, how is it connected?

Which disk contains the kernel?

Just how far does the boot process go before it stops? (I presume you
mean to tell us that after resetting the ATAPI and disabling the DMA,
not much more happens.) It would be very helpfull if you could post what
are the last messages before it hangs... As many messages as possible.

How do you boot the computer? (Do you know? Lilo? Grub?)
What partitions are there?

That was a lot of questions, but the most important is to get some
clear symptoms, prefereable the exact words of some messages. Given
the messages I may be able to find those messages in the kernel source
and figure out what the kernel is trying to do at that point.

If you are strugling to jot down some messages before they fly off the
upper edge of the screen, it may perhaps be usefull for you to look at
this, which my computer outputs when it first begins probing the
disks, and perhaps you find it easier to notice similarities and
differences. I have drawn some horizontal lines to divide the text in
logical chunks, and that may also help.

Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:14.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x10a0-0x10a7, BIOS settings: hdaMA, hdbMA
ide1: BM-DMA at 0x10a8-0x10af, BIOS settings: hdcMA, hddMA
------------------------------------------------------------------------
Probing IDE interface ide0...
hda: WDC WD100BA, ATA DISK drive
hdb: Maxtor 6B200P0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
------------------------------------------------------------------------
Probing IDE interface ide1...
hdc: QUANTUM Bigfoot TX12.0AT, ATA DISK drive
hdd: SONY CD-RW CRX140E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
------------------------------------------------------------------------
hda: max request size: 128KiB
hda: 19541088 sectors (10005 MB) w/2048KiB Cache, CHS=19386/16/63, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 hda3
------------------------------------------------------------------------
hdb: max request size: 1024KiB
hdb: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63, UDMA(33)
hdb: cache flushes supported
hdb: hdb1 hdb4 < hdb5 hdb6 hdb7 hdb8 hdb9 hdb10 >
------------------------------------------------------------------------
hdc: max request size: 128KiB
hdc: 23547888 sectors (12056 MB) w/69KiB Cache, CHS=23361/16/63, UDMA(33)
hdc: cache flushes not supported
hdc: hdc1 hdc2 < hdc5 >
------------------------------------------------------------------------
hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
------------------------------------------------------------------------
ide-floppy driver 0.99.newide

-Enrique

On Sun, 28 Aug 2005 18:41:28 +0200, <mightybigbox@gmail.com> wrote:

> I got a hd issue with fedora. It loops around all the hard drive types
Oops, I mistook this post for a recent one.

Sorry.

Enrique