George, you are the best. You constantly help me out on these forms. If I could take you out for a working lunch I would.
I switched it over to ipxe.efi and it worked.
Hello, I am running into the same problem with some new Lenovo Thinkpad machines. I can get it to Start PXE over IPv4, get an IP address, it loads with NBP filename undionly.kpxe, says the NBP file downloaded successfully and then flips back to the standard boot menu.
When I change the DHCP bootfile name to boot\x64\wdsmgfw.efi I get an IP address, but it says the PXE-E23: Client received TFTP error from the server. I have never used this one but saw it online so thought I would try it.
When you refer to what kid of DHCP and version, what are you referring to? We use a Windows Server 2016 for our DHCP services.
Thanks for the help.
You are the best! We are good to go! Thank you for all your help and for sticking it out with me. I hope this thread helps someone else later on down the line. You’ve also helped me increase my Linux command line knowledge a bunch.
I used the command grow part and now it is showing sda2 as having 800G.
df -h is still showing sda2 as having 500G. Should I try running through the initial commands you gave me and those listed in the YouTube video again to expand it?
Hey George. I’m back working on this today. I followed the instructions on the link you sent while referencing the YouTube video I found but ran into a problem with it only recreating the disk using the size 500G instead of 800G. I found out after doing some more searching that I needed to run sudo lshw -c disk for Ubuntu to rescan the file systems to recognize the 800G drive from vmWare. So I got this fixed and Ubuntu now sees the 800G drive.
But I am running into the problem of the following GPT PMBR size mismatch coming up in red (see below) while going into the sudo fdisk /dev/sda.
I also had the issue of it not resizing to 800G but staying at 500G. I reviewed the YouTube video some more and they talked about the sectors needing to match. For Disk /dev/sda: 800GiB is showing 1677721600 sectors. When my disk is being re-created it is wanting to stay at the original sector numbers that were set for 500G. I tried to change the sector number but continued to get the message that the value was out of range.
I also continued through the commands to finish, but when trying to save (write) it comes back to the GPT PMBR size mismatch and that fdisk: failed to write disklabel: invalid argument.
@george1421 Thanks. I have the backup ready to run tonight and I’ll see about working on it tomorrow or Monday when I’m back in the office. I also used your article and looked up the commands on YouTube. This video was helpful for me to see how each command laid out as it was typed step by step.
My first line would be sudu fdisk /dev/sda2 correct?
Here is the video if you or anyone else is interested.
Is there a way to add a GUI to an already established Ubuntu server? Asking for a friend. (j/k It’s for me. I do feel like I’ve gotten a lot of Linux command line practice in the last two days trying to work on this.)
@george1421 No problem. I have increased it from 500GB to 800GB. We aren’t needing this at the moment. I’ll wait for you if you have the time later today or tomorrow (even later this week). You have been amazing and you have no idea how much I appreciate your help. I have some other things to work on.
@george1421 Sorry I got excited and restarted it. It is up again. Here is the output of lsblk after I restarted.
@george1421 Looking better! Let me see if it will start now.
@george1421 Done. I do not want the Linux power.