RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error
|
2017-04-07, 16:48
Post: #5
|
|||
|
|||
RE: RHEL clone and UEFI booting, aka the dreaded unable to mount initrd error
Just wanted to ask what exactly happens when iPXE loads a compressed image file:
- Does iPXE decompress the file or does the kernel that gets loaded and uses that file do that? - Does the next command (lets say, for example, loading the initrd image file and then the kernel) wait until the previous command has completed? I would think so. Just trying to understand if the bug is inside the kernel where it does not decompress the initrd.img properly or if iPXE is slow loading and expanding the imagefile and when the kernel gets executed, it does not find the file and therefore panics. |
|||
« 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)