Bug 679219

Summary: Can't mount root filesystem
Product: [Fedora] Fedora Reporter: Ed <ed>
Component: dracutAssignee: Harald Hoyer <harald>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: harald, jonathan
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-23 07:47:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ed 2011-02-21 22:46:19 UTC 
Description of problem:

I am trying to do a net boot installation of Fedora using PXE. The initrd.img and vmlinuz0 files are loaded on the client (an aspire one netbook), but dracut mounts the root device and later tries to mount it several times again. Eventually dracut stops the boot process complaining that it can't mount the root filesystem.


Version-Release number of selected component (if applicable):
dracut-006-3.fc14

How reproducible:
Everytime

Steps to Reproduce:

1. Download and mount Fedora-14-i686-Live-Desktop.iso to a filesystem eg,
mount -ro loop,context=system_u:object_r:httpd_sys_content_t:s0 /home/ed/Downloads/Fedora-14-i686-Live-Desktop.iso /tftpboot/fedora

2. Copy initrd0.img and vmlinuz0 from /tftpboot/fedora/isolinux to /tftpboot or wherever your tftp root is.

3. Add the following to /tftpboot/pxelinux.cfg/default

label linux0
  menu label fedora-14
  kernel vmlinuz0
  append initrd=initrd0.img root=/dev/sda2 rdshell rdinitdebug

4. Set client to PXE boot


  
Actual results:
dracut stops in the boot process complaining it can't mount the root filesystem

Expected results:
Expect to boot into the fedora install

Additional info:

dmesg | less : 
mount -t auto -o ro /dev/sda2 /sysroot
mount: /dev/sda2 already mounted or /sysroot busy
mount: according to mtab, /dev/sda2 is already mounted on /sysroot
getarg rd_NO_FSTAB
set +x
return 1
getarg rootflags
set +x
return 1
[ -f /sysroot/etc/fstab ]
[ -d /sysroot/proc ]
i=21
[ 21 gt 20 ]
flock -s 9
emergency_shell Can't mount root filesystem
[ Can't mount root filesystem = -n ]


blkid
/dev/sda1: UUID="00997 ...." TYPE="ext4"
/dev/sda2: UUID="c64c4 ...." TYPE="ext4"
/dev/sda3: UUID="1f0a9 ...." TYPE="swap"
Comment 1 Harald Hoyer 2011-02-22 13:20:13 UTC 
> <ed__> if I try root=192.168.2.1:/fedora dracut says FATAL Don't know how to handle root=192.168.2.1:/fedora
> <ed__> ah would that be because dracut-network is not installed in the fedora image

Exactly!
Comment 2 Ed 2011-02-22 19:25:08 UTC 
(In reply to comment #1)
> > <ed__> if I try root=192.168.2.1:/fedora dracut says FATAL Don't know how to handle root=192.168.2.1:/fedora
> > <ed__> ah would that be because dracut-network is not installed in the fedora image
> 
> Exactly!

Does this mean it's not possible to install Fedora over the network?
Comment 3 Harald Hoyer 2011-02-23 07:47:03 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> > > <ed__> if I try root=192.168.2.1:/fedora dracut says FATAL Don't know how to handle root=192.168.2.1:/fedora
> > > <ed__> ah would that be because dracut-network is not installed in the fedora image
> > 
> > Exactly!
> 
> Does this mean it's not possible to install Fedora over the network?

That's not true! The DVD contains a network image to boot from. This is the anaconda network image, which has nothing to do with dracut.