search for: unboot

...at. I tried installing the current stable drivers from this URL: https://fedoraproject.org/wiki/Windows_Virtio_Drivers But Windows refuses and says the driver is already up-to-date. What worries me is that I want to update other win2008r2 guests as well but now fear that they will all be rendered unbootable by such an update. Regards, Dennis

...From: "Dennis Jacobfeuerborn" <dennisml at conversis.de> > To: "Discussion about the virtualization on CentOS" <centos-virt at centos.org> > Sent: Wednesday, 9 December, 2015 00:00:28 > Subject: Re: [CentOS-virt] win2008r2 update on centos 6 host made system unbootable > On 09.12.2015 00:39, NightLightHosts Admin wrote: >> On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn >> <dennisml at conversis.de> wrote: >>> Hi, >>> today we ran into a strange problem: When performing a regular Windows >>> 2008r2 update...

...at provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message --------- From: Alan McRae via CentOS <centos at centos.org> Date: Sat, Aug 1, 2020, 19:22 Subject: [CentOS] 8.2.2004 Quick recovery and fix for unbootable machines To: CentOS mailing list <centos at centos.org> This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that...

.... https://access.redhat.com/solutions/5272311 Andrea -----Original Message----- From: CentOS <centos-bounces at centos.org> On Behalf Of Alessandro Baggi Sent: Friday, July 31, 2020 11:25 AM To: centos at centos.org Subject: {EXTERNAL} Re: [CentOS] 8.2.2004 Latest yum update renders machine unbootable CAUTION:??This email originated outside of BSWH; avoid action unless you know the content is safe. Send suspicious emails as attachments to BadEmail at BSWHealth.org. 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...

...ollowing was installed: >>> "SUSE - Storage Controller - SUSE Block Driver for Windows" >>> >>> [...] >>> [...] >>> What worries me is that I want to update other win2008r2 guests as well >>> but now fear that they will all be rendered unbootable by such an update. >>> >>> Regards, >>> Dennis >>> >>> _______________________________________________ >>> CentOS-virt mailing list >>> CentOS-virt at centos.org >>> https://lists.centos.org/mailman/listinfo/centos-virt...

...a good idea, if I knew how to "downgrade...". But in any event, I had decided to rebuild from scratch, which of course failed as soon as I did an yum update. So, I'm installing 7.8.2003 with no updates until I see the "all clear -- updates will no longer make your system unbootable" message from the Centos team. In my many years of blindly updating my installations, starting from the free Redhat distributions, through Whitehat and onto Centos, this is the first disaster, and luckily, it didn't hit all my systems. Let's hope there aren't many more....

...>> 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. >>> >>> After some hours I managed to modify another bootable partition >>> (containing older software) and boot it from there. >>> >>> After that, I? found out it is a k...

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. After some hours I managed to modify another bootable partition (containing older software) and boot it from there. After that, I? found out it is a known problem. The main point of this message is to make people aware of t...

Hi, today we ran into a strange problem: When performing a regular Windows 2008r2 update apparently among other things the following was installed: "SUSE - Storage Controller - SUSE Block Driver for Windows" Previously the disk drive was using the Red Hat virtio drivers which worked just fine but after the reboot after the update I just get a blue screen indicating that Windows cannot

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim...

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. > > After some hours I managed to modify another bootable partition > (containing older software) and boot it from there. > > After that, I found out it is a known problem. > > The main point of t...

...at provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message --------- From: Alan McRae via CentOS <centos at centos.org> Date: Sat, Aug 1, 2020, 19:22 Subject: [CentOS] 8.2.2004 Quick recovery and fix for unbootable machines To: CentOS mailing list <centos at centos.org> This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that...

-----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> I agree it is a lot of shorthand because of expectations. In the endwe (the list) don't know what you have on your system or what state itis in. In order to get...

...>>>> "SUSE - Storage Controller - SUSE Block Driver for Windows" >>>> >>>> [...] >>>> [...] >>>> What worries me is that I want to update other win2008r2 guests as well >>>> but now fear that they will all be rendered unbootable by such an >>>> update. >>>> >>>> Regards, >>>> Dennis >>>> >>>> _______________________________________________ >>>> CentOS-virt mailing list >>>> CentOS-virt at centos.org >>>> https...

On Tue, Dec 8, 2015 at 5:26 PM, Dennis Jacobfeuerborn <dennisml at conversis.de> wrote: > Hi, > today we ran into a strange problem: When performing a regular Windows > 2008r2 update apparently among other things the following was installed: > "SUSE - Storage Controller - SUSE Block Driver for Windows" > > Previously the disk drive was using the Red Hat virtio

Op 09-12-15 om 14:23 schreef Dennis Jacobfeuerborn: > Yes, this is a CentOS 6 Host using regular libvirt based virtualization. The Suse driver is apparently an optional update that gets delivered using the regular Microsoft update mechanism. It's hard to believe that they didn't catch a completely broken driver during QA so my hypothesis is that maybe the new Virtio driver is

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 > > Unfortunately I can not boot into the latest > kernel-4.18.0-193.6.3.el8_2.x86_64. >

On 8/1/20 1:59 AM, Jon LaBadie wrote: > 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

On 8/1/20 11:02 AM, Lamar Owen wrote: > ... > [lowen at localhost ~]$ rpm -qa | grep ^kernel|grep 147 > kernel-devel-4.18.0-147.8.1.el8_1.x86_64 > kernel-4.18.0-147.8.1.el8_1.x86_64 > kernel-modules-4.18.0-147.8.1.el8_1.x86_64 > kernel-core-4.18.0-147.8.1.el8_1.x86_64 > [lowen at localhost ~]$ Well, I sure fat-fingered that command.... let's try it again: [lowen at

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 problem or it is random? > >Thank you I have two servers running Centos 7