Rufus: vesamenu upgrade not compatible with HP Service Pack iso, otherwise fine.

[nidarian]

Checklist

• [x] I looked at https://github.com/pbatard/rufus/wiki/FAQ to see if my question has already been answered.
• [x] I performed a search in the issue tracker for similar issues, using keywords relevant to my problem.
• [ ] I clicked the Log button in Rufus and copy/pasted the log into the line that says <FULL LOG> below.
• [ ] The log I am copying is the FULL log, starting with the line Rufus version: x.y.z - I have NOT removed any part of it.

Additionally (if applicable):

• [x] I ran a bad blocks check, by clicking the "bad blocks" check box in Rufus, and confirmed that my USB is not defective
• [x] I also tried one or more of the following:
  
  
  
  • [x] Using a different USB drive
  
  
  • [x] Plugging the USB into a different port
  
  
  • [x] Running Rufus on a different computer
  
  
• [x] If using an ISO image, I clicked on the # button (at the bottom of the Rufus interface), to compute the MD5, SHA1 and SHA256 checksums, which are therefore present in the log I copied. I confirmed, by performing an internet search, that these values match the ones from the official image.

Issue description

vesamenu upgrade not compatible with HP Service Pack iso, otherwise fine.

No log file produced, serveral USB sticks not bootable if vesamenu file is upgraded from internet.

[pbatard]

Please ALWAYS include the log!!! The first 4 checkboxes are NOT optional, and the Log is the one from Rufus, which is ALWAYS available.

There's a VERY GOOD REASON I'm asking for it, ALWAYS, and that's because, if you had copied/paste it:

1. I would know which version of Windows/Rufus you are using.
2. I would know if your download of vesamenu.c32 was successful or not. This may very well be the issue.
3. I would know the exact name of the 'HP Service Pack iso' you are using, giving me a chance to locate it... If you don't tell me precisely where I can find the problematic ISO, it's very difficult for me to fix this issue...

Because you didn't follow the very clear rules, I am very close to just ignore your report and concentare on answering requests from people who are actually capable of following them. There's a reason why these rules are there, and there is nothing more infuriating than not being able to help someone, because they decided that a set of rules they don't understand, but which are CRUCIAL, such as ALWAYS copy/pasting a FULL log, should not apply to them. Don't do that!!

[nidarian]

I sincerely apologize for my lazy behavior. I will reproduce my efforts and submits logs.

[nidarian]

Here is a log of a working instance of the ISO recorded to USB. No changes made.
rufus211_not_upgrading_Vesamenu.log.txt

[pbatard]

Thanks. According to the log, the vesamenu.c32 was not replaced. You should have gotten something like:

...
Extracting: E:\system\squashfs_sys.img (218.1 MB)
Extracting: E:\system\vesamenu.c32 (138.2 KB)
  Replaced with local version ✓
Extracting: E:\system\vmlinuz (4.7 MB)
...

But you only got:

...
Extracting: E:\system\squashfs_sys.img (218.1 MB)
Extracting: E:\system\vesamenu.c32 (138.2 KB)
Extracting: E:\system\vmlinuz (4.7 MB)
...

I'm currently downloading the ISO (bit of a pain in the ass to get, even though it's just a service pack) and will test it to see if there's anything I need to do in Rufus.

[pbatard]

I think your download failed. Here's what I get on my machine:

Rufus version: 2.11.995
Windows version: Windows 10 64-bit (Build 14393)
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.02~beta3
System locale ID: 0x0809
Will use default UI locale 0x0809
Found USB 3.0 device 'SanDisk Extreme USB Device' (0781:5580)
Using autorun.inf label for drive F: 'ESXI-5.1.0-799733-STANDARD'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x012E25DA
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16012894208 bytes)
  Start Sector: 2048, Boot: Yes
Scanning image...
ISO analysis:
  Image is an ISO9660 image
  Will use '/usb/syslinux.cfg' for Syslinux
  Detected Syslinux version: 3.75 (from '/system/isolinux.bin')
Disk image analysis:
  Image does not have an x86 Master Boot Record
ISO label: 'SPP2016040'
  Size: 6167623680 bytes
  Has a >64 chars filename
  Uses: Syslinux/Isolinux v3.75
    With an old vesamenu.c32
  Uses: EFI
Using image: 864794_001_spp-2016.04.0-SPP2016040.2016_0317.20.iso
Downloading 'vesamenu.c32' from http://rufus.akeo.ie/files/syslinux-4.07/vesamenu.c32
File length: 154128 bytes
Successfully downloaded 'vesamenu.c32'

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE5 for write access
Will use 'F:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Syslinux Master Boot Record
Volume has an unknown Partition Boot Record
Clearing MBR/PBR/GPT structures...
Erasing 2048 sectors
Deleting partitions...
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (Large FAT32)...
Opened drive \\?\Volume{624c96e4-6ddd-11e6-9109-fcaa14e7bd8e} for write access
I/O boundary checks disabled
Size : 14.9 GB 31275184 sectors
Cluster size 8192 bytes, 512 Bytes Per Sector
Volume ID is 19fd:3c48
32 Reserved Sectors, 15257 Sectors per FAT, 2 FATs
1952789 Total clusters
1952788 Free Clusters
Clearing out 30562 sectors for reserved sectors, FATs and root cluster...
Initializing reserved sectors and FATs...
FAT #0 sector at address: 32
FAT #1 sector at address: 15289
Writing partition boot record...
Using Standard FAT32 partition boot record
Confirmed new volume has a primary FAT32 boot sector
Setting primary FAT32 boot sector for boot...
Confirmed new volume has a secondary FAT32 boot sector
Setting secondary FAT32 boot sector for boot...
Setting Label (This may take while)...
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Partition is already FAT32 LBA...
Set bootable USB partition as 0x80
Using Syslinux MBR
Found volume GUID \\?\Volume{624c96e4-6ddd-11e6-9109-fcaa14e7bd8e}\
Installing Syslinux 3.75...
Opened drive \\?\Volume{624c96e4-6ddd-11e6-9109-fcaa14e7bd8e} for write access
Successfully wrote 'ldlinux.sys'
Successfully wrote Syslinux boot record
Successfully remounted Volume{624c96e4-6ddd-11e6-9109-fcaa14e7bd8e}\ on F:\
Copying ISO files...
Extracting files...
Image is an ISO9660 image
This image will be extracted using Rock Ridge extensions (if present)
Extracting: F:\compaq\utils\allboards.xml (148.4 KB)
Extracting: F:\compaq\utils\balancedmodeinput.dat (765 bytes)
Extracting: F:\compaq\utils\balancedmodeinput_amd.dat (653 bytes)
Extracting: F:\compaq\utils\balancedmodeinput_gen9.dat (739 bytes)
Extracting: F:\compaq\utils\boot.bin (8 KB)
Extracting: F:\compaq\utils\conrepg8.xml (6.5 KB)
Extracting: F:\compaq\utils\conrepg9.xml (6.7 KB)
Extracting: F:\compaq\utils\cpqhwd.sh (4.4 KB)
Extracting: F:\compaq\utils\culture.sh (1.8 KB)
Extracting: F:\compaq\utils\debug_stuff.sh (1.9 KB)
Extracting: F:\compaq\utils\diags\smartstart-hpdiags.tar.gz (20.2 MB)
Extracting: F:\compaq\utils\discovery-diff.py (3 KB)
Extracting: F:\compaq\utils\drivers.xml (13.3 KB)
Extracting: F:\compaq\utils\ilorcstatus (50.3 KB)
Extracting: F:\compaq\utils\iscsi_cfg.pl (1.9 KB)
Extracting: F:\compaq\utils\iscsi_cfg.vbs (2.8 KB)
Extracting: F:\compaq\utils\kexec-me.sh (3.7 KB)
Extracting: F:\compaq\utils\manitree (2.7 KB)
(...)
Extracting: F:\system\vesamenu.c32 (138.2 KB)
  Replaced with local version ✓
Extracting: F:\system\vmlinuz (4.7 MB)
Extracting: F:\usb\hpusbkey\common.cfg (420 bytes)
Extracting: F:\usb\hpusbkey\eula.en (9.6 KB)
Extracting: F:\usb\hpusbkey\eula.ja (9.4 KB)
Extracting: F:\usb\hpusbkey\hpmboot.cfg (72 bytes)
Extracting: F:\usb\hpusbkey\hpuninst.xml (528 bytes)
Extracting: F:\usb\hpusbkey\hpusb.jpg (6.2 KB)
Extracting: F:\usb\hpusbkey\hpusbkey.exe (3.2 MB)
Extracting: F:\usb\hpusbkey\hpusbkey.inf (6 KB)
Extracting: F:\usb\hpusbkey\install.xml (204 bytes)
Extracting: F:\usb\hpusbkey\mainmenu.cfg (120 bytes)
Extracting: F:\usb\hpusbkey\syslinux.cfg (111 bytes)
Extracting: F:\usb\hpusbkey\syslinux.exe (26.5 KB)
Extracting: F:\usb\hpusbkey\usbhlpen.htm (28 KB)
Extracting: F:\usb\hpusbkey\usbhlpja.htm (31.4 KB)
Extracting: F:\usb\hpusbkey\vesamenu.c32 (144.3 KB)
  Replaced with local version ✓
Extracting: F:\usb\sdgconfig (10 bytes)
Extracting: F:\usb\syslinux (24.9 KB)
Extracting: F:\usb\syslinux.cfg (1.3 KB)
Extracting: F:\usb\syslinux.exe (26.5 KB)
Extracting: F:\usb\usbcreator.cmd (664 bytes)
Extracting: F:\usb\usbcreator.sh (240 bytes)
Extracting: F:\usb\usbcreator.xml (1.9 KB)
Extracting: F:\usb\usbmenu.cfg (1.3 KB)
Extracting: F:\xml\content.xml (1.6 MB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\apache.txt (7.5 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\Apache2.txt (21.5 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\blade_oa.txt (178.8 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\Boost.txt (1.3 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\bsd.txt (1.5 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\curl.txt (1 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\expat.txt (841 bytes)
Extracting: F:\_autorun\HTMLFILES\eulatxt\expat2.txt (1.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\gnugpl20.txt (18.7 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\gnugpl3.txt (32.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\gnulpgl.txt (26.6 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\hpala.txt (5.3 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\IPAFont.txt (9.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\jquery.txt (1.1 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\lgpl.txt (51.5 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\libmba.txt (1.5 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\license.htm (42.6 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\lsi_eula.txt (1.7 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\mit.txt (1.1 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\mozilla.txt (30.7 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\opendlap.txt (2.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\openssl.txt (6.3 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\openssl098.txt (6.3 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\php.txt (3.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\php301.txt (3.2 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\python.txt (2.4 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\sleepcat.txt (5.6 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\ssleaylicense.txt (3.1 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\ssllicense.txt (2.6 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\swing.txt (1.7 KB)
Extracting: F:\_autorun\HTMLFILES\eulatxt\zlib.txt (1.1 KB)
Created: F:\syslinux.cfg
Finalizing, please wait...
Created: F:autorun.inf
Created: F:autorun.ico

Found USB 3.0 device 'SanDisk Extreme USB Device' (0781:5580)
Using autorun.inf label for drive F: 'SPP2016040'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 1946, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x01B25D15
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: FAT32 LBA (0x0c)
  Size: 14.9 GB (16012894208 bytes)
  Start Sector: 2048, Boot: Yes
Saved C:\Users\nil\Desktop\rufus.log

Are you trying to run Rufus from a read-only file system by any chance (e.g. CD-ROM or network drive)? Rufus needs to have the ability to create a rufus_files folder in the directory it is running from. If you don't have the rights to do that, then you can't expect all functionality to work as expected.

If not, can you please compress your rufus_files directory and send it to [email protected]? I'd like to see what your directory contains.

Finally, can you try deleting the directory if it exists and try creating your USB again.
You should see something like this in the log before the format process:

Downloading 'vesamenu.c32' from http://rufus.akeo.ie/files/syslinux-4.07/vesamenu.c32
File length: 154128 bytes
Successfully downloaded 'vesamenu.c32'

This only happens for the first download, or if the rufus_files directory does not exist. You may have gotten an error then, which we'll probably see if you try downloading the file again.

[nidarian]

Sorry about getting the iso file problems. I could have sent the file to you.

Write/Read filesystem: Yes
Rufus rights to write: yes
compressed rufus_files sent to email.
rufus211 log with downloaded new vesamenu file and still not working.
rufus211_downloaded_new_vesamenu_file.log.txt

I have been using rufus2.9 until recently. But now 2.9 did not work either
rufus2.9.934_not_upgrading_vesamenu.log.txt

[pbatard]

Strange, your new log does show:

Extracting: E:\system\vesamenu.c32 (138.2 KB)
  Replaced with local version ✓
Extracting: E:\system\vmlinuz (4.7 MB)
Extracting: E:\usb\hpusbkey\common.cfg (420 bytes)
Extracting: E:\usb\hpusbkey\eula.en (9.6 KB)
Extracting: E:\usb\hpusbkey\eula.ja (9.4 KB)
Extracting: E:\usb\hpusbkey\hpmboot.cfg (72 bytes)
Extracting: E:\usb\hpusbkey\hpuninst.xml (528 bytes)
Extracting: E:\usb\hpusbkey\hpusb.jpg (6.2 KB)
Extracting: E:\usb\hpusbkey\hpusbkey.exe (3.2 MB)
Extracting: E:\usb\hpusbkey\hpusbkey.inf (6 KB)
Extracting: E:\usb\hpusbkey\install.xml (204 bytes)
Extracting: E:\usb\hpusbkey\mainmenu.cfg (120 bytes)
Extracting: E:\usb\hpusbkey\syslinux.cfg (111 bytes)
Extracting: E:\usb\hpusbkey\syslinux.exe (26.5 KB)
Extracting: E:\usb\hpusbkey\usbhlpen.htm (28 KB)
Extracting: E:\usb\hpusbkey\usbhlpja.htm (31.4 KB)
Extracting: E:\usb\hpusbkey\vesamenu.c32 (144.3 KB)
  Replaced with local version ✓
Extracting: E:\usb\sdgconfig (10 bytes)
Extracting: E:\usb\syslinux (24.9 KB)

So at least we know that the vesamenu.c32 files should have been replaced.
I really don't get how your earlier log would not have shown these lines if the file was there (which according to the zip file you sent it was). This is very puzzling. Did you edit your earlier log at all??

Now, because your earlier log didn't show these files being replaced, I didn't test actually booting that USB, so it's possible the problem is still downstream. I'll try to do that when I get a chance.

[nidarian]

Hello Sir, I have not edited the log in any ways. My experience with this ISO is that it will boot on any system, it will not run the "HP" software after it detects the system is non-HP.
I am building more USB sticks today, in an effort to make more logs. Will post soon.

[nidarian]

I found something new, it may help with testing.
We already download the latest SPP, but there is a feature I was not aware of.
Open the downloaded SPP and extract the usb/hpusbkey folder.
Run the HP USB key utility.
This may show differences in the final USB product.
I did not use this before.

[pbatard]

Here's what you need to the USB drive created by Rufus to work:

1. Edit \syslinux.cfg on the root of the USB
2. Replace its content with:

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /system/isolinux.cfg
  APPEND /system/

If you do that, your USB will work.

The problem is there are multiple isolinux/syslinux on the ISO (one in usb/ the other n system/) and of course Rufus has to try to guess which one is the right one. Unfortunately, it's the one in system/, whereas Rufus picks the one in usb/ by default.

[pbatard]

Now, I have to add that, had HP decided not to use their own custom USB generation tool on the ISO (which tries to duplicate what Rufus can do, along with having to replace vesamenu.c32), we wouldn't be having this issue...

[nidarian]

log.txt
Here is a log of all the files and directories from the HP USB tool. This USB stick works.

[nidarian]

my log file is late. Sorry. I see you already discovered the issue. Congrats

[pbatard]

I don't think I will add a special case for a very specific HP ISO. Whenever there exists two config files for Syslinux/Isolinux on the same disc, Rufus tries to use the one with the shortest path, as this is the logic that makes most sense. It so happens that, in the case of this specific media, the logic doesn't work, but it's very possible that someone may create an ISO with a config file in /usb which is the one to pick, so trying to fix things for this HP ISO may have negative consequences.

Therefore I will not fix this issue.

[worldsdream]

This is the issue that I just opened up.

https://github.com/pbatard/rufus/issues/1021#issuecomment-328594480

[pbatard]

And I will give the same answer:

I don't think I will add a special case for a very specific HP ISO. Whenever there exists two config files for Syslinux/Isolinux on the same disc, Rufus tries to use the one with the shortest path, as this is the logic that makes most sense. It so happens that, in the case of this specific media, the logic doesn't work, but it's very possible that someone may create an ISO with a config file in /usb which is the one to pick, so trying to fix things for this HP ISO may have negative consequences.

Therefore I will not fix this issue.

[worldsdream]

Ok then I will be using unetbootin just for the HP iso.

@nidarian format your usb with fat32 in windows. Then use unetbootin with the iso. Works perfect.

[DonKiShoot]

Hi,

I tried the same with Proliant Service Pack 2017.10.1 ISO

After the "Could not find kernel image : vesamenu.c32 ... vmlinuz" bug like here,
i tried to replace "usb" by "system" in /syslinux.cfg like @pbatard suggest but now i have :

Could not find kernel image : /system/syslinux.cfg

It's isolinux.cfg in the folder system

Regards,
rufus.log

[KevBrit]

After RUFUS kept using the HPE SPP "\USB Linux files" to create my USB Flash Drive, and then rewriting the syslinux.cfg file to use the "\SYSTEM Linux files" as PBATARD suggests, I still couldn't get the server to boot from it. I finally tried WORLDSDREAM's solution above to format via Windows to FAT32, then use UNetbootin Diskimage to copy the bootable .ISO over to the USB Flash Drive. "Works perfect."

[mcrommert]

Thanks for the info...i also used Unetbootin and it worked correctly

[contoso-eu]

Event tough this article is closed, but continuing beeing one of the first entries in search engines, i post this for other people that searching for this solution.

Problem:
First thing, why you are trying to make a bootable usb stick, may because you have a slow internet connection for update inside intelligent provisioning or the downloads in intelligent provisioning fail. So now you picked up a mess when:

You try to write a usb flash drive with the iso image of HPE ProLiant Service Pack - SPP AND you decide to write the image with Rufus (my version is 3.4 with standard settings) because, as like me, you know Rufus as one of the fastest an simplest usb tools. Thereforce it was your first choice. However afterwards, your ProLiant Server won't boot from the stick or he does not recognize it as bootable, or you getting mount errors.

So now, some facts:

• It does not matter if you select ISO or DD mode
• It does not matter if you change vesamenu.c32 with that one Rufus suggest or not
• The syslinux does not match the needed version for the SPP ISO (4.07 vs 3.75 at this time)
• Rufus select the wrong isolinux.cfg in addition
• UnetBootin also didn't get it working

Some people say:
Rufus finds two config files, one at /usb/isolinux.cfg and another at /system/isolinux.cfg. It picks the one at /usb but this is the wrong one, and points to it at \syslinux.cfg. So you have to edit \syslinux.cfg and change it to:

DEFAULT loadconfig

LABEL loadconfig
  CONFIG /system/isolinux.cfg
  APPEND /system/ 

In my tests, this was true for usb sticks greater 32GB. Without the syslinux.cfg corrections the usb stick was not recognized at boot time (F11). But it had no impact on sticks with or below 32GB. There it makes no difference which of the two isolinux.cfg the syslinux.cfg file points to. They always where recognized and booting. But:

Finally, after all tests, after correcting the syslinux.cfg file, replacing vesamenu.c32 i was most time able to boot, but finally i always got this error message after selecting automatic or interactive update.
_Warning!!! Unable to mount the file system [cdrom]
Warning!!! Unable to moun the file system
Preboot maintenance mode
/bin/ash: can't access tty: job control turned off_

I did my best, but at this point i have to say, there's no "rufus-way" to get the "very special" HP SPP ISO working. At the end, the syslinux version used inside the ISO and that used by rufus is not compatible. At least i did'nt find it get working.

Working alternative to Rufus - the HPE usbkey tool:
-Your USB Stick should NOT be greater than 32GB, instead it's not viewed by the tool.
-Within the SPP iso file, there is /usb/usbkey/usbkey.exe. With this HPE Tool you can create you stick and it works anytime. However it's much slower than Rufus, but it works and thats the point. Remember you can simply browse the content of the iso file by open with windows explorer.

Conclusions:
To get a working HP ProLiant SPP usb flash disk, you have to choose one of this solutions:
1) The simplest solutions is using the usb drive key tool at /usb/usbkey/usbkey.exe inside the iso file, with a usb stick not greater than 32GB. Then it works, but you just have to have patience and wait. It works.
2) If you have access to ILO, then use the iso file booting with ILO - this works.

There's only one thing left to say... You have nice servers, but shame on you HPE for the most messy iso arround the globe!

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.