Drive Manager dead?

Troubleshooting
1

Creating a bug report/issue

Required Information

  • 8.12.1 | cat /boot/dietpi/.version

  • bullseye 0 | echo $G_DISTRO_NAME $G_RASPBIAN
    -5.15.76-v8 | uname -a

  • Power supply used | (EG: 5V 1A RAVpower)

  • SD card used | (EG: SanDisk ultra)

  • RPI Mod B | echo $G_HW_MODEL_NAME or (EG: RPi3)

Additional Information (if applicable)

Steps to reproduce

I wanted to mount the drive from a USB-Hard-Disk. So Dietpi-Config sent me to the “new” Drive Manager but this failed for serveral times.

I sent a report file, too

2

can you share the exact issue you are facing. Drive manager is not dead. It should be working without issues.

3 
│ APT update                                                                                                           │ 
           │  - Command: apt-get -y update                                                                                        │ 
           │  - Exit code: 100                                                                                                    │ 
           │  - DietPi version: v8.12.1 (MichaIng/master) | HW_MODEL: 4 | HW_ARCH: 3 | DISTRO: 6                                  │ 
           │  - Image creator: DietPi Core Team                                                                                   │ 
           │  - Pre-image: from scratch                                                                                           │ 
           │  - Error log:                                                                                                        │ 
           │ Hit:1 https://deb.debian.org/debian bullseye InRelease                                                               │ 
           │ Get:2 https://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]                                             │ 
           │ Get:3 https://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]                                   │ 
           │ Get:4 https://deb.debian.org/debian bullseye-backports InRelease [49.0 kB]                                           │ 
           │ Err:5 https://download.webmin.com/download/repository sarge InRelease                                                │ 
           │   Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.   │ 
           │ Could not handshake: Error in the certificate verification. [IP: 104.207.151.13 443]                                 │ 
           │ Get:6 https://archive.raspberrypi.org/debian bullseye InRelease [23.6 kB]                                            │ 
           │ Reading package lists...                                                                                             │ 
           │ E: Release file for https://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for     │ 
           │ another 7d 17h 14min 22s). Updates for this repository will not be applied.                                          │ 
           │ E: Release file for https://deb.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet        │ 
           │ (invalid for another 7d 22h 7min 7s). Updates for this repository will not be applied.                               │ 
           │ E: Release file for https://deb.debian.org/debian/dists/bullseye-backports/InRelease is not valid yet (invalid for   │ 
           │ another 7d 17h 14min 21s). Updates for this repository will not be applied.                                          │ 
           │ E: Release file for https://archive.raspberrypi.org/debian/dists/bullseye/InRelease is not valid yet (invalid for    │ 
           │ another 7d 14h 24min 15s). Updates for this repository will not be applied.
4

Is it possible, that this failure only happens because I have installed WEBMIN, too?

5

It workd now… after a reboot. Issue can be closed

6

invalid for another 7d 17h 14min 21s)
Seems like your system time was maybe wrong and the reboot invoked a new time sync?!

7

following will correct system time.

/boot/dietpi/func/run_ntpd 1

Usually time sync should be done on reboot and once a day. At least on default system.