Search results

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??????????????????????

It states to stop corosync service to edit, but stopping the service does NOT allow edits still, weird.

on eastproxmox1 the /etc/pve/corosync.conf file is wrong but i can't edit, permission denied.

I configured a new host (eastproxmox1) on main office network/IP then once my switch was ready, moved it to new office location with different IP. Changed the IP (etc/pve/corosync.conf) but it doesn't show in the cluster, its old IP only shows when logged into proxmox1. Since it didn't work...

ok, I did lower the swappiness, and did a reboot, now the swap usage is 0 again, weird.

I have similar issue with Swap usage maxed out but I don't think I'm over provisioned as you may see below: Any ideas why the Swap is maxed out? And how much of a performance hit do I take with it like this?

Is it normal that linked clones do not see the increase in HDD space on a template? day 1: template created with 80GB HDD. day 2: linked clones created. day 3: template HDD increased to 120GB, but linked clones do not see the difference.

Everything working now. I guess the root partition needed some free space after all.

yeah one test backup tried to go to root drive instead of the actual backup drive and filled it up, I'm freeing up space today.