On 2020-08-03 05:56, John Pierce wrote:
Legacy BIOS has its own set of issues, like no GPT support, MBR disks
are
max 2TB.
I'm booting just fine on an old BIOS system from a pair (mdraid 1) of 3
TB GPT disks.
The MBR compatibility on GPT disks allow the old machine to boot from a
GPT disk
an
Hi,
I've got a task to have a small number of laptops netboot Linux over
WiFi. The kernel is loaded off the USB stick of cource, it's off topic
for now.
The WPA-supplicant daemon is started early by dracut off initrd. It
works. Mostly.
The problem is that upon shutdown systemd terminates a
> Hi,
>
> I've got a task to have a small number of laptops netboot Linux over
> WiFi. The kernel is loaded off the USB stick of cource, it's off topic
> for now.
>
> The WPA-supplicant daemon is started early by dracut off initrd. It
> works. Mostly.
>
> The problem is that upon shutdown systemd t
On 8/2/20 7:51 PM, Pete Biggs wrote:
>
>>
>> You just need to reinstall the kernel and it should work.
>>
>>
> Is it possible to bump the kernel version number to make sure the
> kernel gets re-installed on automated installs? Or would this break
> the compatibility with RHEL?
>
Well .. It woul
On 8/3/20 2:21 AM, Jyrki Tikka wrote:
The boot disks must have an EFI boot partition even though it's not
used in this case.
IIRC, they need a partition at the beginning of the drive to reserve
space for GRUB2. That should be a "BIOS boot partition" not an "EFI
System partition" for GRUB2.
On 2020-08-03 18:43, Gordon Messmer wrote:
On 8/3/20 2:21 AM, Jyrki Tikka wrote:
The boot disks must have an EFI boot partition even though it's not
used in this case.
IIRC, they need a partition at the beginning of the drive to reserve
space for GRUB2. That should be a "BIOS boot partition"
After trying several paths, some suggested on this list, here's my results.
1) Fixing a unbootable system wasn't practical in my
case. Fortunately, all my systems can be rebuilt from scratch.
2) When I was lucky enough to catch an updated system before reboot,
backing out the defective updat
Le 03/08/2020 à 19:24, david a écrit :
> After trying several paths, some suggested on this list, here's my results.
Hi,
Just back from a hiking trip. One of my clients sent me a message that his
CentOS server refuses to boot. So tomorrow I have to drive there to figure out
what's going on. I gue
Hi all,
I had the same problem with my UEFI bios machine and I fixed it so for
Centos 7:
1) Boot from an rescue linux usb
2) When the rescue system is running:
2.1) #chroot /mnt/sysimage
3) Config network:
3.1) # ip addr add X.X.X.X/X dev X
3.2) # ip route add default via X.X.
> Am 04.08.2020 um 08:31 schrieb lpeci :
>
> Hi all,
>
> I had the same problem with my UEFI bios machine and I fixed it so for Centos
> 7:
>
> 1) Boot from an rescue linux usb
>
> 2) When the rescue system is running:
>
> 2.1) #chroot /mnt/sysimage
>
> 3) Config network:
>
> 3.1
10 matches
Mail list logo
