Topic: Latest updates left me with GRUB screen on reboot

[Bozely]

Yesterday I had some trouble after installing the latest updates for SME8, after running

Code: [Select]

yum update
signal-event post-upgrade; signal-event-reboot

The system would just hang at the grub screen when rebooted and would take no input.

Initially tried to boot from each of my RAID disks to no avail.

Then tried to do a repair/upgrade install but was getting an error saying that the partition was unreadable, had a similar error when running the sme rescue disk. I removed one of the HDDs and the repair/upgrade ran but was generating an error along the lines of "SDC1 was not found" (this is the USB backup drive). With one disk installed I booted the sme rescue disk and manually deleted the entry from fstab then ran a repair/upgrade install using

Code: [Select]

sme nodmraid
System came back online, shutdown, installed second HDD and restarted and added the disk to the array in the console.

Not sure if this is a bug or just our setup but thought I would share the experience! 

[chris burnat]

Yesterday I had some trouble after installing the latest updates for SME8, after running

Code: [Select]

yum update
signal-event post-upgrade; signal-event-reboot

The system would just hang at the grub screen when rebooted and would take no input.

Initially tried to boot from each of my RAID disks to no avail.

Then tried to do a repair/upgrade install but was getting an error saying that the partition was unreadable, had a similar error when running the sme rescue disk. I removed one of the HDDs and the repair/upgrade ran but was generating an error along the lines of "SDC1 was not found" (this is the USB backup drive). With one disk installed I booted the sme rescue disk and manually deleted the entry from fstab then ran a repair/upgrade install using

[snip]

Did you have the USB drive connected when doing the upgrade and reboot?

[Bozely]

Did you have the USB drive connected when doing the upgrade and reboot?

Yes USB was connected when doing the upgrade and on the initial reboot, after failing to reboot I removed the USB device but i'm guessing by that point the damage was already done.

[calisun]

Yes USB was connected when doing the upgrade and on the initial reboot, after failing to reboot I removed the USB device but i'm guessing by that point the damage was already done.

I have a server at a co-location facility with USB drive attached as a backup device. I have not done any updates since I have read this post. Has the issue been fixed? It it safe now to update with USB drive attached?

[chris burnat]

Gents my bad, I just updated an sme8 test system to latest packages with a USB drive inserted in USB port, all OK.  Box updated, rebooted and reconfigured itself, no issues. Just to make sure that the USB was OK, I then performed a backup from the console to USB (labelled removable media nowadays..), backup was successful.  So no concern AFAICT about updating your remote server Calisun.  No idea what was the problem with Bozely.
Sorry

[NTILZA]

I had a similar issue around the same time with a dev box I was using that hadn't been run/updated in a couple of months.  No USB drive was attached, but after the reboot the system froze with 'GRUB' on the screen.

I ended up booting Rescue Mode with the install CD, mounting the system partition as indicated, then ran (if I remember correctly):

Code: [Select]

grub-install /dev/md1
and then rebooted the system successfully.

Hope that helps.

[gklaus]

Thanks!! I had the exact same problem, and the "grub-install" was just the command I was looking for! (I vaguely remebered an error like this, but had forgotten the name of the command to re-write grub).

Thanks again

[MSmith]

NTILZA: Thanks so much, you fixed an issue I just had when upgrading a 7.5.1 box with SME software RAID to 8.0.