System crash after apt's update

mitu

Add more info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

The crash happens after you update and reboot or during the apt commands running ?

marcony

Pi Model or other hardware: RPi 3B
Power Supply used: 5v 2A
RetroPie Version Used: 4.5
Built From: Pre made SD Image on RetroPie website - retropie-4.5-rpi2_rpi3.img
USB Devices connected: none
Controller used: none
Error messages received: Stuck on apt (over ssh), and later does not startup again (red light and no green light)

@mitu It crashes after update + reboot :)

Thks

mitu

@marcony Try removing any overclock settings from /boot/config.txt and see if it starts.

marcony

@mitu There's no overclock configuration on the system.

mitu

@marcony Can you post your /boot/config.txt configuration ?

marcony

@mitu

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
hdmi_group=2
hdmi_mode=16

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
gpu_mem_256=128
gpu_mem_512=256
gpu_mem_1024=256
overscan_scale=1

mitu

This doesn't look like a 4.5 image, with the Pi4 sections in it. It doesn't have any overclocks, so that's ok.
Take a look in the Raspberry Pi troubleshooting topic here and see which situations applies to your case.
You could try writing a new 4.7.1 image to see if it boots.

marcony

@mitu It really looks weird.
So, for the path of writing the new image, is there a way to backup settings and modules from this existing retropie installation? So I can reflash all keeping existing things ?

mitu

@marcony said in System crash after apt's update:

So, for the path of writing the new image, is there a way to backup settings and modules from this existing retropie installation? So I can reflash all keeping existing things ?

Re-flashing will overwrite everything on the sdcard. For backup options - see https://retropie.org.uk/docs/Updating-RetroPie/#making-a-backup. Do you have a backup from before the update ?

marcony

@mitu Nothing before the update. Modules can be saved from another system (kodi+cfg, desktop, etc) ?

mitu

If you have a Linux system, yes. Windows cannot read the SDcard's contents. You may take a backup as an .img (with Win32DiskImager, as mentioned in the docs) and try to open it with 7Zip.