Bug#467501: submitter address changed (Stealing this bug ;))
On Mon, Jul 14, 2008 at 04:04:07PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 01:16:58PM +0100, Jonathan McDowell wrote: On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell wrote: It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. Which version did you use for that test? grub-pc 1.96-20080704-2 (installed from unstable/amd64 this morning). Which device did you install grub to? Um. I don't think I got to specify. I just did aptitude install grub-pc and then chose the chainloading option from the existing grub1 install. I didn't get as far as actually replacing the grub1 install as chainloading didn't work. J. -- jid: [EMAIL PROTECTED] Most people are descended from apes. Redheads are descended from cats. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Tue, Jul 15, 2008 at 10:29:40AM +0100, Jonathan McDowell wrote: On Mon, Jul 14, 2008 at 04:04:07PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 01:16:58PM +0100, Jonathan McDowell wrote: On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell wrote: It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. Which version did you use for that test? grub-pc 1.96-20080704-2 (installed from unstable/amd64 this morning). Which device did you install grub to? Um. I don't think I got to specify. I just did aptitude install grub-pc and then chose the chainloading option from the existing grub1 install. I didn't get as far as actually replacing the grub1 install as chainloading didn't work. Then how come you were using 1.96-20080704-2 ? Did you manualy propagate the files to /boot without calling grub-install? If not, you weren't using 1.96-20080704-2. Either purge grub2 completely (from /boot too) and start over, or run grub-install on your disk. -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What good is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Tue, Jul 15, 2008 at 02:17:06PM +0200, Robert Millan wrote:
On Tue, Jul 15, 2008 at 10:29:40AM +0100, Jonathan McDowell wrote:
On Mon, Jul 14, 2008 at 04:04:07PM +0200, Robert Millan wrote:
On Mon, Jul 14, 2008 at 01:16:58PM +0100, Jonathan McDowell wrote:
On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote:
On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell
wrote:
It's not fixed, but behaviour appears to be slightly
different.
root is getting detected as (hd0,1) while prefix is ending
up set to (hd0,1)(md0)/boot/grub/ and I'm still getting
dropped to the rescue shell.
Which version did you use for that test?
grub-pc 1.96-20080704-2 (installed from unstable/amd64 this
morning).
Which device did you install grub to?
Um. I don't think I got to specify. I just did aptitude install
grub-pc and then chose the chainloading option from the existing
grub1 install. I didn't get as far as actually replacing the grub1
install as chainloading didn't work.
Then how come you were using 1.96-20080704-2 ? Did you manualy
propagate the files to /boot without calling grub-install?
root's .bash_history indicates I did the following before rebooting:
apt-cache show grub2
aptitude install grub-pc
dpkg -i /usr/src/linux-image-2.6.26_meepok.1_amd64.deb
An md5sum of /boot/grub/boot.img and /usr/lib/grub/i386-pc/boot.img
shows they are identical files. I did not manually copy anything to
/boot/grub. The timestamp on all the files in /boot/grub is 14th July
except for the old grub1 files. dpkg indicates 1.96+20080704-2 is the
version of grub-pc that is installed, so I kinda assumed that's what I
was using.
If not, you weren't using 1.96-20080704-2. Either purge grub2
completely (from /boot too) and start over, or run grub-install on
your disk.
Running grub-install will wipe the grub1 install and leave me with
grub2, right? Is that more likely to work than the existing chainloading
grub2 from grub1 approach?
I can try an aptitude purge; rm /boot/grub/*.{mod,img}; aptitude
install grub-pc tonight and let you know if that's any better.
J.
--
Revd. Jonathan McDowell, ULC | Ok ramblers, let's get rambling.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Sat, Jul 12, 2008 at 05:20:58PM +0200, Robert Millan wrote: On Sat, Jul 05, 2008 at 02:56:09PM +0100, Jonathan McDowell wrote: On Sat, Jul 05, 2008 at 12:39:13PM +, Debian Bug Tracking System wrote: The submitter address recorded for your Bug report #467501: cannot boot when /boot is in RAID has been changed. Er, WTF? If this bug is fixed then it would be nice if the package maintainer could close it so I know it's worth trying grub2 again on my box. If you have veered off the original bug onto a new one perhaps what you want to do is clone it and retitle the new bug, rather than confusing the issue? Sam improperly reused this bug report for something else; then he told me the original report is most likely fixed, so I said it was ok for him to reuse it and send an explanation. Seems like he forgot the explanation. Anyway, please test if the bug still applies; if it does, then please clone it. Sorry for the inconvenience. It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. root (md0) set prefix=(md0)/boot/grub insmod /boot/grub/boot.mod normal still makes the menu come up and boot happen normally from that point. I've mailed control@ to clone the bug and change the original back to mine. J. -- Programmer, | 101 things you can't have too| Tel/SMS: sysadmin | much of : 23 - Red Dwarf. | +423-663-212343 BHMF. || Made by HuggieTag -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell wrote: It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. Which version did you use for that test? -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What good is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell wrote: It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. Which version did you use for that test? grub-pc 1.96-20080704-2 (installed from unstable/amd64 this morning). J. -- Funny how life imitates LSD. This .sig brought to you by the letter J and the number 28 Product of the Republic of HuggieTag -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Mon, Jul 14, 2008 at 01:16:58PM +0100, Jonathan McDowell wrote: On Mon, Jul 14, 2008 at 02:11:51PM +0200, Robert Millan wrote: On Mon, Jul 14, 2008 at 09:55:22AM +0100, Jonathan McDowell wrote: It's not fixed, but behaviour appears to be slightly different. root is getting detected as (hd0,1) while prefix is ending up set to (hd0,1)(md0)/boot/grub/ and I'm still getting dropped to the rescue shell. Which version did you use for that test? grub-pc 1.96-20080704-2 (installed from unstable/amd64 this morning). Which device did you install grub to? -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What good is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Sat, Jul 05, 2008 at 02:56:09PM +0100, Jonathan McDowell wrote: On Sat, Jul 05, 2008 at 12:39:13PM +, Debian Bug Tracking System wrote: The submitter address recorded for your Bug report #467501: cannot boot when /boot is in RAID has been changed. Er, WTF? If this bug is fixed then it would be nice if the package maintainer could close it so I know it's worth trying grub2 again on my box. If you have veered off the original bug onto a new one perhaps what you want to do is clone it and retitle the new bug, rather than confusing the issue? Sam improperly reused this bug report for something else; then he told me the original report is most likely fixed, so I said it was ok for him to reuse it and send an explanation. Seems like he forgot the explanation. Anyway, please test if the bug still applies; if it does, then please clone it. Sorry for the inconvenience. -- Robert Millan GPLv2 I know my rights; I want my phone call! DRM What good is a phone call… if you are unable to speak? (as seen on /.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#467501: submitter address changed (Stealing this bug ;))
On Sat, Jul 05, 2008 at 12:39:13PM +, Debian Bug Tracking System wrote: The submitter address recorded for your Bug report #467501: cannot boot when /boot is in RAID has been changed. Er, WTF? If this bug is fixed then it would be nice if the package maintainer could close it so I know it's worth trying grub2 again on my box. If you have veered off the original bug onto a new one perhaps what you want to do is clone it and retitle the new bug, rather than confusing the issue? J. -- Web [ fivemack it is bruter-force than a really really stupid ] site: http:// [ elephant [on his Python suduku solver] ] Made by www.earth.li/~noodles/ [ ] HuggieTag 0.0.23 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
