HASS.IO -> transfer from SD card to SSD or USB

So I did a clean 5.8 install (didn’t use the upgrade function from 5.6) with:

RPI 4 4GB
External powered USB3.0 hub with:
Samsung EVO 970 500Gb NvME M.2
SSK Aluminum M.2 NVME SSD Enclosure Adapter, USB 3.1 Gen 2

Everything installed and rebooted fine. This is the first time everything has gone smoothly with this setup.

Here the update from HassOS 5.7 to HassOS 5.8 was done using a USB flash drive and everything is fine. Then update HA from version 0.118.0 to version 2020.12.0 using the user interface and everything went smoothly, everything works fine.Rpi4 8Gb board sata x825 SSD Kingston 120Gb.

Update yesterday to HassOS 5.8 using “ha os update --version=5.8” from ssh. No problems. Today update to 2020.12.0. No problems.

I also updated with this method. But did you make a reboot afterwards?

One reboot, very fast. After couple minutes everything is up and running.

It appears that the Pi is waiting to boot from SD card only and is not trying to boot from SSD - I could be wrong but this seems to be the behaviour that others have reported.

To get it to boot with 5.8, if yours fails to start by itself, remove the SSD and power the Pi on - wait about 5 seconds then plug in the SSD and it should start up.

Tried it, no, it doesn’t work

That’s a shame. It worked here and a friend did the same to restore his.

Ok. You are was partially right. The problem was in USB Zigbee Stick. For some reason system trying to boot from first USB and ignore others USB ports. My fault.

Hey all, just fyi, just upgraded my Rpi setup from SD to SSD. I managed it using this tutorial: https://www.youtube.com/watch?v=Ks-GxF6sd5M. Just follow these instructions, pick the latest stable release for the SSD and it all worked like a charm. Don’t forget to remove the sd card at the end (so it’ll use the SSD for HA). When having the first screen of HA again, if you want to use the recovery, that one worked like a charm as well, but it’ll take a while till it’s all recovered. Just wait a few minutes and try again.

UPDATE: Ok, 1 thing is down still, that’s the ZHA integration with my Conbee II stick. From all of my devices (Aqara motion, Aqara door, Aqara leak, Philips Hue bulbs, Philips Hue motion, Ikea Tradfri, Osram Plug), only the Philips Hue Motion is back after the whole recovery. It seems like there is an issue with that plugin inside the snapshot or something? Anyone familiar with it?

UPDATE 2: I’ve added a usb extension cable between the conbee 2 and my rpi. First I had it directly inserted, but based on the documentation of conbee itself, the recommendation is to add that extension cable. Thanks to the guys on Discord for pointing that out. Also watch out to keep using the same USB port as before, just add the SSD on a free usb port.

Hi all,
I use a Raspberry Pi4 with Home Assistant OS on a SD Card (64Go)
I add a USB external disk (2To). I transfer the data with this method : https://github.com/home-assistant/operating-system/blob/7c70e3ef8491e4abd4123097b7ed6258afda7047/Documentation/partition.md
Everything seems to be good and my installation is still up after reboot. I check files on external drive and they were effectively transfered.
But when I check on Home Assistant UI, disk size is still 64 Go and not 2To (size of the external disk).
I try to copy some files (> 60 Go) on media folder and I have an issue (not enough available space).
Why the size of my installation is still 64 Go ?

Thanks in advance for your answer

I have one question :slight_smile:when you follow these instructions
"Log in as root to get to the Home Assistant CLI and then enter login to continue to the host. "

what do you do after ‘login’. i try to enter root and it mentioned incorrect login.
thanks for your help

I have the same at the beginning(login incorrect). It is not possible to connect via ssh web interface or PuTTY without perform some action :

  1. Enable ssh connection with authorized key (you can generate key with Putty)
  2. Add you public key in your device (with usb drive)

All these actions are described in these two links : DATACTL Tutorial & Enable SSH for developpers

Don’t forget to connect on the 22222 port

So this worked for me.

1st I had to update the firmware of my USB controller, to one that supports NO_UAS. Then I have to boot the pi and unplug/plug the drive and it will boot.

Annoying but at least it is working. hopefully there will be another firmware update from Pi foundation to fix it in the future, if not I may go back to the old firmware

Thank you, this was the only way I could get mine to boot. I’ve now fixed this though by adding the following to the pi eeprom…

USB_MSD_PWR_OFF_TIME=0

https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md

2 Likes

I did an upgrade from OS 5.2 to 5.8 and from 0.118 to 2020.12 via the GUI and all went well and the Pi4 4gb booted up just fine. I have a Intenso SSD and a Sabrent SATA Cable Adapter, USB 3.0.

But now it seems that the whole thing has been crashing every now and then completely. It might be once per day or every two days that Home Assistant completely stops to respond and I have to unplug the power and plug it back in. Then it starts normally. I did notice that if it’s down for a long time (crashed during the night), the Pi is really hot (75 degrees, when it’s maybe 60C normally). Difficult to troubleshoot as the logs do not go far enough or are maybe cleared regarding the host.

Edit: I think this is the issue:

I just started having a similar issue. The only difference I had is I just recently upgraded to an SSD. I did not see any issues with my SD Memory device with the same 5.8 and 2012.7. I only started having this issue once I converted to SSD. I have been running on the SSD for 4 days and had to restart twice.

Hmm, it does seem that it might be SSD related. Then again, I think someone noted somewhere that they are running from an SD card, but maybe this is relevant:

Think I’ll wait for a bit to see if someone figures this out. I guess update to 5.9 should be here shortly too. Downgrading back to 5.2 sounds like the best option for me now, but can’t be the proper solution.

I just froze up again and I have switch back to my SD. I’ll run it a couple of days and see if it has any issues.

Just a wild thought as the issue seem to be related to SSD connected to USB then maybe there is some sort of conflict with other USB devices connected (Zigbee stick, Z-wave stick,…)? My system have only USB music card and seem to work fine.
I am running RPi4B with 4GB on SSD since Dec. 4 (Unitek Y-1039B USB-SSD adapter and Samsung SSD 860EVO 500GB) and yesterday made upgrade to 2020.12.1 and then OS to 5.8 from Supervisor UI. Both went fine in few minutes. Additional reboot with no problems.
And CPU temperature looks OK, peaks when reboot was executed: