Thank you, good suggestion, but unfortunately, that does not seem to have fixed the issue.
I did a fresh install, and this is what the disks looked like right after the build:
[root@localhost:~] esxcli storage filesystem list
Mount Point Volume Name UUID Mounted Type Size Free
------------------------------------------------- ------------------------------------------ ----------------------------------- ------- ------ ------------ ------------
/vmfs/volumes/5f4e5f6d-85c09401-eee0-dca632c425e1 datastore1 5f4e5f6d-85c09401-eee0-dca632c425e1 true VMFS-6 114085068800 112575119360
/vmfs/volumes/5f4e5f6c-820e9f4c-982b-dca632c425e1 OSDATA-5f4e5f6c-820e9f4c-982b-dca632c425e1 5f4e5f6c-820e9f4c-982b-dca632c425e1 true VMFS-L 128580583424 125799759872
/vmfs/volumes/7bb4a8ec-9e43033e-c681-8fbfe0ec2921 BOOTBANK1 7bb4a8ec-9e43033e-c681-8fbfe0ec2921 true vfat 4293591040 4168417280
/vmfs/volumes/fdedeef3-7d4cb56f-e5bf-3f173b16cb2d BOOTBANK2 fdedeef3-7d4cb56f-e5bf-3f173b16cb2d true vfat 4293591040 4293525504
I disabled the arbitrator:
[root@localhost:~] /etc/init.d/usbarbitrator stop
watchdog-usbarbitrator: Terminating watchdog process with PID 132464
stopping usbarbitrator...
usbarbitrator stopped
[root@localhost:~] chkconfig usbarbitrator off
Then, I tried to upload an ISO to the datastore1. The upload got to about 13%, and then errored out. After that, I get this message:
[root@localhost:~] esxcli storage filesystem list
Cannot open volume:
But, it looks like it still sees the disks:
[root@localhost:~] ls /dev/disks
mpx.vmhba32:C0:T0:L0 vml.010000000041413030303030303030303030343839555342204449
mpx.vmhba32:C0:T0:L0:1 vml.010000000041413030303030303030303030343839555342204449:1
mpx.vmhba32:C0:T0:L0:5 vml.010000000041413030303030303030303030343839555342204449:5
mpx.vmhba32:C0:T0:L0:6 vml.010000000041413030303030303030303030343839555342204449:6
mpx.vmhba32:C0:T0:L0:7 vml.010000000041413030303030303030303030343839555342204449:7
mpx.vmhba32:C0:T0:L0:8 vml.010000000041413030303030303030303030343839555342204449:8
Any other ideas?
