Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Ian Jackson writes ("Re: The current kernel doesn't support the Logical Volume
Manager. You may need to load the lvm-mod module."):
> This is all rather unfortunate. Perhaps we could update the package
> name of the module udebs when the kernel is updated, and arrange for
> old installers to use the old udebs ?
Or perhaps we could somehow teach anna to install the older, working,
version of kernel module packages. I know nothing really about anna
but perhaps we could bake a version number into the initrd which would
tell it do download a particular manifest, or something.
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20266.37146.403590.192...@chiark.greenend.org.uk
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Philipp Kern writes: > Currently we only ship udebs on CD images, which in turn cannot sanely be PXE > booted, AFAIK. > > I guess we can then conclude that keeping the old installer binaries doesn't > actually help anybody. Not even keeping those of r0. We should keep the old > sources around in squeeze-r0 though. For all of them. This is all rather unfortunate. Perhaps we could update the package name of the module udebs when the kernel is updated, and arrange for old installers to use the old udebs ? Ian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20266.36721.845248.793...@chiark.greenend.org.uk
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On Wed, Feb 1, 2012 at 22:11:29 +0100, Philipp Kern wrote: > Yeah, I thought that. However I wonder why that is. Where's the ABI > boundary? Old modules keep working with the new kernel. Not necessarily the other way around. Cheers, Julien signature.asc Description: Digital signature
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On Wed, Feb 01, 2012 at 09:12:04PM +0100, Julien Cristau wrote: > On Tue, Jan 31, 2012 at 22:56:02 +0100, Philipp Kern wrote: > > On Tue, Jan 31, 2012 at 09:46:50PM +, Ian Jackson wrote: > > > Would you agree that this is a bug ? > > Can you tell me what's broken? > Loading new modules on an old kernel might fail. I don't think this is > new, if you want an image that works across point releases you need one > that has all the kernel module udebs on it. Yeah, I thought that. However I wonder why that is. Where's the ABI boundary? So it's "just" fixed for some set of symbols known to be used by external modules? And the symbols used by the kernel udebs can change at every time? Currently we only ship udebs on CD images, which in turn cannot sanely be PXE booted, AFAIK. I guess we can then conclude that keeping the old installer binaries doesn't actually help anybody. Not even keeping those of r0. We should keep the old sources around in squeeze-r0 though. For all of them. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Hi all. On Tue, Jan 31, 2012 at 09:46:50PM +, Ian Jackson wrote: Would you agree that this is a bug ? Can you tell me what's broken? Loading new modules on an old kernel might fail. I don't think this is new, if you want an image that works across point releases you need one that has all the kernel module udebs on it. Isn't the latest image/initrd combination also usable with older point releases? Greets Marcus -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f299da1.9000...@gmx.ch
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On Tue, Jan 31, 2012 at 22:56:02 +0100, Philipp Kern wrote: > On Tue, Jan 31, 2012 at 09:46:50PM +, Ian Jackson wrote: > > Would you agree that this is a bug ? > > Can you tell me what's broken? > Loading new modules on an old kernel might fail. I don't think this is new, if you want an image that works across point releases you need one that has all the kernel module udebs on it. Cheers, Julien signature.asc Description: Digital signature
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Philipp Kern writes ("Re: The current kernel doesn't support the Logical Volume
Manager. You may need to load the lvm-mod module."):
> On Tue, Jan 31, 2012 at 11:50:48PM +0300, George Shuklin wrote:
> > 2) We didn't download newer initrd/vmlinuz and using saved images to your
> > servers (some days before they works fine for long time, now stops)
>
> You should probably install one of the debian-installer-6.0-netboot-amd64
> packages on your TFTP boot server. Sadly netboot is not currently guaranteed
> to work across point releases.
Can't we make this work somehow ?
The old images are still in the archive in
installer-{amd64,i386}/
which suggests that they're supposed to work, but they are broken AIUI
by the lack of the appropriate udebs.
Would you agree that this is a bug ?
Ian.
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20264.24906.751670.248...@chiark.greenend.org.uk
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On Tue, Jan 31, 2012 at 09:46:50PM +, Ian Jackson wrote: > Would you agree that this is a bug ? Can you tell me what's broken? Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On Tue, Jan 31, 2012 at 11:50:48PM +0300, George Shuklin wrote: > 2) We didn't download newer initrd/vmlinuz and using saved images to your > servers (some days before they works fine for long time, now stops) You should probably install one of the debian-installer-6.0-netboot-amd64 packages on your TFTP boot server. Sadly netboot is not currently guaranteed to work across point releases. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Hi again. The most strage thing: Wheezy and Squeezy (!) installers both was broken. I feel somehow lost due 'stable' regression. Are you using the kernel.org mirror? This one seems to be out of sync atm. I had the same problem, which has been solved by downloading the images form an up2date mirror. No, we using 'mirror.yandex.ru' mirror to sync our own mirror (we usually checking hashes and CRC before switch from old to new mirror copy). I'm actually don't know where they do their sync... I was not able to solve which package is broken... partman-lvm? partman-lvm-auto? lvm2? I have replaced kernel and initrd with the ones from: ftp://ftp.ch.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/debian-installer/amd64/ and it worked again. Please reply to the list, as it can be useful for others, too. Thanks! For Squeeze it works. For Wheezy, as I can see, does not, because files are dated 2011... ... And parameters names are changed again - it suddenly starts to asking about keyboard language. Anyway, I hope that one will be survivable. Thank you again. You can pass the string console-keymaps-at/keymap=us to the kernel, where us should be replaced with your prefered layout. You may also want to set locale=... Greets Marcus -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f285fc7.7070...@gmx.ch
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Am 31.01.2012 21:59, schrieb George Shuklin: On 01.02.2012 00:53, Marcus Moeller wrote: Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer initrd/vmlinuz and using saved images to your servers (some days before they works fine for long time, now stops) 3) Inside VM it's possible to load dm-mod (initrd/vmlinuz match) 4) After loading module and returning back to installator same error appear. I think something has been changed inside some udebs, but I have no skills to debug logs. Just in case syslog of installer: http://desunote.ru/test/syslog.txt http://desunote.ru/test/partman.txt http://desunote.ru/test/hardware-summary.txt The most strage thing: Wheezy and Squeezy (!) installers both was broken. I feel somehow lost due 'stable' regression. Are you using the kernel.org mirror? This one seems to be out of sync atm. I had the same problem, which has been solved by downloading the images form an up2date mirror. No, we using 'mirror.yandex.ru' mirror to sync our own mirror (we usually checking hashes and CRC before switch from old to new mirror copy). I'm actually don't know where they do their sync... I was not able to solve which package is broken... partman-lvm? partman-lvm-auto? lvm2? I have replaced kernel and initrd with the ones from: ftp://ftp.ch.debian.org/debian/dists/stable/main/installer-amd64/current/images/netboot/debian-installer/amd64/ and it worked again. Greets Marcus -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f285967.4070...@gmx.ch
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
On 01.02.2012 00:53, Marcus Moeller wrote: Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer initrd/vmlinuz and using saved images to your servers (some days before they works fine for long time, now stops) 3) Inside VM it's possible to load dm-mod (initrd/vmlinuz match) 4) After loading module and returning back to installator same error appear. I think something has been changed inside some udebs, but I have no skills to debug logs. Just in case syslog of installer: http://desunote.ru/test/syslog.txt http://desunote.ru/test/partman.txt http://desunote.ru/test/hardware-summary.txt The most strage thing: Wheezy and Squeezy (!) installers both was broken. I feel somehow lost due 'stable' regression. Are you using the kernel.org mirror? This one seems to be out of sync atm. I had the same problem, which has been solved by downloading the images form an up2date mirror. No, we using 'mirror.yandex.ru' mirror to sync our own mirror (we usually checking hashes and CRC before switch from old to new mirror copy). I'm actually don't know where they do their sync... I was not able to solve which package is broken... partman-lvm? partman-lvm-auto? lvm2? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f28561d.7000...@gmail.com
Re: The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module.
Hi all. Few days ago found all our preseed-based installation stated failing with message The current kernel doesn't support the Logical Volume Manager. You may need to load the lvm-mod module. 1) Preseed was untouched 2) We didn't download newer initrd/vmlinuz and using saved images to your servers (some days before they works fine for long time, now stops) 3) Inside VM it's possible to load dm-mod (initrd/vmlinuz match) 4) After loading module and returning back to installator same error appear. I think something has been changed inside some udebs, but I have no skills to debug logs. Just in case syslog of installer: http://desunote.ru/test/syslog.txt http://desunote.ru/test/partman.txt http://desunote.ru/test/hardware-summary.txt The most strage thing: Wheezy and Squeezy (!) installers both was broken. I feel somehow lost due 'stable' regression. Are you using the kernel.org mirror? This one seems to be out of sync atm. I had the same problem, which has been solved by downloading the images form an up2date mirror. Greets Marcus -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f2854c7.1010...@gmx.ch
