Yesterday I did a soup update on a standalone system. Upon reboot I was presented with a grub shell, with a "grub >" prompt.
I booted the livecd, bind mounted /dev /proc /sys, and then mounted the root filesystem and performed a chroot. Running grub-install /dev/sda2 resulted in a cryptic error (it's a work system and I ran out of time on shift before I had to leave for the weekend), but in short, the system is inoperable after this update.
In the very short time I had to resolve the issue I tried a number of commands in the grub shell with no joy. I am not a novice at this sort of thing so I was pretty surprised at what happened.
How can I get grub properly installed, get the system running, and more importantly, is there a known issue in soup updates performed on Friday (or so)?
--
You received this message because you are subscribed to the Google Groups "security-onion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to security-onio...@googlegroups.com.
To post to this group, send email to securit...@googlegroups.com.
Visit this group at http://groups.google.com/group/security-onion.
For more options, visit https://groups.google.com/groups/opt_out.
--
Follow Security Onion on Twitter!
https://twitter.com/securityonion
---
You received this message because you are subscribed to the Google Groups "security-onion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to security-onio...@googlegroups.com.
To post to this group, send email to securit...@googlegroups.com.
Visit this group at https://groups.google.com/group/security-onion.
For more options, visit https://groups.google.com/d/optout.