Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSD vendor information is missing #810

Closed
ghost opened this issue Oct 23, 2020 · 5 comments
Closed

SSD vendor information is missing #810

ghost opened this issue Oct 23, 2020 · 5 comments

Comments

@ghost
Copy link

ghost commented Oct 23, 2020

reference: https://bugs.kde.org/show_bug.cgi?id=417022
screenshots already posted on link above
recommendation to report this issue at this place

SUMMARY
the following SSD is mounted, but no details are displayed in systemsettings/deviceinfo/deviceviewer/harddrive...

SAMSUNG,970 EVO NVMe SSD, PCIe 3.0 M.2 Typ 2280 - 250 GB

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.1
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Kernel Version: 4.12.14-lp151.99.gcb9ba17-default
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics
Memory: 13,6 GiB

ADDITIONAL INFORMATION
see attached screenshot
see specs at the following link
https://www.samsung.com/us/computing/memory-storage/solid-state-drives/ssd-970-evo-nvme-m-2-250gb-mz-v7e250bw/

fstab.txt
gvfs_mount_oi.txt
mountinfo.txt
qdbus_batt.txt
qdbus_out.txt
skdump_dev_nvme.txt
skdump--save_skdump-output_dev_nvme0n1.txt
solid-hardware5_list_details.txt
solid-hardware5_list_qdbus.txt
udevadm_info.txt
udevadm_monitor--udev--property.txt
udisksctl_dump.txt
udisksctl_monitor.txt
version_of_udisks_gvfs_and_libatasmart.txt

@tbzatek
Copy link
Member

tbzatek commented Oct 30, 2020

Can you provide udevadm info /dev/nvme0n1 and udevadm info /dev/nvme0 please? You should see the ID_MODEL and ID_SERIAL attributes present.

# udevadm info /dev/nvme0n1
P: /devices/pci0000:00/0000:00:1c.4/0000:05:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
S: disk/by-id/nvme-KXG50ZNV512G_NVMe_TOSHIBA_512GB_18GF73OFFQCS
S: disk/by-id/nvme-eui.000000000000001000080d0500056605
E: DEVLINKS=/dev/disk/by-id/nvme-KXG50ZNV512G_NVMe_TOSHIBA_512GB_18GF73OFFQCS /dev/disk/by-id/nvme-eui.000000000000001000080d0500056605
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci0000:00/0000:00:1c.4/0000:05:00.0/nvme/nvme0/nvme0n1
E: DEVTYPE=disk
E: ID_MODEL=KXG50ZNV512G NVMe TOSHIBA 512GB
E: ID_PART_TABLE_TYPE=gpt
E: ID_PART_TABLE_UUID=e358d5c0-b478-436e-8081-5c6d1ddf6ce2
E: ID_SERIAL=KXG50ZNV512G NVMe TOSHIBA 512GB_18GF73OFFQCS
E: ID_SERIAL_SHORT=18GF73OFFQCS
E: ID_WWN=eui.000000000000001000080d0500056605
E: MAJOR=259
E: MINOR=0
E: SUBSYSTEM=block
E: USEC_INITIALIZED=5988952

In any case there's no real support for NVMe devices in UDisks, other than the generic information provided by udev. That should be sufficient for basic presentation though.

Related: #386

@ghost ghost closed this as completed Oct 30, 2020
@ghost
Copy link
Author

ghost commented Oct 30, 2020

@ghost
Copy link
Author

ghost commented Nov 1, 2020

@ghost
Copy link
Author

ghost commented Nov 1, 2020

Sorry, I did not close this issue.

@tbzatek
Copy link
Member

tbzatek commented Nov 2, 2020

Thanks, in this case the ID_MODEL attribute is missing from udev side and ID_SERIAL_SHORT is used as an identifier. Nothing we can do on our side, until custom NVMe probes are implemented (#386).

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant