Re: Rebuild initrd to get dev-mapper working

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

 



Craig White wrote:
On Mon, 2006-12-11 at 13:45 +0800, Hadders wrote:
Craig White wrote:
On Mon, 2006-12-11 at 13:17 +0800, Hadders wrote:
Hi all,
  I'm very close to getting my new hardware setup working. It kinda does.

I'm using the Intel SATA RAID to get RAID 0, Grub as a boot manager, have installed XP and copied my existing FC5 setup "over" to the new container.

I can boot into this new setup, but only with the stock Kernel. When I try the latest Kernel, the device mapper doesn't work and as such, the system can't find the filesystems.
Over on the ata.raid list, someone has suggested that I run the following:

 > dmraid -a n && dmraid -a y
Which deactivates/activates the RAID container in one go?
Then rebuild the initrd for the latest kernel I have (but not running)

I would assume the safest place to run this command would be from runlevel 1?

Any tips would be appreciated.
----
can't think of any reason that runlevel would matter since initrd is
loaded only upon boot.

The way I would probably handle it on my system...

mkinitrd initrd-2.6.18-1.2239.fc5.img.custom 2.6.18-1.2239.fc5
cp initrd-2.6.18-1.2239.fc5.img initrd-2.6.18-1.2239.fc5.img.saved
mv initrd-2.6.18-1.2239.fc5.img.custom initrd-2.6.18-1.2239.fc5.img

Though I have learned to check the contents of /etc/modprobe.conf to
make certain that things are the way that I want before I execute
mkinitrd

Craig

I was thinking about the runlevel because I was going to blink the RAID container out/in of existence briefly, figuring the less things running, the less likely something might complain.
----
no way to know - what mount points are involved.

If /bin is involved forgettaboutit

If /var is involved, I would probably suggest runlevel 1 would probably
be a good idea because it's gonna dump messages to console which gets
messy
----
When I download the latest kernel and install it through yum/rpm process, does an initrd get built automatically?
----
yes

Craig

Then I can't see how this will solve my problem, theoretically.

I was running the stock kernel, the RAID container was working, I downloaded and installed the latest kernel, rebooted and it couldn't mount root.

Hmmm, I will try anyway, because I'm not sure what else I can do.

--
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