Recent content by fletch

UPDATE : Clonezilla worked - mostly. I kept the backup with errors. I bought a new drive for the node and attempted a restore. It worked though I did have an id mismatch with LVM -thin. Not sure if this was due to the errors I got from Clonezilla or because I let it expand the drive (went...

Thank you! I had this same issue when backing up my node with clonezilla and restoring to a larger drive. The error did not seem to cause any problems but it's gone now after following steps 1-3. Thanks again!

That is exactly what I mean - I can't trust the backup. What it said was it could not check some of the partitions and then the check aborted. If I had a spare drive, I could see if it would actually restore but right now I don't. I sure wish proxmox had a way to backup the host.

I tried with the latest version tonight and still gives me errors. I have mine set to check the image to be sure it can be restored and that is where it fails every time. Maybe it can really be restored but I don't want to take any chances so I am going to assume that I am upgrading to 8 with...

Have you ever been successful with clonezilla? It would always fail for me and could not complete. Prox is the only thing I have seen it fail on to date.

If you are talking about the 10g switch, yes I had to pull power and reboot to get back web control. I created a network conflict and was not surprised when things went wrong. I can't really do any more until the nic for the nas comes in...right now they are saying Friday. Then hopefully I can...

For anyone else with this issue- these are the additional steps I had to do to get this working. My way was not the correct way but it got me going until I can get help setting up a vlan. Like the tips from the other posters , you have make sure thunderbolt is set to legacy in bios or Proxmox...

I think I am having the same issue with the solo10g adapter. Didn't do ANYTHING until I made the Legacy change in the bios (thank you for that tip) and now another nic shows up under the proxmox node network area. However it won't connect to my switch on ether the 10g side or even the 1g side...

Found someone with similar problem. He gave me his repository configs and they matched mine. His last idea is what did the trick: First do a apt update and then apt upgrade And then finally do the apt dist-upgrade. This is what finally worked for me. Hope this helps someone else!

The file name in the wiki is wrong. No such thing as pve-install-repo.list but rather pve-no-subscription.list. I changed over to this but when I run apt dist-upgrade I get nothing as in nothing to update. So it must still be looking at 6.

I need help doing this another way as the instructions(below) in the wiki don't work and give me a file not found error. I need another way to switch over to the 7 repsositories. Thanks. For the no-subscription repository, see Package Repositories. Rather than commenting out/removing the PVE...

Sure- I got the clue from the other poster but the short story is the config you access from the gui will over ride what ever you set in the actual UEFI. Go to your vm>options>boot order and set it there and that should fix it. Good luck...

Thanks but I am good now. The reason I went from client>standalone>server is because I had some good fortune over the holidays and ended up with several new ups's so my proxmox server now has it's own ups. I don't think they really need it, but I also have my main vm's setup as clients as well...

It was on stack exchange. The guy was saying the client was buggy and would fail without some kind of password even if the system did not require it. I have redone my system 2 times since last week . First as a client , then as standalone and as of today as a server. If you wish, I can give you...

They were right it was that &&*(* client needing a fake password. Now I just need to figure out how to start upsmon automatically on prox bootup but it's working at least manually now.