[Group.of.nepali.translators] [Bug 1900796] Re: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format"
This bug was fixed in the package flash-kernel - 3.103ubuntu1~20.04.1 --- flash-kernel (3.103ubuntu1~20.04.1) focal; urgency=medium * Backport latest upstream version to groovy (LP: #1904890) * This includes Dann Frazier's workaround for LP: #1900796 -- Dave Jones Tue, 12 Jan 2021 17:14:57 + ** Changed in: flash-kernel (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1900796 Title: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format" Status in ubuntu-kernel-tests: New Status in flash-kernel package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in flash-kernel source package in Xenial: New Status in plymouth source package in Xenial: Invalid Status in flash-kernel source package in Bionic: Confirmed Status in plymouth source package in Bionic: Invalid Status in flash-kernel source package in Focal: Fix Released Status in plymouth source package in Focal: Invalid Status in flash-kernel source package in Groovy: Fix Released Status in plymouth source package in Groovy: Invalid Status in flash-kernel source package in Hirsute: Fix Released Status in plymouth source package in Hirsute: Invalid Bug description: [Impact] Due to a firmware (u-boot) bug in reading ext4 filesystems extents, ProLiant m400 systems may fail to boot after installing a new kernel. This seems to be exacerbated when there is limited free space on the /boot filesystem. HPE is no longer providing new firmware fixes for this platform. [Test Case] Install a new kernel and reboot. When this bug is triggered, you'll see the following errors (emphasis <<>> mine): ## Executing script at 400400 11349894 bytes read in 312 ms (34.7 MiB/s) <> ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 5.8.0-25-generic Created: 2020-10-21 5:26:34 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 11349830 Bytes = 10.8 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK Wrong Ramdisk Image Format <> [Where Problems Could Occur] The workaround I've added here is to attempt to defrag the boot files so that the u-boot parsing bug is not triggered. This workaround is only activated for machines tagged with a certain property, and only the m400 server is tagged w/ that property. If there is a bug in detecting the platform or property, it could of course impact other platforms. Though it should be said that this code uses a well-established flash-kernel pattern. On the m400, the code only implements the workaround if /boot is on an ext4 filesystem (the Ubuntu default). If the filesystem detection code is buggy, we may unintentionally run e4defrag on a non-ext4 filesystem which could cause errors. Those errors currently only cause a warning to be printed - it does not fail the script. Users who miss this warning could still end up with an unbootable system if the workaround fails -- which it may, if the disk is very close to full. Long term, we should consider making this error fatal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900796/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1900796] Re: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format"
This bug was fixed in the package flash-kernel - 3.103ubuntu1~20.10.1 --- flash-kernel (3.103ubuntu1~20.10.1) groovy; urgency=medium * Backport latest upstream version to groovy (LP: #1904890) * This includes Dann Frazier's workaround for LP: #1900796 -- Dave Jones Tue, 12 Jan 2021 17:14:57 + ** Changed in: flash-kernel (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1900796 Title: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format" Status in ubuntu-kernel-tests: New Status in flash-kernel package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in flash-kernel source package in Xenial: New Status in plymouth source package in Xenial: Invalid Status in flash-kernel source package in Bionic: Confirmed Status in plymouth source package in Bionic: Invalid Status in flash-kernel source package in Focal: Fix Released Status in plymouth source package in Focal: Invalid Status in flash-kernel source package in Groovy: Fix Released Status in plymouth source package in Groovy: Invalid Status in flash-kernel source package in Hirsute: Fix Released Status in plymouth source package in Hirsute: Invalid Bug description: [Impact] Due to a firmware (u-boot) bug in reading ext4 filesystems extents, ProLiant m400 systems may fail to boot after installing a new kernel. This seems to be exacerbated when there is limited free space on the /boot filesystem. HPE is no longer providing new firmware fixes for this platform. [Test Case] Install a new kernel and reboot. When this bug is triggered, you'll see the following errors (emphasis <<>> mine): ## Executing script at 400400 11349894 bytes read in 312 ms (34.7 MiB/s) <> ## Booting kernel from Legacy Image at 400200 ... Image Name: kernel 5.8.0-25-generic Created: 2020-10-21 5:26:34 UTC Image Type: ARM Linux Kernel Image (gzip compressed) Data Size: 11349830 Bytes = 10.8 MiB Load Address: 0008 Entry Point: 0008 Verifying Checksum ... OK Wrong Ramdisk Image Format <> [Where Problems Could Occur] The workaround I've added here is to attempt to defrag the boot files so that the u-boot parsing bug is not triggered. This workaround is only activated for machines tagged with a certain property, and only the m400 server is tagged w/ that property. If there is a bug in detecting the platform or property, it could of course impact other platforms. Though it should be said that this code uses a well-established flash-kernel pattern. On the m400, the code only implements the workaround if /boot is on an ext4 filesystem (the Ubuntu default). If the filesystem detection code is buggy, we may unintentionally run e4defrag on a non-ext4 filesystem which could cause errors. Those errors currently only cause a warning to be printed - it does not fail the script. Users who miss this warning could still end up with an unbootable system if the workaround fails -- which it may, if the disk is very close to full. Long term, we should consider making this error fatal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1900796/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1900796] Re: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format"
** Also affects: flash-kernel (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: flash-kernel (Ubuntu Hirsute) Importance: Undecided Status: Fix Released ** Also affects: plymouth (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Changed in: plymouth (Ubuntu Groovy) Status: New => Invalid ** Changed in: plymouth (Ubuntu Focal) Status: New => Invalid ** Changed in: plymouth (Ubuntu Bionic) Status: New => Invalid ** Changed in: plymouth (Ubuntu Xenial) Status: New => Invalid ** Changed in: flash-kernel (Ubuntu Groovy) Status: New => Confirmed ** Changed in: flash-kernel (Ubuntu Focal) Status: New => Confirmed ** Changed in: flash-kernel (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1900796 Title: Moonshot ProLiant m400 fails to boot "Wrong Ramdisk Image Format" Status in ubuntu-kernel-tests: New Status in flash-kernel package in Ubuntu: Fix Released Status in plymouth package in Ubuntu: Invalid Status in flash-kernel source package in Xenial: New Status in plymouth source package in Xenial: Invalid Status in flash-kernel source package in Bionic: Confirmed Status in plymouth source package in Bionic: Invalid Status in flash-kernel source package in Focal: Confirmed Status in plymouth source package in Focal: Invalid Status in flash-kernel source package in Groovy: Confirmed Status in plymouth source package in Groovy: Invalid Status in flash-kernel source package in Hirsute: Fix Released Status in plymouth source package in Hirsute: Invalid Bug description: Issue found on ARM64 node ms10-35-mcdivittb0-kernel with F-5.8. Install the plymouth package from proposed will cause system failed to boot, with error message: Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid It's 100% reproducible. Steps to reproduce this: 1. Deploy Focal on this node (Architecture set to arm64/xgene-uboot, it can't be deployed if set to arm64/generic, PXE boot failed with TFTP error: 'File not found' (1)) 2. Enable proposed pocket. 3. Install the linux-generic-hwe-20.04-edge and reboot 4. It's now running with 5.8.0-25-generic on Focal 5. Install plymouth from proposed and reboot In step 5 it will generate the new boot image. $ sudo apt install plymouth Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: plymouth-theme-ubuntu-text Suggested packages: desktop-base plymouth-themes The following packages will be upgraded: plymouth plymouth-theme-ubuntu-text 2 upgraded, 0 newly installed, 0 to remove and 18 not upgraded. Need to get 121 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 plymouth-theme-ubuntu-text arm64 0.9.4git20200323-0ubuntu6.1 [9148 B] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-proposed/main arm64 plymouth arm64 0.9.4git20200323-0ubuntu6.1 [112 kB] Fetched 121 kB in 0s (326 kB/s) (Reading database ... 112559 files and directories currently installed.) Preparing to unpack .../plymouth-theme-ubuntu-text_0.9.4git20200323-0ubuntu6.1_arm64.deb ... Unpacking plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.1) over (0.9.4git20200323-0ubuntu6) ... Preparing to unpack .../plymouth_0.9.4git20200323-0ubuntu6.1_arm64.deb ... Unpacking plymouth (0.9.4git20200323-0ubuntu6.1) over (0.9.4git20200323-0ubuntu6) ... Setting up plymouth (0.9.4git20200323-0ubuntu6.1) ... update-initramfs: deferring update (trigger activated) update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Setting up plymouth-theme-ubuntu-text (0.9.4git20200323-0ubuntu6.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.2) ... Processing
