supportconfig from rescue mode - boot.txt and lsinitrd

[jirib]

Short story: a customer is struggling with multipath boot from SAN. He created supportconfig file after booting from a rescue media. But boot.txt does not show info about initramfs as the kernel booted (rescue media) is mostly not one present in /boot directory inside chroot.

Thinking loudly - are we somehow able to improve boot.txt if we would know that we booted from a rescue media?

Sep 08 10:56:13 rescue kernel: Linux version 4.12.14-120-default (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP Thu Nov 7 16:39:09 UTC 2019 (fd9dc36)
Sep 08 10:56:13 rescue kernel: Command line: initrd=initrd splash=silent rescue=1

^ this indicates booting from rescue media

#==[ Command ]======================================#
# /usr/bin/lsinitrd -k 4.12.14-120-default
No <initramfs file> specified and the default image '/boot/initrd-4.12.14-120-default' cannot be accessed!

Usage: lsinitrd [options] [<initramfs file> [<filename> [<filename> [...] ]]]
Usage: lsinitrd [options] -k <kernel version>

-h, --help                  print a help message and exit.
-s, --size                  sort the contents of the initramfs by size.
-m, --mod                   list modules.
-f, --file <filename>       print the contents of <filename>.
-k, --kver <kernel version> inspect the initramfs of <kernel version>.

^ this is useless, supportconfig was trying to check initramfs with version of rescue mode media.

Could we:

1. detect if it is rescue mode?
2. if so, take default from GRUB menu
3. inspect initramfs of "default" GRUB entry?
4. print info that this supportconfig is taken from rescue mode after chroot (are we sure we are inside chroot?)

Such info - valid lsinitramfs would help "me" to see if multipath is present inside initramfs.