tomasro
(TURNER HAYES)
March 14, 2023, 7:17am
1
I would like to start generating a list of NVME SSDs that work and don’t work with HA Yellow. I would be happy to update this post with everyone’s input
Good:
Samsung 970 EVO Plus (Gen3 PCIe)
WD Red SN700 (Gen3 PCIe)
Bad:
WD Black SN770 (Gen4 PCIe)
4 Likes
EdwardTFN
(Edward Firmo)
March 14, 2023, 7:22am
2
What do you mean by good
and bad
?
chezzo
July 13, 2023, 10:39pm
5
Thanks for starting this list. A couple of people in the Discord channel mentioned they had issues with the Samsung 980, possibly due to the HMB feature. But the 970 seems like a good option.
oehnstro
(Oskar E)
November 28, 2023, 6:32am
6
Bad: Transcend 240GB M.2 SSD 820S (uses SATA, not NVMe)
kd7vrc
(Steven Brown)
January 14, 2024, 12:51am
7
Bad: WD Blue SN580 (I tried and tried and had no luck)
Good: KingSpec SSD Internal Solid State Drive 128GB M.2 NVMe 2280 PCIe Gen 3.0X4
Samsung 980 Pro 1TB does not work
Patriot P300 128Gb does work
Just tried Patriot P300 256GB, P300P256GM28- DOES NOT WORK.
Samsung 970 EVO Plus 500GB- Works
Samsung 850 Evo does not work - tested with two SSDs.
Samsung 970 EVO Plus MZ-V7S250BW (PCIe Gen 3.0) WORKS (as recommended by FAQ – Home Assistant Yellow )!
Verbatim Vi3000 256 GB (model/part number: 49373, PCIe Gen 3.0) does NOT work!
Here’s a list off NVMe SSD’s I was able to test
Working:
Kioxia BG4 256GB - KBG40ZNS256G
Liteon 256GB - CLI-3D256-Q11
Samsung PM981 512GB - MZVLB512HAJQ-000D1
Samsung PM981a 512GB - MZVLB512HBJQ-000H1
Samsung PM991 256GB - MZALQ256HAJD-000L2
SK hynix BC501 - HFM256GDJTNG-8310A
SK hynix BC511 - HFM256GDGTNI-82ADA
WD SN520 256GB - SDAPTUW-256G-1012
WD SN530 256GB - SDBPNPZ-256G-1006
WD SN740 256GB - SDDPTQD-256G-1012
NOT working:
Micron 2200 256GB - MTFDHBA256TCK
WD SN520 256GB - SDAPNUW-256G-1006
Samsung PM991a 256GB - MZVLQ256HBJD-00BH1
2 Likes
BLShark
(Stanislav)
July 31, 2024, 1:43pm
13
Working
Samsung PM991a 256GB
NOT working
Micron 512GB MTFDKBA512QFM
jurgenh
(Jurgen Hannaert)
August 16, 2024, 8:50pm
14
NOT working: Kingston SNV2S/1000G - NV2 PCIe 4.0 NVMe SSD 1TB
And to make sure, the beheviour in my case is that the ssd shows up in the “Move datadisk” dropdown, but when applying the system reboots and nothing happened. Also as of then the SSD no longer is available in that Move datadisk dropdown. Another reboot (disconnect power) is needed to bring it back there.
Is that similar to other’s experiences about not working?
Nyan
August 24, 2024, 11:06pm
15
Good: Samsung PM981 (Model MZ-VLB1T00)
This is an OEM NVME I salvaged from a work station PC many years back. It is paried with a CM4 Lite. Eveything went smoothly sofar.
Hello there.
Following SSD works.
SSD: Samsung PM991a
Capacity: 128Gb
Manufacturer code: MZALQ128HBHQ
P.S. From data below it reads as MZALQ128HC HQ
Type: M.2 PCIe 2242 NVME
Sample image (from 256Gb model)
Ordered on Allegro, from description - new component from disassembled devices which were never sold.
Data gathered from “Configuration > System > Hardware > All hardware”
Details from mounted drive
nvme0n1
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551
ID
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551
DEVLINKS: >-
/dev/disk/by-diskseq/28
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551_1
/dev/disk/by-id/nvme-eui.002538d51104367c
/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-nvme-1
DEVNAME: /dev/nvme0n1
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1
DEVTYPE: disk
DISKSEQ: ‘28’
ID_MODEL: SAMSUNG MZALQ128HCHQ-00BL2
ID_NSID: ‘1’
ID_PART_TABLE_TYPE: gpt
ID_PART_TABLE_UUID: fa953cb0-b05e-40c2-aaa5-894a5fc2d713
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-nvme-1
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-nvme-1
ID_REVISION: 5L2QFXM7
ID_SERIAL: SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551_1
ID_SERIAL_SHORT: S659NE0R532551
ID_WWN: eui.002538d51104367c
MAJOR: ‘259’
MINOR: ‘0’
SUBSYSTEM: block
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘5864304’
nvme0n1p1
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551-part1
ID
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551-part1
DEVLINKS: >-
/dev/disk/by-diskseq/28-part1
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551-part1
/dev/disk/by-id/nvme-SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551_1-part1
/dev/disk/by-id/nvme-eui.002538d51104367c-part1 /dev/disk/by-label/hassos-data
/dev/disk/by-partlabel/hassos-data-external
/dev/disk/by-partuuid/f2b6373f-221f-4d52-86ac-615bba9a6ea7
/dev/disk/by-path/platform-fd500000.pcie-pci-0000:01:00.0-nvme-1-part1
/dev/disk/by-uuid/c796fc10-0246-4695-8d5a-26eff9c59176
DEVNAME: /dev/nvme0n1p1
DEVPATH: >-
/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/nvme/nvme0/nvme0n1/nvme0n1p1
DEVTYPE: partition
DISKSEQ: ‘28’
ID_FS_BLOCKSIZE: ‘4096’
ID_FS_LABEL: hassos-data
ID_FS_LABEL_ENC: hassos-data
ID_FS_LASTBLOCK: ‘31258368’
ID_FS_SIZE: ‘128034275328’
ID_FS_TYPE: ext4
ID_FS_USAGE: filesystem
ID_FS_UUID: c796fc10-0246-4695-8d5a-26eff9c59176
ID_FS_UUID_ENC: c796fc10-0246-4695-8d5a-26eff9c59176
ID_FS_VERSION: ‘1.0’
ID_MODEL: SAMSUNG MZALQ128HCHQ-00BL2
ID_NSID: ‘1’
ID_PART_ENTRY_DISK: ‘259:0’
ID_PART_ENTRY_NAME: hassos-data-external
ID_PART_ENTRY_NUMBER: ‘1’
ID_PART_ENTRY_OFFSET: ‘2048’
ID_PART_ENTRY_SCHEME: gpt
ID_PART_ENTRY_SIZE: ‘250066944’
ID_PART_ENTRY_TYPE: 0fc63daf-8483-4772-8e79-3d69d8477de4
ID_PART_ENTRY_UUID: f2b6373f-221f-4d52-86ac-615bba9a6ea7
ID_PART_TABLE_TYPE: gpt
ID_PART_TABLE_UUID: fa953cb0-b05e-40c2-aaa5-894a5fc2d713
ID_PATH: platform-fd500000.pcie-pci-0000:01:00.0-nvme-1
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-nvme-1
ID_REVISION: 5L2QFXM7
ID_SERIAL: SAMSUNG_MZALQ128HCHQ-00BL2_S659NE0R532551_1
ID_SERIAL_SHORT: S659NE0R532551
ID_WWN: eui.002538d51104367c
MAJOR: ‘259’
MINOR: ‘1’
PARTN: ‘1’
PARTNAME: hassos-data-external
SUBSYSTEM: block
TAGS: ‘:systemd:’
USEC_INITIALIZED: ‘5864371’
Device
HomeAssistant Yellow 1.3
Software ver
Core 2024.9.1
Supervisor 2024.09.1
Operating System 13.1
GUI 20240906.0
Unfortunately, GUI doesn’t show any “healthiness” or S.M.A.R.T. data from drive.
bwaller
(Billy Waller)
September 30, 2024, 3:45pm
17
Good: Western Digital 1TB WD Blue SN580 NVMe
phvo
(Oliver)
October 9, 2024, 1:41pm
18
Bad: Western Digital 250GB Blue SN580 NVMe (WDS250G3B0E-00CHF0)
Good: SAMSUNG 970 EVO Plus SSD 1TB NVMe (MZ-V7S1T0B/AM)
crsarg
October 23, 2024, 2:54pm
19
Inadvertently bought the same Kingston SNV2S/1000G as @jurgenh .
In my case the data migration worked. Upon reboot, Storage showed 0.4% used of 875.9 GB and in the console I saw that most of the partitions where moved to the /dev/nvme0n1p1
device.
Not working: SAMSUNG PM9B1 MZAL4256HBJD-00BL2 (256 Gb). Shows up as an NVME0 device in hardware overview but I can’t migrate any data to it (“No data disk found”). I don’t understand why it doesn’t work if it does show up as a hardware device. I did a secure wipe but no success
Update: Known not to work according to FAQ – Home Assistant Yellow
Working: Integral SSD 256GM NVME M.2 2280 PCIe Gen3x4 (link to amazon)