Looking for some answers..

[Chuck Ebbert]

On 09/11/2007 03:46 AM, Arne Chr. Jorgensen wrote:
> hi,
> 
> I have worked day/night in trying to resolve some issues:
> - the following is what I have copied manually from what I may read from screen:
> .
> .
> ata4: SATA link down (SStatus 0 SControl 300)
> pata_amd 0000:00:06.0: version 0.3.8
> PCI: Setting latency timer of device 0000:00:06.0 to 64
> scsi4: pata_amd
> scsi5: pata_amd
> ata5: PATA max UDMA/133 cmd 0x00000000000101f0 ctl 0x00000000000103f6 bmdma 0x00000000000130c0 irq 14
> ata6: PATA max UDMA/133 cmd 0x0000000000010170 ctl 0x0000000000010376 bmdma 0x00000000000130c8 irq 15
> ata5.00: ATAPI: MATSHITADVD-RAM UJ-851S, 1.50, max MWDMA2
> ata5.00: ATAPI: configured for MWDMA2
> ata6: port disabled. ignoring.
> scsi 4:0:0:0: CD-ROM     MATSHITADVD-RAM UJ-851S, 1.50 PQ: 0 ANSI: 5
> device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel at redhat.com
>   Reading all physical volumes. This may take a while...
>   No volume groups found
>   Volume group "VolGroup00" not found
> Unable to access resume device (/dev/VolGroup00/LogVol01)
> mount: could not find filesystem '/dev/root'
> setuproot: moving /dev failed: No such file or directory
> Setuproot: error mounting /proc: No such file or directory
> Setuproot: error mounting /sys: No such file or directory
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempting to kill init!
> 
>                                      ---------------------------------

We need to see what happens before that.

Try using the boot_delay option... edit /etc/grub.conf and add
"boot_delay=200" to the kernel command line (try different values
than 200 until the delay is reasonable between messages.) Then take
pcitures of the screen while the hard drives are being detected
(lines starting with "ata".)

Then file a bug at https://bugzilla.redhat.com