Description of problem: When booting rawhide boot.iso from USB stick, the internal mSATA device is missing. Yet I can boot the same kernel version from the mSATA drive itself. Granted, it's F21 using the rawhide kernel, which maybe suggests it's not the kernel but systemd or udev related. But I'm not seeing any ahci messages in early boot when booting from the USB stick. So, I'm confused why it's missing and I'm just guessing it's kernel related. Version-Release number of selected component (if applicable): 3.19.0-0.rc3.git2.1.fc22.x86_64 Fedora_22_Rawhide_20141222_Installation How reproducible: Always Steps to Reproduce: 1. Download boot.iso from https://fedoraproject.org/wiki/Test_Results:Fedora_22_Rawhide_20141222_Installation 2. dd to a USB stick 3. boot USB stick Actual results: Boot the rawhide boot.iso from USB, mSATA is missing. Boot an existing F21 system installed on the mSATA drive but with the same rawhide kernel used by boot.iso, and it boots and of course it sees the mSATA drive. Expected results: Should be visible in any case. Additional info: All of these lines are present when booting from the mSATA drive. They're not present at all when booting from a USB stick. [ 1.361943] ahci 0000:00:1f.2: version 3.0 [ 1.373524] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0x4 impl SATA mode [ 1.373570] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo only pio slum part deso sadm sds apst [ 1.376803] scsi host0: ahci [ 1.377599] scsi host1: ahci [ 1.378226] scsi host2: ahci [ 1.378882] scsi host3: ahci
Created attachment 980270 [details] dmesg USB booting rawhide boot.iso from USB stick
Created attachment 980271 [details] dmesg mSATA booting F21 installed to the mSATA drive, but using the rawhide kernel found in boot.iso
Can you attach the output of lsmod from both the mSATA and USB boots?
hdparm reports the drive as Model Number: KINGSTON X70NR-SMS100S3128GD Serial Number: 50026B72460BC8DF lspci snippet when booted from the mSATA drive: 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04) (prog-if 01 [AHCI 1.0]) Subsystem: Dell Device [1028:060a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 40 Region 0: I/O ports at 3088 [size=8] Region 1: I/O ports at 3094 [size=4] Region 2: I/O ports at 3080 [size=8] Region 3: I/O ports at 3090 [size=4] Region 4: I/O ports at 3060 [size=32] Region 5: Memory at f051c000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0f00c Data: 4181 Capabilities: [70] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004 Kernel driver in use: ahci And when booting from the USB stick.... OK wonderful this is apparently going to be one of those non-deterministic bugs, because there's the internal mSATA drive.
I've rebooted from the USB stick 1/2 dozen times and the internal mSATA drive is there each time. Right before it was MIA it was running Windows 8.1, so I went through various Windows 8.1 > Rawhide boots, cold and warm, to try to get to a missing state again and I can't. It must've been a neutrino... But if I can reproduce it I'll get an lsmod.
OK, thanks. If it happens again, please reopen.
Just happened again, but with Fedora 21 live media, which uses kernel 3.17.4-301.fc21.x86_64. I'll attach lsmod.txt and lspci.txt. The lspci command is completely the SATA controller mentioned in comment 4.
Created attachment 981106 [details] lsmod 3.7.4
Created attachment 981107 [details] lspci -vvnn 3.7.4
I'm pretty sure this is a hardware or firmware problem, not a kernel problem. So I think this can be closed. But for posterity and search karma: Every now and then on warm boots I get a "No bootable devices - strike F1 to retry boot, F2 for setup utility. Press F5 to run onboard diagnostics." F1 does nothing but repeat this error. F2 goes to setup utility where there's no useful information, and backing out sometimes fixes the problem sometimes not. For the first time I tried F5 just now and the onboard diagnostics don't find the drive either. hdparm -I reports Model Number: KINGSTON X70NR-SMS100S3128GD Firmware Revision: S8FM07.3 UEFI firmware has two versions, it's either A06, or Build 4228.21.
Ok, thanks.