similar to: 8.2.2004 Quick recovery and fix for unbootable machines

Displaying 20 results from an estimated 4000 matches similar to: "8.2.2004 Quick recovery and fix for unbootable machines"

2020 Aug 02
1
Fwd: 8.2.2004 Quick recovery and fix for unbootable machines with rescue disk
Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message
2020 Aug 02
0
Fwd: 8.2.2004 Quick recovery and fix for unbootable machines
Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message
2020 Aug 02
2
8.2.2004 Latest yum update renders machine unbootable
><snip> > > I'll post here again once we have pushed the EL8 and CentOS Stream updates. > >OK .. I have also now pushed the CentOS Linux 8 update .. you should see >an update to SHIM .. the new versions are: > >PowerTools/x86_64/os/Packages/shim-unsigned-x64-15-8.el8.x86_64.rpm >BaseOS/x86_64/os/Packages/shim-ia32-15-15.el8_2.x86_64.rpm
2020 Aug 02
2
8.2.2004 Latest yum update renders machine unbootable
At 06:10 AM 8/2/2020, you wrote: >On 8/2/20 8:04 AM, david wrote: > > > >> <snip> > > > > > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >> updates. > >> > >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see > >> an update to SHIM .. the new
2020 Aug 02
5
8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 2:04 AM, Alessandro Baggi wrote: > > Il 01/08/20 22:03, Greg Bailey ha scritto: >> On 8/1/20 6:56 AM, david wrote: >>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>> Hi Johnny, >>>> thank you very much for clarification. >>>> >>>> You said that in the centos infrastructure only one server got the >>>>
2020 Aug 02
3
8.2.2004 Latest yum update renders machine unbootable
At 06:37 AM 8/2/2020, Johnny Hughes wrote: >On 8/2/20 8:30 AM, david wrote: > > At 06:10 AM 8/2/2020, you wrote: > >> On 8/2/20 8:04 AM, david wrote: > >> > > >> >> <snip> > >> > > >> > > >> > > >> >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >>
2020 Aug 01
4
8.2.2004 Latest yum update renders machine unbootable
On 8/1/20 6:56 AM, david wrote: > At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >> Hi Johnny, >> thank you very much for clarification. >> >> You said that in the centos infrastructure only one server got the >> problem. >> What are the conditions that permit the breakage? There is a particular >> configuration (hw/sw) case that match always the
2020 Aug 02
3
8.2.2004 Latest yum update renders machine unbootable
> Am 02.08.2020 um 14:34 schrieb Johnny Hughes <johnny at centos.org>: > > ?On 8/2/20 6:59 AM, Johnny Hughes wrote: >>> On 8/2/20 2:04 AM, Alessandro Baggi wrote: >>> >>> Il 01/08/20 22:03, Greg Bailey ha scritto: >>>> On 8/1/20 6:56 AM, david wrote: >>>>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>>>>
2020 Aug 17
2
C8 - Register with Red Hat
On Mon, 17 Aug 2020 16:37:20 -0500 Gregory P. Ennis wrote: > "This system is not registered to Red Hat Subscription Management. You can use > subscription-manager to register." It sounds like you have something installed that doesn't need to be or shouldn't be installed. Under what circumstances does that message appear? I haven't seen it on any of my C8 systems,
2015 Jun 26
2
/boot on a separate partition?
On Fri, Jun 26, 2015 at 9:58 AM, Jonathan Billings <billings at negate.org> wrote: > On Thu, Jun 25, 2015 at 01:27:47PM -0600, Chris Murphy wrote: >> It's bad design. First, it's a nested mount: file system A on /, and >> file system B on /boot, and file system C on /boot/efi. Therefore the >> mount process must make sure they're mounted in that order, or
2020 Aug 02
1
8.2.2004 Latest yum update renders machine unbootable
-----Original Message----- From: Stephen John Smoogen <smooge at gmail.com> Reply-To: CentOS mailing list <centos at centos.org> To: CentOS mailing list <centos at centos.org> Subject: Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable Date: Sun, 2 Aug 2020 10:57:49 -0400 On Sun, 2 Aug 2020 at 10:20, david <david at daku.org> wrote: > > <snip>
2020 Jul 29
3
After update to 8 (2004) ... system is unbootable - UEFI Secure boot
Am 16.06.20 um 22:04 schrieb Fabian Arrotin: > On 16/06/2020 15:06, Leon Fauster via CentOS wrote: >> Hi all, >> >> I updated a Dell XPS laptop from CentOS 8.1 (1911) to 8.2 (2004). >> >> Installed kernels are >> kernel-4.18.0-147.5.1.el8_1.x86_64 >> kernel-4.18.0-147.8.1.el8_1.x86_64 >> kernel-4.18.0-193.6.3.el8_2.x86_64 >> >>
2020 Aug 01
2
8.2.2004 Latest yum update renders machine unbootable
On Fri, Jul 31, 2020 at 10:20:28PM -0500, Johnny Hughes wrote: ... > > The issue seems to be with the shim package (not the grub or kernel > packages) and we are currently working with Red Hat on a fix. This > issue happened in many Linux OSes and even Windows, not just RHEL and > CentOS. > > We will push a fix as soon as one is available. > > I would hold off on
2020 Aug 02
0
8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 6:59 AM, Johnny Hughes wrote: > On 8/2/20 2:04 AM, Alessandro Baggi wrote: >> >> Il 01/08/20 22:03, Greg Bailey ha scritto: >>> On 8/1/20 6:56 AM, david wrote: >>>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>>> Hi Johnny, >>>>> thank you very much for clarification. >>>>> >>>>> You said
2020 Aug 02
0
8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:04 AM, david wrote: > >> <snip> > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream >> updates. >> >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see >> an update to SHIM .. the new versions are: >> >>
2020 Aug 02
0
8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:30 AM, david wrote: > At 06:10 AM 8/2/2020, you wrote: >> On 8/2/20 8:04 AM, david wrote: >> > >> >> <snip> >> > >> > >> > >> >> > I'll post here again once we have pushed the EL8 and CentOS Stream >> >> updates. >> >> >> >> OK .. I have also now pushed the CentOS Linux
2020 Aug 02
0
8.2.2004 Latest yum update renders machine unbootable
On 8/2/20 8:47 AM, david wrote: > At 06:37 AM 8/2/2020, Johnny Hughes wrote: >> On 8/2/20 8:30 AM, david wrote: >> > At 06:10 AM 8/2/2020, you wrote: >> >> On 8/2/20 8:04 AM, david wrote: >> >> > >> >> >> <snip> >> >> > >> >> > >> >> > >> >> >> > I'll post here
2020 Jan 16
2
CentOS 8: several packages have unresolved dependencies after "dnf update all "
All, While updating my package using dnf update all I allow dnf to clean some package with unresolved dependencies. I would like to reinstall some of them but got an error message "but none of the providers can be installed" during the install process as dnf is trying to install the dependencies. . This happens for some critical package like boost-openmpi-devel (see below for
2020 Jul 31
6
8.2.2004 Latest yum update renders machine unbootable
Il 31/07/20 13:08, ja ha scritto: > On Fri, 2020-07-31 at 22:35 +1200, Alan McRae via CentOS wrote: >> I am running an Intel x64 machine using UEFI to boot an SSD. >> >> Installing the latest yum update which includes grub2 and kernel >> 4.18.0-193.14.2.el8_2.x86_64 renders the machine unbootable, blank >> screen where grub should be, no error messages, just hangs.
2020 Jan 16
3
CentOS 8: several packages have unresolved dependencies after "dnf update all "
I am doing a dnf install package_without_version for instance for g++: [piot at paris opal]$ sudo dnf install gcc-c++ Last metadata expiration check: 0:01:06 ago on Thu 16 Jan 2020 06:45:59 AM CST. Error: Problem: package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but