Bug 1214305 - Device in /etc/fstab that was valid in Fedora 21, fails in Fedora 22, prevents system from booting
Summary: Device in /etc/fstab that was valid in Fedora 21, fails in Fedora 22, prevent...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: udev
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-22 12:04 UTC by Jonathan Kamens
Modified: 2015-07-21 20:19 UTC (History)
5 users (show)

Fixed In Version: systemd-219-19.fc22
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-21 20:19:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jonathan Kamens 2015-04-22 12:04:54 UTC
I had this line in /etc/fstab when I upgraded from FEdora 21 to Fedora 22 last night:

/dev/disk/by-id/wwn-0x50014ee102293fcc-part1 /mnt/point ext4 user_xattr,acl 0 0

As I recall, though it was a long time ago, the device path you see there was inserted by the "Disks" application when I originally configured the system to mount this filesystem.

Before the upgrade, this worked just fine. After the upgrade, however, the system hung for a minute and a half trying to mount this filesystem (I hit ESC during the graphical boot and saw the mount job wait that long, which is how I know how long it took), and then failed to boot and fell into recover mode, i.e., prompted me for my root password.

I'm not sure, but I think somehow the device path changed to /dev/disk/by-id/wwn-0x4597051696078737409x-part1 with the upgrade to Fedora 22.

I thought the point of /dev/disk/by-id/whatever is that they're not supposed to change, but apparently not.

Presumably others are going to be bitten by this and find themselves with systems suddenly unable to boot.

Comment 1 Piergiorgio Sartor 2015-06-29 06:28:25 UTC
Same problem here.

I referenced some disks/partitions by WWN and now, in F22, they're gone for different, unclear, WWN numbers.

Checking with "hdparm -I /dev/sdX" confirms the WWN in F22 is not correct, at least assuming "hdparm" reads it properly.

bye,

pg

Comment 2 Piergiorgio Sartor 2015-06-29 17:47:08 UTC
It seems bug #1227503 is duplicate of this one (or the other way around).

In any case, there is explained the reason and, hopefully, there will be soon a solution.

bye,

pg

Comment 3 Zbigniew Jędrzejewski-Szmek 2015-07-21 20:12:32 UTC
*** Bug 1227503 has been marked as a duplicate of this bug. ***


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