Recent content by Riesling.Dry

o.k problem solved! :D iLO was reset by shutting down the server and removing power (unplugging it) for a couple of minutes. As soon it was plugged back in, iLO was accessible again, server booted up fine and everything is back to normal.

In this case the iLO100 has a dedicated Ethernet Port/Network Connection on a sep. Board w. a dedicated IP. Same setup as before Kernel-Update, i.e. the setup that worked before :°) Will report back as soon as we have news.

o.k. - we reproduced the setup locally w. identical server hardware incl. identical iLO100: phresh installed PVE 7.x apt install ipmitool verify IPMI(iLO) reboot upgrade to PVE 8 acc. https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 reboot into Kernel 6.2.16-5 IMPITOOL works fine...

It "should" yes, but as it uses drivers from the host it still might be affected... It is quite unlikely, that the kernel-update did NOT cause the outage, yet it is not positively confirmed. That's why I started this thread. Are there any other users out there w. a hp iLO100 and the PVE...

Thank you for you responses. iLO has its own IP and own/dedicated LAN connection. RESET via ipmitool mc reset cold from pve host does not work as outlined above. PVE is fine, only the iLO is "down". I also thought of trying the old Kernel, but as I do not have proper remote access neither...

Hi all, about three weeks ago, we completely reinstalled the server (HP Proliant DL160 G6 w. HP iLO100) and installed Proxmox 8 with pve-kernel-6.2 - everything worked perfectly finer. A few days ago, the kernel was updated from version 6.2.16-4 to version 6.2.16-5 (and subsequently to 6.2.16-6...

Have you tried the solution proposed by @LnxBil? wget -O /usr/share/misc/enterprise-numbers.txt https://jff.email/cgit/ipmitool.git/plain/debian/enterprise-numbers.txt?h=debian/1.8.19-5

Thank you LnxBil, thing is, I do not have physical access to the server, and with no iLO/IPMI I'd need to travel to the hosting facility to do that. Seems I will have to, if no other proposal/solution comes up :(

yes :( iLO/IPMI apparently gone due to some recent kernel updates? It is possible, that the kernel modules got kicked out by the recent update? Preparing to unpack .../pve-kernel-6.2.16-4-pve_6.2.16-5_amd64.deb ... Unpacking pve-kernel-6.2.16-4-pve (6.2.16-5) over (6.2.16-4) ... Setting up...

404 - the link is now http://ftp.debian.org/debian/pool/main/i/ipmitool/ipmitool_1.8.19-6_amd64.deb :) but that didn't fix it for me: o.k., but what does this do, how is that enterprise-numbers.txt file used/applied? Cheers, ~R.

Just wanted to say, that meanwhile I upgraded 3 more servers and everything went perfectly fine without ANY issue! Again: MANY thanks to you, the proxmox team! Keep up your BRILLIANT work! :)

Thank you Stoiko! yes, the update got interrupted at some point (broken pipe, dunno why/how - I guessed due to the network that went lost during/due to update?) apt sources are/were full bookworm (edited manually). Thanks for the hint to do an "apt update" again though! It gave an error and...

o.k. so we tried to upgrade a latest PVE 7 to 8 with bullseye to bookworm. Box is a hpe proliant, Xeon, 16GB RAM, 4x 4TB HD min. 50% free, was last set up a couple of month ago, worked fine, all updates installed. Duly followed https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 pve7to8 --full...

o.k. sometimes there is plain simple solution, but you have to think of the simple way... ;) Moved the 3 good disks "physically" to the left and added the new on in the last/right/4th slot. Box boots and I can go on adding the new disk to zpool :)

Hi, so (again) a disk went bad ("faulted") in a ZFS pool. Server is a hp Proliant Microserver Gen 8 w. 4 x 4TB - the bad/new disk was/is the 1st/left one in the row, no hardware-RAID configured, not hot-plug. I removed the faulted HD ("zpool offline"). Systems boots fine w. 3 HDs. After...