Hi,
I am using Fedora 16 32+ bit distro and I am getting this error when I try to boot Fedora.
Hi all,
(dual boot)
Fedora 17 64bit
Debian 6.0.6 64bit
On booting Fedora
Code:
......
powernow-k9: try again with latest BIOS
Cannot open font file True
_Fedora=17-x86_6: UNEXPECTED INCONSISTENCY: Run fsck manual.
(i.e.
Relative newb.
When switching on it fails and goes to this screen
Code:
_Fedora-17-x86_6: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY
(ie without -a or -p options)
dracut warning: e2fsck returned with 4
dracut warning: _Fedora-17-x86_6 contains a file systen with errors, check forced
dracut warning: _Fedora-17-x86_6: inodes that were part of a corrupted orphan linked list found.
dracut war
During each boot the recovery console is appeared.
Quote:
/dev/mapper/VolGroup-lv_root: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: /dev/mapper/VolGroup-lv_root contains a file system with errors, check forced.
dracut Warning: /dev/mapper/VolGroup-lv_root: Inodes that were part
I am experiencing errors when I boot up. I get some error messages and get a command prompt at the end. If I type exit at the command prompt it will then boot up.
The error messages are:
/dev/mapper/VolGroup-lv_root:
unexpected inconsistency: Run fsck manually (i.e.
Hello,
I have a problem with booting my fedora 17 from a stick.
I'm using Win 7 with liveusb-creator to write Fedora-17-x86_64-Live-KDE.iso.
When i try to install Fedora 17 Live Desktop from a USB thumb Drive it gives me the following error:
" dracut Warning: Unable to process initgueue
dracut Warning:/dev/disk/by-label/Fedora-17-x86_64-Live-Desktop. is doesnot exist
dracut Warning:/dev/mapper/live-rw does not exist
Dropping to debug shell.
dracut:/# "
Any solution?
Hi guys,
I have the following issue. I want to update from Fedora 12 to Fedora 17.
My Fedora 12 was customized and the installation contains kickstart scripts which are invoked from my isolinux.cfg. Scripts work fine with Fedora 12.
HERE IS THE ERROR MESSAGE I GOT AFTER I BOOT THE INSTALLATION ISO and KERNEL BOOTS. SOMEHOW THE INSTALLATION DOES NOT START.
Hello,
I have been having a problem with disk corruption in the last few days. Tracked it down to the system suspend.