proliant-hbamode | proliant-hbamode-kernel | proliant-hbamode-slackware | proliant-ssacli
you will need a custom kernel with usb mass storage within, unless you do that with a ramdisk (initrd / initramfs).
take good care of the target root partition definition
blkid /dev/${device}1
vi lala/boot/syslinux/syslinux.cfg
...
default hbamode
...
label hbamode
linux /boot/vmlinuz-hbamode
append PARTUUID=... ro mitigations=off vga=791
label hbamode-vsp
linux /boot/vmlinuz-hbamode
append PARTUUID=... ro mitigations=off console=tty1 console=ttyS0,115200n8
and mount points
blkid /dev/${device}1
blkid /dev/${device}2
vi lala/etc/fstab
PARTUUID=...
PARTUUID=...
du -sh lala/ cat lala/boot/syslinux/syslinux.cfg cat lala/etc/fstab sync umount lala/ rmdir lala/
etc etc-15.0-x86_64-17: system configuration files .............[ 130K] chown: warning: '.' should be ':': ‘root.utmp’ chown: warning: '.' should be ':': ‘root.shadow’ eudev eudev-3.2.11-x86_64-1: dynamic device directory system ...[ 8.8M]
==> that’s not harmful, just a warning about chown usage that differs from one system to another
/dev/sda2 has unsupported feature(s): FEATURE_C12
==> disable orphan_file ext4 filesystem feature
https://askubuntu.com/questions/1497523/feature-c12-e2fsck-get-a-newer-version-of-e2fsck