Bug 172052 - Reread partition table (sfdisk -R) after mkrootdev to allow USB devices to boot
Summary: Reread partition table (sfdisk -R) after mkrootdev to allow USB devices to boot
Alias: None
Product: Fedora
Classification: Fedora
Component: mkinitrd   
(Show other bugs)
Version: rawhide
Hardware: i386 Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact: David Lawrence
Whiteboard: bzcl34nup
Depends On:
TreeView+ depends on / blocked
Reported: 2005-10-29 22:52 UTC by Albert Strasheim
Modified: 2008-05-07 00:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-07 00:17:36 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Albert Strasheim 2005-10-29 22:52:47 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1

Description of problem:
When booting from USB devices (I have tested with USB flash disks), the boot fails when mounting the root filesystem because the partition table of the device is stale.

As described in http://fungliding.blogspot.com/2005_04_01_fungliding_archive.html, rereading the partition table using sfdisk -R before mounting the root device fixes the problem. This works on all the USB devices I have tested.

It would be very helpful if the initrd could reread the partition table on /dev/sd* before trying to mount the root device. However, including statically linked sfdisk seems a bit expensive. Instead, this functionality could probably be included into nash. Maybe the kernel should be fixed instead? Which method would be preferred?

If this is something you want to add to nash, I could attempt a patch.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Boot from USB device.  

Actual Results:  Kernel panic because root filesystem is not found

Expected Results:  System should boot

Additional info:

Comment 1 Bug Zapper 2008-04-03 16:35:57 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 2 Bug Zapper 2008-05-07 00:17:35 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

Note You need to log in before you can comment on or make changes to this bug.