6:30 a.m.
I just did a yum update -- no errors, everything went fine, but now my /boot looks like
this:
dr-xr-xr-x. 6 root root 1024 Dec 3 12:23 ./
dr-xr-xr-x. 30 root root 4096 Dec 3 03:27 ../
-rw-r--r--. 1 root root 512 Dec 26 2001 boot.0300
-rw-r--r--. 1 root root 512 Mar 21 2004 boot.1600
-rw-r--r--. 1 root root 5824 Jun 16 2004 boot.b
-rw-r--r--. 1 root root 612 Jun 16 2004 chain.b
-rw-r--r-- 1 root root 117475 Aug 30 15:44 config-2.6.40.4-5.fc15.x86_64
-rw-r--r-- 1 root root 118667 Nov 22 09:17 config-3.1.2-1.fc16.x86_64
drwxr-xr-x. 3 root root 1024 May 14 2008 efi/
drwxr-xr-x. 2 root root 1024 Dec 3 12:23 grub/
drwxr-xr-x 3 root root 7168 Dec 3 12:23 grub2/
-rw-r--r-- 1 root root 14798077 Sep 7 17:36 initramfs-2.6.40.4-5.fc15.x86_64.img
-rw-r--r-- 1 root root 255223 Nov 9 08:17 initrd-plymouth.img
-rw-r--r--. 1 root root 473 Dec 7 2003 kernel.h
drwxr-xr-x. 2 root root 12288 Dec 26 2001 lost+found/
-rw-------. 1 root root 96768 Mar 25 2006 map
-rw-r--r--. 1 root root 640 Jun 16 2004 os2_d.b
-rw------- 1 root root 2358422 Aug 30 15:44 System.map-2.6.40.4-5.fc15.x86_64
-rw------- 1 root root 2459568 Nov 22 09:17 System.map-3.1.2-1.fc16.x86_64
-rwxr-xr-x 1 root root 3972400 Aug 30 15:44 vmlinuz-2.6.40.4-5.fc15.x86_64*
-rwxr-xr-x 1 root root 4129488 Nov 22 09:17 vmlinuz-3.1.2-1.fc16.x86_64*
Isn't there supposed to be an initramfs for 3.1.2-1?
Is this a bug?
If there's supposed to be one, if so, how can I generate one? Once I have, do I need
to reinstall grub?
Grub conf looks like this:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda8
# initrd /initrd-version.img
boot=/dev/sda
default=0
timeout=8
splashimage=(hd0,0)/grub/splash.xpm.gz
#hiddenmenu
title Fedora (3.1.2-1.fc16.x86_64)
root (hd0,0)
kernel /vmlinuz-3.1.2-1.fc16.x86_64 ro root=LABEL=/ vga=791
SYSFONT=latarcyrheb-sun16 LANG=en_GB.UTF-8 KEYTABLE=uk
title Fedora (2.6.40.4-5.fc15.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.40.4-5.fc15.x86_64 ro root=LABEL=/ vga=791
SYSFONT=latarcyrheb-sun16 LANG=en_GB.UTF-8 KEYTABLE=uk
initrd /initramfs-2.6.40.4-5.fc15.x86_64.img
grub.conf (END)
Scott
4:56 a.m.
On 3 Dec 2011, at 21:57, Scott Doty wrote:
On 12/03/2011 12:14 PM, Scott van Looy wrote:
> On 3 Dec 2011, at 15:56, Scott Doty wrote:
>
>> On 12/03/2011 04:30 AM, Scott van Looy wrote:
>>> Isn't there supposed to be an initramfs for 3.1.2-1?
>> My system has:
>>
>> -rw-r--r-- 1 root root 15945815 Dec 1 21:24
>> initramfs-3.1.2-1.fc16.x86_64.img
>>
>> So yes, you should have one.
>>
>>> Is this a bug?
>> Depends. If you used preupgrade to move from f15 to f16, it's probably
>> a bug. If you used yum to do so, I'm not sure that that is an
>> "approved" method of upgrading...one does so at their own risk.
> I did. It's been doing this for a little while now, I just wanted to double check
the new kernel is the same.
> What's new is that it didn't even tell me there was an error this time…I
thought it might have just worked :)
>
>>> If there's supposed to be one, if so, how can I generate one? Once I
have, do I need to reinstall grub?
>>>
>> You could use dracut to build the initrd, but you're probably better off
>> re-installing the kernel package. Something like:
>>
>> $ su -
>> # yumdownloader kernel
>> # rpm -ivh --force kernel.package.file.name.rpm
> I tried yum reinstall kernel and got the same error.
What error? (You didn't mention one before.)
Sorry, for the whole of F15 I was getting an error when upgrading.
Installing : kernel-3.1.2-1.fc16.x86_64
1/1
Non-fatal POSTTRANS scriptlet failure in rpm package kernel-3.1.2-1.fc16.x86_64
Installed:
kernel.x86_64 0:3.1.2-1.fc16
Complete!
Which in itself is a lie, as it leaves the system unbootable...
Also, you might try using the rpm command, unless you'd rather not. ;)
kernel-3.1.2-1.fc16.x86_64.rpm
| 24 MB 00:03
[root@novak ~]# rpm -ivh --force kernel-3.1.2-1.fc16.x86_64.rpm
Preparing... ########################################### [100%]
1:kernel ########################################### [100%]
Usage: /sbin/dracut [OPTION]... <initramfs> <kernel-version>
...... the whole of dracut's help file .....
mkinitrd failed
warning: %posttrans(kernel-3.1.2-1.fc16.x86_64) scriptlet failed, exit status 1
I have no idea what would cause dracut to fail in this way. I can only think maybe
environment settings or something?
>> You don't need to re-install grub, but you should double-check grub.conf
>> before rebooting to the new kernel.
> I currently have grub and grub2 - how can I tell which my system is using? Or do I
just amend grub2 then run grub2-install /dev/sda?
I am not sure what the status of grub2 is -- and as I said before, I'm a
grub2 noob. ;)
But you can find out the version of grub installed on /dev/sda with:
# file - < /dev/sda
(You need the dash to tell file(1) to read from stdin).
/dev/stdin: x86 boot sector, LInux i386 boot LOader; GRand Unified Bootloader, stage1
version 0x3, stage2 address 0x2000, stage2 segment 0x200; partition 1: ID=0x83, active,
starthead 1, startsector 63, 208782 sectors; partition 2: ID=0x83, starthead 0,
startsector 208845, 117210240 sectors; partition 3: ID=0x83, starthead 254, startsector
117420032, 78137344 sectors; partition 4: ID=0x5, starthead 254, startsector 195559245,
390508020 sectors, code offset 0x63
bash-4.2#
Not sure if that's grub or grub2, mind ;)
>> Also, I do believe f16 includes a move to grub2 -- at least, the tools
>> are installed after I ran preupgrade& upgraded. But my system was left
>> still using grub. That's not such a bad thing, since the grub2.conf
>> syntax has completely changed, making us all grub noobs again.
>>
>> There's also a wiki page somewhere that talks about post-upgrade
>> cleanups one should perform to make sure old packages are thoroughly
>> removed...ask in #fedora about that, or maybe someone will post the link.
> Yeah, I followed all that.
> I was given some advice a while back to run dracut in sh -x - that works for me (but
installing the rpm in sh -x doesn't work for me)
> But it doesn't work in bash.
>
> /sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 in bash just
prints out the help associated with dracut, as if I'd not given it any arguments.
> sh -x /sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 works
>
> I have no real idea what the issue could be, if you or anyone else has any
suggestions it'd be appreciated!
>
Is the error you mentioned earlier from dracut? Might want to check to
ensure you have one (and only one) dracut installed:
$ rpm -qa | grep dracut
dracut-013-18.fc16.noarch
dracut-013-19.fc16.noarch yup.
I've checked through the dracut.conf file, it's the default, but I have the
following line in it:
# install local /etc/mdadm.conf
mdadmconf="yes"
# install local /etc/lvm/lvm.conf
lvmconf="yes"
/etc/lvm.conf exists, /etc/mdadm.conf doesn't and yum whatprovides /etc/mdadm.conf
gives me nothing. I don't know if that would cause this behaviour though.
Am perplexed and confused :)
Scott
2:14 p.m.
On 3 Dec 2011, at 15:56, Scott Doty wrote:
On 12/03/2011 04:30 AM, Scott van Looy wrote:
>
> Isn't there supposed to be an initramfs for 3.1.2-1?
My system has:
-rw-r--r-- 1 root root 15945815 Dec 1 21:24
initramfs-3.1.2-1.fc16.x86_64.img
So yes, you should have one.
> Is this a bug?
Depends. If you used preupgrade to move from f15 to f16, it's probably
a bug. If you used yum to do so, I'm not sure that that is an
"approved" method of upgrading...one does so at their own risk.
I did. It's been doing this for a little while now, I just wanted to double check the
new kernel is the same.
What's new is that it didn't even tell me there was an error this time…I thought
it might have just worked :)
> If there's supposed to be one, if so, how can I generate one? Once I have, do I
need to reinstall grub?
>
You could use dracut to build the initrd, but you're probably better off
re-installing the kernel package. Something like:
$ su -
# yumdownloader kernel
# rpm -ivh --force kernel.package.file.name.rpm
I tried yum reinstall kernel and got the same error.
You don't need to re-install grub, but you should double-check grub.conf
before rebooting to the new kernel.
I currently have grub and grub2 - how can I tell which my system is using? Or do I just
amend grub2 then run grub2-install /dev/sda?
Also, I do believe f16 includes a move to grub2 -- at least, the tools
are installed after I ran preupgrade & upgraded. But my system was left
still using grub. That's not such a bad thing, since the grub2.conf
syntax has completely changed, making us all grub noobs again.
There's also a wiki page somewhere that talks about post-upgrade
cleanups one should perform to make sure old packages are thoroughly
removed...ask in #fedora about that, or maybe someone will post the link.
Yeah, I followed all that.
I was given some advice a while back to run dracut in sh -x - that works for me (but
installing the rpm in sh -x doesn't work for me)
But it doesn't work in bash.
/sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 in bash just prints out
the help associated with dracut, as if I'd not given it any arguments.
sh -x /sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 works
I have no real idea what the issue could be, if you or anyone else has any suggestions
it'd be appreciated!
Scott
9:56 a.m.
On 12/03/2011 04:30 AM, Scott van Looy wrote:
Isn't there supposed to be an initramfs for 3.1.2-1?
My system has:
-rw-r--r-- 1 root root 15945815 Dec 1 21:24
initramfs-3.1.2-1.fc16.x86_64.img
So yes, you should have one.
Is this a bug?
Depends. If you used preupgrade to move from f15 to f16, it's probably
a bug. If you used yum to do so, I'm not sure that that is an
"approved" method of upgrading...one does so at their own risk.
If there's supposed to be one, if so, how can I generate one?
Once I have, do I need to reinstall grub?
You could use dracut to build the initrd, but you're probably better off
re-installing the kernel package. Something like:
$ su -
# yumdownloader kernel
# rpm -ivh --force kernel.package.file.name.rpm
You don't need to re-install grub, but you should double-check grub.conf
before rebooting to the new kernel.
Also, I do believe f16 includes a move to grub2 -- at least, the tools
are installed after I ran preupgrade & upgraded. But my system was left
still using grub. That's not such a bad thing, since the grub2.conf
syntax has completely changed, making us all grub noobs again.
There's also a wiki page somewhere that talks about post-upgrade
cleanups one should perform to make sure old packages are thoroughly
removed...ask in #fedora about that, or maybe someone will post the link.
-Scott
3:57 p.m.
On 12/03/2011 12:14 PM, Scott van Looy wrote:
On 3 Dec 2011, at 15:56, Scott Doty wrote:
> On 12/03/2011 04:30 AM, Scott van Looy wrote:
>> Isn't there supposed to be an initramfs for 3.1.2-1?
> My system has:
>
> -rw-r--r-- 1 root root 15945815 Dec 1 21:24
> initramfs-3.1.2-1.fc16.x86_64.img
>
> So yes, you should have one.
>
>> Is this a bug?
> Depends. If you used preupgrade to move from f15 to f16, it's probably
> a bug. If you used yum to do so, I'm not sure that that is an
> "approved" method of upgrading...one does so at their own risk.
I did. It's been doing this for a little while now, I just wanted to double check the
new kernel is the same.
What's new is that it didn't even tell me there was an error this time…I thought
it might have just worked :)
>> If there's supposed to be one, if so, how can I generate one? Once I have, do
I need to reinstall grub?
>>
> You could use dracut to build the initrd, but you're probably better off
> re-installing the kernel package. Something like:
>
> $ su -
> # yumdownloader kernel
> # rpm -ivh --force kernel.package.file.name.rpm
I tried yum reinstall kernel and got the same error.
What error? (You didn't mention one before.)
Also, you might try using the rpm command, unless you'd rather not. ;)
> You don't need to re-install grub, but you should
double-check grub.conf
> before rebooting to the new kernel.
I currently have grub and grub2 - how can I tell which my system is using? Or do I just
amend grub2 then run grub2-install /dev/sda?
I am not sure what the status of grub2 is -- and as I said before, I'm a
grub2 noob. ;)
But you can find out the version of grub installed on /dev/sda with:
# file - < /dev/sda
(You need the dash to tell file(1) to read from stdin).
> Also, I do believe f16 includes a move to grub2 -- at least, the
tools
> are installed after I ran preupgrade& upgraded. But my system was left
> still using grub. That's not such a bad thing, since the grub2.conf
> syntax has completely changed, making us all grub noobs again.
>
> There's also a wiki page somewhere that talks about post-upgrade
> cleanups one should perform to make sure old packages are thoroughly
> removed...ask in #fedora about that, or maybe someone will post the link.
Yeah, I followed all that.
I was given some advice a while back to run dracut in sh -x - that works for me (but
installing the rpm in sh -x doesn't work for me)
But it doesn't work in bash.
/sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 in bash just prints
out the help associated with dracut, as if I'd not given it any arguments.
sh -x /sbin/dracut initramfs-3.1.2-1.fc16.x86_64.img 3.1.2-1.fc16.x86_64 works
I have no real idea what the issue could be, if you or anyone else has any suggestions
it'd be appreciated!
Is the error you mentioned earlier from dracut? Might want to check to
ensure you have one (and only one) dracut installed:
$ rpm -qa | grep dracut
dracut-013-18.fc16.noarch
-Scott
4528
days inactive
4529
days old
5 comments
2 participants
participants (2)
-
Scott Doty -
Scott van Looy