I have the same problem. The disk show up under " All Hardware" with the DEVNAME /dev/nvme0n1, but it is not found when I want to move the data disk.
Found out the hard way that WD SN810 is not supported, and used a different brand SSD and it works. Now i cant seem to get ZHA workingā¦
I installed a wd red ssd. When it is in the yellow, the yellow doesnāt start home assistant anymore. Only the red and the green light are constantly on.
Is picking a ssd kind of a lottery?
What can I do? I already sent back a ssd because I thought it was broken.
I have the nvme m.2 
Is it possible that the yellow boots from the new and empty ssd? Because with the ssd installed, it doesnāt work anymore.
1 Like
Good question. It depends on how the boot order is configured in the CM4. I had to change mine to boot from the NVME drive first. 
Thanks for your answer. Do you know how to change the boot order?
I used this guide, as it explains it in detail. It does require a non-windows computer to make the necessary changes. I used another RPi 4 to do so.
1 Like
Hey guys. I have my yellow PoE for a while now but still waiting on the CM4s to arrive. I will try to get another one, more expensive grr, but Iām wondering if thereās any advantage to have an M.2 or the pi ssd is enough.
Is there a noticeable performance boost with the NVMe? Or is there a particular use case that Iām missing?
I should point out that I have a Sinology NAS available on the network so backups would be done there.
Yes, the NVMe drive will be a little quicker than the eMMC which is found on some models of the CM4. Thus, one use case for booting off of an m.2 NVME drive is to allow you to purchase a CM4 without eMMC storage.
Another use is to allow the storage of much larger files. The eMMC maxes out at 32GB, while you can easily add a 1 to 2TB NVMe drive. I run an InfluxDB time-series database as an Add-on. That database can grow fairly larger over time.
Finally, even though eMMC is believed to much better than a microSD cardā¦ I still worry about it failing if one is using it exclusively for Home Assistant. Since it cannot be easily replaced when it wears out, I would choose to not use it exclusively on a HA Yellow. It is fine to install HAOS on the CM4ās eMMC storage, but I would still add a NVMe drive and make it the HAOS āData Diskā to ensure the high volume of write I/O operations only hit the NVMe drive. The NVMe SSDās will support a much higher number of write cycles, especially with wear leveling over a 512MB to 2TB drive. The 32GB eMMC just does not have as many flash memory cells to spread the writes over to prevent failures over time.
Hi everyone! Iām using a Home Assistant Yellow with its 16gb eMMC (the only option I could find with 4GB RAM when buying the CM4 Module). Now Iām interested in upgrading the storage.
I came here to find which model was better, I was thinking of finding something āserver-gradeā, just to have a product that lasts longer. Anyway I donāt do video recording or media sharing, only switches controlling.
I saw a post recommending this model: Kingston NV2 M.2 500GBS NV2S/500G. Any other recommendations? Anything with better āqualityā that has been proven to work fine with the Yellow?
Thanks,
Rodrigo
Edit: Iām thinking of buying a 128 or 256 card, I think a 500 one might be too big, also any comments on this?
- The thread above has several references to known working SSDs - use the search.
- FAQ ā Home Assistant Yellow
1 Like
Thanks @FloatingBoater!
Just one question, if I use the āmove data diskā will it move the whole installation to the NVMe? Or does it just move a part of it (the ādata diskā?) and keep using the eMMC?
Thanks,
R.
The HA OS will stay on the eMMC. While things like the database will be moved to the NVMe drive as part of the Data Disk. This will drastically reduce I/O writes to the eMMC.
1 Like
Hereās the tech details from my own Yellow move data disk:
As already mentioned, the internal eMMC basically only gets writes when you update HASS.
The jury is still out on using the extra user space to fill /media with large files as it makes HASS backups big, slow, and unreliable for some (hence the benefit in 2023.06 from mounting files on a separate NAS - your music and video is available, but not part of HASS backups).
2 Likes
After I used the āmove data diskā command, all the file system seems to have been moved to the NVMe disk:
I thought that the HA OS would lie somewhere under the ā/ā root directory, but maybe Iām wrongā¦ Is there a way to verify where the HA OS really lies after āmove data diskā is executed?
Hi ogiewon. Thanks for the reply. I ordered an CM4 without eMMC and ordered a M.2 to have a proper yellow setup.
1 Like
Based on the official Home Assistant documentation, only the Boot/FW and OS are left on the eMMC after moving the data disk.
Youāve got console access, but the use of Docker containers by HASSOS abstracts and rather hides the actual storage devices - e.g. thereās no lsblk command.
ls /dev/mmc* /dev/nvme* should show the RPiCM4 eMMC (if you have one), and the added NVME SSD.
mount |grep nvme will show the āuserā data patitions on the SSD which you can compare with my version:
Other than that, the System and Storage pages under Settings try to hide the real workings of Linux mounts and devices.
Docker is a bit new for this greybeard sysadmin 
, but root / looks to be really an immutable Docker HASSOS image, with user data mounted underneath.