P3608 ssd: lspci OK while fdisk fail to find device.

[llpyh]

My P3608 ssd seems to have some problems recently. lspci works fine and I can find /dev/nvme*n1.

However, fdisk doesn't show this device.

isdct also cannot find information about this disk.

When using fio to test, it works fine without option "direct=1" while fails with it.

Does someone knows what happened to this ssd???

ps. information in details is listed below.

lspci -s 3d:00.0 -vv

3d:00.0 Non-Volatile memory controller: Intel Corporation PCIe Data Center SSD (rev 02) (prog-if 02 [NVM Express])

Subsystem: Intel Corporation DC P3600 SSD [Add-in Card]

Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

Interrupt: pin A routed to IRQ 755

NUMA node: 0

Region 0: Memory at ab100000 (64-bit, non-prefetchable) [size=16K]

Expansion ROM at ab110000 [disabled] [size=64K]

Capabilities: [40] 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: [50] MSI-X: Enable- Count=32 Masked-

Vector table: BAR=0 offset=00002000

PBA: BAR=0 offset=00003000

Capabilities: [60] Express (v2) Endpoint, MSI 00

DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 <4us

ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W

DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-

RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset-

MaxPayload 256 bytes, MaxReadReq 512 bytes

DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-

LnkCap: Port # 0, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <4us, L1 <4us

ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+

LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-

ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-

DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported

AtomicOpsCap: 32bit- 64bit- 128bitCAS-

DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

AtomicOpsCtl: ReqEn-

LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-

Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

Compliance De-emphasis: -6dB

LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+

EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-

Capabilities: [100 v1] Advanced Error Reporting

UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-

UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-

CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-

MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-

HeaderLog: 00000000 00000000 00000000 00000000

Capabilities: [150 v1] Virtual Channel

Caps: LPEVC=0 RefClk=100ns PATEntryBits=1

Arb: Fixed- WRR32- WRR64- WRR128-

Ctrl: ArbSelect=Fixed

Status: InProgress-

VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-

Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-

Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff

Status: NegoPending- InProgress-

Capabilities: [180 v1] Power Budgeting <?>

Capabilities: [190 v1] Alternative Routing-ID Interpretation (ARI)

ARICap: MFVC- ACS-, Next Function: 0

ARICtl: MFVC- ACS-, Function Group: 0

Capabilities: [270 v1] Device Serial Number 55-cd-2e-41-4c-a2-c3-e1

Capabilities: [2a0 v1] # 19

Kernel modules: nvme

[idata]

Hi lpyh,

Thanks for the reply. We will investigate your issue with our additional resources. We will keep you posted with any updates. Regards, Junior M.

[idata]

Hi lpyh,

We would like to let you know that Fedora* is not exactly the same as RedHat*, therefore we recommend you to use the supported operating systems by the SSD: Intel(R) ProvidedWindows* Server 2012 R2,Windows* Server 2008 R2 x64, Windows* 7(32bit/64bit), Windows* 8(32bit/64bit), Windows* 8.1(32bit/64bit).In-box DriverRHEL* 6.5,RHEL* 6.6,RHEL* 6.7,RHEL* 7.0,RHEL* 7.1,SLES11* SP4, Windows* Server 2012 R2,Windows* 8.1,Citrix* Xenserver 6.5,CentOS* 6.5.Please let us know the outcome of your situation. Regards, Junior M.

[llpyh]

Hi，

I prefer to believe that something goes wrong with the hardware. I have tried to put this ssd on different machines and both have problems. What's more, everything is well only several days before. Maybe firmware doesn't so important for this problem. The message "Inappropriate ioctl for device" seems more important.

[idata]

Hi lpyh,

Thanks for the reply. Please keep in mind that you are using an Operating System that is not validated for the SSD so errors are expected. It's possible that this could be a driver issue, since the drives are embedded in the Kernel and driver development happens in the open-source Linux community, we recommend you to contact https://ask.fedoraproject.org/en/questions/ Fedora* support community for further assistance.NOTE: Any links provided for third party tools or sites are offered for your convenience and should not be viewed as an endorsement by Intel® of the content, products, or services offered there. We do not offer support for any third party tool mentioned here.Regards, Junior M.