RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error
|
2017-04-07, 22:41
Post: #6
|
|||
|
|||
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error
iPXE does nothing, however, if a http server responds with a gzip stream that stream is decompressed, some http servers does send such headers for .gz which means you will have a uncompressed image in memory.
Yes everything is done one thing at a time. And kernels pre 3.16 is buggy in regards to handling initrd in efi mode - it is corruption of the image itself - you could always try to decompress initrd server side and load it uncompressed in case that triggers the bug. I would look for the original patch that was added in 3.16 to fix this issue to see what exactly is going on, but I don't think there is no way to avoid it - you are just lucky if it doesn't happen. Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - zix - 2016-10-02, 00:31
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - NiKiZe - 2016-10-02, 22:32
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - zix - 2016-10-04, 15:49
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - NiKiZe - 2016-10-04, 18:48
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - pxe_curious - 2017-04-07, 16:48
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error - NiKiZe - 2017-04-07 22:41
|
User(s) browsing this thread: 1 Guest(s)