OK, looks like I got it. I had a line in fstab to mount a folder that was failing. I removed it and reboot worked as expected.
I probably added it when playing with Jellyfin and forgot to remove.
Apr 15 17:24:37 proxmox networking[1465]: error: vmbr0 : eno1 : (eno1: up cmd...
Looks like this is happening at each boot -
Apr 15 15:59:28 proxmox kernel: [ 1725.371481] vmbr0: port 1(eno1) entered blocking state
Apr 15 15:59:28 proxmox kernel: [ 1725.371484] vmbr0: port 1(eno1) entered disabled state
Apr 15 15:59:28 proxmox kernel: [ 1725.371672] device eno1 entered...
Sorry sorry, that was my bad, left that there while I was trying something. I saw the 'inet manual' and forgot about the 'inet dhcp'.
So That did fix my IP issue, but networking is still failing to start upon reboot.
systemctl restart networking doesn't seem to work, but the 'ip link set eno1...
So I couldn't connect to my host today. Got a monitor hooked up and with some research found the interface was not up. I have it hard coded, but when I manually brought it up using 'ip link set eno1 up', it got a DHCP address it seems. I also had to use 'ifup vmbr0'
If I reboot, I have to...
Currently running 1.9 and only have 1 machine I really need to save before upgrading to 3. Trying to export it to an external USB drive, but I cant seem to mount the drive. Proxmox sees it when I connect it, and shows it as sdg1, but when I try to define it with <pvcreate /dev/sdg1> it tells me...
Was trying to add a samba share in my fstab and didnt realize the editor didnt like the numpad and apparently I deleted and changed some characters in it.
Can anyone tell me how it should look?
Here is what I have now:
/dev/pve/root / ext3 errors=remount-ro 0 1/dev/pve/data /var/lib/vz ext3...
Went to upload another ISO today and the page never loads, no error, it just spins and keeps looking.
I can SSH into the ProxMox box, but I dont know enough about linux to look for the actual location of the file to see if it is there or not.
It seems like all the other pages on the web...
What happens when you dont read all of the instructions? You get home and realize you should have brought TWO clonezilla disks for this procedure... luckily my server has a dvd drive so I had a disk for that.
Anyway, the only thing that didnt go along with the instructions was the fdisk part, I...
I thought so too! ;)
Im going to load up a rescue CD ISO on there and boot to that to see if it sees any of the machine data on that disk, if that doesnt reveal anything, I will just try the clonezilla method tonight when I get home.
Thanks so much for your quick replies.
I dont see where it is possible to change that once you have set it up, but it does appear to be looking at the right place.
The vm-105-disk-1.raw is the file i created
If I ssh the whole partition, how could it miss anything?
I will pick up some CD's on the way home and try that way.
The only other thing I see that is different than the other XP machine I just created on Proxmox as a fresh machine, is the file size seems to be actual data and not the partition...
That was originally what I was going to do, but I only had clonezilla on USB and DVD and this machine is so old it only has a CD drive, so I thought I would use the SSH method as it seemed fairly simple as well.
I followed the SSH instructions from this page and it seemed to go just fine. If I ssh into the promox machine, I can see the raw file and it is about the same size as the physical partition I copied, (40GB)
I originally created a 45GB drive on proxmox to make sure I had enough room.
When I did...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.