CL5 (PXE-Client)

[dcj9]

https://bugzilla.redhat.com/show_bug.cgi?id=2104398

• This is the exact error. However it is on the PXE client. Im not sure how to apply this to a PXE boot

https://www.digitalocean.com/community/tutorials/how-to-partition-and-format-storage-devices-in-linux

Bios version = A01 Service TAG = C3LFX12

• _https://i.dell.com/sites/csdocuments/Business_smb_merchandizing_Documents/en/us/Dell-OptiPlex-3030-AIO-Technical-Spec-Sheet-New.pdf_
• https://www.dell.com/support/home/en-us/product-support/servicetag/0-c084bGJESmhqd1pxT3d4YVd5Rkladz090/overview

[dcj9]

Miss understood the PXE booting parameters. The boot process never hits the hard drive on the PC. It goes the UEFI Network Stack which talks to the server Located on chile, but that is a seperate issue

[dcj9]

This is just a reminder to myself. Remember when you reformated the drive on CL5 in a really suspect way and didn't do anything with the fstab or whatever because you said "I think it does that when the OS installed " yeah it doesnt. Cause it has no idea what its writing on. I think. I gotta look at how to make the file system mount or whatever I didnt do after I reformated that drive.

[dcj9]

Gotta write down the exact error message in the morning.

• https://www.fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria#Final_Release_Requirements
• https://docs.fedoraproject.org/en-US/workstation-docs/#_system_requirements

[dcj9]

liveruser@localhost-live:~$ sudo part /dev/sda mklabel gpt

Error: Partition(s) on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

Okay, Rebooted. Going to try running the same command.

Lemme see if STK is in his office real fast actually, Going now. That worked.

Information: You may need to update /etc/fstab.

Okay, Negative. Thats fine. Found out it was the kernel anyway. Question for myself.

Kernels relate to ... processors? processors have different architectures and bit range? CL5 may be able to handle a 64 bit system, but that kernel may not relate to... the processor? Is the processor what sets the bit value of the system? its not the ram. Its gotta be.

[dcj9]

Incorrect kernel. thats why, its not even getting to the hard drive aspect. It wont load the initrd or what not from the vimluz package on chile because it cant.

• What the hell does this thing have for a processor Dunc?

[dcj9]

These are the URLs which need to be "doctored" to install the 39 version

• https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/os/
• https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/os/

Getting the kernel and initrd

• https://download.fedoraproject.org/pub/fedora/linux/releases/36/Server/x86_64/os/images/pxeboot/vmlinuz
• https://download.fedoraproject.org/pub/fedora/linux/releases/39/Server/x86_64/os/images/pxeboot/initrd.img

I am pretty sure I did this accurately. Resetting the interface on the PXE server on chile and taking chile off the CS network entirely

[dcj9]

dracut-initqueue[1184]: Warning: can't find installer main image path in .treeinfo