Is this a flaw or not?
fedora
fedora at ayni.com
Mon Oct 19 15:50:10 UTC 2015
On 2015-10-18 21:44, jd1008 wrote:
>
>
> On 10/18/2015 12:37 PM, fedora wrote:
>> Hi listers
>>
>> I have a workstation with two disks:
>>
>> [root at casablanca ~]# parted -l
>> Model: ATA WDC WD20EFRX-68E (scsi)
>> Disk /dev/sda: 2000GB
>> Sector size (logical/physical): 512B/4096B
>> Partition Table: gpt
>> Disk Flags: pmbr_boot
>>
>> Number Start End Size File system Name Flags
>> 1 20.5kB 262MB 262MB BIOS boot partition
>> bios_grub
>> 2 262MB 21.7GB 21.5GB ext4 Linux filesystem
>> 3 21.7GB 32.5GB 10.7GB swsusp Linux swap
>> 4 32.5GB 870GB 838GB ext4 Linux filesystem
>> 5 870GB 900GB 30.0GB ext4 Linux filesystem
>> 6 900GB 2000GB 1100GB btrfs
>>
>>
>> Model: ATA WDC WD10EADS-00L (scsi)
>> Disk /dev/sdb: 1000GB
>> Sector size (logical/physical): 512B/512B
>> Partition Table: msdos
>> Disk Flags:
>>
>> Number Start End Size Type File system Flags
>> 1 1049kB 52.4GB 52.4GB primary xfs boot
>> 2 52.4GB 61.1GB 8703MB primary linux-swap(v1)
>> 3 61.1GB 1000GB 939GB primary xfs
>>
>>
>> [root at casablanca ~]#
>>
>> NOTE: the first disk has got a gpt partition table and a BIOS boot
>> partition, the second has got an msdos partition table.
>> Both disks have got fedora 22 installed. They can run independently
>> from one another.
>> ----------
>>
>> Just now, I did an update
>>
>> dnf update
>> ...
>> ...
>> ...
>>
>> on both disks. I rebooted both disks.
>>
>> The result on the first disk (with gpt partition table) is this:
>> [root at thunder ~]# uname -r
>> 4.2.3-200.fc22.x86_64
>> [root at thunder ~]#
>>
>> [root at thunder ~]# dnf list installed |grep kernel |sort
>> abrt-addon-kerneloops.x86_64 2.6.1-2.fc22 @System
>> kernel-core.x86_64 4.1.6-200.fc22 @System
>> kernel-core.x86_64 4.1.6-201.fc22 @System
>> kernel-core.x86_64 4.1.8-200.fc22 @System
>> kernel-debug-core.x86_64 4.1.4-200.fc22 @System
>> kernel-debug-core.x86_64 4.1.6-200.fc22 @System
>> kernel-debug-core.x86_64 4.1.6-201.fc22 @System
>> kernel-debug-modules-extra.x86_64 4.1.4-200.fc22 @System
>> kernel-debug-modules-extra.x86_64 4.1.6-200.fc22 @System
>> kernel-debug-modules-extra.x86_64 4.1.6-201.fc22 @System
>> kernel-debug-modules.x86_64 4.1.4-200.fc22 @System
>> kernel-debug-modules.x86_64 4.1.6-200.fc22 @System
>> kernel-debug-modules.x86_64 4.1.6-201.fc22 @System
>> kernel-devel.x86_64 4.1.8-200.fc22 @System
>> kernel-headers.x86_64 4.1.8-200.fc22 @System
>> kernel-modules-extra.x86_64 4.1.8-200.fc22 @System
>> kernel-modules.x86_64 4.1.6-200.fc22 @System
>> kernel-modules.x86_64 4.1.6-201.fc22 @System
>> kernel-modules.x86_64 4.1.8-200.fc22 @System
>> kernel.x86_64 4.1.6-200.fc22 @System
>> kernel.x86_64 4.1.6-201.fc22 @System
>> kernel.x86_64 4.1.8-200.fc22 @System
>> libreport-plugin-kerneloops.x86_64 2.6.2-1.fc22 @System
>> [root at thunder ~]#
>>
>>
>> Apparently, the kernel 4.2.3-200.fc22.x86_64 is not installed, but the
>> machine according to uname -r
>> booted from it?????
>>
>> ------
>>
>> The result on the second disk (with msdos partition table) is this:
>>
>> [root at casablanca ~]# uname -r
>> 4.2.3-200.fc22.x86_64
>> [root at casablanca ~]#
>>
>> [root at casablanca ~]# dnf list installed |grep kernel |sort
>> abrt-addon-kerneloops.x86_64 2.6.1-5.fc22 @updates
>> kernel-core.x86_64 4.1.7-200.fc22 @updates
>> kernel-core.x86_64 4.1.8-200.fc22 @updates
>> kernel-core.x86_64 @updates
>> kernel-debug-core.x86_64 4.1.7-200.fc22 @updates
>> kernel-debug-core.x86_64 4.1.8-200.fc22 @updates
>> kernel-debug-core.x86_64 4.2.3-200.fc22 @updates
>> kernel-debug-modules-extra.x86_64 4.1.7-200.fc22 @updates
>> kernel-debug-modules-extra.x86_64 4.1.8-200.fc22 @updates
>> kernel-debug-modules-extra.x86_64 4.2.3-200.fc22 @updates
>> kernel-debug-modules.x86_64 4.1.7-200.fc22 @updates
>> kernel-debug-modules.x86_64 4.1.8-200.fc22 @updates
>> kernel-debug-modules.x86_64 4.2.3-200.fc22 @updates
>> kernel-devel.x86_64 4.1.7-200.fc22 @updates
>> kernel-devel.x86_64 4.1.8-200.fc22 @updates
>> kernel-devel.x86_64 4.2.3-200.fc22 @updates
>> kernel-headers.x86_64 4.2.3-200.fc22 @updates
>> kernel-modules.x86_64 4.1.7-200.fc22 @updates
>> kernel-modules.x86_64 4.1.8-200.fc22 @updates
>> kernel-modules.x86_64 4.2.3-200.fc22 @updates
>> kernel.x86_64 4.1.7-200.fc22 @updates
>> kernel.x86_64 4.1.8-200.fc22 @updates
>> kernel.x86_64 4.2.3-200.fc22 @updates
>> libreport-plugin-kerneloops.x86_64 2.6.2-4.fc22 @updates
>> [root at casablanca ~]#
>>
>> Here, the kernel 4.2.3-200.fc22 is installed and the machine according
>> to uname -r booted from it.
>>
>> ---------
>>
>> Does the BIOS boot partition make the difference? Can anybody explain
>> this strange behaviour?
>>
>> Thanks for your attention.
>>
>> suomi
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe at httpd.apache.org
>> For additional commands, e-mail: users-help at httpd.apache.org
>>
> Does /usr/lib/modules contain the dir
> 4.2.3-200.fc22.x86_64 ?
No, it did not. I had to create it after updating.
>
> Does /boot/grub2/grub.cfg have a menuentry like this one:
> menuentry 'Fedora (4.1.10-200.fc22.x86_64) 22 (Twenty Two)' --class
> fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_
> id_option
> 'gnulinux-4.1.10-200.fc22.x86_64-advanced-3e3ce754-4cf3-4673-9449-a42929c3ed31'
> {
>
> Note that 3e3ce754-4cf3-4673-9449-a42929c3ed31 is my disk's uuid for the
> root partition.
>
following are the menuentries of /boot/grub2/grub.cfg:
[root at thunder ~]# grep menuentry /boot/grub2/grub.cfg
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
menuentry_id_option=""
export menuentry_id_option
menuentry 'Fedora (4.1.6-201.fc22.x86_64) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-4.0.4-301.fc22.x86_64-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry 'Fedora (4.1.6-201.fc22.x86_64+debug) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-4.0.4-301.fc22.x86_64-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry 'Fedora (4.1.6-200.fc22.x86_64+debug) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-4.0.4-301.fc22.x86_64-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry 'Fedora (4.1.6-200.fc22.x86_64) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-4.0.4-301.fc22.x86_64-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry 'Fedora (4.1.4-200.fc22.x86_64+debug) 22 (Twenty Two)' --class
fedora --class gnu-linux --class gnu --class os --unrestricted
$menuentry_id_option
'gnulinux-4.0.4-301.fc22.x86_64-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry 'Fedora (0-rescue-302578b1d7b84aebb486be014ce1be91) 22 (Twenty
Two)' --class fedora --class gnu-linux --class gnu --class os
--unrestricted $menuentry_id_option
'gnulinux-0-rescue-302578b1d7b84aebb486be014ce1be91-advanced-b8e065e1-2507-4a33-8224-f31620ad29f7'
{
menuentry '3boot via chainloader from other disk' {
[root at thunder ~]#
Sorry for the late answer, but I was away all day.
Thank you very much for your interest.
suomi
More information about the users
mailing list