MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.89k stars 498 forks source link

Error updating DietPi #5356

Closed doobersn closed 2 years ago

doobersn commented 2 years ago

I run only pihole on my pi zero w on dietpi. Noticed pihole wasnt blocking everything correctly (though some stuff still seems to be blocked) even though status shows everything is fine. So I updated pihole but it made no difference. Tried updating dietpi and it gave me this error:

RPi Zero W (armv6l) | IP: 192.168.1.8Pi-Update ├───────────────────────────────┐
│ APT update                                                                   │
│  - Command: apt-get -q update                                                │
│  - Exit code: 100                                                            │
│  - DietPi version: v7.6.2 (MichaIng/master) | HW_MODEL: 1 | HW_ARCH: 1 |     │
│ DISTRO: 5                                                                    │
│  - Image creator: DietPi Core Team                                           │
│  - Pre-image: Raspbian Lite                                                  │
│  - Error log:                                                                │
│ Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]    │
│ Reading package lists...                                                     │
│ E: Method https has died unexpectedly!                                       │
│ E: Sub-process https received a segmentation fault.                          │
│                                                                              │
│    Retry          : Re-run the last command that failed                 ↑    │
│    DietPi-Config  : Edit network, APT/NTP mirror settings etc           ▮    │
│    Open subshell  : Open a subshell to investigate or solve the issue   ▒    │
│    Send report    : Uploads bugreport containing system info to DietPi  ▒    │
│                   ●─ Devs only ──────────────────────────────────────●  ↓    │
│                                                                              │
│                                                                              │
│                     <Ok>                         <Exit>                      │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

Any suggestions on what to do to fix it? Thank you very much!

Joulinar commented 2 years ago

Can you try following

apt update && apt upgrade

MichaIng commented 2 years ago

We saw this error a few times, but never were able to find out what's causing it and how to resolve:

Must be some issue with an underlying library used by APT or dpkg. The problem is that we cannot reinstall packages due to exactly this error, without rewriting sources.list to use plain HTTP instead of encrypted+authenticated HTTPS. But even stranger, in your case http://raspbian.raspberrypi.org/raspbian was used, as the Raspbian repo is not available via HTTPS, but still the "https" method died. But let's see first the output of Joulinar's commands, to get the full ficture.

doobersn commented 2 years ago

Can you try following

apt update && apt upgrade

I usually try that first. I also tried (I think it was) sudo apt-get update && sudo apt-get dist-upgrade by accident. Here is the output:

dietpi@DietPi:~$ apt update && apt upgrade
Reading package lists... Error!
E: Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
E: can not open /var/lib/apt/lists/raspbian.raspberrypi.org_raspbian_dists_buster_InRelease - fopen (13: Permission denied)
E: The package lists or status file could not be parsed or opened.

That same command with sudo gives me:

dietpi@DietPi:~$ sudo apt update && apt upgrade
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Reading package lists... Done                                                  
E: Method https has died unexpectedly!
E: Sub-process https received a segmentation fault.
doobersn commented 2 years ago

We saw this error a few times, but never were able to find out what's causing it and how to resolve:

Must be some issue with an underlying library used by APT or dpkg. The problem is that we cannot reinstall packages due to exactly this error, without rewriting sources.list to use plain HTTP instead of encrypted+authenticated HTTPS. But even stranger, in your case http://raspbian.raspberrypi.org/raspbian was used, as the Raspbian repo is not available via HTTPS, but still the "https" method died. But let's see first the output of Joulinar's commands, to get the full ficture.

Thanks a lot! Do you think I messed it up by trying sudo apt-get update && sudo apt-get dist-upgrade? I didnt mean to copy and past that, but was googling to see what it did and accidentally did iirc.

Joulinar commented 2 years ago

The issue has no relation to the usage of apt-get

MichaIng commented 2 years ago

Running an APT list update and package upgrade, including distro upgrades, is a common task, not causing such errors. But indirectly, a filesystem corruption or such may have happened. Can you also check:

dmesg -l emerg,alert,crit,err
MichaIng commented 2 years ago

If the above does not give further hints. Please try to reinstall the apt package manually, which includes the method file /usr/lib/apt/methods/https:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/a/apt/apt_1.8.2.3_armhf.deb'
dpkg -i apt_1.8.2.3_armhf.deb
rm apt_1.8.2.3_armhf.deb
doobersn commented 2 years ago

Running an APT list update and package upgrade, including distro upgrades, is a common task, not causing such errors. But indirectly, a filesystem corruption or such may have happened. Can you also check:

dmesg -l emerg,alert,crit,err

For this I got:

dietpi@DietPi:~$ dmesg -l emerg,alert,crit,err
[   17.111755] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip  BCM43430/1
[   17.418007] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   17.418266] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   17.418422] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   17.419743] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[   24.261064] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[   27.525326] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:805: group 25, block bitmap and bg descriptor inconsistent: 7994 vs 10042 free clusters
[  101.610978] mmc0: timeout waiting for hardware interrupt.

Should I go ahead and reinstall the apt package like you mentioned? Thank you so much for helping me!

MichaIng commented 2 years ago

There is at least one filesystem error in the logs, though seems to be not critical and was shortly after boot. However, please do an fsck scan and repair on reboot first:

> /forcefsck
reboot
# after reboot
journalctl -t systemd-fsck

If you have a screen attached: Depending on the SD card size and speed this may take a while. Leave it running, the greenish LED should give a hint about I/O activity, so when it calms down, it's ready for SSH access.

doobersn commented 2 years ago

When

There is at least one filesystem error in the logs, though seems to be not critical and was shortly after boot. However, please do an fsck scan and repair on reboot first:

> /forcefsck
reboot
# after reboot
journalctl -t systemd-fsck

If you have a screen attached: Depending on the SD card size and speed this may take a while. Leave it running, the greenish LED should give a hint about I/O activity, so when it calms down, it's ready for SSH access.

When I try to run > /forcefsck (even with sudo) it says: Permission denied. My gosh, im not cut out for this, haha.

Joulinar commented 2 years ago

Try using root user

MichaIng commented 2 years ago

Ah, do so:

sudo eval '> /forcefsck'

sudo does not span across shell redirects, so those need to be wrapped into eval, a subshell or similar.

doobersn commented 2 years ago

Ah, do so:

sudo eval '> /forcefsck'

sudo does not span across shell redirects, so those need to be wrapped into eval, a subshell or similar.

Alrighty, that gives me:

dietpi@DietPi:~$ sudo eval '> /forcefsck' sudo: eval: command not found dietpi@DietPi:~$ sudo eval > /forcefsck -bash: /forcefsck: Permission denied

I tried with and without the `! Insanity! Thanks for sticking with me through this. :)

Joulinar commented 2 years ago

Try using root user. This will simplify thinks.

MichaIng commented 2 years ago

Or:

sudo dash -c '> /forcefsck'
doobersn commented 2 years ago

Try using root user. This will simplify thinks.

I do sudo -I for that right?

Or:

sudo dash -c '> /forcefsck'

This worked (I think) but didnt say anything. Then when I did reboot it said Failed to connect to bus: No such file or directory. So Im thinking maybe its running? Or maybe not, lol.

MichaIng commented 2 years ago
sudo reboot

How did you reboot before? 😄

doobersn commented 2 years ago
```shell
sudo reboot

How did you reboot before? 😄

🤦‍♂️ Whoops, lol.

Okie dokie so, I'm here now:

dietpi@DietPi:~$ journalctl -t systemd-fsck
Hint: You are currently not seeing messages from other users and the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
No journal files were opened due to insufficient permissions.
dietpi@DietPi:~$ sudo journalctl -t systemd-fsck
Illegal instruction

I wish I knew how to format these posts so it would appear as it does in the terminal. Sorry about that!

MichaIng commented 2 years ago

Use code fences for multi line console pasts, like so:

line 1 line 2

Illegal instruction hmm, that doesn't sound so good. Can you please login as root user and try that again (without sudo)? Also it makes things easier for package reinstalls etc. Does journalctl (without any arguments) return Illegal instructions as well? Also check again dmesg -l emerg,alert,crit,err then.

And let's see whether APT can be repaired now:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/a/apt/apt_1.8.2.3_armhf.deb'
dpkg -i apt_1.8.2.3_armhf.deb
rm apt_1.8.2.3_armhf.deb
/boot/dietpi/func/dietpi-set_software apt-cache clean
apt update
apt upgrade
doobersn commented 2 years ago

O

Use code fences for multi line console pasts, like so:

line 1 line 2

Illegal instruction hmm, that doesn't sound so good. Can you please login as root user and try that again (without sudo)? Also it makes things easier for package reinstalls etc. Does journalctl (without any arguments) return Illegal instructions as well? Also check again dmesg -l emerg,alert,crit,err then.

And let's see whether APT can be repaired now:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/a/apt/apt_1.8.2.3_armhf.deb'
dpkg -i apt_1.8.2.3_armhf.deb
rm apt_1.8.2.3_armhf.deb
/boot/dietpi/func/dietpi-set_software apt-cache clean
apt update
apt upgrade

Ooooh, thank you! Okay, I have no idea how to login as a root user. I tried sudo -I and that was an illegal command. I'm seeing varying things when I google. Should I try this?

You will need to do:

sudo passwd root Then go ahead to set password. Use the root user using

su root

Which honestly the second part makes no sense to me, lol. Man, I hate this! I feel like im taking up too much of your time. I really should just buy a new sd card and reinstall, but it takes so long.

Joulinar commented 2 years ago

How do you login as user dietpi? Simply use user root instead.

doobersn commented 2 years ago

O

Use code fences for multi line console pasts, like so:

line 1 line 2

Illegal instruction hmm, that doesn't sound so good. Can you please login as root user and try that again (without sudo)? Also it makes things easier for package reinstalls etc. Does journalctl (without any arguments) return Illegal instructions as well? Also check again dmesg -l emerg,alert,crit,err then. And let's see whether APT can be repaired now:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/a/apt/apt_1.8.2.3_armhf.deb'
dpkg -i apt_1.8.2.3_armhf.deb
rm apt_1.8.2.3_armhf.deb
/boot/dietpi/func/dietpi-set_software apt-cache clean
apt update
apt upgrade

Ooooh, thank you! Okay, I have no idea how to login as a root user. I tried sudo -I and that was an illegal command. I'm seeing varying things when I google. Should I try this?

You will need to do: sudo passwd root Then go ahead to set password. Use the root user using su root

Which honestly the second part makes no sense to me, lol. Man, I hate this! I feel like im taking up too much of your time. I really should just buy a new sd card and reinstall, but it takes so long.

Logfile attached. Click to expand! ``` root@DietPi:~# journalctl -- Logs begin at Sun 2022-03-13 19:44:08 GMT, end at Sun 2022-03-13 19:45:16 GMT . -- Mar 13 19:44:08 DietPi kernel: Booting Linux on physical CPU 0x0 Mar 13 19:44:08 DietPi kernel: Linux version 5.10.63+ (d om@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GN U ld (GNU Binutils for Ubuntu) 2.34) #1457 Tue Sep 28 11:24:51 BST 2021 Mar 13 19:44:08 DietPi kernel: CPU: ARMv6-compatible processor [410fb767] revisi on 7 (ARMv7), cr=00c5387d Mar 13 19:44:08 DietPi kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT non aliasing instruction cache Mar 13 19:44:08 DietPi kernel: OF: fdt: Machine model: Raspberry Pi Zero W Rev 1 .1 Mar 13 19:44:08 DietPi kernel: random: fast init done Mar 13 19:44:08 DietPi kernel: Memory policy: Data cache writeback Mar 13 19:44:08 DietPi kernel: Reserved memory: created CMA memory pool at 0x1ac 00000, size 64 MiB Mar 13 19:44:08 DietPi kernel: OF: reserved mem: initialized node linux,cma, com patible id shared-dma-pool Mar 13 19:44:08 DietPi kernel: Zone ranges: Mar 13 19:44:08 DietPi kernel: Normal [mem 0x0000000000000000-0x000000001eff ffff] Mar 13 19:44:08 DietPi kernel: Movable zone start for each node Mar 13 19:44:08 DietPi kernel: Early memory node ranges Mar 13 19:44:08 DietPi kernel: node 0: [mem 0x0000000000000000-0x000000001effffff] Mar 13 19:44:08 DietPi kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000001effffff] Mar 13 19:44:08 DietPi kernel: On node 0 totalpages: 126976 Mar 13 19:44:08 DietPi kernel: Normal zone: 1116 pages used for memmap Mar 13 19:44:08 DietPi kernel: Normal zone: 0 pages reserved Mar 13 19:44:08 DietPi kernel: Normal zone: 126976 pages, LIFO batch:31 Mar 13 19:44:08 DietPi kernel: pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 Mar 13 19:44:08 DietPi kernel: pcpu-alloc: [0] 0 Mar 13 19:44:08 DietPi kernel: Built 1 zonelists, mobility grouping on. Total pages: 125860 Mar 13 19:44:08 DietPi kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fb height=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:4B:7B:21 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=cb7b86f7-02 r ootfstype=ext4 fsck.repair=yes rootwait Mar 13 19:44:08 DietPi kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear) Mar 13 19:44:08 DietPi kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear) Mar 13 19:44:08 DietPi kernel: mem auto-init: stack:off, heap alloc:off, heap free:off Mar 13 19:44:08 DietPi kernel: Memory: 423116K/507904K available (8683K kernel code, 1324K rwdata, 2824K rodata, 420K init, 837K bss, 19252K reserved, 65536K cma-reserved) Mar 13 19:44:08 DietPi kernel: SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Mar 13 19:44:08 DietPi kernel: ftrace: allocating 30718 entries in 60 pages Mar 13 19:44:08 DietPi kernel: ftrace: allocated 60 pages with 4 groups Mar 13 19:44:08 DietPi kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 Mar 13 19:44:08 DietPi kernel: random: get_random_bytes called from start_kernel+0x324/0x560 with crng_init=1 Mar 13 19:44:08 DietPi kernel: sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns Mar 13 19:44:08 DietPi kernel: clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns Mar 13 19:44:08 DietPi kernel: bcm2835: system timer (irq = 27) Mar 13 19:44:08 DietPi kernel: Console: colour dummy device 80x30 Mar 13 19:44:08 DietPi kernel: printk: console [tty1] enabled Mar 13 19:44:08 DietPi kernel: Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792) Mar 13 19:44:08 DietPi kernel: pid_max: default: 32768 minimum: 301 Mar 13 19:44:08 DietPi kernel: LSM: Security Framework initializing Mar 13 19:44:08 DietPi kernel: Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) Mar 13 19:44:08 DietPi kernel: Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear) Mar 13 19:44:08 DietPi kernel: cgroup: Disabling memory control group subsystem Mar 13 19:44:08 DietPi kernel: CPU: Testing write buffer coherency: ok Mar 13 19:44:08 DietPi kernel: Setting up static identity map for 0x8200 - 0x8238 Mar 13 19:44:08 DietPi kernel: devtmpfs: initialized Mar 13 19:44:08 DietPi kernel: VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5 Mar 13 19:44:08 DietPi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Mar 13 19:44:08 DietPi kernel: futex hash table entries: 256 (order: -1, 3072 bytes, linear) Mar 13 19:44:08 DietPi kernel: pinctrl core: initialized pinctrl subsystem Mar 13 19:44:08 DietPi kernel: NET: Registered protocol family 16 Mar 13 19:44:08 DietPi kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations Mar 13 19:44:08 DietPi kernel: audit: initializing netlink subsys (disabled) Mar 13 19:44:08 DietPi kernel: thermal_sys: Registered thermal governor 'step_wise' Mar 13 19:44:08 DietPi kernel: hw-breakpoint: found 6 breakpoint and 1 watchpoint registers. Mar 13 19:44:08 DietPi kernel: hw-breakpoint: maximum watchpoint size is 4 bytes. Mar 13 19:44:08 DietPi kernel: Serial: AMBA PL011 UART driver Mar 13 19:44:08 DietPi kernel: audit: type=2000 audit(0.100:1): state=initialized audit_enabled=0 res=1 Mar 13 19:44:08 DietPi kernel: bcm2835-mbox 2000b880.mailbox: mailbox enabled Mar 13 19:44:08 DietPi kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2021-09-28T11:33:07, variant start_cd Mar 13 19:44:08 DietPi kernel: raspberrypi-firmware soc:firmware: Firmware hash is 778b6a4f3c7d8d48bb63c02c47bcfbac79417bea Mar 13 19:44:08 DietPi kernel: Kprobes globally optimized Mar 13 19:44:08 DietPi kernel: bcm2835-dma 20007000.dma: DMA legacy API manager, dmachans=0x1 Mar 13 19:44:08 DietPi kernel: SCSI subsystem initialized Mar 13 19:44:08 DietPi kernel: usbcore: registered new interface driver usbfs Mar 13 19:44:08 DietPi kernel: usbcore: registered new interface driver hub Mar 13 19:44:08 DietPi kernel: usbcore: registered new device driver usb Mar 13 19:44:08 DietPi kernel: clocksource: Switched to clocksource timer Mar 13 19:44:08 DietPi kernel: VFS: Disk quotas dquot_6.6.0 Mar 13 19:44:08 DietPi kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Mar 13 19:44:08 DietPi kernel: FS-Cache: Loaded Mar 13 19:44:08 DietPi kernel: CacheFiles: Loaded Mar 13 19:44:08 DietPi kernel: NET: Registered protocol family 2 Mar 13 19:44:08 DietPi kernel: IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear) Mar 13 19:44:08 DietPi kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) Mar 13 19:44:08 DietPi kernel: TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear) Mar 13 19:44:08 DietPi kernel: TCP bind hash table entries: 4096 (order: 2, 16384 bytes, linear) Mar 13 19:44:08 DietPi kernel: TCP: Hash tables configured (established 4096 bind 4096) Mar 13 19:44:08 DietPi kernel: UDP hash table entries: 256 (order: 0, 4096 bytes, linear) Mar 13 19:44:08 DietPi kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear) Mar 13 19:44:08 DietPi kernel: NET: Registered protocol family 1 Mar 13 19:44:08 DietPi kernel: RPC: Registered named UNIX socket transport module. Mar 13 19:44:08 DietPi kernel: RPC: Registered udp transport module. Mar 13 19:44:08 DietPi kernel: RPC: Registered tcp transport module. Mar 13 19:44:08 DietPi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Mar 13 19:44:08 DietPi kernel: hw perfevents: no irqs for PMU, sampling events not supported Mar 13 19:44:08 DietPi kernel: hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available Mar 13 19:44:08 DietPi kernel: Initialise system trusted keyrings Mar 13 19:44:08 DietPi kernel: workingset: timestamp_bits=14 max_order=17 bucket_order=3 Mar 13 19:44:08 DietPi kernel: zbud: loaded Mar 13 19:44:08 DietPi kernel: FS-Cache: Netfs 'nfs' registered for caching Mar 13 19:44:08 DietPi kernel: NFS: Registering the id_resolver key type Mar 13 19:44:08 DietPi kernel: Key type id_resolver registered Mar 13 19:44:08 DietPi kernel: Key type id_legacy registered Mar 13 19:44:08 DietPi kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering... Mar 13 19:44:08 DietPi kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... Mar 13 19:44:08 DietPi kernel: Key type asymmetric registered Mar 13 19:44:08 DietPi kernel: Asymmetric key parser 'x509' registered Mar 13 19:44:08 DietPi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) Mar 13 19:44:08 DietPi kernel: io scheduler mq-deadline registered Mar 13 19:44:08 DietPi kernel: io scheduler kyber registered Mar 13 19:44:08 DietPi kernel: bcm2708_fb soc:fb: FB found 1 display(s) Mar 13 19:44:08 DietPi kernel: Console: switching to colour frame buffer device 90x30 Mar 13 19:44:08 DietPi kernel: bcm2708_fb soc:fb: Registered framebuffer for display 0, size 720x480 Mar 13 19:44:09 DietPi kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled Mar 13 19:44:09 DietPi kernel: bcm2835-rng 20104000.rng: hwrng registered Mar 13 19:44:09 DietPi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x1fa00000 mem_size:0x20000000(512 MiB) Mar 13 19:44:09 DietPi kernel: gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000 Mar 13 19:44:09 DietPi kernel: brd: module loaded Mar 13 19:44:09 DietPi kernel: loop: module loaded Mar 13 19:44:09 DietPi kernel: Loading iSCSI transport class v2.0-870. Mar 13 19:44:09 DietPi kernel: libphy: Fixed MDIO Bus: probed Mar 13 19:44:09 DietPi kernel: usbcore: registered new interface driver smsc95xx Mar 13 19:44:09 DietPi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Mar 13 19:44:09 DietPi kernel: Core Release: 2.80a Mar 13 19:44:09 DietPi kernel: Setting default values for core params Mar 13 19:44:09 DietPi kernel: Finished setting default values for core params Mar 13 19:44:09 DietPi kernel: Using Buffer DMA mode Mar 13 19:44:09 DietPi kernel: Periodic Transfer Interrupt Enhancement - disabled Mar 13 19:44:09 DietPi kernel: Multiprocessor Interrupt Enhancement - disabled Mar 13 19:44:09 DietPi kernel: OTG VER PARAM: 0, OTG VER FLAG: 0 Mar 13 19:44:09 DietPi kernel: Dedicated Tx FIFOs mode Mar 13 19:44:09 DietPi kernel: Mar 13 19:44:09 DietPi kernel: WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = dad14000 dma = 0x9ad14000 len=9024 Mar 13 19:44:09 DietPi kernel: FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled Mar 13 19:44:09 DietPi kernel: dwc_otg: Microframe scheduler enabled Mar 13 19:44:09 DietPi kernel: Mar 13 19:44:09 DietPi kernel: WARN::hcd_init_fiq:457: FIQ on core 0 Mar 13 19:44:09 DietPi kernel: Mar 13 19:44:09 DietPi kernel: WARN::hcd_init_fiq:458: FIQ ASM at c065c3d8 length 36 Mar 13 19:44:09 DietPi kernel: Mar 13 19:44:09 DietPi kernel: WARN::hcd_init_fiq:497: MPHI regs_base at df810000 Mar 13 19:44:09 DietPi kernel: dwc_otg 20980000.usb: DWC OTG Controller Mar 13 19:44:09 DietPi kernel: dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1 Mar 13 19:44:09 DietPi kernel: dwc_otg 20980000.usb: irq 56, io mem 0x00000000 Mar 13 19:44:09 DietPi kernel: Init: Port Power? op_state=1 Mar 13 19:44:09 DietPi kernel: Init: Power Port (0) Mar 13 19:44:09 DietPi kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 Mar 13 19:44:09 DietPi kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Mar 13 19:44:09 DietPi kernel: usb usb1: Product: DWC OTG Controller Mar 13 19:44:09 DietPi kernel: usb usb1: Manufacturer: Linux 5.10.63+ dwc_otg_hcd Mar 13 19:44:09 DietPi kernel: usb usb1: SerialNumber: 20980000.usb Mar 13 19:44:09 DietPi kernel: hub 1-0:1.0: USB hub found Mar 13 19:44:09 DietPi kernel: hub 1-0:1.0: 1 port detected Mar 13 19:44:09 DietPi kernel: dwc_otg: FIQ enabled Mar 13 19:44:09 DietPi kernel: dwc_otg: NAK holdoff enabled Mar 13 19:44:09 DietPi kernel: dwc_otg: FIQ split-transaction FSM enabled Mar 13 19:44:09 DietPi kernel: Module dwc_common_port init Mar 13 19:44:09 DietPi kernel: usbcore: registered new interface driver usb-storage Mar 13 19:44:09 DietPi kernel: mousedev: PS/2 mouse device common for all mice Mar 13 19:44:09 DietPi kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer Mar 13 19:44:09 DietPi kernel: sdhci: Secure Digital Host Controller Interface driver Mar 13 19:44:09 DietPi kernel: sdhci: Copyright(c) Pierre Ossman Mar 13 19:44:09 DietPi kernel: mmc-bcm2835 20300000.mmcnr: could not get clk, deferring probe Mar 13 19:44:09 DietPi kernel: sdhost-bcm2835 20202000.mmc: could not get clk, deferring probe Mar 13 19:44:09 DietPi kernel: sdhci-pltfm: SDHCI platform and OF driver helper Mar 13 19:44:09 DietPi kernel: ledtrig-cpu: registered to indicate activity on CPUs Mar 13 19:44:09 DietPi kernel: hid: raw HID events driver (C) Jiri Kosina Mar 13 19:44:09 DietPi kernel: usbcore: registered new interface driver usbhid Mar 13 19:44:09 DietPi kernel: usbhid: USB HID core driver Mar 13 19:44:09 DietPi kernel: Initializing XFRM netlink socket Mar 13 19:44:09 DietPi kernel: NET: Registered protocol family 17 Mar 13 19:44:09 DietPi kernel: Key type dns_resolver registered Mar 13 19:44:09 DietPi kernel: registered taskstats version 1 Mar 13 19:44:09 DietPi kernel: Loading compiled-in X.509 certificates Mar 13 19:44:09 DietPi kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver Mar 13 19:44:09 DietPi kernel: mmc-bcm2835 20300000.mmcnr: mmc_debug:0 mmc_debug2:0 Mar 13 19:44:09 DietPi kernel: mmc-bcm2835 20300000.mmcnr: DMA channel allocated Mar 13 19:44:09 DietPi kernel: sdhost: log_buf @ (ptrval) (9ad13000) Mar 13 19:44:09 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Mar 13 19:44:09 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Mar 13 19:44:09 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Mar 13 19:44:09 DietPi kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Mar 13 19:44:09 DietPi kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) Mar 13 19:44:09 DietPi kernel: of_cfs_init Mar 13 19:44:09 DietPi kernel: of_cfs_init: OK Mar 13 19:44:09 DietPi kernel: Waiting for root device PARTUUID=cb7b86f7-02... Mar 13 19:44:09 DietPi kernel: mmc0: host does not support reading read-only switch, assuming write-enable Mar 13 19:44:09 DietPi kernel: mmc0: new high speed SDHC card at address 0007 Mar 13 19:44:09 DietPi kernel: mmcblk0: mmc0:0007 SD32G 28.9 GiB Mar 13 19:44:09 DietPi kernel: mmcblk0: p1 p2 Mar 13 19:44:09 DietPi kernel: EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) Mar 13 19:44:09 DietPi kernel: VFS: Mounted root (ext4 filesystem) readonly on device 179:2. Mar 13 19:44:09 DietPi kernel: devtmpfs: mounted Mar 13 19:44:09 DietPi kernel: Freeing unused kernel memory: 420K Mar 13 19:44:09 DietPi kernel: Kernel memory protection not selected by kernel config. Mar 13 19:44:09 DietPi kernel: Run /sbin/init as init process Mar 13 19:44:09 DietPi kernel: with arguments: Mar 13 19:44:09 DietPi kernel: /sbin/init Mar 13 19:44:09 DietPi kernel: with environment: Mar 13 19:44:09 DietPi kernel: HOME=/ Mar 13 19:44:09 DietPi kernel: TERM=linux Mar 13 19:44:09 DietPi kernel: mmc1: new high speed SDIO card at address 0001 Mar 13 19:44:09 DietPi systemd[1]: System time before build time, advancing clock. Mar 13 19:44:09 DietPi kernel: NET: Registered protocol family 10 Mar 13 19:44:09 DietPi kernel: Segment Routing with IPv6 Mar 13 19:44:09 DietPi systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +K MOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) Mar 13 19:44:09 DietPi systemd[1]: Detected architecture arm. Mar 13 19:44:09 DietPi systemd[1]: Set hostname to . Mar 13 19:44:09 DietPi kernel: random: systemd: uninitialized urandom read (16 bytes read) Mar 13 19:44:09 DietPi kernel: random: systemd: uninitialized urandom read (16 bytes read) Mar 13 19:44:09 DietPi systemd[1]: Started Dispatch Password Requests to Console Directory Watch. Mar 13 19:44:09 DietPi kernel: random: systemd: uninitialized urandom read (16 bytes read) Mar 13 19:44:09 DietPi systemd[1]: Reached target Slices. Mar 13 19:44:09 DietPi systemd[1]: Listening on initctl Compatibility Named Pipe. Mar 13 19:44:09 DietPi systemd[1]: Created slice system-getty.slice. Mar 13 19:44:09 DietPi systemd[1]: Listening on udev Kernel Socket. Mar 13 19:44:09 DietPi systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Mar 13 19:44:09 DietPi systemd[1]: Listening on fsck to fsckd communication Socket. Mar 13 19:44:09 DietPi systemd[1]: Started Apply Kernel Variables. Mar 13 19:44:09 DietPi systemd[1]: Started File System Check on Root Device. Mar 13 19:44:09 DietPi systemd[1]: Starting Remount Root and Kernel File Systems... Mar 13 19:44:09 DietPi systemd-journald[96]: Journal started Mar 13 19:44:09 DietPi systemd-journald[96]: Runtime journal (/run/log/journal/5636630d4cbb49349ed8bba3cee5b706) is 2.9M, max 23.8M, 20.8M free. Mar 13 19:44:09 DietPi systemd[1]: Started Journal Service. Mar 13 19:44:08 DietPi systemd-fsck[99]: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system. Mar 13 19:44:09 DietPi systemd-fsck[99]: fsck failed with exit status 8. Mar 13 19:44:09 DietPi systemd-fsck[99]: Ignoring error. Mar 13 19:44:09 DietPi fake-hwclock[79]: Sun 13 Mar 19:44:07 UTC 2022 Mar 13 19:44:09 DietPi systemd-fsck[99]: Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x6da4d2a6 Mar 13 19:44:09 DietPi systemd-fsck[99]: fsck: Warning... fsck.ext4 for device /dev/mmcblk0p2 exited with signal 11. Mar 13 19:44:10 DietPi systemd[1]: Started Set the console keyboard layout. Mar 13 19:44:10 DietPi kernel: EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended Mar 13 19:44:10 DietPi kernel: EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Mar 13 19:44:10 DietPi systemd[1]: Started Remount Root and Kernel File Systems. Mar 13 19:44:10 DietPi systemd[1]: Starting Load/Save Random Seed... Mar 13 19:44:10 DietPi systemd[1]: Activating swap /var/swap... Mar 13 19:44:10 DietPi systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Mar 13 19:44:10 DietPi systemd[1]: Starting Create System Users... Mar 13 19:44:10 DietPi systemd[1]: Activated swap /var/swap. Mar 13 19:44:10 DietPi kernel: Adding 1605628k swap on /var/swap. Priority:-2 extents:9 across:1884156k SSFS Mar 13 19:44:10 DietPi systemd[1]: Reached target Swap. Mar 13 19:44:10 DietPi systemd[1]: Started udev Coldplug all Devices. Mar 13 19:44:10 DietPi systemd[1]: Starting Helper to synchronize boot up for ifupdown... Mar 13 19:44:11 DietPi systemd[1]: Started Helper to synchronize boot up for ifupdown. Mar 13 19:44:11 DietPi systemd[1]: Started Load/Save Random Seed. Mar 13 19:44:11 DietPi systemd[1]: Started Create System Users. Mar 13 19:44:11 DietPi systemd[1]: Starting Create Static Device Nodes in /dev... Mar 13 19:44:11 DietPi systemd[1]: Started Create Static Device Nodes in /dev. Mar 13 19:44:11 DietPi systemd[1]: Starting udev Kernel Device Manager... Mar 13 19:44:11 DietPi systemd[1]: Reached target Local File Systems (Pre). Mar 13 19:44:11 DietPi systemd[1]: Mounting /tmp... Mar 13 19:44:11 DietPi systemd[1]: Mounting /var/log... Mar 13 19:44:11 DietPi systemd[1]: Mounted /tmp. Mar 13 19:44:11 DietPi systemd[1]: Mounted /var/log. Mar 13 19:44:11 DietPi systemd[1]: Starting Flush Journal to Persistent Storage... Mar 13 19:44:11 DietPi systemd[1]: Started udev Kernel Device Manager. Mar 13 19:44:12 DietPi systemd-journald[96]: Runtime journal (/run/log/journal/5636630d4cbb49349ed8bba3cee5b706) is 2.9M, max 23.8M, 20.8M free. Mar 13 19:44:12 DietPi systemd[1]: Started Flush Journal to Persistent Storage. Mar 13 19:44:14 DietPi kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Mar 13 19:44:15 DietPi kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Mar 13 19:44:15 DietPi kernel: brcmfmac: F1 signature read @0x18000000=0x1541a9a6 Mar 13 19:44:15 DietPi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 Mar 13 19:44:15 DietPi kernel: usbcore: registered new interface driver brcmfmac Mar 13 19:44:16 DietPi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 Mar 13 19:44:16 DietPi kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 Mar 13 19:44:16 DietPi kernel: brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available Mar 13 19:44:16 DietPi kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd Mar 13 19:44:16 DietPi systemd[1]: Found device /dev/disk/by-partuuid/cb7b86f7-01. Mar 13 19:44:17 DietPi systemd-udevd[133]: Using default interface naming scheme 'v240'. Mar 13 19:44:18 DietPi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Mar 13 19:44:18 DietPi systemd[1]: Starting File System Check on /dev/disk/by-partuuid/cb7b86f7-01... Mar 13 19:44:18 DietPi systemd[1]: Starting Load/Save RF Kill Switch Status... Mar 13 19:44:18 DietPi systemd-fsck[188]: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system. Mar 13 19:44:18 DietPi systemd[1]: Found device /sys/subsystem/net/devices/wlan0. Mar 13 19:44:18 DietPi systemd[1]: Started Load/Save RF Kill Switch Status. Mar 13 19:44:19 DietPi systemd-fsck[188]: fsck.fat 4.1 (2017-01-24) Mar 13 19:44:19 DietPi systemd-fsck[188]: /dev/mmcblk0p1: 357 files, 104436/516191 clusters Mar 13 19:44:19 DietPi systemd[1]: Started File System Check on /dev/disk/by-partuuid/cb7b86f7-01. Mar 13 19:44:19 DietPi systemd[1]: Mounting /boot... Mar 13 19:44:20 DietPi systemd[1]: Mounted /boot. Mar 13 19:44:20 DietPi systemd[1]: Reached target Local File Systems. Mar 13 19:44:20 DietPi systemd[1]: Starting Create Volatile Files and Directories... Mar 13 19:44:20 DietPi systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. Mar 13 19:44:20 DietPi systemd[1]: Starting Set console font and keymap... Mar 13 19:44:20 DietPi systemd[1]: Started vmtouch. Mar 13 19:44:20 DietPi systemd[1]: Started Set console font and keymap. Mar 13 19:44:20 DietPi systemd[1]: Started Create Volatile Files and Directories. Mar 13 19:44:20 DietPi systemd[1]: Starting Update UTMP about System Boot/Shutdown... Mar 13 19:44:20 DietPi systemd[1]: Started Update UTMP about System Boot/Shutdown. Mar 13 19:44:20 DietPi systemd[1]: Reached target System Initialization. Mar 13 19:44:20 DietPi systemd[1]: Started Clean PHP session files every 30 mins. Mar 13 19:44:20 DietPi systemd[1]: Started Daily Cleanup of Temporary Directories. Mar 13 19:44:20 DietPi systemd[1]: Reached target Timers. Mar 13 19:44:21 DietPi systemd[1]: Reached target Basic System. Mar 13 19:44:21 DietPi systemd[1]: Starting DietPi-RAMlog... Mar 13 19:44:21 DietPi systemd[1]: Condition check resulted in Turn on SSH if /boot/ssh is present being skipped. Mar 13 19:44:21 DietPi systemd[1]: Starting rng-tools.service... Mar 13 19:44:21 DietPi systemd[1]: Starting dhcpcd on all interfaces... Mar 13 19:44:21 DietPi rng-tools[200]: Starting Hardware RNG entropy gatherer daemon: rngd. Mar 13 19:44:21 DietPi rngd[204]: rngd 2-unofficial-mt.14 starting up... Mar 13 19:44:21 DietPi systemd[1]: Started rng-tools.service. Mar 13 19:44:21 DietPi dhcpcd[201]: Not running dhcpcd because /etc/network/interfaces Mar 13 19:44:21 DietPi dhcpcd[201]: defines some interfaces that will use a Mar 13 19:44:21 DietPi dhcpcd[201]: DHCP client or static address Mar 13 19:44:21 DietPi systemd[1]: dhcpcd.service: Control process exited, code=exited, status=6/NOTCONFIGURED Mar 13 19:44:21 DietPi systemd[1]: dhcpcd.service: Failed with result 'exit-code'. Mar 13 19:44:21 DietPi systemd[1]: Failed to start dhcpcd on all interfaces. Mar 13 19:44:21 DietPi kernel: random: crng init done Mar 13 19:44:21 DietPi kernel: random: 7 urandom warning(s) missed due to ratelimiting Mar 13 19:44:21 DietPi rngd[204]: entropy feed to the kernel ready Mar 13 19:44:21 DietPi systemd[1]: Started DietPi-RAMlog. Mar 13 19:44:21 DietPi systemd[1]: Starting DietPi-PreBoot... Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: DietPi-CPU_set Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: ───────────────────────────────────────────────────── Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: Mode: Applying CPU governor settings: ondemand Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: [ INFO ] DietPi-CPU_set | Setting up_threshold: 50 % Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: [ INFO ] DietPi-CPU_set | Setting sampling_rate: 25000 microseconds Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: [ INFO ] DietPi-CPU_set | Setting sampling_down_factor: 80 Mar 13 19:44:22 DietPi DietPi-PreBoot[213]: [ OK ] DietPi-CPU_set | Applied CPU governor settings: ondemand Mar 13 19:44:22 DietPi systemd[1]: Started DietPi-PreBoot. Mar 13 19:44:22 DietPi systemd[1]: Reached target Network (Pre). Mar 13 19:44:22 DietPi systemd[1]: Starting ifup for wlan0... Mar 13 19:44:22 DietPi systemd[1]: Starting Raise network interfaces... Mar 13 19:44:22 DietPi systemd[1]: Starting DietPi-Boot... Mar 13 19:44:23 DietPi wpa_supplicant[255]: Successfully initialized wpa_supplicant Mar 13 19:44:23 DietPi DietPi-Boot[235]: [ INFO ] DietPi-Boot | Waiting for valid network connection before continuing boot | Mode=1 Mar 13 19:44:23 DietPi kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled Mar 13 19:44:23 DietPi systemd[1]: Started Raise network interfaces. Mar 13 19:44:23 DietPi systemd[1]: systemd-rfkill.service: Succeeded. Mar 13 19:44:24 DietPi DietPi-Boot[235]: [ INFO ] DietPi-Boot | Waiting for valid network connection before continuing boot | Mode=1 Mar 13 19:44:24 DietPi wpa_supplicant[304]: wlan0: Trying to associate with SSID 'netwerkk' Mar 13 19:44:24 DietPi wpa_supplicant[304]: wlan0: Associated with a0:04:60:6c:5a:d2 Mar 13 19:44:25 DietPi wpa_supplicant[304]: wlan0: CTRL-EVENT-CONNECTED - Connection to a0:04:60:6c:5a:d2 completed [id=0 id_str=] Mar 13 19:44:25 DietPi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Mar 13 19:44:25 DietPi wpa_supplicant[304]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Mar 13 19:44:25 DietPi systemd[1]: Started ifup for wlan0. Mar 13 19:44:25 DietPi systemd[1]: Reached target Network. Mar 13 19:44:25 DietPi systemd[1]: Starting Permit User Sessions... Mar 13 19:44:25 DietPi systemd[1]: Reached target Network is Online. Mar 13 19:44:25 DietPi systemd[1]: Starting /etc/rc.local Compatibility... Mar 13 19:44:25 DietPi DietPi-Boot[235]: [ INFO ] DietPi-Boot | Waiting for valid network connection before continuing boot | Mode=1 Mar 13 19:44:25 DietPi systemd[1]: Starting Lighttpd Daemon... Mar 13 19:44:25 DietPi DietPi-Boot[235]: [ OK ] DietPi-Boot | Valid network connection found Mar 13 19:44:25 DietPi systemd[1]: Starting LSB: pihole-FTL daemon... Mar 13 19:44:25 DietPi systemd[1]: Started /etc/rc.local Compatibility. Mar 13 19:44:25 DietPi systemd[1]: Started Permit User Sessions. Mar 13 19:44:25 DietPi pihole-FTL[363]: Not running Mar 13 19:44:26 DietPi su[381]: (to pihole) root on none Mar 13 19:44:26 DietPi su[381]: pam_unix(su:session): session opened for user pihole by (uid=0) Mar 13 19:44:26 DietPi DietPi-Boot[235]: [ .... ] DietPi-Run_NTPD | systemctl restart systemd-timesyncd Mar 13 19:44:26 DietPi kernel: EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:805: group 25, block bitmap and bg descriptor inconsistent: 7994 vs 10042 free clusters Mar 13 19:44:26 DietPi systemd[1]: Starting Network Time Synchronization... Mar 13 19:44:26 DietPi systemd[1]: Started Lighttpd Daemon. Mar 13 19:44:28 DietPi systemd[1]: Started Network Time Synchronization. Mar 13 19:44:28 DietPi DietPi-Boot[235]: [ OK ] DietPi-Run_NTPD | systemctl restart systemd-timesyncd Mar 13 19:44:28 DietPi systemd[1]: Reached target System Time Synchronized. Mar 13 19:44:41 DietPi systemd-timesyncd[387]: Synchronized to time server for the first time 195.22.17.7:123 (0.debian.pool.ntp.org). Mar 13 19:44:42 DietPi pihole-FTL[363]: FTL started! Mar 13 19:44:42 DietPi su[381]: pam_unix(su:session): session closed for user pihole Mar 13 19:44:42 DietPi DietPi-Boot[235]: [ OK ] DietPi-Run_NTPD | systemd-timesyncd synced Mar 13 19:44:42 DietPi systemd[1]: Started LSB: pihole-FTL daemon. Mar 13 19:44:42 DietPi systemd[1]: Stopping Network Time Synchronization... Mar 13 19:44:42 DietPi systemd[1]: systemd-timesyncd.service: Succeeded. Mar 13 19:44:42 DietPi systemd[1]: Stopped Network Time Synchronization. Mar 13 19:44:42 DietPi DietPi-Boot[235]: [ OK ] Network time sync | Completed Mar 13 19:44:42 DietPi systemd[1]: Started DietPi-Boot. Mar 13 19:44:42 DietPi systemd[1]: Started DietPi-PostBoot. Mar 13 19:44:42 DietPi systemd[1]: Started Getty on tty1. Mar 13 19:44:42 DietPi systemd[1]: Reached target Login Prompts. Mar 13 19:44:42 DietPi systemd[1]: Starting LSB: Lightweight SSH server... Mar 13 19:44:43 DietPi dropbear[426]: Starting Dropbear SSH server: dropbear. Mar 13 19:44:43 DietPi systemd[1]: Started LSB: Lightweight SSH server. Mar 13 19:44:43 DietPi dropbear[430]: Running in background Mar 13 19:44:43 DietPi systemd[1]: Reached target Multi-User System. Mar 13 19:44:43 DietPi systemd[1]: Reached target Graphical Interface. Mar 13 19:44:43 DietPi systemd[1]: Starting Update UTMP about System Runlevel Changes... Mar 13 19:44:43 DietPi systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. Mar 13 19:44:43 DietPi systemd[1]: Started Update UTMP about System Runlevel Changes. Mar 13 19:44:43 DietPi systemd[1]: Startup finished in 4.419s (kernel) + 26.512s (userspace) = 30.932s. Mar 13 19:44:44 DietPi systemd[1]: Started Regular background program processing daemon. Mar 13 19:44:44 DietPi cron[449]: (CRON) INFO (pidfile fd = 3) Mar 13 19:44:44 DietPi cron[449]: (CRON) INFO (Running @reboot jobs) Mar 13 19:44:44 DietPi CRON[453]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 13 19:44:44 DietPi CRON[452]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 13 19:44:44 DietPi CRON[456]: (root) CMD (/usr/sbin/logrotate --state /var/lib/logrotate/pihole /etc/pihole/logrotate) Mar 13 19:44:44 DietPi CRON[455]: (root) CMD ( PATH="$PATH:/usr/sbin:/usr/local/bin/" pihole updatechecker remote reboot) Mar 13 19:44:45 DietPi CRON[453]: (CRON) info (No MTA installed, discarding output) Mar 13 19:44:45 DietPi CRON[453]: pam_unix(cron:session): session closed for user root Mar 13 19:44:54 DietPi dropbear[466]: Child connection from 192.168.1.203:61744 Mar 13 19:44:57 DietPi dropbear[466]: Password auth succeeded for 'root' from 192.168.1.203:61744 Mar 13 19:45:03 DietPi systemd[1]: systemd-fsckd.service: Succeeded. Mar 13 19:45:16 DietPi CRON[452]: pam_unix(cron:session): session closed for user root ``` then: ``` root@DietPi:~# dmesg -l emerg,alert,crit,err [ 16.982147] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 17.284429] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 17.284689] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 17.284851] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 17.286148] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd [ 24.430209] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled [ 27.657032] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:805: group 25, block bitmap and bg descriptor inconsistent: 7994 vs 10042 free clusters ``` then ``` root@DietPi:~# cd /tmp root@DietPi:/tmp# curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/a/apt/apt_1.8.2.3_armhf.deb' % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 356 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 1317k 100 1317k 0 0 1348k 0 --:--:-- --:--:-- --:--:-- 2693k root@DietPi:/tmp# dpkg -i apt_1.8.2.3_armhf.deb (Reading database ... 25253 files and directories currently installed.) Preparing to unpack apt_1.8.2.3_armhf.deb ... Unpacking apt (1.8.2.3) over (1.8.2.3) ... Setting up apt (1.8.2.3) ... apt-daily-upgrade.timer is a disabled or a static unit not running, not starting it. apt-daily.timer is a disabled or a static unit not running, not starting it. Processing triggers for libc-bin (2.28-10+rpt2+rpi1) ... root@DietPi:/tmp# rm apt_1.8.2.3_armhf.deb root@DietPi:/tmp# /boot/dietpi/func/dietpi-set_software apt-cache clean DietPi-Set_software ───────────────────────────────────────────────────── Mode: apt-cache (clean) [ OK ] apt-cache clean | Completed root@DietPi:/tmp# apt update Reading package lists... Done E: Method https has died unexpectedly! E: Sub-process https received signal 4. root@DietPi:/tmp# apt upgrade ```
MichaIng commented 2 years ago
systemd-fsck[99]: Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x6da4d2a6

fsck itself fails with a segmentation fault 🤔. Let's try to reinstall it as well:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/e/e2fsprogs/e2fsprogs_1.44.5-1+deb10u3_armhf.deb'
dpkg -i e2fsprogs_1.44.5-1+deb10u3_armhf.deb
rm e2fsprogs_1.44.5-1+deb10u3_armhf.deb

Let's also try to switch to plain HTTP with the RPi repo:

sed -i 's|https://|http://|' /etc/apt/sources.list.d/raspi.list
apt update
doobersn commented 2 years ago
systemd-fsck[99]: Signal (11) SIGSEGV si_code=SEGV_MAPERR fault addr=0x6da4d2a6

fsck itself fails with a segmentation fault 🤔. Let's try to reinstall it as well:

cd /tmp
curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/e/e2fsprogs/e2fsprogs_1.44.5-1+deb10u3_armhf.deb'
dpkg -i e2fsprogs_1.44.5-1+deb10u3_armhf.deb
rm e2fsprogs_1.44.5-1+deb10u3_armhf.deb

Let's also try to switch to plain HTTP with the RPi repo:

sed -i 's|https://|http://|' /etc/apt/sources.list.d/raspi.list
apt update

Alrighty, here's another!

root@DietPi:~# sed -i 's|https://|http://|' /etc/apt/sources.list.d/raspi.list
root@DietPi:~# apt update
Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:4 http://archive.raspberrypi.org/debian buster/main armhf Packages [393 kB]
Get:5 http://raspbian.raspberrypi.org/raspbian buster/contrib armhf Packages [58.8 kB]                                             
Get:6 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages [104 kB]                                             
Get:7 http://raspbian.raspberrypi.org/raspbian buster/rpi armhf Packages [1,360 B]                                                 
Fetched 13.6 MB in 30s (461 kB/s)                                                                                                  
Reading package lists... Done
Building dependency tree       
Reading state information... Done
44 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@DietPi:~# cd /tmp
root@DietPi:/tmp# curl -LO 'http://raspbian.raspberrypi.org/raspbian/pool/main/e/e2fsprogs/e2fsprogs_1.44.5-1+deb10u3_armhf.deb'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0   383    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  519k  100  519k    0     0   610k      0 --:--:-- --:--:-- --:--:-- 1794k
root@DietPi:/tmp# dpkg -i e2fsprogs_1.44.5-1+deb10u3_armhf.deb
(Reading database ... 25253 files and directories currently installed.)
Preparing to unpack e2fsprogs_1.44.5-1+deb10u3_armhf.deb ...
Unpacking e2fsprogs (1.44.5-1+deb10u3) over (1.44.5-1+deb10u3) ...
Setting up e2fsprogs (1.44.5-1+deb10u3) ...
root@DietPi:/tmp# rm e2fsprogs_1.44.5-1+deb10u3_armhf.deb
root@DietPi:/tmp# 

Btw, when you post these commands, can I literally copy and paste them when they are multiple lines? Thank you so so much!

doobersn commented 2 years ago

OMFG!!!!

IT WORKED!!!

Longest install ever but it apparently even fixed the pihole webgui!! THANK YOU @MichaIng! Also thank you to @Joulinar!!!

I think the only thing not correct is the timezone now!

MichaIng commented 2 years ago

I try to have the commands in code blocks so that they can be copy&pasted all together. But it may have some advantage to paste them one by one to have more control.

44 packages can be upgraded. Run 'apt list --upgradable' to see them.

44 packages were waiting for an upgrade, which is the reason it took a while 🙂.

The time zone can be adjusted via dietpi-config or dpkg-reconfigure tzdata.

Great that it worked now. Still, I'd retry the fsck and after that worked try to fix HTTPS for APT:

sudo dash -c '> /forcefsck'
sudo reboot
# after reboot
sudo journalctl -t systemd-fsck
MichaIng commented 2 years ago

Marking this as closed now. Feel free to reopen when required.