Bug 716639 - remount-rootfs fails for NFS root
Summary: remount-rootfs fails for NFS root
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-25 21:22 UTC by Göran Uddeborg
Modified: 2011-06-27 10:50 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 10:50:38 UTC
Type: ---


Attachments (Terms of Use)

Description Göran Uddeborg 2011-06-25 21:22:53 UTC
Description of problem:
We are trying to make a diskless Fedora 15 client with / on NFS.  We have made a "yum Base --installroot ..." installation on the server.  The client gets past the DHCP and PXE phases, but when booting up the systemd service remount-rootfs fails.

Version-Release number of selected component (if applicable):
systemd-units-26-4.fc15.x86_64

How reproducible:
Every time

Actual results:
remount-rootfs.service    loaded failed failed        Remount Root FS

Additional info:
We are new to systemd, so maybe we are doing something wrong and misunderstanding things.  But it looks like a bug at first sight.

We get other problems later on.  But we are not sure to what extent they may be related.  We believe this to be the first thing that fails.

Comment 1 Lennart Poettering 2011-06-27 09:43:12 UTC
most likely you simply don't have listed the root file system in /etc/fstab?

We try to remount it so that all options specified in /etc/fstab are applied.

If you call "/bin/mount / -o remount" what do you get?

Comment 2 Göran Uddeborg 2011-06-27 10:50:38 UTC
> most likely you simply don't have listed the root file system in /etc/fstab

That was it!  Not a systemd issue then.

The mount command didn't write anything, but gave exit status 32.  After I added the root file system to fstab, it exits with status 0.

Thanks for the pointer, and sorry for the confusion.


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