Bug 6572 - Install fails with - a module named raid0 already exists
Install fails with - a module named raid0 already exists
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-10-31 12:53 EST by mcooper
Modified: 2015-01-07 18:39 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-01 09:38:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mcooper 1999-10-31 12:53:13 EST
The initial boot from the RH 6.1 boot diskette (normal
diskette, not the net or pcmcia) fails during boot.  After
twice (not sure why it does it twice!) something like
"Loading aic7xxx...", I get the following errors:

"/tmp/raid0.o: a module named raid0 already exists
/tmp/raid1.o: a module named raid1 already exists
exec: Permission denied
install exited abnormally"

My system config is

P III 450
128MB memory
Adaptec 2948AU with: 2 SCSI hard drives, 1 SCSI removable
hard drive (SyQuest SyJet 1.5GB), 1 SCSI CD-ROM, 1 Umax
Scanner, 1 Exabyte 8mm tape
1 IDE disk drive

Mandrake 6.0 and SuSe 6.1 installed without problems on this
same system (on removable SyJet cartridges which are not
present during install).
Comment 1 Bill Nottingham 1999-10-31 21:16:59 EST
Did you burn your own CD, or download to an NFS partition?

If so, are you sure the permissions in RedHat/instimage are correct?
Comment 2 Jay Turner 1999-11-01 09:38:59 EST
This is a permissions problem with the files in the RedHat/instimage
directory.  Make sure that the executable files have the executable
bit set and then retry the installation and you should not see the
same problems.  Reopen the bug is you are still having problems.

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