install.sh not asking to load drivers or tools after successfully copying to USB

[jeffh2os]

Per install document:

"After the image is completely written to your USB flash drive, then installation script will then ask you if you'd like to install any proprietary RAID controller CLI tools (optional). Some of these tools (eg, StorCLI, arcconf, etc.) are required for certain TUI functions in ESOS. The script will print the required files and download locations with instructions on where to place the files and complete the installation."

I have tried both the downloaded tarball and building from git (both 4.x branch) and neither is asking for my extra drivers and tools.
*Update after posting this tried on 3.x branch and it also did not ask to install or add any drivers/tools after the install to USB.
(output)

[admin@linux1 esos]$ sudo ./install.sh 
cat: VERSION: No such file or directory
***  Install Script ***

### Checking for required tools...

### Verifying checksums...
esos-4.1.8_z.img.tar.bz2: OK
esos-4.1.8_z.img.tar.bz2: OK

### Here is a list of disk devices on this machine:
NAME         VENDOR   MODEL                          REV   SIZE TRAN   SUBSYSTEMS
/dev/sda     ATA      Samsung SSD 860 EVO 1TB   RVT04B6Q 931.5G sata   block:scsi:pci
/dev/sdb     ATA      Samsung SSD 860 EVO 1TB   RVT04B6Q 931.5G sata   block:scsi:pci
/dev/sdc     ATA      Samsung SSD 850 EVO 250GB EMT02B6Q 232.9G sata   block:scsi:pci
/dev/sdd     ATA      HUA723020ALA640           MK7OAA30   1.8T sata   block:scsi:pci
/dev/sde     ATA      Samsung SSD 860 EVO 250GB RVT04B6Q 232.9G sata   block:scsi:pci
/dev/sdf     ATA      WDC WD5001AALS-00J7B1     05.00K05 465.8G sata   block:scsi:pci
/dev/sdg              USB DISK 2.0                  PMAP  14.5G usb    block:scsi:usb:pci
/dev/nvme1n1          PCIe SSD                  ECFM22.4 953.9G nvme   nvme:pci
/dev/nvme0n1          PCIe SSD                  ECFM13.3   1.9T nvme   nvme:pci

### Please type the full path of your destination device node (eg, /dev/sdz):
/dev/sdg

### Proceeding will completely wipe the '/dev/sdg' device. Are you sure (yes/no)?
yes

### Writing 'esos-4.1.8_z.img.tar.bz2' to '/dev/sdg'; this may take a while...
0+131853 records in
0+131853 records out
8589934592 bytes (8.6 GB, 8.0 GiB) copied, 1953.13 s, 4.4 MB/s

### It appears the image was successfully written to disk (no errors reported)!

### ESOS boot device installation complete!
[admin@linux1 esos]$

[msmith626]

The documentation is out of date (sorry)... the installer script no longer in-lines the third-party CLI tools. Now after you boot up your ESOS instance, you can use the 'raid_tools.py' script from the root shell to "add" these tools. That said, I'm not sure what shape this tool is in. If you, can please try it and submit any fixes on GH.

[jeffh2os]

Yes, I did find that document after a while and am successfully using ssacli with esos. However after turning off smart ssd functionality I had to grab a newer ssacli binary as it said it was too old to function with the p440 raid card in my DL380G9. Regards Sent from Proton Mail mobile

…

-------- Original Message --------

On Oct 2, 2023, 10:01, Marc A. Smith wrote: The documentation is out of date (sorry)... the installer script no longer in-lines the third-party CLI tools. Now after you boot up your ESOS instance, you can use the 'raid_tools.py' script from the root shell to "add" these tools. That said, I'm not sure what shape this tool is in. If you, can please try it and submit any fixes on GH. — Reply to this email directly, [view it on GitHub](#298 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AWQNWHFFYOBO54XD46GTEL3X5LJLJAVCNFSM6AAAAAA3OHBC2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBTGE4DIMZZGY). You are receiving this because you authored the thread.Message ID: ***@***.***>