Software :: How To Cancel Swap Mounting At Boot In Debian Initrd
Oct 9, 2010
When I installed Debian stable on a headless machine of mine, I configured a partition with LUKS encryption (intended for swap), but told the installer not to use it. After installation, I configured that encrypted partition as swap and mounted it. I wanted my headless machine to boot all the way without manual intervention, so I can log in via ssh and mount my encrypted partitions.However, since the kernel was updated (and the initrd regenerated), the machine now waits during boot for me to enter the swap encryption password, but no others, only the swap.I have been unable to find in my searchings how the initrd is generated with that setting or how I can change it, preferably permanently so future regenerated initrd's don't try activating my encrypted swap on boot. Does anyone know how to configure a Debian style initrd generator to generate an initrd that will not try to activate swap?
Just the last day or so, I've noticed a long pause when I boot my laptop, with lots of disk activity. dmesg says:
[Code]...
Why would there be a 15-second pause (during which the disk is slammed) between mounting root and mounting swap? During this time I see nothing but a blank purple screen, there are no cycling dots or text scroll. Is this normal and I'm just freaking out over nothing because there's no indicator of progress? GRUB default boot options: quiet splash nomodeset video=uvesafb:mode_option=1920x1200-24,mtrr=3,scroll=ywrap vt.handoff=7
When 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..
I'm running Debian testing and after a recent software update, suddenly I can no longer boot into my single Linux kernel image anymore. I did look at the software update before I did it and I don't believe that it removed any software packages. When I try to boot into my linux 2.6.26-1-amd64 image, I get the following message from grub:"error: unknown command `initrd'"..The same error appears if I try to boot into single-user mode. I have a Windows XP partition on the same hard disk and I am still able to boot into that from grub. I've searched the net and haven't really found my same problem replicated anywhere. I would imagine that the problem is just that somehow the initrd package got removed in my last software update, but again I don't recall seeing any software that the update planned to remove.
Any thoughts on how I would go about fixing this problem? Since I'm unable to get into Linux at all, I imagine I'll have to use a LiveCD to get in and fix the problem, but I don't know where to begin looking.
I have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
My swap is not mounted at boot. get it to mount again? I CAN make it mount after booting but I need to hibernate. I read that I have to edit /etc/fstab but I'm not quite sure as to what I have to do specifically.
my Fedora 12 does fsck on boot time to time and sometimes it's really annoying having to wait for the check to complete. In Linux Mint pressing <Esc> cancelled the check; however in Fedora this does not work (nor does Ctrl+C nor anything other I've tried). What is the key to cancel the check in Fedora?
I have the swap partition configured normally in fstab but it doesn't automount when I boot up. Not only that but I can't manually mount it either (ie with 'swapon -a', 'swapon -L /dev/sda7' etc). When I try I get this error -
Ubuntu has been complaining about swap not being ready during boot. The swap partition was showing up un-known in gparted. I booted off CD, reformatted it to swap. Error message gone but system monitor > resources shows my swap size to be 86GB (the exact size of my shared NTFS volume). gparted shows the swap partition as not 'swapped on'
I am running Ubuntu 11.04 along side Windows 7 (as well as my factory restore partition) and an NTFS shared partition.
My partition structure in order of location on disc. Screen shot below to help. sda1-2 Windows 7 sda4, extended partition --sda6 Ubuntu --sda7 swap --sda5 NTFS shared partition sda3 Factory restore image
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.
I'm having difficulties mounting an FTP address to my file system automatically during boot. After a bit of research I have discovered a package called curlftpfs, I've installed this package using aptitude and I had no errors.
I've successfully mounted an FTP address manually using curlftpfs at the command line and proved to myself that this is working as it should...However, I can't get this to mount automatically and I am receiving the following error during boot when I try and mount it through /etc/fstab...
Error connecting to ftp: Failed to connect to (IP address of server): Network is unreachable
My research indicates this package should be able to do this.
I'm still a learner when it comes to Linux, but could this be because TCP/IP services are not started at the time of mounting the filesystems? I've tried a continuous ping at this computer whilst it is booting and I don't get a response until after /etc/fstab has been processed. If this is the reason, can I start them these processes earlier?
Another option would be to have a script/command run when the computer boots, but prior to MySQL loading. If this is possible, it would also satisfy my problems.
I have long been avoiding Grub2, but it got installed without my permission when I upgraded to Maverick. I was using the legacy Grub from Fedora and was quite happy, but after partitioning Ubuntu did not give me the choice of not installing Grub2. Anyway, I can live with it if I can learn it well enough to edit it as easily as I did legacy grub. My problem is that although Fedora boots fine, grub did not add the initrd entry to boot the Slackware kernel Which of course it requires.) I edited /boot/grub/grub.cfg and manually added, but as soon as I ran "update-grub" it removed it again. Does anyone know how to permenently add this line to the kernel line in Grub2 for Slackware.
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code: make gconfig make -j4 all (or make all) make modules_all make install The last command edits my grub.conf file and writes this: [Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
I am using CentOS 5.2 with GRUB booting a software RAID configuration. The first disk is md0 and is mirrored across sda1 and sdb1.I manually re-installed grub using grub-install and the machine will no longer boot off of the HD. The grub menu comes up, I can select my kernel the machine then jumps to loading the initrd and hangs.It will go no further. I have a live DVD that can boot from the HD. If I use that to first boot from the DVD, then specifiy the HD, it shows the same grub menu and then the machine boots fine w/o the initrd hang.I have tried re-installing grub but not been able to get the machine to work again w/o the DVD.
upon installing 4 2TB drives, my server will not boot. I have tried booting from a slackware 11 dvd and passing these boot paramaters:
huge26.s root=/dev/sda1 noinitrd ro in addition to just trying to boot from the DVD using the huge26.s kernel. the kernel starts to load and says "Ready." Then sits there with a flashing cursor... The problem only exists with the new 2TB drives installed. I never had any problems when I had 750GB drives installed. Also, everything works fine if I boot from the DVD using "huge26.s root=/dev/sda1 noinitrd ro" as boot paramaters, and insert the 4 2TB drives (hot add) after the system starts booting.
I have also tried booting from a backtrack 3 cd but experience the same problem (boot halt after loading initrd)
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:
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
So, I had fun with this one the past week. I had an FC11 system running just fine. Then one day it would not boot - it was hung somewhere inside the init script of the initrd image. CTRL-ALT-DEL would reboot the system. Using grub editor, I could temporarily delete the initrd line and boot into the system OK. But what was going on?
mkinitrd was of no help to me. I even did a yum update, which got a new kernel, which also generated a new initrd - no joy. I extracted the initrd file system and edited the init script. I eventually hit on this tidbit: If I commented out this line:
daemonize --ignore-missing /bin/plymouthd and rebuild the initrd image - the system would finally at least tell me what the problem was: mount failed for selinuxfs on /selinux. No such file or directory.
So, I examine the root (the real root, not the initrd temporary root) - and sure enough, no /selinux. I make one and reboot. The system goes into a "targeted policy relabel" operation, reboots, and I am back in business - even with my original, unmodified, initrd.
I have no idea what happened to my /selinux directory, but I think the initrd "init" script needs to check for this directory's existance, and make it if necessary. Or at least report that it isn't there. In FC11 right now the system just HANGS without this directory being present, without any clue as to what the problem is!
Im 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.
I 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
I just removed a proprietary (fglrx ) driver which didnt work out well.Now all my updates hanging on: Setting up initramfs-tools (0.98.1ubuntu6) ...update-initramfs: deferring update (trigger activated)Setting up linux-image-2.6.36-020636-generic (2.6.36-020636.201010210905) ...Running depmod.update-initramfs: Generating /boot/initrd.img-2.6.36-020636-genericAnd I dont know how to solve it...besides a clean install.
So I'm building a custom kernel cuz I want the fbcondecor patch in my kernel. I use the same .config that 2.6.32 debian kernel package comes with. This kernel runs perfectly. I pass --initrd to make-kpkg when building the package but no initrd is built when I install it so I have to make it using "mkinitramfs -o /boot/initrd.img-2.6.33 2.6.33" to get it to boot. Now when I try to build the nvidia drivers it complains it can't find the source. I did build kernel_headers and installed them also the source is in /usr/src/linux. I also tried to specify the path by passing --kernel-source-path= to the nvidia script but no change. What is going on? I've done this fifty times before and never had any problems. Has there been some changes to how debian kernel packages are built? EDIT: Just thought I'd add some info about the steps I took.
Code: tar xjvf linux-2.6.33.tar.bz2 ln -s linux-2.6.33 linux cd linux patch -p1 < ../fbcondecor-0.9.6-2.6.33-rc7.patch cp /boot/config-2.6.32-trunk-686 ./.config
make menuconfig Loaded .config then I removed support for maxtorfb, tile blitting and some sirrusfb thing, nothing thats relevant to my system. Changed cpu from Pentium 4 to Core 2 and added framebuffer decor support from my patch, exited and saved. Then:
[Code]....
EDIT2: I have now tried to build 2.6.32.8 in the same way with the same strange results, anyone have any thoughts as to what I'm doing wrong just throw it at me, I'm getting desperate and running out of ideas. I've checked all the kernel source symlinks and everything looks good.
I'm running 9.10 off of a 4 GiB CF card. I keep running into space issues with updates, so I purchased an 8 GiB replacement card. I've cloned the 4 GiB card to a .IMG file using DD.I've then copied the 4 GiB image back to the 8 GiB card using the Ubuntu startup disk creator program. Once done, I'm able to properly boot off of the new 8 GiB clone.Unfortunately, the clone ends up with 3.67 GiB of unallocated space at the end *see attached). I tried deleting the "extended" partition that the swap is located at after booting from a Live CD and the system was unable to boot after this. I was thinking that I would delete the swap entirely and create a swap file after I merged the existing partitions, but I was unable to do this.
best way to do this (e.g. get one large 8 GiB partition with my old image on it)? I still have the original untouched 4 GiB card and also have an external CF drive if I need to redo the cloning. I've also used Clonezilla before, so perhaps there's a way to do this that allow me to grow the image as it's being cloned.
I then only created /dev/md0 which consist of /dev/sda2 & /dev/sdb2 in RAID 1 mirror.
When I boot the system, I show that Swap fails during boot in bright 'red' letters. I don't know if it failed activating both or just any swap partitions in general. When I look at 'df -h' while my system is booted, I show:
