My ProxMox upgrade went smoothly. I was stunned as to how smooth. I went from 5.4 to 6 and then onto 7 in one day with no issues. Needed a reboot after upgrading to 7 though. Even though it did go smoothly, I wish I had found your video before I did it!
I just upgrade my Proxmox home-lab server following this video and everything went OK. My VM's and LXC containers started without any problem. Thank you Tim
This was a scary update. Have based on your videos started to use Proxmox for everything. So have Truenas running (with a PCI passthrough to a discshelf), Nextcloud, Plex, OpenVPN, Portainer (with a Ngnix reversed proxy and Bitwarden), Pihole and finally a HomeAssistant server that handles my whole house with the alarm, security cameras and window-shutters. So if this update would have failed I would have had a lot of work in front of me. But had the exact same "scary" questions and everything started up as it should. So thanks for doing it first so I dared to do it for my homelabb as well. Keep up the great work and greetings from Sweden.
Wish this showed up in my suggested views, just upgraded proxmox last week and it went south.. It passed the pre-check, but wound up removing PVE, had to re-install from USB and restore from backup. Great videos as always!
I have just added 4 more pve 7 nodes to my proxmox ve 6 cluster. It works seamlessly except live migrating from pve 7 to pve 6. I live migrated all my 250+ vms from 6 to 7 than remove 6s from cluster. It just works perfect. I was using cluster shared volumes from storage via SAN switches and now mixed it with ceph. Dude, this is awesome. Well done Proxmoxers.
Thanks for the video, I just upgraded my home server and your steps were flawless on my process to upgrade. Now I can apply this to a Production system that I support :)
I upgraded from scratch, fully back-up my machines to another one with proxmox backup server and was able to restore everything extremely quickly. In the past I've had post-update problems and now in major updates I prefer it that way. I don't use cluster (although I have 3 proxmox in NUC here) because that way and with the use of proxmox backup sever I have 100% autonomy. I can just reinstall and or replace without a headache with the cluster.
Tim, just stepped thru upgrading my PVE cluster from v6.13 to v7.1 without any issues or flaws. Brilliant!!! Now to tackle the Proxmox Backup Server...
I'm still very new to proxmox but I just upgraded mine using the official instructions and your video. Your video gave me reassurance that I could choose the same options on those warnings and not mess anything up!
I already upgraded and killed my PSU the day after... But now a PSU and reinstall later it runs fantastically! I can finally utilities my BTRFS array fully!
@@TechnoTim 2 out of 3 hosts done, not a problem so far. Good guide! Glad to see someone else isn't sure what the right answer is to all of the different prompts that pop up. I just wing it and hope for the best.
I only found out it was out because I needed to download an ISO to install a new node today... Saw 7 listed on the page and saw the date was 6th of July. Downloaded 6.x anyway because I didn't want to upgrade the existing nodes yet.
Great video. Very greatful for it. On my system a DELL r720xd during the upgrade, towards the end it requested which hdd/sdd GRUB should be installed on. Being a NOOB at this I gingerly selected sda. After the reboot all came up. I got it right! Woohoo.
I’ve been hooked on your channel lately. I’ve followed and replicated several of your projects based on your in depth, beginning to end videos. Keep up the great work, solid fan here! Love watching what new projects you’re getting into every time you upload
You're on top of it Tim! I didn't even know PVE7 was out yet, but given I use this both at home and in business production, your input into what's coming is greatly appreciated! Edit* I've always ran Webmin alongside PVE to net certain features such as downloading images from the web in their file browser, as well as a handful of other items even though Webmin isn't to be relied on heavily for some of it's 3rd party modules, but to that regard I will say the APC module still works (APCUPSD) as I've used this to trigger graceful shutdown of the guest systems during extended power loss.
I think it's brilliant...your videos are always informative to watch. I took the approach of backing up my VMs, including TrueNAS which handles my storage, and reinstalled Proxmox 7. The whole experience for me was very smooth. The additional work I had to do was for gpu passthrough but that was simply repasting previously used commands and changes then reboot and all is well again. The extra item I did was to install the dark theme and that for me lcompletes the whole new look for Proxmox and the v7 experience. Thanks for the video.
This is very relevant to me. Nice to do a video on Proxmox 7-upgrade. :-) You mentioned Cronezilla. Video suggestion: Purposely run a failed upgrade of Proxmox, then show us how to roll back configs from backup made from the Cronezilla + copy of /etc folder. How does it all come back together making me back online again? This would be a handy piece of hands-on experience :-) Keep up the good talks, Tim !
I got a whole bunch of those errors about GRUB. when rebooting, there was a black screen that lasted about 10 seconds... it feels like 10 hours, ya know? all good and running, thanks again
I find it helpful to view a 3 way comparison to view the changes that were done and if I remember correctly you can come back to the choice screen and choose what you want to after seeing the changes. They might have changed some defaults or something else. Thanks for the video :) .
You could definitely backup your /etc directory then when it asks if you want to replace a config with the new default, you can do it but remember what file it was. Then after run a diff on the file with your backup and put any changes you made back into the new one.
Seems like a good time to revisit my homelab, which I haven't touched in months and is an horrific mish-mash of components. I think the plan will be to start fresh with 7.0 once I've sorted out the hardware. The plan was to roll everything into one box and play around with a Win10/11 VMs, TrueNAS, etc, etc, etc, before rolling anything out to my home network. BTW; I was hoping his name would be Sudo ;-)
Nice video (as always), been considering proxmox for a while but will continue with xcp-ng for my "big racked homeserver". The last months I have been migrating from it to a smaller K3s cluster of some rpi4s and some used Dell Optiplex 3040 Micros. Less is more :-)
Keeping it Real, I appreciate that! I hate it when I get prompted with the y/n and it's not clear which way to turn. It would be nice if the Release Notes discussed what the options were doing. Thanks for the time you put into the vid's. BTW, the Johnny Deep dew works for you. cheers
Thanks for a helpful video. Yes I will upgrade (in my own sweet time ;). When apt is asking what to do about a config file, often I'll choose "D" to see the differences. If you keep your current version of "/etc/foo.conf" for example, apt will store the new version as "/etc/foo.conf.dpkg-dist". So if you want to be really careful, you can merge the changes into your own custom file. "/etc/issue" is just some text that's shown to you when you log in, so I would do "mv /etc/issue.dpkg-dist /etc/issue". Thanks again o/
Oh my god! thank youuuuu. For anyone following his great tutorial blindly like me(no sarcasm) make sur you are on 6.4-12 o 6.4-12 because I tried update from 6.4-4 and it was a chaos of repositories but I managed to revert them to Buster, upgrade to 6.4-15 and then to 7.2-11 Phew! rollercoaster but Homelab is running baby!
Dude! Your the freaking man! So those "scary" prompts... That my entire homelab life! That's how everything goes for me! I'm kinda split decisioned about how I feel. Option 1: "sweet, I'm not an idiot! Tim has these issues too!" Option 2 "wait, if 'my guy Tim' doesn't know how the hell am I supposed to know" But either way, that stuff makes me laugh my butt off. "Totem settings are OK, whatever those are!" Lol
I did a scratch install of 7 after upgrading/adding some hardware to my machine. The new features are nice! I've been having some issues with the web gui not refreshing mainly when doing ISO uploads, and start/stopping VMs.
FWIW I have a spare machine, configured with proxmox, running the latest backup of my pfsense VM, pihole VM and a critical server VM loaded and ready to go, but powered down. Anything goes wrong with my primary box I spool that second box up and I'm good to go. Yes, I have the VMs backed up separately too, but for the critical stuff it's a good way to ensure your critical network infrastructure has as little downtime as possible.
Just upgraded my three servers cluster from 6.4 to 7.1. Overall very painless. Your video was very helpful. Did have to update the ceph repository, even though I don’t have ceph installed (or you get a scary warning). Ran into a problem with proftpd which I have installed. The Debian 11 version of proftpd is buggy. It doesn’t upgrade properly, and when you finally purge and reinstall it, the rewrite module doesn’t work correctly. I finally removed it , created an Ubuntu 20.04 VM and installed it in that (Ubuntu installs an earlier version without the bugs). The buggy version is 1.3.7a, 1.3.6 works fine.
Updated with no errors. pve6to7 gave me a warning about an deprecated "maxfiles" parameter in the storage configuration. Changing "maxfiles 3" to "prune-backups keep-last=3" in /etc/pve/storage.cfg solved the issue. And the scary /etc/issue file update prompt: it's just a text file that contains the text you see on the screen before you log into the system.
Normally, on config files, you would want to review the differences just in case a new feature requires as config setting. Lately, I've seen options to do a git like merge where you can pick and choose what to keep in Linux software like this.
Yep, hit diff and see what it says. Also this is where your backup of etc comes in handy. I go with "install" the manually apply the diffs from my original etc I want to keep. This is effectively the merge option.
I wasn't sure about upgrading but this has helped me make my mind up. Thank you Tim. Are you planning on doing a more detailed video based on the changes and new features? It would be great if you could.
Thanks for the video Tim! I don't have a lot of stuff running on my little one node promox install, so I'm going to do a full reinstall and apply backups afterwards. I'm also going to be putting in a 4-port NIC and running pfSense on proxmox, wish me luck!
"all the people that don't have a subscription" hey that's me! wish they had a cheaper homelab tier, without generating income from the server it is just too pricey to justify for my dual cpu server.
That's me too! I asked them if there was something cheaper, like an enthusiast / homelab license and they said "no, just use the no subscription repository". At least I tried!
Not sure what the prices are in the US but over here in the UK it’s like €90 per year per CPU. I’m currently on a single node with dual CPU so it costs me around £155/£160 GBP per year. Personally I think that’s really good value considering what Proxmox does for me and the value I feel I get out of it. I’m also just a home lab user. I can see how the costs might start to become a little prohibitive if you’re running multiple nodes though. But for £155 a year I think that’s fair and means I’m also supporting the developers in some small way.
Nice video, thanks! You forgot to mention that if you host pfsense (or other router/DNS/DHCP service) and you stop it well...apt dist-upgrade won't work. I've upgraded with pfsense and piHole turned on
Great video! Should of waited and follow along did the update earlier this week and bonked the update and had to start over with a fresh install
3 года назад
I have a bunch of clusters to uprade, but first ones will be the ones, that have Ceph installed. Starting from 16.2 cephfs has a cephfs-mirror feature, that solves me a lot of problems! :)
I had been putting off just upgrading to 6.4 before watching this. I recently created a 7.0 VM to check if my containers would be okay for the upgrade. It looks like I'm ready to crossover (in a month or so, lol).
For the Debian config files I usually use the show difference function to see what manual changes are there, usually there are non and then I pick to overwrite with the new file. If the change is important I merge them manually into the new files. That’s usually better than going with the old files.
@@TechnoTim I think that’s not one of the best corners of Debian but luckily it also doesn’t matter much of the time (In the beginning a ring Config could really mess up things, now most packages only evolve gradually - but I don’t have experience with proxmox. Comparing sometimes involves guesswork for the more exotic config, but then again, if you can’t recognize the reason for a difference it might not need to be kept, (fingers crossed)
I am kinda glad I was able to start with 7 as I am a complete NOOB and hearing your comments in several points of the upgrade "Scary" makes me wonder if an expert is scared....what hope do average users have in taking the right path?
The warnings are honestly typical "upgrade" warnings, you sorta get used to it from any upgrades of a distro \o/ it defo can be unnerving at first, but, distro upgrades in general are, which is honestly why backups are important so that you can roll back out if stuff goes sideways Generally the defaults are fine, and if you modified less of the system files yourself, generally the defaults are fine, I've upgraded the issues file (still upgrading, however as we speak)
Whichever option you choose when you get those "config file has been modified" prompts, the other option is always available to you later. If you choose to keep the current (modified) version of the file, the new config file will be put right next to it with an additional "dpkg-dist" extension. If you choose to overwrite the current version, the old version is backed up with an "dpkg-old" extension. This way you always have access to both versions of the config file. I personally tend to choose to keep the current version of my config files, unless I know I want the system defaults that come with the updated package. I didn't make those changes for nothing, after all. After an upgrade I use "diff" to compare my modified config file with the "dpkg-dist" version to see if there are any new configuration options that I want to incorporate into my config, or perhaps the new version of the package has certain defaults that are more sane than the modifications I made in the past.
OK, this is the 1st Techno Tim tutorial that has bombed out miserably for me. (I don't blame you, Tim.) Did everything step by step (thank goodness I did the backup part too.) I got no error messages the whole way thru but after the upgrade I could not access the server via SSL, I could not ping any of the VMs or LXCs running under Proxmox, couldn't get the GUI to work BUT I could use the CLI from the server itself, with keyboard, monitor and mouse plugged in to it. I suspected it was a network config issue as everything was working properly within the server but I couldn't get anything to work outside the server. 3 hours later and no joy - everything seemed to be configured OK - I bit the bullet and installed the ISO from scratch and reloaded my config and VMs from the backup. Now everything is back up and running perfectly except for a weird thing where I can remote access my proxmox server via the Internet if I use MS Edge browser but not if I use Chrome. I have to say that at 1:30AM I wasn't inclined to chase down that minor problem. A real-life reinforcement of the value of good backups.
Using 7. on a test system - nvidia does not support this newest kernel yet so the install of the vgpu drivers fail :( - very bad i must say so i had to use gpu unlock teams install file to get it working again
I'm going to wipe out my current v6.x environment and replace it (from scratch) with version 7. Obviously this is for home use! Nice video (as always); thanks!
When it comes to default file upgrades I go with "Did I change that file?" If the answer is no, it's easy => upgrade. If the answer is yes.. well you can either keep the original.. or note down the file, upgrade and edit it later (you still have those backups) .. or do it manually. In general I think it's safe to upgrade those files though.
it depends on why the file was modified and what you are getting with the new config. Most often the config was modified by you to add some functionality you want to keep so you should keep your config.
thanks tim for the video. Would you concider doing a video on converting vmdk files to qcow so i can use my vmware/virtualbox vms on proxmox? thanks in advance
I installed Proxmox yesterday on my new home lab and I was wondering, why alot of things are different. After watching this video, I found out that I was running one of the latest proxmox 😂
It's probably been said hundreds of times but Techno Tim (to me) reminds me of Johnny Depp? Equally I've recently got into ProxMox myself, so this is helpful, thanks JD (Tim I mean!!) 😂🤫
My ProxMox upgrade went smoothly. I was stunned as to how smooth. I went from 5.4 to 6 and then onto 7 in one day with no issues. Needed a reboot after upgrading to 7 though. Even though it did go smoothly, I wish I had found your video before I did it!
When you showed us Nano and then went to grab a second puppy I was sure you were going to say it was called either Vim or Emacs.
I had one named Pico, then Nano, then Buddy…. We adopted him and we were going to name him Vim or Micro but he already knew his name so well.
My boxer is named Buddy also.
I just upgrade my Proxmox home-lab server following this video and everything went OK. My VM's and LXC containers started without any problem. Thank you Tim
Nice work!
Great video! For me 6.4 is so stable right now. Going to hold off as it's for production.
Same
Upgraded my second PVE server last night. I'm liking the new features so far.
This was a scary update. Have based on your videos started to use Proxmox for everything. So have Truenas running (with a PCI passthrough to a discshelf), Nextcloud, Plex, OpenVPN, Portainer (with a Ngnix reversed proxy and Bitwarden), Pihole and finally a HomeAssistant server that handles my whole house with the alarm, security cameras and window-shutters. So if this update would have failed I would have had a lot of work in front of me. But had the exact same "scary" questions and everything started up as it should. So thanks for doing it first so I dared to do it for my homelabb as well. Keep up the great work and greetings from Sweden.
Thank you so much! Sounds like you have quite the stack! Glad it helped!
Wish this showed up in my suggested views, just upgraded proxmox last week and it went south.. It passed the pre-check, but wound up removing PVE, had to re-install from USB and restore from backup. Great videos as always!
If you sub, they show up in your recommendations ;)
I have just added 4 more pve 7 nodes to my proxmox ve 6 cluster. It works seamlessly except live migrating from pve 7 to pve 6. I live migrated all my 250+ vms from 6 to 7 than remove 6s from cluster. It just works perfect. I was using cluster shared volumes from storage via SAN switches and now mixed it with ceph. Dude, this is awesome. Well done Proxmoxers.
Nice work!
Thanks for the video, I just upgraded my home server and your steps were flawless on my process to upgrade. Now I can apply this to a Production system that I support :)
I upgraded from scratch, fully back-up my machines to another one with proxmox backup server and was able to restore everything extremely quickly.
In the past I've had post-update problems and now in major updates I prefer it that way. I don't use cluster (although I have 3 proxmox in NUC here) because that way and with the use of proxmox backup sever I have 100% autonomy. I can just reinstall and or replace without a headache with the cluster.
Tim, just stepped thru upgrading my PVE cluster from v6.13 to v7.1 without any issues or flaws. Brilliant!!! Now to tackle the Proxmox Backup Server...
Nice work!
Did it 2 days ago. I was worried, but it worked out and still working.
I followed your upgrade process to the T. Worked flawless. Thanks for the video!!
I'm still very new to proxmox but I just upgraded mine using the official instructions and your video. Your video gave me reassurance that I could choose the same options on those warnings and not mess anything up!
Nice work!
I already upgraded and killed my PSU the day after... But now a PSU and reinstall later it runs fantastically! I can finally utilities my BTRFS array fully!
Followed you guide to upgrade Proxmox and everything went smoothly... Thanks !!!
Just about to upgrade thank you for all your awesome videos.
Thank you! Good luck! Please report back!
@@TechnoTim Upgrade just finished, pings returned after a ~2min reboot. Phew haha. Thanks again, everything went swell!
Lets goo, Proxmox is getting better and better! ,
Let's gooooo!
Thanks Tim. Just finished my update. And also happy to report that the old Dark Mode Theme script still works.
I had no idea Proxmox 7 was out until I saw this video. Sounds like I have a fun weekend project now!
Good luck! Report back!
@@TechnoTim 2 out of 3 hosts done, not a problem so far. Good guide! Glad to see someone else isn't sure what the right answer is to all of the different prompts that pop up. I just wing it and hope for the best.
I only found out it was out because I needed to download an ISO to install a new node today... Saw 7 listed on the page and saw the date was 6th of July.
Downloaded 6.x anyway because I didn't want to upgrade the existing nodes yet.
Great video. Very greatful for it.
On my system a DELL r720xd during the upgrade, towards the end it requested which hdd/sdd GRUB should be installed on. Being a NOOB at this I gingerly selected sda. After the reboot all came up. I got it right! Woohoo.
Worked 100% without any issue. Thank you.
Thanks Tim, perfect overview, my server is upgraded with no errors. Thanks again!
I’ve been hooked on your channel lately. I’ve followed and replicated several of your projects based on your in depth, beginning to end videos. Keep up the great work, solid fan here! Love watching what new projects you’re getting into every time you upload
Thank you!
You're on top of it Tim! I didn't even know PVE7 was out yet, but given I use this both at home and in business production, your input into what's coming is greatly appreciated!
Edit* I've always ran Webmin alongside PVE to net certain features such as downloading images from the web in their file browser, as well as a handful of other items even though Webmin isn't to be relied on heavily for some of it's 3rd party modules, but to that regard I will say the APC module still works (APCUPSD) as I've used this to trigger graceful shutdown of the guest systems during extended power loss.
Thank you! Glad you enjoy it!
Used this to upgrade to 7.1, thanks so much for these videos!
Great to hear!
I just upgraded. Thanks for the video. No problems!!
I think it's brilliant...your videos are always informative to watch. I took the approach of backing up my VMs, including TrueNAS which handles my storage, and reinstalled Proxmox 7. The whole experience for me was very smooth. The additional work I had to do was for gpu passthrough but that was simply repasting previously used commands and changes then reboot and all is well again. The extra item I did was to install the dark theme and that for me lcompletes the whole new look for Proxmox and the v7 experience. Thanks for the video.
I was just looking at this process yesterday. Your videos are always on point!
Happy to help!
Thanks! Really appreciate you beating the path for the rest of us.
No problem!
This is very relevant to me. Nice to do a video on Proxmox 7-upgrade. :-) You mentioned Cronezilla. Video suggestion: Purposely run a failed upgrade of Proxmox, then show us how to roll back configs from backup made from the Cronezilla + copy of /etc folder. How does it all come back together making me back online again? This would be a handy piece of hands-on experience :-) Keep up the good talks, Tim !
I got a whole bunch of those errors about GRUB. when rebooting, there was a black screen that lasted about 10 seconds... it feels like 10 hours, ya know? all good and running, thanks again
I actually upgraded at the same time you did with your youtube video and official docs of course.
Thanks Tim! Upgraded my PVE just now, all went smoothly!
Great to hear!
Thank you for your great video AND web notes. I wanted to move to 7.1 and it was pain-free thanks to you. ✔
I find it helpful to view a 3 way comparison to view the changes that were done and if I remember correctly you can come back to the choice screen and choose what you want to after seeing the changes. They might have changed some defaults or something else. Thanks for the video :) .
Thank you!
Thanks Tim for being the guinea pig, and for the mid installation puppy melt ;)
Always!
You could definitely backup your /etc directory then when it asks if you want to replace a config with the new default, you can do it but remember what file it was. Then after run a diff on the file with your backup and put any changes you made back into the new one.
Thanks!
Brilliant video Tim. I didn't even know Proxmox 7 was out yet. I'll probably wait a few months before doing as upgraded a V6 works a treat...
Thanks for the great vid! I just upgraded and your instructions worked perfectly. Thank you.
Great to hear!
Seems like a good time to revisit my homelab, which I haven't touched in months and is an horrific mish-mash of components.
I think the plan will be to start fresh with 7.0 once I've sorted out the hardware. The plan was to roll everything into one box and play around with a Win10/11 VMs, TrueNAS, etc, etc, etc, before rolling anything out to my home network.
BTW; I was hoping his name would be Sudo ;-)
Great name!
Thanks. Had no problems whatsoever!
If you're looking to upgrade to Proxmox 8, you can follow this same process, just use pve7to8 instead!
Have you upgraded proxmox yet?
Yip, I actually upgraded my Proxmox server earlier today.
I was holding the update, but after this video i’m starting right now
Yep, did it last night. May be me but find the UI quicker.
@@spikeukspikeuk me too, expecially the vm console tab
yep day one 😨 but no problem with the upgrade
Tim, thank you for putting out all this great content! I appreciate you.
Thank you!
Nice video (as always), been considering proxmox for a while but will continue with xcp-ng for my "big racked homeserver". The last months I have been migrating from it to a smaller K3s cluster of some rpi4s and some used Dell Optiplex 3040 Micros. Less is more :-)
Keeping it Real, I appreciate that! I hate it when I get prompted with the y/n and it's not clear which way to turn. It would be nice if the Release Notes discussed what the options were doing. Thanks for the time you put into the vid's. BTW, the Johnny Deep dew works for you. cheers
Thanks for a helpful video. Yes I will upgrade (in my own sweet time ;). When apt is asking what to do about a config file, often I'll choose "D" to see the differences. If you keep your current version of "/etc/foo.conf" for example, apt will store the new version as "/etc/foo.conf.dpkg-dist". So if you want to be really careful, you can merge the changes into your own custom file. "/etc/issue" is just some text that's shown to you when you log in, so I would do "mv /etc/issue.dpkg-dist /etc/issue". Thanks again o/
Great strategy!
Oh my god! thank youuuuu. For anyone following his great tutorial blindly like me(no sarcasm) make sur you are on 6.4-12 o 6.4-12 because I tried update from 6.4-4 and it was a chaos of repositories but I managed to revert them to Buster, upgrade to 6.4-15 and then to 7.2-11 Phew! rollercoaster but Homelab is running baby!
Dude! Your the freaking man!
So those "scary" prompts... That my entire homelab life! That's how everything goes for me! I'm kinda split decisioned about how I feel.
Option 1: "sweet, I'm not an idiot! Tim has these issues too!"
Option 2 "wait, if 'my guy Tim' doesn't know how the hell am I supposed to know"
But either way, that stuff makes me laugh my butt off. "Totem settings are OK, whatever those are!"
Lol
Haha! Yeah, I've never known what to do there and I am not going to pretend like I do!
I did a scratch install of 7 after upgrading/adding some hardware to my machine. The new features are nice! I've been having some issues with the web gui not refreshing mainly when doing ISO uploads, and start/stopping VMs.
Thanks for sharing! Hopefully in the next patch your issues get cleared up!
FWIW I have a spare machine, configured with proxmox, running the latest backup of my pfsense VM, pihole VM and a critical server VM loaded and ready to go, but powered down. Anything goes wrong with my primary box I spool that second box up and I'm good to go.
Yes, I have the VMs backed up separately too, but for the critical stuff it's a good way to ensure your critical network infrastructure has as little downtime as possible.
Tim,
Fantastic video, really helped me out. Amazing job man. Thank you.
Just upgraded my three servers cluster from 6.4 to 7.1. Overall very painless. Your video was very helpful.
Did have to update the ceph repository, even though I don’t have ceph installed (or you get a scary warning).
Ran into a problem with proftpd which I have installed. The Debian 11 version of proftpd is buggy. It doesn’t upgrade properly, and when you finally purge and reinstall it, the rewrite module doesn’t work correctly.
I finally removed it , created an Ubuntu 20.04 VM and installed it in that (Ubuntu installs an earlier version without the bugs).
The buggy version is 1.3.7a, 1.3.6 works fine.
Modern kernel, modern debian, and updated qemu.
Yea, will definitely upgrade when i have some free time.
GREAT VIDEO!!!! I have upgraded my Proxmox very very smoothly!!!!
Question: why you under Updates -> Repositories -> bullseye-security is not enabled?
Excellent, excellent content; no bs guessing etc.
Updated with no errors.
pve6to7 gave me a warning about an deprecated "maxfiles" parameter in the storage configuration. Changing "maxfiles 3" to "prune-backups keep-last=3" in /etc/pve/storage.cfg solved the issue.
And the scary /etc/issue file update prompt: it's just a text file that contains the text you see on the screen before you log into the system.
Normally, on config files, you would want to review the differences just in case a new feature requires as config setting. Lately, I've seen options to do a git like merge where you can pick and choose what to keep in Linux software like this.
Love the idea of a merge! Thanks for the advice!
Yep, hit diff and see what it says. Also this is where your backup of etc comes in handy. I go with "install" the manually apply the diffs from my original etc I want to keep. This is effectively the merge option.
I wasn't sure about upgrading but this has helped me make my mind up. Thank you Tim.
Are you planning on doing a more detailed video based on the changes and new features? It would be great if you could.
Thanks! That's an idea!
Thanks for the video Tim! I don't have a lot of stuff running on my little one node promox install, so I'm going to do a full reinstall and apply backups afterwards. I'm also going to be putting in a 4-port NIC and running pfSense on proxmox, wish me luck!
Glad I could help! Good luck!
"all the people that don't have a subscription" hey that's me! wish they had a cheaper homelab tier, without generating income from the server it is just too pricey to justify for my dual cpu server.
That's me too! I asked them if there was something cheaper, like an enthusiast / homelab license and they said "no, just use the no subscription repository". At least I tried!
@@TechnoTim me too, i'd subscribe immediately a "homelab" license...
Not sure what the prices are in the US but over here in the UK it’s like €90 per year per CPU. I’m currently on a single node with dual CPU so it costs me around £155/£160 GBP per year. Personally I think that’s really good value considering what Proxmox does for me and the value I feel I get out of it. I’m also just a home lab user. I can see how the costs might start to become a little prohibitive if you’re running multiple nodes though. But for £155 a year I think that’s fair and means I’m also supporting the developers in some small way.
Thanks! It's per socket here too, so for me I have 6 sockets total 😭
Thx for this! Will use your vid to upgrade my old laptop running proxmox 😊✌️
Nice video, thanks!
You forgot to mention that if you host pfsense (or other router/DNS/DHCP service) and you stop it well...apt dist-upgrade won't work.
I've upgraded with pfsense and piHole turned on
Great video! Should of waited and follow along did the update earlier this week and bonked the update and had to start over with a fresh install
I have a bunch of clusters to uprade, but first ones will be the ones, that have Ceph installed. Starting from 16.2 cephfs has a cephfs-mirror feature, that solves me a lot of problems! :)
I had been putting off just upgrading to 6.4 before watching this. I recently created a 7.0 VM to check if my containers would be okay for the upgrade. It looks like I'm ready to crossover (in a month or so, lol).
Great video. Thank you! Might try the upgrade tonight
Good luck!
Love this guy's videos.
Thank you!
For the Debian config files I usually use the show difference function to see what manual changes are there, usually there are non and then I pick to overwrite with the new file. If the change is important I merge them manually into the new files. That’s usually better than going with the old files.
Thank you! I will give this a go next time. I can't believe I've never tried to compare them. Thank you!
@@TechnoTim I think that’s not one of the best corners of Debian but luckily it also doesn’t matter much of the time (In the beginning a ring Config could really mess up things, now most packages only evolve gradually - but I don’t have experience with proxmox. Comparing sometimes involves guesswork for the more exotic config, but then again, if you can’t recognize the reason for a difference it might not need to be kept, (fingers crossed)
I am kinda glad I was able to start with 7 as I am a complete NOOB and hearing your comments in several points of the upgrade "Scary" makes me wonder if an expert is scared....what hope do average users have in taking the right path?
The warnings are honestly typical "upgrade" warnings, you sorta get used to it from any upgrades of a distro \o/ it defo can be unnerving at first, but, distro upgrades in general are, which is honestly why backups are important so that you can roll back out if stuff goes sideways
Generally the defaults are fine, and if you modified less of the system files yourself, generally the defaults are fine, I've upgraded the issues file (still upgrading, however as we speak)
Whichever option you choose when you get those "config file has been modified" prompts, the other option is always available to you later. If you choose to keep the current (modified) version of the file, the new config file will be put right next to it with an additional "dpkg-dist" extension. If you choose to overwrite the current version, the old version is backed up with an "dpkg-old" extension. This way you always have access to both versions of the config file.
I personally tend to choose to keep the current version of my config files, unless I know I want the system defaults that come with the updated package. I didn't make those changes for nothing, after all. After an upgrade I use "diff" to compare my modified config file with the "dpkg-dist" version to see if there are any new configuration options that I want to incorporate into my config, or perhaps the new version of the package has certain defaults that are more sane than the modifications I made in the past.
done it, with ceph cluster too..
no issues so far..
Woah! Didn't even notice the update!
Thanks, thumbs up ! cluster is upgraded !
Great to hear!
Thanks a lot. I was considering to upgrade. I am not sure. ... I guess I will wait a few months.
No worries!
OK, this is the 1st Techno Tim tutorial that has bombed out miserably for me. (I don't blame you, Tim.) Did everything step by step (thank goodness I did the backup part too.) I got no error messages the whole way thru but after the upgrade I could not access the server via SSL, I could not ping any of the VMs or LXCs running under Proxmox, couldn't get the GUI to work BUT I could use the CLI from the server itself, with keyboard, monitor and mouse plugged in to it. I suspected it was a network config issue as everything was working properly within the server but I couldn't get anything to work outside the server. 3 hours later and no joy - everything seemed to be configured OK - I bit the bullet and installed the ISO from scratch and reloaded my config and VMs from the backup. Now everything is back up and running perfectly except for a weird thing where I can remote access my proxmox server via the Internet if I use MS Edge browser but not if I use Chrome. I have to say that at 1:30AM I wasn't inclined to chase down that minor problem. A real-life reinforcement of the value of good backups.
Really good video. Thanks a lot!
When you showed the pups, that's when I decided to click the like button
Thank you!
Using 7. on a test system - nvidia does not support this newest kernel yet so the install of the vgpu drivers fail :( - very bad i must say so i had to use gpu unlock teams install file to get it working again
Just upgraded, works fine
I'm going to wipe out my current v6.x environment and replace it (from scratch) with version 7. Obviously this is for home use! Nice video (as always); thanks!
great video as always! Future content suggestion - nvidia vGPU unlock and pass it to a docker container from host
Thanks! I have a video that shows how to passthrough a video card from the host to the guest and then to docker containers
Look great. I suppose it will also upgrade the proxmox-backup-manager as well?
Already upgraded. It’s nice.
awesome 👏 thank you for all you do
Thank you for watching!
i usaly wait a month or two after a new version no matter what it is. let them find some bugs and start with a more stable base
Hi nano and buddy! Really good to have cute puppies while we´re testing stuff.
Thank you!
Thanks for a great and explaining video! =)
Glad it was helpful!
great vid, did it exactly this way and it worked without any problem. thx, sub
When it comes to default file upgrades I go with "Did I change that file?" If the answer is no, it's easy => upgrade. If the answer is yes.. well you can either keep the original.. or note down the file, upgrade and edit it later (you still have those backups) .. or do it manually. In general I think it's safe to upgrade those files though.
Great tip!
Yeah... unless you changed sshd_config and 1) break your install and 2) lock yourself out of ssh
grub_default too
Thank you worked great for me!
Glad it helped!
Hi Tim, super useful as always!
One question, did you already covered Proxmox best practices or planning to do a video on those?
Thank you!
I have a video on the first 11 things I do on Proxmox, which contains some of those!
it depends on why the file was modified and what you are getting with the new config. Most often the config was modified by you to add some functionality you want to keep so you should keep your config.
Thanks for the info!
I was confused for a second, as my node is also named helios! Good name.
Good choice!
thanks tim for the video. Would you concider doing a video on converting vmdk files to qcow so i can use my vmware/virtualbox vms on proxmox? thanks in advance
Thank you!
I installed Proxmox yesterday on my new home lab and I was wondering, why alot of things are different. After watching this video, I found out that I was running one of the latest proxmox 😂
Great to hear!
Holding off for a while will upgrade at the end of the month.
It's probably been said hundreds of times but Techno Tim (to me) reminds me of Johnny Depp? Equally I've recently got into ProxMox myself, so this is helpful, thanks JD (Tim I mean!!) 😂🤫
haha!
It was updated correctly from 6 to 7 but after starting the containers that had docker they stopped working, any idea how to solve it?
Re-creating the containers with Docker version 20.10.7 on debian10 works
Today I learned that some people refer to /etc as “Etsy”. I’ve never called it anything but “et cetera” in nearly three decades of dealing with it!
Haha! I've heard it a few times, especially when saying "etcd" as "etsy dee" :)