Linux

Ask something
Discussion Locked

Install keeps choking

0 helpful
7 replies

by paul

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am trying to install RedHat v7.3 on a machine with an Adaptec 2100S with two drives in a non-RAID configuration. The install keeps choking - reporting "media failure or hardware failure or out of space".

I've tried reducing the SCSI data rate,tried different media, tried different combinations of partitions, etc.

Any ideas?

7 replies

by tg2

Have you tried low level formatting the drives?
In the SCSI bios there should be an option for low level format or a "drive verification" option.. (*caution low level formatting *WILL* erase all data on the drive, drive verification may or may not,consult your SCSI Card Manual*)

If the low level format fails, that would point to a problem right there... it could be a drive problem or it could be termination.

Many times, SCSI termination can cause odd or 'flaky' issues. Termination can sometimes be the hardest part of SCSI installation if for no other reason then whether your card needs termination power supplied to the buss or taken from it.

by paul

I appreciated the thought - I had tried swapping out the drives and it didn't make a difference. Ultimately, the problem turned out to be poorly-seated memory modules

by dsuski

I recall something about linux needing an ide drive to boot from...long time ago though, otherwise check if the right scsi module(s) are being loaded accordign to your hardware

by paul

I appreciated the suggestion although I was using the kernel options that are required for booting from scsi. But your suggestion did serve as a reminder to check them.

by unix4me

I had a similar experience trying to install RH7.2 on an IBM with an adaptec SCSI adapter on the motherboard.
It seemed to work and then developed mystery errors; the install never finished and booted correctly.
My problem was a bad SCSI cable.
If you have or can borrow an extra, this could be a quick thing to check....

by paul

Thanks for the suggestion - I had pretty much swapped all the hardware between the one machine that worked and the two that did not. In the end, it turned out to be a problem with poorly-seated memory modules. Go figure....

This discussion is closed to new replies.