Bug 860525 - dracut-pre-pivot[272]: mount: wrong fs type, bad option, bad superblock on /var/lib/nfs/rpc_pipefs,
Summary: dracut-pre-pivot[272]: mount: wrong fs type, bad option, bad superblock on /v...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dracut
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: dracut-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F18Blocker, F18FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-09-26 04:31 UTC by xset1980
Modified: 2012-12-20 05:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-20 05:37:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dracut-pre-pivot (8.90 KB, image/png)
2012-09-26 04:31 UTC, xset1980
no flags Details

Description xset1980 2012-09-26 04:31:02 UTC
Created attachment 617382 [details]
dracut-pre-pivot

Description of problem:

After initrd load and start the systemd load dracut show:

dracut-pre-pivot[272]: mount: wrong fs type, bad option, bad superblock on /var/lib/nfs/rpc_pipefs,
dracut-pre-pivot[272]: missing codepage or helper program, or other error
dracut-pre-pivot[272]: In some cases useful info is found in syslog - try
dracut-pre-pivot[272]: dmesg | tail or so


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

Fedora 18 Alpha KDE spin up to date
dracut-023-39.git20120910.fc18.i686
systemd-188-3-fc18.i686
kernel-3.6.0-0.rc6.git0.2.fc18.i686
grub2-2.00-5.fc18.i686
util-linux-2.22-1.fc18.i686

How reproducible:
Always on every boot.

Steps to Reproduce:
1.Install F18 Alpha KDE spin
2.yum update -y
3.reboot
  
Actual results:


Expected results:


Additional info:

attach screenshot

Comment 1 D. Charles Pyle 2012-11-11 07:57:07 UTC
I get these same and similar errors with complete install of Fedora 18-Alpha that is not a spin. Even with the latest updates from updates-testing I still get the errors.

Comment 2 D. Charles Pyle 2012-11-11 08:10:53 UTC
Here are the versions of the above components listed in the initial post that I am running:

$ rpm -qa dracut systemd kernel grub2 util-linux
grub2-2.00-12.fc18.x86_64
util-linux-2.22.1-2.1.fc18.x86_64
dracut-024-5.git20121019.fc18.x86_64
kernel-3.6.5-2.fc18.x86_64
kernel-3.6.3-3.fc18.x86_64
systemd-195-6.fc18.x86_64
kernel-3.6.6-3.fc18.x86_64

Comment 3 D. Charles Pyle 2012-11-11 08:32:02 UTC
The part of the boot screen that I see gives an added error to the above, as follows, in the exact order in which it displays on my screen on every boot.

dracut-cmdline[66]: /etc/locale.conf: line 1: locale.LANG=en_US.UTF-8: command n
[  OK  ] Started Show Plymouth Boot Screen
[  OK  ] Reached target Basic System
dracut-pre-pivot[331]: mount: wrong fs type, bad option, bad superblock on /var/lib/nfs/rpc_pipefs,
dracut-pre-pivot[331]: missing codepage or helper program, or other error
dracut-pre-pivot[331]: In some cases useful info is found in syslog - try
dracut-pre-pivot[331]: dmesg | tail or so

I noticed that there is no file locale.conf in /etc also.

Comment 4 D. Charles Pyle 2012-11-11 08:35:43 UTC
Never mind the line in my above comment about a missing locale.conf file. The latest updates I just did put one there. However, the other errors remain, as does the very first line I gave in comment 3.

I am not sure what is causing this.

Comment 5 D. Charles Pyle 2012-11-11 09:39:59 UTC
The error:

dracut-cmdline[66]: /etc/locale.conf: line 1: locale.LANG=en_US.UTF-8: command n

No longer appears after I removed the "LANG=..." variable from the kernel line in /etc/default/grub and rebuilt the grub2 menu without it, after reading discussion here:

https://bugzilla.redhat.com/show_bug.cgi?id=870632

The dracut-pre-pivot error still occurs as above in comment 3.

Comment 6 D. Charles Pyle 2012-11-11 09:41:03 UTC
The error:

dracut-cmdline[66]: /etc/locale.conf: line 1: locale.LANG=en_US.UTF-8: command n

No longer appears after I removed the "LANG=..." variable from the kernel line in /etc/default/grub and rebuilt the grub2 menu without it, after reading discussion here:

https://bugzilla.redhat.com/show_bug.cgi?id=870632

The dracut-pre-pivot error still occurs as above in comment 3.

Comment 7 D. Charles Pyle 2012-11-11 09:41:33 UTC
The error:

dracut-cmdline[66]: /etc/locale.conf: line 1: locale.LANG=en_US.UTF-8: command n

No longer appears after I removed the "LANG=..." variable from the kernel line in /etc/default/grub and rebuilt the grub2 menu without it, after reading discussion here:

https://bugzilla.redhat.com/show_bug.cgi?id=870632

The dracut-pre-pivot error still occurs as above in comment 3.

Comment 8 D. Charles Pyle 2012-11-30 03:02:20 UTC
The error still is occurring in Fedora 18-Beta.

Comment 9 xset1980 2012-11-30 04:32:18 UTC
(In reply to comment #8)
> The error still is occurring in Fedora 18-Beta.

Confirm that Charles, still on F18 Beta rc1.

Comment 10 Tim Flink 2012-11-30 18:16:57 UTC
I'm not sure that I understand the effects of this bug or how it qualifies as a release blocker.

My current understanding is that this is some extra error messages in kmsg on startup and might be related to #870632.

Is this causing errors in the boot process or preventing boot post-install?

Comment 11 Harald Hoyer 2012-12-03 12:25:17 UTC
somehow current kernels do not like:

     mount --move /var/lib/nfs/rpc_pipefs $NEWROOT/$rpcpipefspath

but

        mount --bind /var/lib/nfs/rpc_pipefs $NEWROOT/$rpcpipefspath
        umount /var/lib/nfs/rpc_pipefs

seems to work fine.

This would prevent possible NFS install errors.

Comment 12 Adam Williamson 2012-12-03 18:45:00 UTC
Discussed at 2012-12-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-12-03/f18final-blocker-review-1.2.2012-12-03-17.25.log.txt . There was much confusion about the extent and impact of this bug, we really don't understand it at all. We postponed decision on its status until the nature of the bug is clearer.

Comment 13 D. Charles Pyle 2012-12-04 20:58:40 UTC
What in dracut is causing the above error? Is it some configuration file somewhere? It slows down booting slightly but so far as I am aware it isn't really breaking anything else that I use at the moment.

Comment 14 Harald Hoyer 2012-12-05 12:52:11 UTC
(In reply to comment #13)
> What in dracut is causing the above error? Is it some configuration file
> somewhere? It slows down booting slightly but so far as I am aware it isn't
> really breaking anything else that I use at the moment.

see comment #11

Comment 15 D. Charles Pyle 2012-12-05 17:02:38 UTC
OK, but in what file is this offending text in comment 11 to be found?

Comment 16 Tim Flink 2012-12-07 16:58:07 UTC
I still don't quite understand the extent and impact of this bug. Has it been a problem for NFS installs? If so, how common is it? How fatal is it to the install? Are there workarounds? Could it be fixed with an update?

Comment 17 D. Charles Pyle 2012-12-07 19:23:06 UTC
I do not use NFS, so far as I am aware. I do not even understand why I see such an error or what it might be doing on my system. I just want to know where the offending line of code occurs in what configuration file.

I ran multiple searches on the content of various files and groups of files and still have turned up nothing. I do not even know what causes the error, or what it does or how it affects the system other than the slight delay in booting that it causes.

But, if anyone knows where or in what configuration file(s) this is occurring so I can at least employ a workaround in the interim, I would appreciate it very much.

Comment 18 Harald Hoyer 2012-12-14 09:34:39 UTC
(In reply to comment #17)
> I do not use NFS, so far as I am aware. I do not even understand why I see
> such an error or what it might be doing on my system. I just want to know
> where the offending line of code occurs in what configuration file.
> 
> I ran multiple searches on the content of various files and groups of files
> and still have turned up nothing. I do not even know what causes the error,
> or what it does or how it affects the system other than the slight delay in
> booting that it causes.
> 
> But, if anyone knows where or in what configuration file(s) this is
> occurring so I can at least employ a workaround in the interim, I would
> appreciate it very much.

If you don't have root or /usr on network, just:

# yum remove dracut-network
# dracut -f

And the error should be gone.

Comment 19 Fedora Update System 2012-12-18 15:57:16 UTC
dracut-024-15.git20121218.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/dracut-024-15.git20121218.fc18

Comment 20 Fedora Update System 2012-12-18 21:27:37 UTC
Package dracut-024-15.git20121218.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-024-15.git20121218.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20580/dracut-024-15.git20121218.fc18
then log in and leave karma (feedback).

Comment 21 Adam Williamson 2012-12-19 18:12:27 UTC
Discussed at 2012-12-19 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-19/f18final-blocker-review-6.2012-12-19-17.02.log.txt . Agreed we're still not clear on the actual impact of this - whether it was breaking anything, or just cosmetic - so we still can't make a decision. Harald has not answered that question. But the fix is likely to come in anyway, with the other dracut blocker, so this might go away soon.

Comment 22 D. Charles Pyle 2012-12-19 22:02:48 UTC
The update stopped the error in its tracks. I have not seen the error since applying the update linked above in comment 20.

Comment 23 Fedora Update System 2012-12-20 05:37:16 UTC
dracut-024-15.git20121218.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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