Created attachment 1452392 [details] Commands used for task's purpose Description of problem: Tool util-linux fails to handle correctly a partition. Version-Release number of component: util-linux.x86_64 2.32-2.fc28 @anaconda Actual results: attempting to handle partition that host the volume group produces error: # fdisk /dev/sda2 ... Device does not contain a recognized partition table. Expected results: Allow for partition handling. Allow for deleting partitions associated to the a dual-booted system. Once both partition deletions would have been accomplished I intended to run 'sudo grub2-mkconfig -o /boot/grub2/grub.cfg' –for – and reboot the system. Additional info: Centos and Fedora OSs are installed as dual boot systems on a common SCSI hard disk. Both can be booted, but Centos persists to boot with an older kernel version despite kernel has been updated to last version. Goal to achieve: from Fedora to remove Centos system –volume group containing three logical volumes on sda2– and the boot partition on sda1 –which is the disk's main boot partition–. Both sda2 and sda1 are deactivated in order to allow their own deletion. As noticeable from 'fdisk -l' output, no partition overlaps another one. Commands used: see attachment.
The command fdisk behaves as expected. The usual fdisk command line argument is whole-disk device where is the partition table, in your case: # fdisk /dev/sda
I must have been distracted since did not notice that the number '2' was too much in '# fdisk /dev/sda2'. # fdisk /dev/sda (...) Command (m for help): d Partition number (1-5, default 5): 2 Partition 2 has been deleted. Command (m for help): d Partition number (1,3-5, default 5): 1 Partition 1 has been deleted. Command (m for help): w The partition table has been altered. Syncing disks. Thought the boot instruction has not been transferred automatically to /dev/sda3. I expect system not to boot to the only left system at next reboot. # fdisk /dev/sda (...) Command (m for help): p Device Boot Start End Sectors Size Id Type /dev/sda3 77342720 79439871 2097152 1G 83 Linux /dev/sda4 79439872 488396799 408956928 195G 5 Extended /dev/sda5 79441920 488396799 408954880 195G 8e Linux LVM Neither the newly generated grub configuration file resulting from 'sudo grub2-mkconfig -o /boot/grub2/grub.cfg' succeed to apply such expected change.
fdisk (and another low-level partitioning tools) just modify partition table and nothing else.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.