Search results

It wouldn't, but by using the fallback boot loader (efi/boot/BOOTx64.EFI), the bios will automatically make a bootable entry in bios, and you can ignore the proxmox variable and select whatever disk you want to boot from the list of automatically created fallback boot loaders.

perhaps do a grub-install --removable on both and control the boot order in bios.

bet one of the disks has been a member of an exported pool, use -f to force.

Had this issue with a J4105 Gemini Lake part. Perhaps it's the same as the X55's J5005 Gemini Lake part? http://rob.com/porteus/ProxmoxH2.iso is a 642Meg Proxmox VE 5.3 install image that works on the Gemini Lake and Coffee Lake systems I own in uEFI mode. It boots and runs normally, but...

Ran into this issue with a Gemini Lake (j4105) part but this time it didn't have a legacy boot option to fall back on. The grub2 in Ubuntu 18.10 (Cosmic Cuttlefish) 2.02dfsg1-5ubuntu8 worked so this might be a recent intel graphics issue with grub2. http://rob.com/porteus/ProxmoxH2.iso is a...

Sometimes to get the ZFS root file system the way we want requires an install in legacy mode and conversion to uEFI mode, perhaps because of: Installer creates an undesirable partition table Installer can't find cdrom image after grub2 load hardware requires uEFI bios to initialize (emmc)...

I can offer my working config: in /etc/pve/status.cfg influxdb: server 149.59.225.132 port 8089 in /etc/influxdb/influxdb.conf [[udp]] enabled = true database = "proxmox"

I also had this issue, and the fix for the Coffee Lake NUC is to turn on the Legacy Boot option in BIOS.

apt-get purge $( dpkg --list | grep -P -o "pve-kernel-\d\S+" | grep -v $(uname -r | grep -P -o ".+\d") )

> This next step re-formats the Solaris reserved partition for FAT as required by an EFS parition Thanks for your notes, but why would you want to overwrite two vdevs? http://www.giis.co.in/Zfs_ondiskformat.pdf Yea I know there are two more at the front, but one could use the part in L1 that's...

would ssh root@12345678HV1 qm stop 2254 be an acceptable workaround?

Does the emergency boot from the install cd bring it up normaly? Does pointing the legacy boot to the other disk make a difference? (grub-install for fun too) Does turning on uEFI along with Legacy boot help your MB bios find the Legacy boot partition?

Does the emergency boot from the install cd bring it up normaly? Does pointing the legacy boot to one of the other three disks make a difference? (grub-install on all 4 again for fun too) Does turning on uEFI along with Legacy boot help your MB bios find the Legacy boot partition?

on the node with the high IO wait, type: `dmesg | grep libceph` I've seen stack traces like you shared, perhaps the root error is: https://forum.proxmox.com/threads/ceph-snapshot-lxc-backup-hanging.39689/

hmm, with only the dump snapshot it still hangs. dmesg is similar: [147928.992344] libceph: get_reply osd3 tid 638001 data 933888 > preallocated 131072, skipping USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 11148 0.0 0.0 21984 1240 ? D 20:47...

hmm, had a hang with a "stopped" backup, so its not a /dev/rbd1 mounting issue. I'm going to stop rotating snapshots and remove them all and move back to a snapshot mode for backup. [ 5621.020944] libceph: get_reply osd2 tid 333933 data 933888 > preallocated 131072, skipping

Ah, it seems to be related to RBD_MAX_SNAP_COUNT as I rotate between 14 snapshots in this lxc. This is fewer than the 510 snapshots per image as stated below, but likely related. http://tracker.ceph.com/issues/16630#note-13

I've had a number of stuck backup jobs of lxc containers using a ceph snapshot as a source. Have you noticed this too? Its been happening for awhile: While it looks like a disk errors, and this home cluster has a bunch of old junk computers it, the failures follow OSDs where the backup is...

another reference for google: https://forum.proxmox.com/threads/lxc-aa_profile-is-deprecated-and-was-renamed-to-lxc-apparmor-profile.38505/#post-191228

I know it sounds funny, but turn on both legacy and uEFI boot options in your BIOS. Proxmox will boot via the legacy partition, but the devices will be enumerated correctly. (the copy of /etc/zfs/zpool.cache in /boot/initrd.img* isn't using /dev/disk/by-id/* so it can't find the pool as the...