SEO

1) Downloaded Fedora ISOs

2) Ran md5sum against all 3 iso files and compared with the MD5SUM
file. All OK.

3) Burned all 3 ISO's

4) Booted-up using Fedora CD 1/3

5) Ran media check on all 3 CDs ... all PASSed.

6) Gone past HD partitioning using diskdruid. Selected packages to
installat in Workstation installation.

7) Began install


Then begins the problem ....

From the GUI, it was complaining about setup-2.5.27-1.1.noarch.rpm,
clicked OK to retry and same complaint.

Ctrl-Alt-F3 ( or F4 ... ) to view the syslog output.
Turns out it was having an ioerror.
Mostly, I see something like ( if I remember correctly ):

hdc: irq timeout: status=0xd0 { Busy }
hdc: ATAPI reset complete

... .and also something like:
xxxx { Seek }


It looks like it was mounting and unmounting the CD, since every time
I click on OK from the GUI, I then switch to the shell in Ctrl-Alt-F1,
and I can see CD being mounted on /mnt/source, and view files mounted on
the CD ... and then the mount point is gone again.


Just to confirm, I booted back to an existing RedHat 7.2 installation
( on the same machine where I was intending to install Fedora ),
mounted the CD, and then tried to query and view the contents of
setup-2.5.27-1.1.noarch.rpm ... and there was no problem at all!!! (
See below ).


What am I missing ? The strange thing is that Fedora __booted__ from
the CD in graphical mode and confirmed that all 3 medias are OK!!

Do I need to specify some BIOS setting or boot option ?

I just installed RedHat 7.2 from CD on this same machine a week ago to
the same disk ( hdb ) ... just to try out that the new hard disk works
( WDC 80GB with 8MB Cache ). Note that CD is on hdc.

Help!!!!!!


[john@localhost john]$ ls -al
/mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm
-rw-r--r-- 60 root root 28506 Oct 29 2003
/mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm

[john@localhost john]$ rpm -qilp
/mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm
Name : setup Relocations: (not
relocateable)
Version : 2.5.27 Vendor: Red Hat, Inc.
Release : 1.1 Build Date: Wed 03 Sep
2003 07:09:58 EST
Install date: (not installed) Build Host:
bugs.devel.redhat.com
Group : System Environment/Base Source RPM:
setup-2.5.27-1.1.src.rpm
Size : 34969 License: public domain
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Summary : A set of system configuration and setup files.
Description :
The setup package contains a set of important system configuration and
setup files, such as passwd, group, and profile.
/etc/bashrc
/etc/csh.cshrc
/etc/csh.login
/etc/exports
/etc/filesystems
/etc/group
/etc/gshadow
/etc/host.conf
/etc/hosts.allow
/etc/hosts.deny
/etc/inputrc
/etc/motd
/etc/passwd
/etc/printcap
/etc/profile
/etc/profile.d
/etc/protocols
/etc/securetty
/etc/services
/etc/shadow
/etc/shells
/usr/share/doc/setup-2.5.27
/usr/share/doc/setup-2.5.27/uidgid
/var/log/lastlog

[john@localhost john]$ rpm --checksig --nogpg
/mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm

/mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm: md5 OK

noone wrote:
>
> Ctrl-Alt-F3 ( or F4 ... ) to view the syslog output.
> Turns out it was having an ioerror.
> Mostly, I see something like ( if I remember correctly ):
>
> hdc: irq timeout: status=0xd0 { Busy }
> hdc: ATAPI reset complete
>

This is driving me nuts!!

Tried it again ... the full entry form syslog was:

<4>hdc: command error: status=0x51 { DriveReady SeekComplete Error }
<4>hdc: bad_request: error=0x54 I/O error, dev 16:00 (hdc) sector 1196808

This happens when the installer tries to copy or read
setup-2.5.27-1.1.noarch.rpm.

So it looks like a defective CD problem, despite the fact that the
checkmedia process says it passed ... but there's more to this as you
will see below.



As mentioned in the my OP, Fedora would unmount the CD until you click
on OK to try again. So while the CD is unmounted, from the shell in
Ctrl-Alt-F1, I did:

mkdir /mnt/source
mount /dev/hdc /mnt/source
cp /mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm /dev/null


.... and I get the same error as the one I noted above. So I can
replicate it. So it seems definitely like a CD / media problem.

..... until ...


I rebooted back to Redhat 7.2, mounted the CD, and did:

cp /mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm /dev/null


.... and there was no error!!! No error logged at all in /var/lgo/messages.

So I thought it may be when copying from the CD to the hard disk that
where I wanted Fedora installed. So I mounted /dev/hdb2 on /mnt/hdb2,
and did:

cp /mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm /mnt/hdb2

.... no problem again. Even ran cksum against the rpm in the CD and on /m
nt/hdb2 ... both returned the same MD5 sum.

So from the point, it does not seem to be a CD / media problem.


arggghhh!!!!!!

noone <noone@noone.org> wrote:
> <4>hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> <4>hdc: bad_request: error=0x54 I/O error, dev 16:00 (hdc) sector 1196808

Fix your cable or cdrom drive or controller (maybe torn off/on dma).

You sure it's jumpered correctly? It says its master on the second ide
bus - so there should be nothing else on that bus except maybe another
cdrom. That is, if it is _really_ a cdrom, and not a cdrw, or dvd ...

> This happens when the installer tries to copy or read
> setup-2.5.27-1.1.noarch.rpm.

Move it to the other bus.

> So it looks like a defective CD problem, despite the fact that the

Looks like a defective something, but your test does not identify what.
Put another cd in the drive and read it all (use live cd mode).

> As mentioned in the my OP, Fedora would unmount the CD until you click
> on OK to try again. So while the CD is unmounted, from the shell in
> Ctrl-Alt-F1, I did:

> mkdir /mnt/source
> mount /dev/hdc /mnt/source
> cp /mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm /dev/null


> ... and I get the same error as the one I noted above. So I can
> replicate it. So it seems definitely like a CD / media problem.

More or less. Or cable. Or controller. Changing the media and leaving
everything else stable would be the test!

> I rebooted back to Redhat 7.2, mounted the CD, and did:

> cp /mnt/cdrom/Fedora/RPMS/setup-2.5.27-1.1.noarch.rpm /dev/null

> ... and there was no error!!! No error logged at all in /var/lgo/messages.

So it looks like a controller problem. Check the dma mode, and change
it.

> So from the point, it does not seem to be a CD / media problem.

Peter

> So from the point, it does not seem to be a CD / media problem.
>
> arggghhh!!!!!!

I once had a similar kind of problem (RH 9.0), although it
was with a floppy. It booted fine from a floppy but it failed
completely to read the drvimg floppy after booting.
Turned out in the BIOS a wrong type of floppydrive was selected.
after setting it to the proper device, everything was okay again.
check the BIOS and see if the CD drive is detected properly
by the BIOS. If not, correct that.

Eric

P.T. Breuer wrote:
> noone <noone@noone.org> wrote:
>
>><4>hdc: command error: status=0x51 { DriveReady SeekComplete Error }
>><4>hdc: bad_request: error=0x54 I/O error, dev 16:00 (hdc) sector 1196808
>
>
> Fix your cable or cdrom drive or controller (maybe torn off/on dma).
>
> You sure it's jumpered correctly? It says its master on the second ide
> bus - so there should be nothing else on that bus except maybe another
> cdrom. That is, if it is _really_ a cdrom, and not a cdrw, or dvd ...
>
>

There is the CDROM drive and a CDRW drive on the second bus.
I have used the CDROM drive and CDRW drive for a long time without any
problems from either win and the working RH 7.2 installation, and have
installed RH 7.2 from the CDROM drive just a week before.

How did "know" that the CDROM is master on the second IDE bus when you
said "It says its master on the second ide bus" ?


>>This happens when the installer tries to copy or read
>>setup-2.5.27-1.1.noarch.rpm.
>
>
> Move it to the other bus.

Only problem with moving the CDROM to the other bus is all are used, and
winoze ( dual-boot ) may not like it

noone <noone@noone.org> wrote:
> P.T. Breuer wrote:
> > noone <noone@noone.org> wrote:
> >
> >><4>hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> >><4>hdc: bad_request: error=0x54 I/O error, dev 16:00 (hdc) sector 1196808
> >
> >
> > Fix your cable or cdrom drive or controller (maybe torn off/on dma).
> >
> > You sure it's jumpered correctly? It says its master on the second ide
> > bus - so there should be nothing else on that bus except maybe another
> > cdrom. That is, if it is _really_ a cdrom, and not a cdrw, or dvd ...

> There is the CDROM drive and a CDRW drive on the second bus.

That's what's wrong then. A cdrom must be slave to a cdrw.

> I have used the CDROM drive and CDRW drive for a long time without any
> problems from either win and the working RH 7.2 installation, and have
> installed RH 7.2 from the CDROM drive just a week before.

Jumper them correctly - the cdrom must be slave and the cdrw
master.

> How did "know" that the CDROM is master on the second IDE bus when you
> said "It says its master on the second ide bus" ?

Because it says so three times in those two lines of error messages.

> >>This happens when the installer tries to copy or read
> >>setup-2.5.27-1.1.noarch.rpm.
> >
> > Move it to the other bus.

> Only problem with moving the CDROM to the other bus is all are used, and

Either you change something or you stay in the same sitauation.

I would jumper them the right way round before even bothering to start
thinking.

> winoze ( dual-boot ) may not like it

Then ask in a windows group why it doesn't like it and how to fix it.

Peter

"noone" <noone@noone.org> wrote in message
news:btjmhb$kn3$1@lust.ihug.co.nz...
>
> So it looks like a defective CD problem, despite the fact that the
> checkmedia process says it passed ... but there's more to this as you
> will see below.


Possibly a CD-ROM drive problem. Did you try:

linux ide=nodma

at the boot prompt?

--
William Hooper

It's sad that a family can be torn apart by something as simple as a pack of
wild dogs.

P.T. Breuer wrote:

> noone <noone@noone.org> wrote:
>
>>P.T. Breuer wrote:
>>
>>>noone <noone@noone.org> wrote:
>
>
>>There is the CDROM drive and a CDRW drive on the second bus.
>
>
> That's what's wrong then. A cdrom must be slave to a cdrw.
>

OK ... call me naive ... but why does a CDROM must be a slave to a CDRW ?

Hello

P.T. Breuer (<ptb@oboe.it.uc3m.es>) wrote:

> noone <noone@noone.org> wrote:

>> I have used the CDROM drive and CDRW drive for a long time without
>> any problems from either win and the working RH 7.2 installation, and
>> have installed RH 7.2 from the CDROM drive just a week before.
>
> Jumper them correctly - the cdrom must be slave and the cdrw
> master.

I have been using a cdrom and a cdrw drive for a long time without any
problems with the cdrom being jumpered to master (/dev/hdc) and the
cdrw being jumpered as slave (/dev/hdd).

best regards
Andreas Janssen

--
Andreas Janssen
andreas.janssen@bigfoot.com
PGP-Key-ID: 0xDC801674
Registered Linux User #267976

Andreas Janssen <andreas.janssen@bigfoot.com> wrote:
> P.T. Breuer (<ptb@oboe.it.uc3m.es>) wrote:

> > noone <noone@noone.org> wrote:

> >> I have used the CDROM drive and CDRW drive for a long time without
> >> any problems from either win and the working RH 7.2 installation, and
> >> have installed RH 7.2 from the CDROM drive just a week before.
> >
> > Jumper them correctly - the cdrom must be slave and the cdrw
> > master.

> I have been using a cdrom and a cdrw drive for a long time without any
> problems with the cdrom being jumpered to master (/dev/hdc) and the
> cdrw being jumpered as slave (/dev/hdd).

The electronics isn't on the cdrom to make it work. Maybe you have been
using them to read only. Or maybe you hit lucky and got a cdrom with
more than the absolute minimum of drive electronics on it. Who can
tell!

Peter