Bug#760127: initramfs-tools: creating initrd fails
On Fri, 2014-09-26 at 21:39 -0400, westlake wrote: WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps ^ Already implies the kernel since the first message. I thought the provided information was replicable enough. If someone wants to test this out, be my guest. I'm just going to repeat my questions: You wrote: a booted custom kernel is being used and installing a new kernel package fails as the initramfs script in /etc/kernel/postinst.d/ fails In what way does it fail? What are the error messages? The initramfs-tools maintainers cannot address the bug without this information. apt-get install linux-image-3.14-2-amd64enter was issued , and mkinitramfs also fails ' mkinitramfs -k -o initrd.img-3.14-2-amd64 [...] You didn't specify the kernel version to build for, so mkinitramfs defaulted to the running kernel version. The error handling could definitely be improved here though. I.e. what this command asks for is an initramfs for the running kernel version, called initrd.img-3.14-2-amd64. You presumably wanted to build it for kernel version 3.14-2-amd64, so you need to specify that on the mkinitramfs command line. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#760127: initramfs-tools: creating initrd fails
apt-get install linux-image-3.14-2-amd64enter and fails. I suggest to close the bug because nobody is using a custom kernel. The scripts are looking for /lib/modules/kernel version where kernel version==My unpackaged kernel that has been copied to /boot. And this is the running kernel. I already explained what I did to work around it so that apt-get does not fail. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
On Sat, 2014-09-27 at 15:25 -0400, westlake wrote: apt-get install linux-image-3.14-2-amd64enter and fails. But it works for me, so how am I supposed to know in what way it went wrong for you? I suggest to close the bug because nobody is using a custom kernel. That is not true; many Debian users use custom kernels and generally initramfs-tools works for them. We do try to support custom kernels. The scripts are looking for /lib/modules/kernel version where kernel version==My unpackaged kernel that has been copied to /boot. And this is the running kernel. They're not supposed to do that. I did find one instance where they do, and intend to fix it, but it only affects the way we find out what firmware files may be needed. I already explained what I did to work around it so that apt-get does not fail. Yes, but that doesn't tell us what went wrong. The error messages you sent were for an incorrect invocation of mkinitramfs, not for the package installation. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#760127: initramfs-tools: creating initrd fails
If someone tests it without any kernel modules paths (/lib/modules empty), and with a kernel(not needing an initrd in /boot as well), apt-get install kernel will fail I can understand why nobody wants to verify anything here because it takes time to compile a kernel without initrd nor any /lib/modules, and then boot up with it to see if this error occurs. I doubt anyone here is using this type of custom kernel with these conditions otherwise they'd notice the same. fwiw, the workaround output from message 5(first) message is actually completely a coincidence of wording from program output. the actual workaround I took can be found in message 12 and 17. The reason why I said is a bug or not, is testifying if this is a policy just as the name of the file edited for working around this is /etc/initramfs-tools/conf.d/driver-policy There's not much else to this report. If you want me to confirm anything you'll just have to apply the same condition tests. 1) no /lib/modules have this directory EMPTY 2) /boot/kernel one kernel nothing else (no initrd) 3) Boot this kernel, and try installing a kernel from the debian repos using initramfs 0.116 It'll fail, but that workaround works well to getting a kernel installed. Not rocket science once the same conditions are applied and should be immediately noticeable once you run a simple apt-get. The only thing non-debian on this system is that custom kernel which is booted from. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
Control: retitle -1 Cannot find root device if booted without initramfs; MODULES=dep fails On Sat, 2014-09-27 at 19:56 -0400, westlake wrote: If someone tests it without any kernel modules paths (/lib/modules empty), and with a kernel(not needing an initrd in /boot as well), apt-get install kernel will fail You could have been that someone. I can understand why nobody wants to verify anything here because it takes time to compile a kernel without initrd nor any /lib/modules, and then boot up with it to see if this error occurs. I doubt anyone here is using this type of custom kernel with these conditions otherwise they'd notice the same. [...] Well, I've now spent the time to do this, and I can confirm the problem. It looks like mkinitramfs fails because when a boot without initramfs the kernel will generate a mount entry with the device name '/dev/root' rather than the root device name on the kernel command line. I suppose we must work around that by reading the kernel command line. Ben. -- Ben Hutchings This sentence contradicts itself - no actually it doesn't. signature.asc Description: This is a digitally signed message part
Bug#760127: initramfs-tools: creating initrd fails
the kernel version is quite irrelevant because it occurs with any custom kernel that does not have modules built outside the kernel. So it happens for 3.14, 3.15 and 3.16 kernels that don't have any /lib/modules/kernel version paths needed for them. The problem is dramatic because I would be using such a particular kernel build and not any other available kernel and the user is stuck if they ever wish to install a packaged kernel later. Simply the custom kernel booted only has it's kernel image being booted from and nothing else. For some reason the workaround of commenting out a line in a policy driver file seems to do the trick. The name of the kernel in the quotation is actually /boot/3.16.1--std-ipv6-64-vps and it doesn't have any modules external of it(this is by intention to minimize surface attacks on a server) The scripts are definitely failing when a module path doesn't exists for the current runinng kernel and I was hoping it is not something that is mandatory by debian policy, if it is then feel free to close this bug report. thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
(/boot/bzImage-3.16.1--std-ipv6-64 to be more complete, but it occurs with any kernel that doesn't have modules built externally) /boot/3.16.1--std-ipv6-64-vps and it doesn't have any modules external of it(this is by intention to minimize surface attacks on a thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
On Fri, 2014-09-26 at 11:33 -0400, westlake wrote: the kernel version is quite irrelevant [...] It is very relevant as mkinitramfs cannot read your mind. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#760127: initramfs-tools: creating initrd fails
WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps ^ Already implies the kernel since the first message. I thought the provided information was replicable enough. If someone wants to test this out, be my guest. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
Control: tag -1 moreinfo You wrote: a booted custom kernel is being used and installing a new kernel package fails as the initramfs script in /etc/kernel/postinst.d/ fails In what way does it fail? What are the error messages? apt-get install linux-image-3.14-2-amd64enter was issued , and mkinitramfs also fails ' mkinitramfs -k -o initrd.img-3.14-2-amd64 WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps Device driver support needs thus be built-in linux image! depmod: ERROR: could not open directory /lib/modules/3.16.1--std-ipv6-64-vps: No such file or directory depmod: FATAL: could not search modules: No such file or directory /dev/disk/by-uuid: Is a directory mkinitramfs: for root /dev/disk/by-uuid missing disk/by-uuid /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug ' You didn't specify the kernel version to build for, so mkinitramfs defaulted to the running kernel version. The error handling could definitely be improved here though. Ben. -- Ben Hutchings The two most common things in the universe are hydrogen and stupidity. signature.asc Description: This is a digitally signed message part
Bug#760127: initramfs-tools: creating initrd fails
fwiw I commented-out line MODULES=dep (there's only one line in this file) /etc/initramfs-tools/initramfs.conf and installation(apt-get -f install) was able to complete while making an initrd image for kernel 3.14-2-amd64 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
update: path actually - /etc/initramfs-tools/conf.d/driver-policy Not sure if this is a bug or not but it prevents a kernel install from completing. My apology for sending report 760126 without a proper subject heading, thanks mika and everyone revising. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760127: initramfs-tools: creating initrd fails
Package: initramfs-tools Version: 0.116 Severity: important a booted custom kernel is being used and installing a new kernel package fails as the initramfs script in /etc/kernel/postinst.d/ fails apt-get install linux-image-3.14-2-amd64enter was issued , and mkinitramfs also fails ' mkinitramfs -k -o initrd.img-3.14-2-amd64 WARNING: missing /lib/modules/3.16.1--std-ipv6-64-vps Device driver support needs thus be built-in linux image! depmod: ERROR: could not open directory /lib/modules/3.16.1--std-ipv6-64-vps: No such file or directory depmod: FATAL: could not search modules: No such file or directory /dev/disk/by-uuid: Is a directory mkinitramfs: for root /dev/disk/by-uuid missing disk/by-uuid /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug ' The current kernel I'm using was compiled with modules built-in the kernel without any external module path. My understanding is if I'm installing a new kernel from a package it should not depend that a module path exists for the current kernel because it could be customized similar to the case I'm using (that is without using a module path) please look into, thanks -Scott -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
