Lost history after copying HD drive

Configuration
1

Hi
all working nicely , albeit a bit sluggish on an Odroid XU4 , octal SBC like a rasp PI3 ish
I copied the SDcard to an eMMC card with dd
now no history and notifications gives

title: Invalid config
message: The following components and platforms could not be set up:

 - [recorder](https://home-assistant.io/components/recorder/)
 - [history](https://home-assistant.io/components/history/)
 - [logbook](https://home-assistant.io/components/logbook/)

Please check your config.

So I did and read the bits above
my config doesn’t show any errors when check from the UI

updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

I’m up to date with the latest version 0.91.2
pip3 install --upgrade homeassistant says up to date

is there such a thing as pip3 install --reinstall homeassistant ???
or way of reinstalling, dd is a bit by bit copy, so doesn’t make sense.
thanks
Richard

2

It’s odd that it’s calling out recorder and you don’t have recorder in your config file. Have you tried removing those entries and starting up? Are you sure you’re looking at the correct files?

3

its very strange, the config is identical to before.
and definitely looking at configuration.yaml
I wonder if its not a HA problem, I’ve seen odd things happen when cloning cards before, which often go away after a few power cycles.

I’ll give that a try, it may be that simple , if not some head scratching

4

Recorder
History
Logbook

What they have in common is the need to write to a database file located in the config directory.

Maybe it’s a permissions issue? Perhaps the account running Home Assistant lacks write permission to the database?

5

I did wonder about that so I set the permissions to 666, read /write for everyone, no difference on that. I’ll give a few more power cycles , the root device name has changed so it could be that.
PITA

Richard

6

This concept of ‘repeated power-cycling fixes things’ is worrisome. It’s like repeatedly throwing dice until they come up boxcars.

7

… or repeatedly rebooting a Windows box and it starts working. :frowning:

That should almost NEVER be a solution unless the OS kernel is updated.

8

its not a windows box.

restarting is acceptable to allow the OS linux to update the devices attached, in this case the
eMMC card

odroid@odroid:~/.homeassistant$ lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0 14.6G  0 disk 
├─mmcblk0p1  179:1    0  128M  0 part /media/boot
└─mmcblk0p2  179:2    0 14.3G  0 part /
mmcblk0boot0 179:16   0    4M  1 disk 
mmcblk0boot1 179:32   0    4M  1 disk 
mmcblk0rpmb  179:48   0    4M  0 disk

The SDcard was mmcblk1

9

I was referring that rebooting is a generally accepted Microsoft solution that is usually not needed with a sane OS.

As was previously stated, we doubt power cycling will resolve the issue.

10

the problem is the sqlite db has got malformed, so trying to sort it out now

1 Like
11

Just delete the db. Restart Home Assistant and it’ll create a new one.

1 Like
12

Thanks , thats a hell of a lot easier thatn trying to rebuild it using sqlite.
now restarted with the history running

1 Like