Does this systemctl status indicate a problem?

[dfuerpo]

I have just set up a new RPi 4 with a fresh install of Raspbian Buster and PiHole. This was mainly to replace the previous RPi 3B which was my PiHole server. I notice these results from systemctl command and wondered if this indicates a problem:

Code: Select all

pi@raspberrypi:~ $ systemctl status
● raspberrypi
    State: degraded
     Jobs: 0 queued
   Failed: 1 units
    Since: Wed 1969-12-31 19:00:01 EST; 49 years 9 months ago
   CGroup: /
           ├─user.slice
           │ ├─user-1000.slice
           ......

Then this:

Code: Select all

pi@raspberrypi:~ $ systemctl --failed
  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION                          
● rpi-eeprom-update.service loaded failed failed Check for Raspberry Pi EEPROM updates

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

If I try to restart the rpi-eeprom-update.service, I get a similar failed message.
So, is this something I should worry about?

Any help is greatly appreciated.

[DirkS]

Something seems to go wrong with the eeprom version check. I wouldn't worry too much about that...

What is the output of

Code: Select all

systemctl status rpi-eeprom-update.service

[dfuerpo]

Here is that output:

Code: Select all

pi@raspberrypi:~ $ systemctl status rpi-eeprom-update.service
● rpi-eeprom-update.service - Check for Raspberry Pi EEPROM updates
   Loaded: loaded (/lib/systemd/system/rpi-eeprom-update.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-10-27 09:49:05 EDT; 1 day 4h ago
  Process: 9513 ExecStart=/usr/bin/rpi-eeprom-update -a (code=exited, status=2)
 Main PID: 9513 (code=exited, status=2)

Oct 27 09:49:04 raspberrypi systemd[1]: Starting Check for Raspberry Pi EEPROM updates...
Oct 27 09:49:04 raspberrypi rpi-eeprom-update[9513]: CURRENT: Fri 10 May 2019 06:40:36 PM UTC (1557513636)
Oct 27 09:49:04 raspberrypi rpi-eeprom-update[9513]:  LATEST: Tue 10 Sep 2019 10:41:50 AM UTC (1568112110)
Oct 27 09:49:04 raspberrypi rpi-eeprom-update[9513]: *** INSTALLING REQUIRED UPDATE ***
Oct 27 09:49:04 raspberrypi rpi-eeprom-update[9513]: cp: cannot create regular file '/boot/pieeprom.upd': Read-only file system
Oct 27 09:49:04 raspberrypi rpi-eeprom-update[9513]: Failed to copy /tmp/tmp.G6b6rSjFdN to /boot
Oct 27 09:49:05 raspberrypi systemd[1]: rpi-eeprom-update.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 27 09:49:05 raspberrypi systemd[1]: rpi-eeprom-update.service: Failed with result 'exit-code'.
Oct 27 09:49:05 raspberrypi systemd[1]: Failed to start Check for Raspberry Pi EEPROM updates.

Is it because /boot is running as read-only?

UPDATE: That was the problem! I forgot that I had tried using the overlayfs initially but decided against it, but I didn't change the boot partition back to read-write. I changed it back and the rpi-eeprom-update service now starts normally. I feel stupid...

[andrum99]

It seems that your /boot filesystem is mounted as read only. Usually this happens because there is some kind of problem with the filesystem. Just to confirm, can you post the output of the following command - it will attempt to create a new empty file under /boot:

Code: Select all

touch /boot/test123.txt

Also, can you post the output of the following command:

Code: Select all

df -h

[dfuerpo]

See the update to my post above. That was the problem. I changed the /boot partition back to read-write.

Thanks.