Happily I found the reference to the datastore which I clobbered and have removed it from the file on the USB stick. Given the error messages in my earlier post, it is clear that something remembered that datastore. A manual browse didn’t turn anything up (but was interesting for other reasons) so I tried the following command to search all files for a portion of the datastore ID:<\/p>\n
Removing the file makes esxi forget about that datastore and boot in normal time.<\/p>\n I am even more convinced that it is possible to make a USB datastore now that I can see that the USB stick which boots vSphere has vmfs portions on it. Consequently I am going to persevere on that for a bit.<\/p>\n","protected":false},"excerpt":{"rendered":" Happily I found the reference to the datastore which I clobbered and have removed it from the file on the USB stick. Given the error messages in my earlier post, it is clear that something remembered that datastore. A manual … Continue reading ~ # find \/ -type f -exec egrep 4c17e548 {} \\; -print
\n\/vmfs\/volumes\/4c17e548-9da6c4fd-ff79-001b215b7069\/.locker 0
\n\/etc\/vmware\/locker.conf
\n^C
\n<\/code>
\nAnd yes the file looks like:<\/p>\n~ # ls -l \/etc\/vmware\/locker.conf
\n-rw-r--r-T\u00a0\u00a0 1 root\u00a0\u00a0\u00a0\u00a0 root\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 60 Jun 18 17:29 \/etc\/vmware\/locker.conf<\/code><\/p>\n