From: Rod Rodolico <rodo@dailydata.net>
To: development@lists.ipfire.org
Subject: grub broken in IPFire upgrade from 85 to 87
Date: Fri, 20 Mar 2015 00:20:34 -0500 [thread overview]
Message-ID: <550BAE22.6070901@dailydata.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
I believe those are the correct versions. I upgraded the machine and now
get a grub error 15. I have no further information except the following:
It is an HVM virtual, running on an LV (should not make a difference)
To troubleshoot, I use kpartx to break it apart. When I mount the /boot
partition, I see grub.menu.old, then a grub/ directory. The config file
in the grub/ directory has none of the configuration options I expect.
I have made a copy of the image in case anyone wants me to do anything
to it. Two other routers have worked just fine with this upgrade, but
they are not on an LVM partition?
Anyone has any clues on what I should look for, let me know.
Rod
--
Rod Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
http://www.dailydata.net
next reply other threads:[~2015-03-20 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 5:20 Rod Rodolico [this message]
2015-03-20 6:22 ` Rod Rodolico
2015-03-20 7:43 ` Robertm
2015-03-22 19:21 ` Rod Rodolico
2015-04-07 11:37 ` Michael Tremer
2015-04-07 21:09 ` Rod Rodolico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=550BAE22.6070901@dailydata.net \
--to=rodo@dailydata.net \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox