Custom Query (993 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (7 - 9 of 993)

1 2 3 4 5 6 7 8 9 10 11 12 13
Ticket Resolution Summary Owner Reporter
#1337 fixed Add OWC Mercury Elite Pro Quad USB ids (0x1e91:0xa4a7) Christian Franke yammering
Description
Index: drivedb.h
===================================================================
--- drivedb.h	(revision 5059)
+++ drivedb.h	(working copy)
@@ -5788,6 +5788,13 @@
     "",
     "-d sat"
   },
+  // 0x1e91 (?)
+  { "USB: OWC Mercury Elite Pro Quad; ",
+    "0x1e91:0xa4a7",
+    "", // 0x0100
+    "",
+    "-d sat"
+  },
   // Innostor
   { "USB: ; Innostor IS611", // USB3->SATA+PATA
     "0x1f75:0x0611", // SMART access via PATA does not work
#1336 fixed Crucial MX500 firmware M3CR032 also returns bogus attribute 197 Christian Franke linux203
Description
May 28 21:44:56 smartd[76153]: Device: /dev/da6 [SAT], 1 Currently unreadable (pending) sectors
May 28 22:14:55 smartd[76153]: Device: /dev/da6 [SAT], No more Currently unreadable (pending) sectors, warning condition reset after 1 email

=== START OF INFORMATION SECTION ===
Model Family:     Crucial/Micron MX500 SSDs
Device Model:     CT1000MX500SSD1
Serial Number:    < snip >
LU WWN Device Id: < snip >
Firmware Version: M3CR032
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri May 29 02:34:27 2020 EDT

similar to ticket:1227 and ticket:1311, but with newer firmware.

#1333 invalid NVMe Support for SMART reporting on VMware vSphere ESXi mc1903
Description

Hi,

I am trying to use smartctl 7.2 2020-04-23 to interrogate my Samsung 970 Pro NVMe PCIe M.2 drives and I am having no luck.

I compiled the executable on an Ubuntu machine, but I am running it on a VMware vSphere ESXi 6.7 host server.

I have two 970 Pro devices installed:

[root@mc-esxi-p-101:/opt/smartmontools] ls -l /dev/disks | grep Samsung
-rw-------    1 root     root      953.9G May 14 21:37 t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500
-rw-------    1 root     root      953.9G May 14 21:37 t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500:1
-rw-------    1 root     root      953.9G May 14 21:37 t10.NVMe____Samsung_SSD_970_PRO_1TB_________________88FAB2915A382500
-rw-------    1 root     root      953.9G May 14 21:37 t10.NVMe____Samsung_SSD_970_PRO_1TB_________________88FAB2915A382500:1
lrwxrwxrwx    1 root     root          68 May 14 21:37 vml.0100000000343046415f423239315f354133385f323530300053616d73756e -> t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500
lrwxrwxrwx    1 root     root          70 May 14 21:37 vml.0100000000343046415f423239315f354133385f323530300053616d73756e:1 -> t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500:1
lrwxrwxrwx    1 root     root          68 May 14 21:37 vml.0100000000383846415f423239315f354133385f323530300053616d73756e -> t10.NVMe____Samsung_SSD_970_PRO_1TB_________________88FAB2915A382500
lrwxrwxrwx    1 root     root          70 May 14 21:37 vml.0100000000383846415f423239315f354133385f323530300053616d73756e:1 -> t10.NVMe____Samsung_SSD_970_PRO_1TB_________________88FAB2915A382500:1
[root@mc-esxi-p-101:/opt/smartmontools]

I seem to be able to open the NVMe device successfully:

[root@mc-esxi-p-101:/opt/smartmontools] ./smartctl --device=nvme /dev/disks/t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500
smartctl 7.2 2020-04-23 r5053 [x86_64-linux-6.7.0] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

NVMe device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

[root@mc-esxi-p-101:/opt/smartmontools]

But when I try to show any information about the drive with -x or -a I get the same error:

[root@mc-esxi-p-101:/opt/smartmontools] ./smartctl -a --device=nvme /dev/disks/t10.NVMe____Samsung_SSD_970_PRO_1TB_________________40FAB2915A382500
smartctl 7.2 2020-04-23 r5053 [x86_64-linux-6.7.0] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: NVME_IOCTL_ADMIN_CMD: Function not implemented
[root@mc-esxi-p-101:/opt/smartmontools]

I know the 970 Pros support SMART reporting, as I was able to interrogate them in the same machine/hardware configuration when it was previously running a Windows 10 OS, admittedly I was using Crystal Disk Info.

Is there anything I can do to get this working or is the NVMe support for SMART reporting in smartctl just not available yet?

Any help will be greatly appreciated.

Many Thanks Martin

1 2 3 4 5 6 7 8 9 10 11 12 13
Note: See TracQuery for help on using queries.