Re: Help with Kickstart on FC7

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Things have changed but not a great deal of improvement. It is loading the vmlinuz and initrd.img from 2.6.22.9-91 kernel. It progresses further during the initrd but then panics with:

Trying to resume from /dev/Volgroup00/LogVol01
No suspend signature on swap, not resuming

Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

This this has two SATA drives using hardware RAID1.



Phil Meyer wrote:
Gary Schlachter wrote:
I am having great difficulty trying to load FC7 via kickstart on a new server. Here is the process I have followed:

 1) Loaded FC7 on the server via Live-CD with no issues.
2) Copied initrd.img from server to my DHCP/tftp kickstart server along with vmlinuz 3) Created new ks.cfg for this server based on anaconda.cfg from /root on server
 4) Booted the server.

 The results:

 1) I can see my kernel and init.img files downloaded to the new server.
2) Vast amounts of information displayed on console ending with the following:

     RAMDISK: Compressed image found at block 0
grow_buffers: requested out-of-ranger block BIGNUMBERHERE for device ram0
     isofs_fill_super:  bread failed, dev=ram0, iso_blknum=17 block=...
     No filesystem could mount root, tried: iso9660
     kernel panic ...

I have tried loading additional modules into initrd.img but no joy. Any and all thoughts are greatly appreciated!

Gary

For PXE loads you need to use the images from images/pxeboot on the CD/DVD image.

You also need to specify some kernel parameters:

From: http://www.linux-sxs.org/internet_serving/pxeboot.html

8) Now create the default pxelinux configuration inside the new file
/tftpboot/pxelinux.cfg/default:
prompt 1
default linux
timeout 100

label linux
kernel vmlinuz
append initrd=initrd.img ramdisk_size=9216

Good Luck!



--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux