This does not:
grub> root (hd0,0)
grub> kernel /vmlinuz-2.6.25-14.fc9.i686 ro root=/dev/VG/rootfs rhgb quiet
Error 13: invalid or unsupported executable format
# mount
/dev/mapper/VG-rootfs on / type ext4dev (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/mapper/VG-var on /var type ext4dev (rw)
/dev/mapper/VG-usr on /usr type ext4dev (rw)
/dev/mapper/VG-home on /home type ext4dev (rw)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/user/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=user)
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-23-2008, 02:47 AM
"Antti J. Huhtala"
New kernels do not work.
to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> Please help. PC stuck in grub> prompt.
>
Does the system loudspeaker also ring like a firebell? I just recovered
from the same situation - and your grub.conf confirms it is very likely
the same problem I had.
The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
updated at the same time - rewrote grub.conf so that (in my case) the
line which should have read:
Somehow my /dev/VolGroup... had been changed to UUID=...
The same error had been applied to the previous kernel (2.6.25-14.fc9)
so that neither would boot.
In short, boot the computer with F9 DVD, choose "Rescue previous
installation", press OK to go to CLI, type "chroot /mnt/sysimage", and
type "cd boot/grub".
"ls" will list, among others, grub.conf. Then type "vi grub.conf" and
edit the kernel lines to contain *your* /dev/filesystem instead of your
UUID. Then ":write" to save your new grub.conf and ":quit" to exit vi.
Once in CLI, type "exit" *twice* and remove the DVD while the system is
closing down. It will reboot automatically.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-23-2008, 05:15 PM
"Antti J. Huhtala"
New kernels do not work.
pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> > Please help. PC stuck in grub> prompt.
> >
> The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> updated at the same time - rewrote grub.conf so that (in my case) the
> line which should have read:
>
> kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> rhgb quiet
>
> actually read:
>
> kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
>
> Somehow my /dev/VolGroup... had been changed to UUID=...
>
> The same error had been applied to the previous kernel (2.6.25-14.fc9)
> so that neither would boot.
>
Bugzilla # 448132.
> <snip>
>
> HTH
>
> Antti
>
Antti
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-24-2008, 07:52 PM
Steve
New kernels do not work.
---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> > > Please help. PC stuck in grub> prompt.
> > >
> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> > updated at the same time - rewrote grub.conf so that (in my case) the
> > line which should have read:
> >
> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> > rhgb quiet
> >
> > actually read:
> >
> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> >
> > Somehow my /dev/VolGroup... had been changed to UUID=...
> >
> > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> > so that neither would boot.
> >
> Bugzilla # 448132.
I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
Any futher suggestions?
Steve
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-24-2008, 10:16 PM
"slamp slamp"
New kernels do not work.
On Sat, May 24, 2008 at 3:52 PM, Steve <zephod@cfl.rr.com> wrote:
>
> ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
>> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
>> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
>> > > Please help. PC stuck in grub> prompt.
>> > >
>> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
>> > updated at the same time - rewrote grub.conf so that (in my case) the
>> > line which should have read:
>> >
>> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
>> > rhgb quiet
>> >
>> > actually read:
>> >
>> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
>> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
>> >
>> > Somehow my /dev/VolGroup... had been changed to UUID=...
>> >
>> > The same error had been applied to the previous kernel (2.6.25-14.fc9)
>> > so that neither would boot.
>> >
>> Bugzilla # 448132.
>
> I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
>
> Any futher suggestions?
>
> Steve
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
well my issue was either fedora or grub not being able work well with
"fakeraid". anything i tried nothing helped. i reinstalled grub to the
right fakeraid device and it did not help. so what i did was deleted
the "fakeraid" from intel bios and just did a software raid (mdadm).
this works better than dmraid and grub or fedora seems to properly use
the /dev/md* device. "fakeraid" sucks, too bad i did not catch this
when i bought my pc (powerspec e361).
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-25-2008, 03:43 AM
"Antti J. Huhtala"
New kernels do not work.
la, 2008-05-24 kello 18:16 -0400, slamp slamp kirjoitti:
> On Sat, May 24, 2008 at 3:52 PM, Steve <zephod@cfl.rr.com> wrote:
> >
> > ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> >> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> >> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> >> > > Please help. PC stuck in grub> prompt.
> >> > >
> >> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> >> > updated at the same time - rewrote grub.conf so that (in my case) the
> >> > line which should have read:
> >> >
> >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> >> > rhgb quiet
> >> >
> >> > actually read:
> >> >
> >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> >> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> >> >
> >> > Somehow my /dev/VolGroup... had been changed to UUID=...
> >> >
> >> > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> >> > so that neither would boot.
> >> >
> >> Bugzilla # 448132.
> >
> > I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
> >
> > Any futher suggestions?
> >
> > Steve
> >
> > --
> >
>
> well my issue was either fedora or grub not being able work well with
> "fakeraid". anything i tried nothing helped. i reinstalled grub to the
> right fakeraid device and it did not help. so what i did was deleted
> the "fakeraid" from intel bios and just did a software raid (mdadm).
> this works better than dmraid and grub or fedora seems to properly use
> the /dev/md* device. "fakeraid" sucks, too bad i did not catch this
> when i bought my pc (powerspec e361).
>
Unfortunately I know next to nothing of RAIDed filesystems, but it would
seem logical to assume that if you're stuck with "GRUB" it is because
grub doesn't know where to go next.
Another thread today deals with /etc/fstab containing UUIDs instead of
filesystem partitions. It would be my guess that a working Fedora system
knows how to handle UUIDs but I doubt that GRUB knows how to do it. If
I'm wrong about this, I'll be happy to stand corrected.
See my other reply today in this thread for something to try...
Antti
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-25-2008, 04:03 AM
"Antti J. Huhtala"
New kernels do not work.
la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti:
> ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> > pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> > > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> > > > Please help. PC stuck in grub> prompt.
> > > >
> > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> > > updated at the same time - rewrote grub.conf so that (in my case) the
> > > line which should have read:
> > >
> > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> > > rhgb quiet
> > >
> > > actually read:
> > >
> > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> > > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> > >
> > > Somehow my /dev/VolGroup... had been changed to UUID=...
> > >
> > > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> > > so that neither would boot.
> > >
> > Bugzilla # 448132.
>
> I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
>
> Any futher suggestions?
>
Sorry, looking back at my cryptic hand-written notes I realize I forgot
to mention that I ran 'grub-install' before editing grub.conf. On the
basis of time-stamps of the files in /boot/grub, almost all files were
rewritten but grub.conf was not. My notes don't record whether I tried
rebooting after running grub-install but IIRC I probably did. I seem to
recollect that I was still stuck at "GRUB".
Therefore I edited grub.conf and tried again. This time reboot worked
for me so I didn't delve into it further.
Whether the real remedy was running grub-install or editing grub.conf
*or both*, I don't know. The fact remains I'm typing this with 'fully'
operational F9 system.
Antti
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-25-2008, 01:23 PM
Aaron Konstam
New kernels do not work.
On Sun, 2008-05-25 at 07:03 +0300, Antti J. Huhtala wrote:
> la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti:
> > ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> > > pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> > > > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> > > > > Please help. PC stuck in grub> prompt.
> > > > >
> > > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> > > > updated at the same time - rewrote grub.conf so that (in my case) the
> > > > line which should have read:
> > > >
> > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> > > > rhgb quiet
> > > >
> > > > actually read:
> > > >
> > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> > > > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> > > >
> > > > Somehow my /dev/VolGroup... had been changed to UUID=...
> > > >
> > > > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> > > > so that neither would boot.
> > > >
> > > Bugzilla # 448132.
> >
> > I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
> >
> > Any futher suggestions?
> >
> Sorry, looking back at my cryptic hand-written notes I realize I forgot
> to mention that I ran 'grub-install' before editing grub.conf. On the
> basis of time-stamps of the files in /boot/grub, almost all files were
> rewritten but grub.conf was not. My notes don't record whether I tried
> rebooting after running grub-install but IIRC I probably did. I seem to
> recollect that I was still stuck at "GRUB".
> Therefore I edited grub.conf and tried again. This time reboot worked
> for me so I didn't delve into it further.
> Whether the real remedy was running grub-install or editing grub.conf
> *or both*, I don't know. The fact remains I'm typing this with 'fully'
> operational F9 system.
>
> Antti
>
>
Running grub-install should just re-install the boot block. Changing
grub.conf should not need another grub-install.
--
================================================== =====================
Disraeli was pretty close: actually, there are Lies, Damn lies,
Statistics, Benchmarks, and Delivery dates.
================================================== =====================
Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-25-2008, 02:51 PM
Steve
New kernels do not work.
---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti:
> > ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> > > pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> > > > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> > > > > Please help. PC stuck in grub> prompt.
> > > > >
> > > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> > > > updated at the same time - rewrote grub.conf so that (in my case) the
> > > > line which should have read:
> > > >
> > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> > > > rhgb quiet
> > > >
> > > > actually read:
> > > >
> > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> > > > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> > > >
> > > > Somehow my /dev/VolGroup... had been changed to UUID=...
> > > >
> > > > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> > > > so that neither would boot.
> > > >
> > > Bugzilla # 448132.
> >
> > I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
> >
> > Any futher suggestions?
> >
> Sorry, looking back at my cryptic hand-written notes I realize I forgot
> to mention that I ran 'grub-install' before editing grub.conf. On the
> basis of time-stamps of the files in /boot/grub, almost all files were
> rewritten but grub.conf was not. My notes don't record whether I tried
> rebooting after running grub-install but IIRC I probably did. I seem to
> recollect that I was still stuck at "GRUB".
> Therefore I edited grub.conf and tried again. This time reboot worked
> for me so I didn't delve into it further.
> Whether the real remedy was running grub-install or editing grub.conf
> *or both*, I don't know. The fact remains I'm typing this with 'fully'
> operational F9 system.
> > Steve
> Antti
>
...and I should have added in my note that after I edited grub.conf, rebooted and I was still stuck with just GRUB on the screen, that I re-installed grub from the DVD while in rescue mode and then rebooted again. No luck - still just GRUB. At this point I think my next move may be to do a complete re-install. <Sigh!>
Steve
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
05-25-2008, 03:01 PM
Steve
New kernels do not work.
---- slamp slamp <slackamp@gmail.com> wrote:
> On Sat, May 24, 2008 at 3:52 PM, Steve <zephod@cfl.rr.com> wrote:
> >
> > ---- "Antti J. Huhtala" <ahuhtal4@welho.com> wrote:
> >> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti:
> >> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti:
> >> > > Please help. PC stuck in grub> prompt.
> >> > >
> >> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files
> >> > updated at the same time - rewrote grub.conf so that (in my case) the
> >> > line which should have read:
> >> >
> >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00
> >> > rhgb quiet
> >> >
> >> > actually read:
> >> >
> >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro
> >> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet
> >> >
> >> > Somehow my /dev/VolGroup... had been changed to UUID=...
> >> >
> >> > The same error had been applied to the previous kernel (2.6.25-14.fc9)
> >> > so that neither would boot.
> >> >
> >> Bugzilla # 448132.
> >
> > I have the same problem except that correcting my grub.conf file did not help. I'm still stuck with just GRUB showing on the screen. Also I did not get any sounds.
> >
> > Any futher suggestions?
> >
> > Steve
> >
> > --
> > fedora-list mailing list
> > fedora-list@redhat.com
> > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
> >
>
> well my issue was either fedora or grub not being able work well with
> "fakeraid". anything i tried nothing helped. i reinstalled grub to the
> right fakeraid device and it did not help. so what i did was deleted
> the "fakeraid" from intel bios and just did a software raid (mdadm).
> this works better than dmraid and grub or fedora seems to properly use
> the /dev/md* device. "fakeraid" sucks, too bad i did not catch this
> when i bought my pc (powerspec e361).
I have 2 250G disks in this computer; one has Windows while the other has Fedora. I'll have to check when I get back to work but I think I remember there being only one disk mentioned in the boot order in the BIOS so perhaps this fake raid is turned on in the BIOS. This is an HP dc7700 machine and I know precious little about RAID, fake or otherwise so I don't use it or at least not on purpose.
Steve
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
New kernels do not work.
