I heard somewhere that by creating custom initrd image and default compiled kernel image, we can do PXE linux installation. can anyone please guide me 'what content will be placed inside initrd?'I know the process of creating custom initrd file .
View 1 RepliesWhen I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
the difference between initrd images and vmlinuz images. I've gone through many documents,but didn't got an exact answer.
View 6 Replies View Relatedhow to create an initrd image using cpio, instead of mkfs?
Now im doing it like this:
Code:
dd if=/dev/zero of=initrd bs=1024 count=10000
mkfs -t ext2 -F -m 0 -b 1024 -i 1024 initrd
But i would like to move to cpio, because with dd, if you add something new, you might need to change the count. Also cpio is used in distro's like Fedora and Ubuntu.
i upgraded from 11.1 to 11.2. Unfortunately the new kernel does not work with my sata/southbridge (i googled and figured its a known issue). So i tried to boot a 11.1 64bit rescue system to install the older kernel and the corresponding initrd. The problem is, that i cant find the kernel and initrd on the rescue system.
View 2 Replies View RelatedIm trying to build an initrd image for my livecd using cpio -o -H newc, but the livecd can't boot. If I create the initrd image using mkfs.ext2 then it works.
View 2 Replies View RelatedA fault in my USB key killed the contents of the /boot partition. I could restore grub, and got back kernel files by extracting kernel-desktop-2.6.31.14-0.4.1.i586.rpm, but now I miss initrd! (I have currently no means to make it.)Would someone having this one be kind enough to e-mail it to me? (It's around 6 MB so it should be OK.) I'll PM you my e-mail address.
View 8 Replies View RelatedI just did a new install of Ubuntu 10.04 (64 bit) on a system with multiple older versions of Ubuntu already installed. There was a dpkg error during the install with no useful information provided, otherwise the install completed normally. When I rebooted, the old grub2 ran and presented my old boot menu. When I mounted the 10.04 partition to see what was there, I found that /boot/grub/ was empty and /boot/initrd.img was missing. The other boot files were present.
View 2 Replies View RelatedIn short. I've cracked open the initrd file of the openSuSE installer to have a look - I've determined it's an initramfs which by default would execute ''/init''GREAT! But not so much... init should find the installation files et cetera - but I haven't a clue how it does this because it's a compiled binary So, my question is this - do anyone know where I can find the source for this file ?
If not, who should I contact to find it? I really, really need to look at it.. I'm trying to throw the installer over to a USB harddrive (with multiple other installers, each in their own directory etc. etc.) - the idea is to create a USB HDD with installation mediums for the OS's I use so the recommended methods of dedicating a partition to openSuSE is not going to work...
I need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
initrd.lz is a Lzip file in the casper directory of the Ubuntu install iso.
I'm having trouble finding a program that will extract it.
Lzip - fails
file-roller fails
How to extract it?
today some one of my friends removed /boot/grub directory from my pc. i tried both
root (hd0,0) Kernel /vm - but it's not coming (coz that file is already removed.
and after
root (hd0,0)
setup (hd0)
it showed grub file is installed but i couldn't find
/boot/grub/grub/conf or vm linuz
and after i used rescue method.
/sbin/grub-install /dev/sda
tried this method but still couldn't make effect.
[Code]...
Suddenly, after installing, boot was failed.
[Code]...
i was surprise, because in initrd-2.6.34.7-0.2-default all was ok.
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
If you can access Suse Studio here is thlink to the buildLFS Host - SUSE GalleryGoogle hasn't been friendly and neither has a search on these forums, I don't know which man to read so a finger in the right dirrection (preferably not the middle) would be nice as far as that goesRight now the yast live installer trips up at %84 while saving the boot loader configuration and displays a popup that says �An error occurred during initrd creation. /sbin/mkinitrd: illegal optionI then press enter to acknowledge the message and the installation continues without a hitch.
When I go to boot up (no other os installed) grub says it cant find the file initrd-2.6.34.7-0.5-defaultIf you boot the live cd again you can mount the boot partition and you�ll find a broken symlink called initrd that islooking for the missing file above.Like I said above, if it an obvious fix, all I need is some direction, I don't mind reading. (been doing that all day)If you need more specifics Id be happy to supply, I'm just not sure whats relevant and don't want to bloat the post.
I have installed "open-SUSE 11.4" on a "500GB Free Agent External Hard Drive". I didn't have any problem in booting since last week that I booted it from my laptop. Also I did it before several times from then when I try to boot it e.g. from an "Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz" PC the time between loading INITRD and starting boot sequence messages lasts nearly 30 minutes!(i didn't actually measure it but it take a long time in the same order). after starting boot sequence which is showed on monitor everything looks normal. e.g copy of files would be done by speeds between 2MB/s to 30 MB/s depending on the targets.I used to use the external hard derive to boot from different laptops and PC's from start but I didn't have such a problem anytime.
View 1 Replies View RelatedI liked to move away from LUKS and LVM.
I just like to have a simple hard disk with 3 partitions for boot, / and swap
What i did so far is:
1.) i unlocked the disk and copied the content from /boot and / to the new disk into sda1 and sda3 (sda2 should be swap)
2.) i changed the fstab
3.) I changed the grub.conf
Somehow my settings in fstab and grub.conf are being ignored and during boot my system still complains about the missing /dev/sda2 for LVM
I do not like to use LVM.
I expect this is caused by the initrd
I already did boot from the Live CD and did chroot into my system and tryed to make a new initrd.
I used mkinitrd without any options.
During boot i still get the LVM error message, complaining about the missing /dev/sda2
I have an encrypted root and encrypted boot drive... To avoid entering a passphrase multiple times I'd like to add a keyfile for my root drive to my initrd... I've done this in Arch and it was relatively simple but I've hit a road block in debian finding the analog processes...
Code: Select all#Part 1) Generate the keyfile, give it suitable permissions and add it as a LUKS key:
dd bs=512 count=4 if=/dev/urandom of=/crypto_keyfile.bin
chmod 000 /crypto_keyfile.bin
chmod 600 /boot/initramfs-linux*
cryptsetup luksAddKey /dev/sdX# /crypto_keyfile.bin
[Code] ....
Code: Select allupdate-initramfs -v -k -u all
What is the analog to Part 2 (and Part 3 if I'm wrong about how to regenerate the initramfs...)??
I do not find any initramfs-2.6.33.5-112.fc13.i686.PAE.img in my /boot folder after I updated Fedora 13 after a fresh installation. The vmlinuz file is present in the /boot folder.he grub.conf file does not show any initrd entry too.
View 3 Replies View RelatedI'm running FC 13. I believe that the base install is kernel 2.6.33.6-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 2.6.34.7-56 nor 2.6.34.8-68 installed an initramfs file. Since my root volume is in LVM, I can't boot with those kernels. I saw in another post that doing a "yum install kernel" would install the missing files. I tried that and it tells me that kernel-2.6.34.8-68.fc13.x86_64 is already installed and latest version.
I ultimately want to upgrade to FC 15 because I've got a new nVidia video card and need driver 270.41.06 for fc15. My fear is that if I upgrade I might not get the initramfs files in the new versions of FC and end up with an unusable system. Is there a way to add the initramfs files for the newer kernels and/or will I have the files after an upgrade?
i am using linux for couple of years. suddenly i a question arises in my mind. Before loading kernel during booting linux box initrd image loads necessary real mount point, file system, modules etc. but how initrd loads them ?? is there predefined modules list stored in initrd image or something else....what is the background procedure of it
View 1 Replies View RelatedI have compiled the linux kernel. My bzImage is 1,14 mb big
Anyway. It's only 2 programs i need and it's Python and Busybox. I have compiled python and busybox and put them together in a folder. Busybox is 146 kb and pyton is 4,4 mb.
But how do i make an initrd file of them? Or should a make an initrd file of them?
I get this error when a runt with a compiled busybox to gz format as initrd, and without initrd.
Quote:
VFS: Cannot open root device "sda1" or unknow-block(0,0)
Please append a correct "root=" boot option; here are the available partions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)Pid: 1, comm: swapper Not tainted 2.6.38.3 #1
Do you know how to make an initrd?
creation of initrd manually(not using mkinitrd).
View 1 Replies View Relatedi am using rhel5 and i just wanted to see the contents of the initrd image. I have copied that from /boot/grub and saved in /tmp directory. Then i did the following
#mv initrd-2.6.18-53.el5.img initrd-2.6.18-53.el5.img.gz
#gunzip initrd-2.6.18-53.el5.img.gz
#mount -o loop initrd-2.6.18-53.el5.img /mnt
when i gave that, it says "mount: you must specify the filesystem type" Then i included "-t ext2" option in the mount command. Now it says,
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Then i created a ext2 filesystem and did the same thing. But there is no difference.
i want to boot from UUID using initrd,
View 1 Replies View RelatedI've always booted Slackware with an initrd until recently. With my new installation of Slack Current (13.37), I didn't bother to create an initrd because of the constantly updating/transient nature of the current branch at the moment.My question is this: when 13.37 does go final in a few days, should I go back to my normal practice of booting with an initrd? Also, I think I understand how the initial ramdisk works, but is it really needed with the more modern kernels?
View 14 Replies View RelatedAll I see is: Quote: Loading vmlinuz Loading initrd.img
View 7 Replies View RelatedI have encountered a bug in the live-build in Debian Live. The persistence does not work it is because of the bug #767195. I cannot recreate another live img file because of bandwidth problem, is there any way to repack the initrd and enable the cryptsetup?
as per suggested:
#767195 – cryptsetup needs to be enabled for initramfs inclusion – Debian Bug report logs
On Wed, Oct 29, 2014 @ 18:09, Evgeni Golov <evgeni@grml.org> wrote:
....
Edit: Line 77 -79 @
# nano /usr/lib/live/build/chroot_hacks
[Code] ....
Why use nash instead of busybox in initrd and initramfs? I'm just looking for pros and cons of both really (and any other applications with similar functionality). I'm currently leaning towards busybox being the better option, why redhat and fedora use nash in their initrd.
View 2 Replies View RelatedI debootstrapped an install into an existing lvm and booted into it and everything is working great except that after initrd hands off to boot the real root, the text font changes and the resolution is unsupported by my old monitor. The box is up and running because I can ssh in. This is more of an annoyance than anything as I only use the console when something is broken, but it does need to be resolved.
I used dpkg-reconfigure console-setup as described in the debootstrap config guide but I don't see an option for changing the "vga" statement before it regenerates the initrd.