Bug 744403

I restricted to KDE file system because I could not escape selecting an item. I don't have enough knowledge to specify the component. It would be helpful to add an "I don't know" item.

There's actually a "distribution" component for when there's really no fitting package.

In this case, kde-filesystem or any other KDE stuff cannot possibly have anything to do with it, because this fails inside the initrd, in very early boot, as evidenced by the "dracut" in the debug shell.

The "can't access tty" message only comes up when the debug shell is already getting started, so it can't be the cause of the boot failure. The real problem must be one of the earlier messages. I've put the last one into the bug topic, but I'm also not sure whether that's the fatal error here.

I'm reassigning this to "kernel" in the hope that one of the kernel maintainers can figure out what's going wrong there. Is this a hardware issue?

Which kernel is this?  Is there any way you can run 'dmesg' from the prompt and copy the output somewhere?

Has any version of Fedora booted on this machine from this drive before, and if so what kernel version is that using?

Lastly, if you can boot from the LiveUSB key or some other Linux version, can you provide the output of the SMART data on the drive?

Thanks for answers by Kevin Kofler and Josh Boyer
Here are the informations you asked for:
I think I found the source of the problem
-------------------------------------------------------------------------------------
Computer : TOSHIBA Satellite P770/P775
	Manufacturer		TOSHIBA
	Processor			Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz
	RAM						4.00 GB
-------------------------------------------------------------------------------------
Disk drive on which Fedora 15 is installed : TOSHIBA MK5075GSX 
Properties (Information below got under Windows 7)
	Hardware Ids
		IDE\DiskTOSHIBA_MK5075GSX_______________________GT001M__
		IDE\TOSHIBA_MK5075GSX_______________________GT001M__
		IDE\DiskTOSHIBA_MK5075GSX_______________________
		TOSHIBA_MK5075GSX_______________________GT001M__
		GenDisk
	Compatible Ids
		GenDisk
	Service
		disk
	Device class
		DiskDrive
	Device class guid
		{4d36e967-e325-11ce-bfc1-08002be10318}
	Driver key
		{4d36e967-e325-11ce-bfc1-08002be10318}\0003
	Config rags
		00000000
	Manufacturer
		(Standard disk drives)
	Friendly name
		TOSHIBA MK5075GSX
	Location information
		0
	Physical disk object name
		\Device\Ide\IAAStorageDevice-1
	Capabilities
		00000080
		CM_DEVCAP_SURPRISEREMOVALOK
	Bus type guid
		{1530ea73-086b-11d1-a09f-00c04fc340b1}
	Legacy bus type
		0000000F
	Bus number
		00000000
	Enumerator
		IDE
	Address
		0000FFFF
	Power data
		Current power state:
		D0
		
		Power capabilities:
		0000000B
		PDCAP_D0_SUPPORTED
		PDCAP_D1_SUPPORTED
		PDCAP_D3_SUPPORTED
		
		Power state mappings:
		S0 -> D0
		S1 -> D1
		S2 -> Unspecified
		S3 -> D3
		S4 -> D3
		S5 -> D3
	Removal policy
		00000001
	Removal policy default
		00000001
	Install state
		00000000
	Base container Id
		{00000000-0000-0000-ffff-ffffffffffff}
	Display name
		TOSHIBA MK5075GSX
	Device instance path
		IDE\DISKTOSHIBA_MK5075GSX_______________________GT001M__\4&3B404081&0&0.0.0
	DevNode status
		0180000A
		DN_DRIVER_LOADED
		DN_STARTED
		DN_NT_ENUMERATOR
		DN_NT_DRIVER
	Problem code
		00000000
	Removal relations
		STORAGE\Volume\{68166db9-a82a-11e0-9fc0-806e6f6e6963}#0000000000100000
		STORAGE\Volume\{68166db9-a82a-11e0-9fc0-806e6f6e6963}#000000005DD00000
		STORAGE\Volume\{68166db9-a82a-11e0-9fc0-806e6f6e6963}#00000070A1B00000
	Parent
		PCI\VEN_8086&DEV_1C03&SUBSYS_FC301179&REV_04\3&11583659&0&FA
	Siblings
		IDE\DiskTOSHIBA_MK5075GSX_______________________GT001M__\4&3b404081&0&0.1.0
		IDE\CdRomTSSTcorp_CDDVDW_TS-L633F________________TF01____\4&3b404081&0&0.2.0
	Container Id
		{00000000-0000-0000-ffff-ffffffffffff}
	Safe removal required
		<false>
	Bus reported device description
		TOSHIBA MK5075GSX
	Drive Node Strong Name
		disk.inf:disk_device.NTamd64:disk_install:6.1.7600.16385:gendisk
	Install date
		07/07/2011 01:48:45
	First Intall date
		07/07/2011 01:48:45
	Driver assembly date
		21/06/2006 02:00:00
	Driver assembly version
		6.1.7600.16385
	Driver assembly description
		Disk drive
	Inf name
		disk.inf
	Inf section
		disk_install
	Inf section extension
		.NT
	Matching device Id
		gendisk
	Provider
		Microsoft
	Rank of installed driver
		00FF0004
	Class upper filters
		PartMgr
	Class lower filters
		thpdrv
	Class default device type
		00000007
	Class default characterisics
		00000100
	Class long name
		Disk drives
	Class short name
		DiskDrive
	Class installer
		StorProp.Dll,DiskClassInstaller
	No install class
		<true>
	Silent install class
		<true>
	Class icon path
		%SystemRoot%\System32\imageres.dll,-32
	Display name
		Disk drives
	Class co-installers
		SysClass.Dll,StorageCoInstaller
		SysClass.Dll,CriticalDeviceCoInstaller
-------------------------------------------------------------------------------------
Fedora 15 installation
	I downloaded Fedora-15-x86_64-Live-KDE.iso
	I made a USB live using LiveUSB Creator
	No boot problem from USB
	I installed to Hard disk
	Everything worked well
	I restarted
	I updated KDE to version 4.7 (as advised in http://linuxtweaking.blogspot.com/2011/08/fedora-15-kde-how-to-upgrade-to-kde-47.html)
	  cd /etc/yum.repos.d
	  su -c 'yum install wget'
	  su -c 'wget http://repos.fedorapeople.org/repos/rdieter/kde47/fedora-kde47.repo'
	  su -c 'yum update'
	On restarting, GRUB displayed the following :
	  Fedora (2.6.40.6-0.fc15.x86_64)
	  Fedora (2.6.38.6-26.rc1.fc15.x86_64)
	  Other
	  This seems strange : I have only one linux system
	Boot failed on both choices with the screen I have sent to you
	I re-installed Fedora 15 from USB
	Menus are unusable in kde 4.6 ; they display garbage
	I updated kde using KPakageKit and kde 4.6 is corrected : works fine
	It seems that the problem comes from kde 4.7 or the repository of rdieter
-------------------------------------------------------------------------------------
Please, advise
  . Shall I keep kde 4.6
  . Is there an official kde 4.7 ?
  . Shall I wait for Fedora 16 ?

I'd advise simply using what works for you.  Fwiw, there won't be any official kde-4.7 for f15 (beyond the unofficial builds you mentioned), kde-4.7 will be included with F16.

I really don't see how KDE SC 4.7 can possibly break your boot so early in the boot process, at a time where nothing KDE-related has even been started at all.

I strongly suspect that there's some hardware issue involved.

In addition, the HDD information you posted did not include SMART information, i.e. the information relevant to establish your HDD's health.

Please post the output of the following GNU/Linux command (i.e. run this in a Konsole or a text-mode terminal under Fedora):
smartctl --all /dev/sda

You may also want to test your RAM, there should be an option to boot a memory checker (memtest86+) on your live USB stick.

Oh, and what kind of drive is sdc? Is that a HDD? If so, run smartctl on that, too.