What do you miss?The checksums file on the enterprise download http page has no hashes for ISOs beyond 8-beta. Please update.
We have a prototype here for a pure serial console install, but it was to late in the dev cycle for Proxmox VE 8.0 and the TUI installer is already helpful for many without that, but we will ship supporting plain serial consoles with a future release.where ist the Changelog file for install iso because need Serial Console install Iso
mm, interesting. I think the file was cached somewhere as from another device I still keep downloading the days old list!
Ok, secure boot was disabled, and the ISO boots with the Proxmox logo, but gets stuck at the same position saying "Loading initial ramdisk..."Of course I followed it as I could not invent my own procedure. Went down to systemctl reboot and then got stuck.
Yes, I had to upgrade gradually due to my ZFS configuration (about 100 disks), and my encrypted root. Didn't really want to remake all this, especially knowing that it can work according to the previous kernel upgrade.
I can try ISO, yes.
Can you also try the "Console Mode nomodeset" option from the advanced GRUB menu of the ISO?Ok, secure boot was disabled, and the ISO boots with the Proxmox logo, but gets stuck at the same position saying "Loading initial ramdisk..."
Seems it can't work in either configuration.
Ok, could get passed the ramdisk ambush!Can you also try the "Console Mode nomodeset" option from the advanced GRUB menu of the ISO?
Good to hear!Ok, could get passed the ramdisk ambush!
Proxmox VE's metrics system will do some small but relatively frequent writes, so using something that doesn't wear out quickly makes sense. In general, we recommend small enterprise SSD with power loss protection, that ensures all data including the one in the SSD caches, is written to persistent storage on power loss. As while most file systems are nowadays quite good at ensuring reliability without that, it just makes sense to have protection here at the storage level too.Question: at some point it reaches the menu to select the target harddisk. I have various types, which one is adequate for Proxmox VE Installer? I typically put OS on the least impressive small SSD. Does the same tactic apply or should I, oppositely, choose a bulletproof Optane? I just don't know what tasks it's going to perform on this disk.
Hi, If I have the Proxmox Backup Server installed and upgrade to PVE 8 - will it break or simply not recommended/tested enough?Great work proxmox team.
I have a small doubt. In the prerequisites you say "Co-installed Proxmox Backup Server should wait until a public beta or final version will be released". Does that mean that if a have a PBS as a VM on my proxmox host i must not update yet and wait for a PBS beta at least?
Likely break, as the packages are not available and there will be clashes on upgrade due to that.Hi, If I have the Proxmox Backup Server installed and upgrade to PVE 8 - will it break or simply not recommended/tested enough?
Ok, looks like I could use my OS SSDs. But how does the installer act: does it need a separate disk that it would first format or will it install onto a disk with an existing bootable system without damaging it and simply by listing it in the GRUB menu?Good to hear!
Proxmox VE's metrics system will do some small but relatively frequent writes, so using something that doesn't wear out quickly makes sense. In general, we recommend small enterprise SSD with power loss protection, that ensures all data including the one in the SSD caches, is written to persistent storage on power loss. As while most file systems are nowadays quite good at ensuring reliability without that, it just makes sense to have protection here at the storage level too.
Size wise you can get away even with 10 GB if you keep that this for Proxmox VE only, but I'd really not recommend that, as future upgrades can then get painful and one might need to watch out for log size increases and other things, rather at least 64 GB, and ideally more (e.g., there's a bunch of 480 GB enterprise SSD models which are often a nice fit and cost ~40 - 45 € excl. VAT, so relatively affordable). Having 100 GB on an Optane sounds good enough to me for both, durability and basic capacity needs.
In the installer you select the disk you want to install Proxmox VE on, it will format that fully, currently you cannot select just a partition. For ZFS and BTRFS you can also select more than one disk, all of those selected will be formatted in full and used for Proxmox VE.Ok, looks like I could use my OS SSDs. But how does the installer act: does it need a separate disk that it would first format or will it install onto a disk with an existing bootable system without damaging it and simply by listing it in the GRUB menu?
That's OK, but I think it'd be better done in a separate thread to avoid crowding the general release thread with the now rather off-topic discussion.Sorry that I ask basic questions, but trying is a lot more devastating.
Yes, thank you. I think since I have reached the Install button stage, I have no more questions to ask. I just need to restart a few times now to figure out which disks aren't preoccupied by an OS booster or RAIDZ2 configuration, and start a real installation.In the installer you select the disk you want to install Proxmox VE on, it will format that fully, currently you cannot select just a partition. For ZFS and BTRFS you can also select more than one disk, all of those selected will be formatted in full and used for Proxmox VE.
That's OK, but I think it'd be better done in a separate thread to avoid crowding the general release thread with the now rather off-topic discussion.
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
python3-cephfs : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
python3-rados : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
python3-rbd : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
python3-rgw : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
E: Unable to correct problems, you have held broken packages.
Seems like missing repos, see https://pve.proxmox.com/wiki/Package_RepositoriesCode:W: (pve-apt-hook) !! WARNING !! W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W: (pve-apt-hook) W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
PVE now no longer exists on one of my nodes.
- Followed the guide, system was originally installed off a 7.2 iso.
- No modifications to the system itself, other than installs and configs for telegraf, nut & rsyslog's output.
- Ceph was on Quincy.
- No extra kernels were installed as were listed in the install notes.
Looks like its gonna be a fun day diagnosing and probably re-installing everything from scratch.
"yay".
As a quick diagnostic step - running apt install 'proxmox-ve' yields this error -
Code:Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-cephfs : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed python3-rados : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed python3-rbd : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed python3-rgw : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed E: Unable to correct problems, you have held broken packages.
Added the repo's from the upgrade guide....Seems like missing repos, see https://pve.proxmox.com/wiki/Package_Repositories
For more help please open a new thread.