Search results

Perfect, I didn't even think to look on the DataCenter side.

api error (status = 400 Bad Request): error creating token: api error (status = 400 Bad Request): Parameter verification failed.tokenid: Token already exists How do I use existing token or delete the one that's already there?

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. So clearly there is more bug fixes that are being fixed we will wait for a stable version of the tool. its not even version1.0.0 yet.

We updated to 0.7.0 of the esxi import tool to fix the transfer issue. But your solution makes sense also.

Hypervisor: VMware ESXi, 7.0.3, 19193900

pve-esxi-import-tools: Installed: 0.6.1 Candidate: 0.6.1 Version table: *** 0.6.1 500 500 http://download.proxmox.com/debian/pve bookworm/pve-no-subscription amd64 Packages 100 /var/lib/dpkg/status 0.6.0 500 500 http://download.proxmox.com/debian/pve...

root@proxmoxVDI1:~# pveversion -v proxmox-ve: 8.1.0 (running kernel: 6.5.11-5-pve) pve-manager: 8.1.10 (running version: 8.1.10/4b06efb5db453f29) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-8 proxmox-kernel-6.5.13-3-pve-signed: 6.5.13-3 proxmox-kernel-6.5: 6.5.13-3...

**Update**, after waiting 15 minutes I can rejoin the server now. What is going on here?

Well, I tried it on one of the other VMWARE boxes and it did the exact same thing. I now only have one VMWARE box I can connect to, although I can't migrate any VM from any box.

I connected to 3 vmware vsphere boxes. 1 dropped during a VM migration. I deleted the storage and now cannot re-add it. I get the below error: create storage failed: (vim.fault.HostConnectFault) { dynamicType = <unset>, dynamicProperty = (vmodl.DynamicProperty) [], msg = '503 Service...

Beats me, all 3 server were created at same time but magically one got stripe. hmmm oh well, restore from backups it is I guess. thanks for helping.

ok, somehow through the Proxmox system we can create RAIDZ1 pools as stripes, here's another server setup exactly the same way which looks like RAIDZ1 (parity), but maybe it isn't?:

here's the command in bash history, not zpool history: zpool create -f -o ashift=12 RAIDZ /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg /dev/sdh

root@proxmox2:~# zpool history RAIDZ cannot open 'RAIDZ': no such pool

I made the pool from the drop down, so you're telling me that Proxmox goes from a stripe to RAIDZ2 (parity 2 disk), where there is no single disk parity? like hardware RAID5? If so in what universe does that make any sense that Proxmox would offer such a selection? Hopefully an Admin can see...

Well, then where is the RAIDZ-1 in the drop down list in Proxmox as shown in my screenshot?

No "RAIDZ" is same as RAIDZ1, which is 1 parity drive. my zpool should be fine. If not, then in proxmox the definitions are wrong and cost me my data, minus backup recovery.

Error I get when attempting an import: root@proxmox2:~# zpool import -d /dev/disk/by-id pool: RAIDZ id: 1648085228702377083 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see...

I would like to test my existing sytem (has data already), so I need a NONdestructive (read only) test. The tests lists in the article look like read/write and destroy's existing data.

Anyone else want to chime in with some great advice??????????????????????