{"id":323,"date":"2017-10-23T19:28:58","date_gmt":"2017-10-23T19:28:58","guid":{"rendered":"http:\/\/www.cribbstechnologies.com\/?page_id=323"},"modified":"2017-10-30T20:15:43","modified_gmt":"2017-10-30T20:15:43","slug":"moving-home-assistant-logs","status":"publish","type":"page","link":"https:\/\/www.cribbstechnologies.com\/index.php\/home-assistant\/moving-home-assistant-logs\/","title":{"rendered":"Moving Home Assistant Logs"},"content":{"rendered":"

[et_pb_section bb_built=”1″ admin_label=”Section” fullwidth=”on” specialty=”off”][et_pb_fullwidth_header admin_label=”Fullwidth Header” title=”Moving Home Assistant Logs” subhead=”Stop eating my SD card” background_layout=”light” text_orientation=”left” header_fullscreen=”off” header_scroll_down=”off” parallax=”off” parallax_method=”off” content_orientation=”center” image_orientation=”center” custom_button_one=”off” button_one_letter_spacing=”0″ button_one_use_icon=”default” button_one_icon_placement=”right” button_one_on_hover=”on” button_one_letter_spacing_hover=”0″ custom_button_two=”off” button_two_letter_spacing=”0″ button_two_use_icon=”default” button_two_icon_placement=”right” button_two_on_hover=”on” button_two_letter_spacing_hover=”0″ \/][\/et_pb_section][et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row”][et_pb_column type=”4_4″][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”]<\/p>\n

“Read only file system” “No disk available” Most of us have been there at some time or another. Impatience or ignorance of knowing not shutting down a Raspberry Pi properly can chew up a SD card. Another lesser known issue is that SD cards have a limited lifespan; they only get a certain number of write cycles before they stop working. It’s like that Eddie Murphy movie where he’s only got a limited number of words he can say and they’re counted by leaves on a tree.\"\"<\/p>\n

Because of this write-intensive stuff like logs and databases a card can get worn out\u00a0far<\/em> before it should due to excessive writes. There’s hope! You can use a USB drive and redirect all of this write-heavy activity there and your SD card will be safe.<\/p>\n

[\/et_pb_text][et_pb_text admin_label=”Instructions” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”]<\/p>\n

First you need to figure out where Linux thinks the USB drive lives; in my case it was \/dev\/sda. Plug your drive into your Pi and then run the following command: (Thanks to Tinkerer<\/a> for the better than ‘figure it out’ solution)<\/p>\n

sudo dmesg|tail -n 20|grep sd<\/pre>\n
You’ll get output that will look something like:<\/p>\n
[ 3.773637] sd 0:0:0:0: [sda] 62333952 512-byte logical blocks: (31.9 GB\/29.7 GiB) \r\n[ 3.783125] sd 0:0:0:0: [sda] Write Protect is off \r\n[ 3.791694] sd 0:0:0:0: [sda] Mode Sense: 0b 00 00 08 \r\n[ 3.792618] sd 0:0:0:0: [sda] No Caching mode page found \r\n[ 3.801020] sd 0:0:0:0: [sda] Assuming drive cache: write through \r\n[ 3.817186] sda: sda1 sda2 \u00a0 \r\n<\/pre>\n
Next you’ll create a mount point somewhere on the file system that you’ll use to mount the USB disk.<\/p>\n
sudo mkdir \/mnt\/usb-disk<\/pre>\n
Now you’ll use the mount commad to mount the usb disk to the directory<\/p>\n
sudo mount \/dev\/sda \/mnt\/usb-disk<\/pre>\n
We’ll want to make this permanent so we’ll have to add an fstab entry for it. First we’ll need to figure out what filesystem type to use. We’ll use fdisk to list out our disks<\/p>\n
sudo fdisk -l<\/pre>\n
Find the part where your drive is and it should look something like this:<\/p>\n
Disk \/dev\/sda: 7.5 GiB, 8053063680 bytes, 15728640 sectors\r\nUnits: sectors of 1 * 512 = 512 bytes\r\nSector size (logical\/physical): 512 bytes \/ 512 bytes\r\nI\/O size (minimum\/optimal): 512 bytes \/ 512 bytes\r\nDisklabel type: dos\r\nDisk identifier: 0x6f20736b\r\n<\/pre>\n
If the Disklabel type: says dos it’s FAT32. Otherwise it should spell out what the type is.<\/p>\n
sudo vim \/etc\/fstab<\/pre>\n
You’ll add a new line in the file replacing my example values with your actual values:<\/p>\n
\/dev\/sda \/mnt\/usb-disk fat32 auto<\/pre>\n
The goal here is to move the commonly written stuff to the USB drive to reduce writes to the SD card we’ll move the home-assistant.log and the database to the drive. Shut down home assistant before doing this stuff.<\/p>\n
mv \/home\/homeassistant\/.homeassistant\/home-assistant.log \/mnt\/usb-disk\/ \r\nmv \/home\/homeassistant\/.homeassistant\/home-assistant_v2.db \/mnt\/usb-disk<\/pre>\n
The files are now on the drive but we have to make sure that home assistant can write to them. We’ll create a symbolic link from the Home Assistant config directory to the USB disk<\/p>\n
ln -s \/home\/homeassistant\/.homeassistant\/home-assistant.log \/mnt\/usb-disk\/home-assistant.log \r\nln -s \/home\/homeassistant\/.homeassistant\/home-assistant_v2.db \/mnt\/usb-disk\/home-assistant_v2.db<\/pre>\n
Restart home assistant and make sure everything’s working appropriately. If not, check your permissions on the files on your USB drive. They should be owned by the user that you run Home Assistant as.<\/p>\n
sudo systemctl restart home-assistant.service<\/pre>\n
The logging is a bit trickier. We’ll need to modify the systemd unit for home assistant and add a new configuration file for journalctl. The venv install method already makes sure that the log messages from home assistant are tagged with the identifier ‘hass’. You can check your syslog by editing \/var\/log\/syslog and look for home assistant messages. If they’re already tagged at the beginning with something that looks like Oct 20 06:25:28 ubuntu hass[21411]: you can skip modifying the system unit. To modify the system unit you just need to edit the file:<\/p>\n
sudo vim \/etc\/systemd\/system\/home-assistant.service<\/pre>\n
and add (or modify) the following<\/p>\n
StandardOutput=syslog \r\nSyslogIdentifier=hass<\/pre>\n
This tells it to redirect standard output to the syslog file and to tag the messages with hass.<\/p>\n
Make sure to reload the system unit.<\/p>\n
sudo systemctl daemon-reload<\/pre>\n
Now we need to configure journalctl to split those messages out to a different log location. Create a hass config for journalctl:<\/p>\n
sudo vim \/etc\/rsyslog.d\/hass.conf<\/pre>\n
enter the following and save the file<\/p>\n
if $programname == 'hass' then \/mnt\/usb-disk\/hass-syslog.log<\/pre>\n
restart rsyslog<\/p>\n
sudo systemctl restart rsyslog<\/pre>\n
check to make sure it’s logging appropriately<\/p>\n
tail -f \/mnt\/usb-disk\/hass-syslog.log<\/pre>\n
Everything should be logging and using files on your external drive which should greatly prolong the life of your SD card. Happy automating!<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
[et_pb_section bb_built=”1″ admin_label=”Section” fullwidth=”on” specialty=”off”][et_pb_fullwidth_header admin_label=”Fullwidth Header” title=”Moving Home Assistant Logs” subhead=”Stop eating my SD card” background_layout=”light” text_orientation=”left” header_fullscreen=”off” header_scroll_down=”off” parallax=”off” parallax_method=”off” content_orientation=”center” image_orientation=”center” custom_button_one=”off” button_one_letter_spacing=”0″ button_one_use_icon=”default” button_one_icon_placement=”right” button_one_on_hover=”on” button_one_letter_spacing_hover=”0″ custom_button_two=”off” button_two_letter_spacing=”0″ button_two_use_icon=”default” button_two_icon_placement=”right” button_two_on_hover=”on” button_two_letter_spacing_hover=”0″ \/][\/et_pb_section][et_pb_section bb_built=”1″ admin_label=”section”][et_pb_row admin_label=”row”][et_pb_column type=”4_4″][et_pb_text admin_label=”Text” background_layout=”light” text_orientation=”left” use_border_color=”off” border_color=”#ffffff” border_style=”solid”] “Read only file system” “No disk available” Most […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":364,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-323","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/comments?post=323"}],"version-history":[{"count":7,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/323\/revisions"}],"predecessor-version":[{"id":366,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/323\/revisions\/366"}],"up":[{"embeddable":true,"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/pages\/364"}],"wp:attachment":[{"href":"https:\/\/www.cribbstechnologies.com\/index.php\/wp-json\/wp\/v2\/media?parent=323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}