TrueNAS installation killed Optane drive

[Ericloewe]

Surely not, SMART data applies to the whole device, and I've never seen a case to the contrary.

 

[joeschmuck]

As I mentioned above, BSD and Linux use different commands. Here is a command to try out, you choose the flavor you need:
FreeBSD (CORE)

Code:

nvmecontrol devlist

Debian (SCALE)

Code:

nvme id-ctrl /dev/nvme0 -H

If these do not return something promising then more work needs to be done, likely with the BIOS or USB connection or both.

@1326 Your issue appears to be a BIOS issue. Did you look for a newer BIOS? Also, do not use the RAID setting as that just adds more to look at. AHCI should be fine, and did you try to second M.2 slot if you have one? Also you do not list your Motherboard make/model which is critical so we can look at the user guide and see if you just have the configuration messed up. The BIOS in todays machines has gotten so damn complicated. I really dislike the BIOS in my new server, drives me crazy! Life was easy in the 1990's, only a few things to configure.

 

[1326]

I tried `nvme` but it didn't work. The drive was only showing up in `lspci`, not showing up in `/dev/`

Code:

root@ubuntu:/home/ubuntu# nvme id-ctrl /dev/nvme0 -H
/dev/nvme0: No such file or directory
Usage: nvme id-ctrl <device> [OPTIONS]

Send an Identify Controller command to the given device and report
information about the specified controller in human-readable or binary
format. May also return vendor-specific controller attributes in hex-dump if
requested.

Options:
  [  --vendor-specific, -v ]            --- dump binary vendor infos
  [  --raw-binary, -b ]                 --- show infos in binary format
  [  --human-readable, -H ]             --- show infos in readable format
  [  --output-format=<FMT>, -o <FMT> ]  --- Output format: normal|json|binary
root@ubuntu:/home/ubuntu# ls /dev/nv*
/dev/nvram

And I ordered another M10 and just got it in my mailbox hours ago, I found out that the LBA count is significantly less than my old drive. The left one is the old and problematic one, the right one is the "New" one I just got.

The old one has 31277232 LBA, but the new one only has 28131328.

So here is my motherboard model and BIOS version, it detects the new drive just fine, like it did with the old drive before it dies.


I put the old drive back to the enclousure and connected it to an USB 2 port, still no luck, and got this with `dmesg`, `smartctl` and `nvme`.

Code:

[  145.901233] usb 1-3: new high-speed USB device number 10 using xhci_hcd
[  146.059695] usb 1-3: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01
[  146.059701] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  146.059704] usb 1-3: Product: RTL9210
[  146.059707] usb 1-3: Manufacturer: Realtek
[  146.059710] usb 1-3: SerialNumber: 012345678903
[  146.089807] usb-storage 1-3:1.0: USB Mass Storage device detected
[  146.090303] scsi host5: usb-storage 1-3:1.0
[  147.123516] scsi 5:0:0:0: Direct-Access     Realtek  RTL9210 NVME     1.00 PQ: 0 ANSI: 6
[  147.124110] sd 5:0:0:0: Attached scsi generic sg1 type 0
[  147.130962] sd 5:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  147.130968] sd 5:0:0:0: [sdb] Sense Key : Illegal Request [current]
[  147.130973] sd 5:0:0:0: [sdb] Add. Sense: Invalid command operation code
[  147.130981] sd 5:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[  147.130984] sd 5:0:0:0: [sdb] 0-byte physical blocks
[  147.133110] sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled
[  147.135626] sd 5:0:0:0: [sdb] Asking for cache data failed
[  147.135629] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[  147.165983] sd 5:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[  147.165985] sd 5:0:0:0: [sdb] Sense Key : Illegal Request [current]
[  147.165987] sd 5:0:0:0: [sdb] Add. Sense: Invalid command operation code
[  147.170994] sd 5:0:0:0: [sdb] Attached SCSI removable disk


root@ubuntu:/home/ubuntu# smartctl --all /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.4.0-42-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdb: Unknown USB bridge [0x0bda:0x9210 (0x2001)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

root@ubuntu:/home/ubuntu# nvme id-ctrl /dev/sdb -H
identify controller: Invalid argument

Intel MAS reads the new drive just fine. While keeping everything the same, and just swapped the new M10 with the old M10, Intel MAS only sees the Samsung, but no Intel drive.

I also ordered a PCIE to M.2 adpater card, and will use that going forward, intead of risking another drive by using it with the enclosure.

 

[joeschmuck]

The old one has 31277232 LBA, but the new one only has 28131328.

Odd, but that makes your old drive 16GB and your new to you drive ~14GB. (LBA * 512)

Intel MAS reads the new drive just fine.

Well that is good and bad. Good that your new drive is recognized, bad because now it looks like it the old drive has definitely failed.

 

[1326]

Odd, but that makes your old drive 16GB and your new to you drive ~14GB. (LBA * 512)


Well that is good and bad. Good that your new drive is recognized, bad because now it looks like it the old drive has definitely failed.

Yeah, Intel might quietly updated their firmware to reserve more blocks for spare.

Hopefully this one will last, I received the PCIE->M.2 adapter today and the new stick is already hosting a sqlite database file, so far so good.