Search results

Are you certain it's just not something running inside the container that's the problem?

Why are you even playing on Proxmox ? Makes no sense to me.

There is your problem. You can disable the nouveau driver (open source nvidia driver) You will get a lower resolution, but it will work, trust me: nano /etc/modprobe.d/blacklist-nouveau.conf - paste this this: blacklist nouveau blacklist lbm-nouveau options nouveau modeset=0 alias...

You are not using an nvidia card right? I had to disable the nouveau driver to make this go away for me. Probably not the same causing it for you. Just though I would ask.

Can you link me the bug report?

Yes, I have this problem as well :) I do have a workaround, if you can't wait: https://forum.proxmox.com/threads/cant-install-grub-on-dev-nvme0n1.35602/#post-174711

Okay, so because ZFS is not supported on Debian (on root partition) and the scripts I found did not include support for NVMe, i managed to work around this: - Install Proxmox 5.0 on SATA-SSD with same size (I used a Samsung 850 evo for SATA, and a 960 Evo for NVMe) - sgdisk...

I will try that when I get home today :) Will report back if that works.

I had this problem as well. After removing my Nvidia card from the system it stopped (it's been stable for 24 hours now) - Seems nouveau drivers were the problem.

Yes, updated as soon as I got it. Updates to 2.50: http://www.asrock.com/MB/AMD/AB350M%20Pro4/index.asp#BIOS

You should probably use: systemctl edit -full pvesr.timer This will move a local file to /etc/ instead of /lib/ which will be overwritten on next update :) Thanks for the advice though, this log was driving me crazy.

Hey First of, thank you for 5.0! it's been great. So I have a problem with installing Proxmox 5.0 on my NVMe drive (Samsung Evo 960). When installing from Proxmox install-USB, it will stay at 0% forever. I tried both ext4 + ZFS, same result. I don't know if this worked in 4.4, but this is a...

So, how is ryzen working now? I'm ready to pull the trigger and buy, but I don't want to buy if I should wait for 5.1 and newer kernel.

I have tried this a few times (on 4.4) usually rebooting the computer (not the proxmox node) helps and all is back.

I don't think many of us are using 3.4 anymore, so it will be harder to get support for that :(

What would happen if I used parted to shrink the sda2 + sdb2 partitions on my rpool? Would that even be possible, and if yes, what steps would I take if its on my boot pool (I can't really export the pool?)

I would like something like this as well :) It would be awesome to partition the disks used for ZFS boot-drives. I'm currently using something like 20GB/250 so it would be good for longer lifespan.

Are you sure you don't have watchdog enabled in BIOS?

Can't wait for final 5.0 :) Thank you for your hard work. I'm trying my best to push Proxmox at work ;)

Thank you for your reply. I don't think (hope) so. They are brand new and original LSI cables. These are the ones: "CBL-SFF8087OCF-10M 1 unit of 1m Multi-lane Internal (SFF-8087) Serial ATA breakout cable, forward" - anyway they have worked just fine for several weeks, this only happened once...