Bug 3938 - second stage loader fails to execute
Summary: second stage loader fails to execute
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-07-07 20:59 UTC by michal
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-07-08 19:32:01 UTC
Embargoed:


Attachments (Terms of Use)

Description michal 1999-07-07 20:59:31 UTC
In Red Hat distribution 6.0 for i386 with all current
updates (CD
created from 6.0 binaries posted on ftp sites and confirmed
that
various mirrors have the same contents in RedHat/base/ and
images/) an
attempt to boot fails silently at the start of the second
stage
loader.

Last messages on screen 3 look like follows:
....
* method selection completed
* state saved to /tmp
* error in exec of second stage loader :-(
*       error:Permission denied

Unfortunately after this the machine is practically dead
which
prevents an examination of a ramdisk.

This error occured on two different machines and persisted
even after
replacing an updated boot.img with the one from the original
distribution.  This error can be worked around by forcing,
from an
expert mode, a loading of supp.img; after that one can
proceed even if
modules.img was not loaded (because of a deliberate error).

A common factor may be that both machines on which this was
tried
have SCSI CD drive.

  Michal Jaegermann
  michal

Comment 1 David Lawrence 1999-07-08 19:32:59 UTC
are you downloading these files preserving all permissions as they
appear on our ftp site? it sounds like the install2 binary is not
marked as executable on your install media. If it is incorrect it can
be assumed that alot of other necessary binaries may be incorrectly
set. Reopen this bug if this is of no help.


Note You need to log in before you can comment on or make changes to this bug.