Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FAILED Diet-Pi Update | APT upgrade - command : apt-get -qq upgrade #4041

Closed
MeshuggahMischell opened this issue Jan 5, 2021 · 11 comments
Closed

FAILED Diet-Pi Update | APT upgrade - command : apt-get -qq upgrade #4041

MeshuggahMischell opened this issue Jan 5, 2021 · 11 comments

Comments

@MeshuggahMischell
Copy link

Details:

  • Date | Tue Jan 5 12:29:17 GMT 2021
  • DietPi version | v6.33.3 (MichaIng/master)
  • Image creator | DietPi Core Team
  • Pre-image | Raspbian Lite
  • Hardware | RPi 3 Model B+ (armv7l) (ID=3)
  • Kernel version | Linux DietPi 5.4.72-v7+ https not working for Punycode domain #1356 SMP Thu Oct 22 13:56:54 BST 2020 armv7l GNU/Linux
  • Distro | buster (ID=5,RASPBIAN=1)
  • Command | apt-get -qq upgrade
  • Exit code | 100
  • Software title | DietPi-Update

Steps to reproduce:

  1. ...
  2. ...

Expected behaviour:

  • ...

Actual behaviour:

  • ...

Extra details:

  • ...

Additional logs:

W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

root@DietPi:~# dpkg --configure -a
dpkg: error: unable to access the dpkg database directory /var/lib/dpkg: Read-only file system
@MeshuggahMischell
Copy link
Author

just rebooted the Pi isn't responding to any Ping SSH requests whatever ...

@Joulinar
Copy link
Collaborator

Joulinar commented Jan 5, 2021

Hi,

many thanks for your message. Probably your SD card died. Can you connect a screen to see what happen?

@MeshuggahMischell
Copy link
Author

plugged the Pi to my monitor now, but I didn't got display, have to check if the Pi maybe died.
I unplugged the SD Card and tried it on my windows 10 computer and I was able to access and see the files...
Strange...

@Joulinar
Copy link
Collaborator

Joulinar commented Jan 5, 2021 •
edited
Loading

you have a spare SD card? and try a fresh install?

There is a long guide in RPi board to check why a Pi is not booting. As well some error codes on flashing LED https://www.raspberrypi.org/forums/viewtopic.php?t=58151

@MeshuggahMischell
Copy link
Author

Good morning, I just took a new SD Card installed everything from scratch but run into the same problem again.
As soon as I start installing the upgrade the installation fails and the Pi isn't resonding after a reboot.

[FAILED] DietPi-Update | APT upgrade

  • Command: apt-get -qq upgrade
    [ INFO ] DietPi-Update | APT upgrade, please wait...
    W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
    W: Not using locking for read only lock file /var/lib/dpkg/lock
    E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
    [FAILED] DietPi-Update | APT upgrade
  • Command: apt-get -qq upgrade

Details:

  • Date | Wed Jan 6 06:22:18 GMT 2021
  • DietPi version | v6.31.2 (MichaIng/master)
  • Image creator | DietPi Core Team
  • Pre-image | Raspberry Pi OS 64-bit
  • Hardware | RPi 3 Model B+ (aarch64) (ID=3)
  • Kernel version | Linux DietPi 5.4.51-v8+ Rock64 | rootFS re-partition/resize no effect #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64 GNU/Linux
  • Distro | buster (ID=5,RASPBIAN=0)
  • Command | apt-get -qq upgrade
  • Exit code | 100
  • Software title | DietPi-Update

Steps to reproduce:

  1. ...
  2. ...

Expected behaviour:

  • ...

Actual behaviour:

  • ...

Extra details:

  • ...

Additional logs:

W: Not using locking for read only lock file /var/lib/dpkg/lock-frontend
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

[FAILED] DietPi-Update | Unable to continue, DietPi-Update will now terminate.

@MeshuggahMischell
Copy link
Author

I am not able to reinstall it, it starts the Upgrade automatically and runs into this problem over and over again....

@MeshuggahMischell
Copy link
Author

─────────────────────────────────────────────────────
DietPi v6.31.2 : Update available
─────────────────────────────────────────────────────

  • LAN IP : 192.168.178.2 (eth0)
    [ OK ] DietPi-Login | Checking network connectivity
    [ OK ] DietPi-Login | Checking DNS resolver
    [ OK ] Network time sync | Completed
    [FAILED] DietPi-Update | RootFS is currently Read Only (R/O) mounted. Aborting...
    [ INFO ] DietPi-Update | DietPi requires RootFS to be Read/Write (R/W) mounted. Please run "dietpi-drive_manager" to re-enable.

When i run "dietpi-drive_manager" I just get the message " RootFS is currently set to "Read Only (R/O)". DietPi-Drive_Manager requires "Read Write (R/W)" access to function."

How can I set it to R/W ?

@Joulinar
Copy link
Collaborator

Joulinar commented Jan 6, 2021

Hi,
That's basically main issue on your side to have RootFS r/o. Usually this should not be the case. You can try following to mount it r/w
mount -o remount,rw /

@MeshuggahMischell
Copy link
Author

MeshuggahMischell commented Jan 6, 2021 via email

@Joulinar
Copy link
Collaborator

Joulinar commented Jan 6, 2021

running into this problem usually indicates problems (like corruption) on the SD card. But good that it is working now. I will close the issue. Feel free to reopen if needed.

@Joulinar Joulinar closed this as completed Jan 6, 2021
@MichaIng
Copy link
Owner

MichaIng commented Jan 6, 2021

running into this problem usually indicates problems (like corruption) on the SD card.

Seconded, have a regular eye on dmesg -l emerg,alert,crit,err for SD card I/O errors. Possible that there are bad blocks (permanently un-writable parts on the SD card), that is attempted to be written to by chance during APT upgrades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MichaIng @Joulinar @MeshuggahMischell