Re: can't boot after botched RHEL 5 build
- From: TEK <tommy.knight@xxxxxxxxx>
- Date: Thu, 22 May 2008 10:02:34 -0700 (PDT)
On May 22, 11:17 am, Mark Madsen <mark.s.madsen+n...@xxxxxxxxx> wrote:
On Thu, 22 May 2008 10:02:20 -0500, General Schvantzkopf wrote:
I have done the following multiple times and once again after your
post. 1. restore bios settings to defaults and saved. 2. set boot
order to CD then network then IDE 3. used 3 different KNOWN GOOD boot
disks to attempt boot from cdrom. 4. Placed a BRAND NEW ide hard drive
into the machine and system booted.
A windows system sees the hard drive as NOT FORMATTED.
Ideas?
Just to clarify, with the old drive in the box the Windows boot disk
does nothing, but with a new drive in the box it boots and tells you
that the drive is unformated?
Sounds like the hard drive jumpers may not be correct, or possibly bad
contact on the IDE cable.
It's not an issue with the jumper or hardware. None of that has
changed and putting the HD in a windows machine as a slave shows the
disk exists but is NOT formatted.
.
- References:
- can't boot after botched RHEL 5 build
- From: TEK
- Re: can't boot after botched RHEL 5 build
- From: Jan Gerrit Kootstra
- Re: can't boot after botched RHEL 5 build
- From: TEK
- Re: can't boot after botched RHEL 5 build
- From: General Schvantzkopf
- Re: can't boot after botched RHEL 5 build
- From: TEK
- Re: can't boot after botched RHEL 5 build
- From: General Schvantzkopf
- Re: can't boot after botched RHEL 5 build
- From: TEK
- Re: can't boot after botched RHEL 5 build
- From: General Schvantzkopf
- Re: can't boot after botched RHEL 5 build
- From: Mark Madsen
- can't boot after botched RHEL 5 build
- Prev by Date: Re: can't boot after botched RHEL 5 build
- Next by Date: Re: can't boot after botched RHEL 5 build
- Previous by thread: Re: can't boot after botched RHEL 5 build
- Next by thread: Re: can't boot after botched RHEL 5 build
- Index(es):
Relevant Pages
|
