I googled a lot and find out, that the error seems to be related to brocken rs-filesystem, which could indicate a broken hdd.
I was able to repair the hdd/fs with fsck.ext4 command and started up as usual (first thing I did, I copied all needed configuration, etc. to external devices). It could be, that it then runs for some hours or longer then 48 h, before the issue appears again.
OK, I came to the conclusion to start from scratch:
I replaced SD-Card with new one, set up a new openhabian on it. Second step I performed was to move ‘root to USB’ with the commands from openhabian-config to a brand-new SSD.
After I reboot, I run exactly in the same error as mention above.
I have a new SD-Card, new SSD, new openhabian installation - why I get this error?
What’s program are you using to make the sd card? On windows etcher is the best. I have seen issues using win32 imager.
Also it will do all the extraction for you no need to do anything else.
What I would try is burn a new sd card with etcher. Power on and leave on for 2 days with no config at all. There is no reason it should have an issue. Once that is stable you can start to configure bindings and such.
The Raspberry Pi Foundation also recommends formatting the card withthe official SD Card Formatter first. I have heard of people resurrecting supposedly dead cards using that.
I can’t say if the official formatter will make a difference or not but I can say that Etcher works on flashing to an SSD. Just make sure to change the setting to allow danger mode.
The point is, it is not the SD-Card, it is the SSD disk. Therefore it is hard for me to believe, that the Formatter would have done a huge difference. But good to know for the next projects.
This would be helpful at the moment, the Raspi 4 would allow boot from USB - this is not supported yet.
Have you tried to load OH on just the SD card, have OH working, then power down the Pi remove the SD and use GParted or some other partition tool to move the root files to SSD manually?