Micron 1100 SATA SSD not recognized by smartctl

Bug #1802720 reported by Nichita Uțiu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
smartmontools
Unknown
Unknown
smartmontools (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

smartmontools reports that my SDD (a Micron 1100) is not recognized:

Device Model: Micron 1100 SATA 256GB
Serial Number: 18301DB34F37
LU WWN Device Id: 5 00a075 11db34f37
Firmware Version: M0DL022
User Capacity: 256,060,514,304 bytes [256 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: Solid State Device
Form Factor: M.2
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-3 T13/2161-D revision 5
SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sun Nov 11 12:49:43 2018 EET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

lshw -class disk output:

  *-disk
       description: ATA Disk
       product: ST1000LM035-1RK1
       vendor: Seagate
       physical id: 0.0.0
       bus info: scsi@0:0.0.0
       logical name: /dev/sda
       version: SDM3
       serial: ZDEBYFSW
       size: 931GiB (1TB)
       capabilities: gpt-1.00 partitioned partitioned:gpt
       configuration: ansiversion=5 guid=57f4d701-b63c-401f-8a73-d532db8ffd3b logicalsectorsize=512 sectorsize=4096
  *-disk
       description: ATA Disk
       product: Micron 1100 SATA
       physical id: 0.0.0
       bus info: scsi@1:0.0.0
       logical name: /dev/sdb
       version: L022
       serial: 18301DB34F37
       size: 238GiB (256GB)
       capabilities: gpt-1.00 partitioned partitioned:gpt
       configuration: ansiversion=5 guid=262c41c0-0c1f-4c23-bb2b-15ab0baad86a logicalsectorsize=512 sectorsize=4096

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: smartmontools 6.5+svn4324-1 [modified: var/lib/smartmontools/drivedb/drivedb.h]
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 11 13:00:23 2018
InstallationDate: Installed on 2018-11-08 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: smartmontools
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nichita Uțiu (nikita.utiu) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

That usually means the smartmontools DB isn't new enough for your new device.
Could you give the version 6.6 that is in the current Development release of Ubunut (19.04 Disco Dingo) a try if that has an updated device DB that would know yours?

OTOH the 1100 series seems not too new in general.
But that would still mean the tools themselves would not know about it and it would be best to file an upstream bug about that.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I'm sure it'll be helpful to others experiencing the same issue.

This sounds like an upstream bug to me. Please can you verify this by building directly from the latest upstream source (or the 6.6 in Disco that I mentioned)? If this can be confirmed as an upstream bug, the best route to getting it fixed in Ubuntu in this case would be to file an upstream bug if you're able to do that. Otherwise, I'm not sure what we can do directly in Ubuntu to fix the problem.

If you do end up filing an upstream bug, please link to it from here. Thanks!

Changed in smartmontools (Ubuntu):
status: New → Incomplete
Revision history for this message
Nichita Uțiu (nikita.utiu) wrote :

Ok, tested with 6.6, which didn't make much of a difference as I had already updated my drivedb.h to the version found in the 6.6 version. I suspect the issue is due to this line in the database:

    "Micron_1100_MTFDDA[KV](256|512|1T0|2T0)TBN|" // Marvell 88SS1074, tested Micron_1100_MTFDDAK256TBN/M0MU020

As you can see, presumably there exist rules for the model, but the identifier is formatted differently than mine. I will fill n upstream bug report to signal this.

Revision history for this message
Christian Franke (christian-franke) wrote :

Fixed upstream 2018-11-25:
https://www.smartmontools.org/ticket/1131#comment:5
Included in smartmontools-7.0 and in 5.41-6.6 drivedb branches.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.