Hi All. Thanks very much to everyone for making and supporting proxmox. I'm still pretty new to proxmox and I'm very impressed with it, but I've encountered
three problems in
my first two weeks that make me begin to wonder if this is really the right solution for me.
The
first problem (which occurred last week) was an apparent inability to change the node's ip address (see previous posts to this forum on that topic). I haven't figured out how to solve that, but it's moot for me now because the node is back in its original network.
The
second problem (occurred this past weekend) was that the node could not perform automatic updates (I saw error messages in the web interface indicating this and solved it by changing the /etc/apt/sources.list.d/ file to point to the non-enterprise non-subscription sources).
But fixing the
second problem seems to have created the
third problem I've encountered (occurred today) which is the exact same problem as the original poster (euant) in this thread had a month ago. Their screenshot looks identical to mine except that (to be expected, I know) my volume ID or disk ID is different than theirs.
My hardware is an HP ProLiant ML10 v2 with 5 physical disks (each 4TB total space as advertised) connected to the HP Smart Array B120i RAID controller set to AHCI mode in the BIOS. The proxmox 5.1 install image worked beautifully from a USB stick and seems to have created a RAID array and logical volumes with ZFS all very much to my satisfaction and with minimal time and effort during installation. The install was truly a quick, simple, and problem-free process. But with the first upgrade, I can now no longer boot from either the hard drive or the install image (rescue mode) on the USB stick.
I managed to successfully reboot this server at least 8 times between original installation and encountering this third problem, but nightly automatic updates (apt-get update) were failing before because the sources were pointing only to the enterprise update archives, and I have not yet subscribed. So as soon as I fixed that problem (apt-get update failing), the node apparently updated itself, and in the process, broke itself so it no longer boots.
I'd like to try booting from lankaster's boot stick that euant used successfully, but I don't see an image to write to my USB stick?
And of course ideally, I'd like to again be able to boot from the hard drives.
Since there seems to be several people experiencing this same problem, is there anything I can do to help find the root cause so that someone can fix it?
Thank you fabian for asking euant for some details. For me, the output of "set" in the grub rescue shell is identical to that of euant:
Code:
> set
cmdpath=(hd0)
prefix=(hd0)/ROOT/pve-1@/boot/grub
root=hd0
And the output of "ls" in the grub rescue shell is also similar, but I have 5 identical physical disks, so:
Code:
> ls
(hdX) (hdX,gpt9) (hdX,gpt2) (hdX,gpt1)...
where X=0,1,2,3,4
Not being able to boot into the node, I don't know how to give you my ZFS pool layout.
Thanks for any suggestions on how to resolve, and I'll be happy to try anything else to help troubleshoot the root cause.
-Kevin
