Hi there,
I just found out this error during fist booth in f17:

cannot open font file True
dracut Warning: Unable to process initqueue
dracut Warning: /dev/vg_dtwebserver/lv_root does not exist
dracut Warning: /dev/vg_dtwebserver/lv_root does not exist

Dropping to debug shell

do we have work around for this?

Thank you for your help

just how did you install fedora 17 ?

also you do know that fedora 17 will hit it's End of life in about 3 months
1 month after fedora 19 comes out

"vg_dtwebserver/lv_root "
odd location and name for the root partition " /"

the normal install for fedora is
sda1 /boot ( ext4 format)
sda2 / ( on a LVM format)

Hi John,

Thank you for your respond. What we did is we installed it by default. Anyway do we need to upgrade our F17 to F19 or to any higher version? If we do so,does data was still reminds on the root? Because F17 that we are using is dedicated for Ajax Explorer repository. Were Ajax Repository serves as FTP. That some users used to upload the files with the Ajax Explorer.

Thank you so much

fedora comes out with a very NEW and sometimes very different OS about every 6 months
They only support any one version for 13 months
( 1 month after the the second new version comes out )
17 hits End of Life 30 days after fedora 19 is released

now fedora has been getting better at "upgrading" inplace
it is still best to do a FULL new and clean install

to go from 17 to 19
back up data
reformat
and do a new install

manually import or migrate data from the old versions of programs to the new versions , from the back up

taking note that fedora might not even be using some program in 19 that is is currently using in 17

like the default database
as i recall it is going from mysql to MariaDB


this is not a "good" use for fedora
Unless you DO want to do a fresh install every 6 months on a production ftp server.And that is not recommend


look into installing RHEL 6.4
or the FREE rebuild CentOS 6.4
it has about 5 to 7 YEARS of life in it

I'm extremely thankful for your info John. Very much appreciated. Another thing, If I'm going to back my file up, is there any way to get those files using dracut:/# ? Because during the boot of the machine, the prompt were used to be dracut:/# . This is something new for me. -su command is not working likewise with sudo command?

Being Sunday you might not have this fixed yet


i take it you are using some sort of RAID set up on the drives

it is a bit odd that there is a dracut prompt
normally grub pops up
" GRUB > "

is this a remote server or are you sitting in front of it

if you have physical access , just pop in the install dvd and fallow the on screen directions to enter " rescue mode"
then try reinstalling grub on fedora 17
-- a fedora 16 fedoraforum post
http://forums.fedoraforum.org/showthread.php?t=273809

but you need to find out the correct drive you used

or you can mount the "/" partition and a usb drive and copy over to the usb


I have never seen your error so at this point i am mostly guessing

That "dracut/#" prompt sounds like you have been dropped into the dracut shell during the early stages of booting (after the kernel is running , but prior to the invocation of init on the real root filesystem). Even in the presence of an error, that normally wouldn't happen without either "rdshell" or "rdbreak" on the kernel command line. See the dracut manpage. I'm not familiar with what functions are available in that shell, but you are likely still running from the initramfs, and not the real root filesystem.