[Fedora] Re: FC14 Installation Hangs
Ashley M. Kirchner
ashley at pcraft.com
Mon Jan 24 22:51:26 UTC 2011
On 1/24/2011 2:32 PM, JB wrote:
> Let's take a shot at hard disk problems:
> keep only -> ignore_loglevel enforcing=0 initcall_debug
>
> Keep these 2 runs separately.
>
> 1st run:
> add -> pci=nomsi pci=nommconf pci=nocrs
>
> 2nd run (remove 1st run added parameters):
> rdblacklist=ahci
>
> JB
Now we're starting to get into the more cryptic stuff ...
1st run:
On tty0, it gets past the 'waiting for the cows to come home'
message and gives me a blue screen, asking me to test the Media. If I
let it test the media, it goes nowhere. The screen also has some junk
on it [1]. If I tell it to skip it, the dialog box goes away, and
that's as far as it goes. When I switch to tty2 to see what's going on,
I see this:
Detected stage 2 image on CD (url: cdrom:///dev/sr0:/mnt/stage2)
loader: stage 2 url is cdrom:///dev/sr0:/mnt/stage2
ata3: lost interrupt (Status 0x58)
ata3: drained 65536 bytes to clear DRQ.
ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
sr 2:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 4f 40 00 00 40 00
ata3.01: cmd a0/01:00:00:00:fc/00:00:00:00:00/b0 tag 0 dma 131072 in
res 40/00:02:00:0c:00/00:00:00:00:00/b0 Emask 0x4 (timeout)
ata3.01: status: { DRDY }
ata3: soft resetting link
ata3.00: configured for MWDMA2
ata3.01: configured for UDMA/25
ata3: EH complete
This repeats 3 times, and eventually it bails with a few lines of:
Buffer I/O error on device sr0, logical block [various]
Then cycles back to the top error section.
Ok, so perhaps I have a bad disk. Perhaps the drive itself is also
bad even though it ran the CentOS install just fine - I did it through
CD install, and it read all 7 disks with no problems, no errors, nothing.
So, I ripped the drive out, put in a DVD drive instead. Burned a
DVD install disk and powered up the machine. It gets as far as 'GRUB
Loading stage2..' on screen and that's it. The drive's light is
blinking non-stop and it's been sitting there for about 15 minutes now.
Worse than before.
Back to the CD drive and a *new* install disk, just in case the old
one was indeed fubared ... No dice, same thing as posted above. And I
made sure the checksums passed.
Now on to run 2:
Same thing!
As the machine is now in production (running CentOS), it's more
difficult to go through rebooting the thing every time to try and figure
this out. Just saying. I'm willing to keep trying things, but I have
to limit the amount of times I reboot this time every day (and
eventually stop alltogether.)
[1]: http://www.yeehaw.net/bootjunk.jpg
More information about the users
mailing list