ESXi 5.0 HP v125w 16GB Issue
Posted: Thu May 07, 2015 5:14 am
Our ESXi5 host boots on the HP v125w 16GB USB drive.
It fails during boot with following error: "Error loading /s.v00 Fatal error: 33 (Inconsistent data). After several reboots it now fails at an earlier file. I found a blog pointing to using USB image Tool to image system.
So on a Windows 7 unit I plug in the USB and windows sees the device (no drive letter assigned).
I fire up USB image tool and it sees the device, but I would have thought in the volume area it would have show something, but all it showed was the following:
Path was empty.
name was empty,.
Serial was 0-0
Size was 0 bytes
Free was 0 bytes.
I went ahead and did an image which was just shy of 16GB and no errors reported.
The question I have now... is this image valid based on the above info?
I stuck another USB in later which mounted as Drive L since it was one created on Windows. I ejected it and a few minutes later inserted the USB flash from the ESXi server and now it pops up saying it is also Drive L and says you need to format the disk in drive L before you use it. I said NO, but wasn't sure why I was now seeing this when it wasn't doing this when I first put it in.
I then put it back in the ESXi server thinking it would be in the same state it was originally. Now it doesn't even attempt to boot as if it doesn't see a boot loader.
Could Windows (even thought I did NOT allow it to format or do anything)... have written to the USB drive corrupting it?
Thoughts?
Thanks,
Greg
It fails during boot with following error: "Error loading /s.v00 Fatal error: 33 (Inconsistent data). After several reboots it now fails at an earlier file. I found a blog pointing to using USB image Tool to image system.
So on a Windows 7 unit I plug in the USB and windows sees the device (no drive letter assigned).
I fire up USB image tool and it sees the device, but I would have thought in the volume area it would have show something, but all it showed was the following:
Path was empty.
name was empty,.
Serial was 0-0
Size was 0 bytes
Free was 0 bytes.
I went ahead and did an image which was just shy of 16GB and no errors reported.
The question I have now... is this image valid based on the above info?
I stuck another USB in later which mounted as Drive L since it was one created on Windows. I ejected it and a few minutes later inserted the USB flash from the ESXi server and now it pops up saying it is also Drive L and says you need to format the disk in drive L before you use it. I said NO, but wasn't sure why I was now seeing this when it wasn't doing this when I first put it in.
I then put it back in the ESXi server thinking it would be in the same state it was originally. Now it doesn't even attempt to boot as if it doesn't see a boot loader.
Could Windows (even thought I did NOT allow it to format or do anything)... have written to the USB drive corrupting it?
Thoughts?
Thanks,
Greg