Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Title
r
refined-analyst-8898
05/13/2023, 2:15 PMI noticed something unexpected with the v1.1.2 ISO installer. I installed v1.1.2 on a different disk on the same machine where v1.1.1 had previously been installed, and the previous disk was silently, unexpectedly re-used by the new install as a persistence volume.
Put another way, my intention was to allocate the disk from the previous v1.1.1 install as a Longhorn storage class. Unexpectedly, the installation succeeded on the correct disk, but the persistence volumes from the v1.1.1 installation were re-used with the v1.1.2 installation. I only selected the new disk in the v1.1.2 installer, but the old disk was used as well as the new disk.
w
witty-jelly-95845
05/16/2023, 5:27 PMWhilst not the same reason, advice is to delete all partitions first when reusing disks - https://www.suse.com/c/rancher_blog/when-to-use-k3s-and-rke2/
👍 1