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.

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

Images | Update all images #2026

Closed
Fourdee opened this issue Aug 20, 2018 · 43 comments
Closed

Images | Update all images #2026

Fourdee opened this issue Aug 20, 2018 · 43 comments

Comments

@Fourdee
Copy link
Collaborator

Fourdee commented Aug 20, 2018

As per:
https://github.com/Fourdee/DietPi/issues/2020

Some users are experiencing this during 1st run, where NTP system fails on their network.

This has been replaced with systemd-timesyncd, which appears more stable and should resolve the above issues. However, all v6.11 or lower images will need updating to have this system by default.

@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

Completed, and, resolved issues with date:

  • 🈯️ RPi
  • 🈯 Asus TB
  • 🈯 RockPro64
  • 🈯️ Odroid C2
  • 🈯️ Rock64
  • 🈯️ NanoPi K1+
  • 🈯️ NanoPi NEO
  • 🈯️ NanoPi NEO2
  • 🈯️ Sparky SBC
  • 🈯️ Odroid XU4
  • 🈯️ PineA64
  • 🈯️ NanoPi M1
  • 🈯️ NanoPi M2
  • 🈯️ NanoPi M3

x86_64

  • 🈯️ VMware Stretch
  • 🈯️ VMware Buster
  • 🈯️ VB Stretch
  • 🈯️ VB Buster

Should not be affected as HW clock
https://github.com/Fourdee/DietPi/issues/1753#issuecomment-420182483

  • 🈯️ All VM's
  • x86_64

bios.forceSetupOnce = "TRUE"

@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

Rock64:

NanoPi M1/M1+:

  • Use existing RootFS, upgrade kernel to 4.x from official image (which runs jessie)

@MichaIng
Copy link
Owner

Actually we switched already to systemd-timesyncd with v6.9.

As time sync should occur on first boot as well before first run update, I am wondering how the error can occur. Maybe something with run_ntpd being called from old dietpi-update but with already new scripts in place. Have to investigate. Hope we can also find a solution for pre v6.9 users, perhaps with a pre-patch that is done before even dietpi-update goes too far, putting new script versions on place.

Rework of emergency patch actually would be it, or updater updating itself in the first place?

@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

ASUS TB | Rock64


🈯️ Fixed with commit in this ticket

  • .network is NULL, yet has connection

Driver always reports state unknown:

3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000

ASUS TB 2.0.7

🈴 WiFi can scan, but fails to connect with both DHCP and STATIC. No errors in dmesg

@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

@MichaIng

Maybe something with run_ntpd being called from old dietpi-update but with already new scripts in place. Have to investigate. Hope we can also find a solution for pre v6.9 users, perhaps with a pre-patch that is done before even dietpi-update goes too far, putting new script versions on place.

Yep, it needs resolving. If i can replicate it during image updates, i'll start debugging.

6.9

Yeah, but, may as well do the lot while we are here 👍

Fourdee referenced this issue Aug 20, 2018
@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

Simple fix for the date issue?

  • on VPS echo date > file
  • EMR patch grab file and set date

Ok, Issue occurs on 1st run, prior to patching, with:

G_CHECK_URL deb.debian.org

When the date is lower than the cert of the site being checked. This only occured for me, when I manually set the date back a couple of years, even on the v6.0 images. I am unable to replicate a failed timesync as of yet.

Therefore, the EMR patch is pointless.


Regardless of the cause (still unknown, most likely NTP issue with some networks?), the only solution is to redo the images. As the issue occurs pre-patching for some users.


Ok this is strange, v6.0 > v6.14 went fine, after reboot the issue occured:

root@DietPi:~# systemctl status systemd-timesyncd -l
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vend
or preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
           └─disable-with-time-daemon.conf
   Active: inactive (dead)
     Docs: man:systemd-timesyncd.service(8)

Nov 03 17:20:15 DietPi systemd[1]: Starting Network Time Synchronization...
Nov 03 17:20:15 DietPi systemd[1]: Started Network Time Synchronization.
Aug 20 23:30:47 DietPi systemd-timesyncd[1413]: Synchronized to time server 193.
150.34.2:123 (0.debian.pool.ntp.org).
Aug 20 23:31:17 DietPi systemd[1]: Stopping Network Time Synchronization...
Aug 20 23:31:17 DietPi systemd[1]: Stopped Network Time Synchronization.
Aug 20 23:31:17 DietPi systemd[1]: Starting Network Time Synchronization...
Aug 20 23:31:17 DietPi systemd[1]: Started Network Time Synchronization.
Aug 20 23:31:17 DietPi systemd-timesyncd[1603]: Synchronized to time server 134.
0.16.1:123 (0.debian.pool.ntp.org).
Aug 20 23:31:19 DietPi systemd[1]: Stopping Network Time Synchronization...
Aug 20 23:31:19 DietPi systemd[1]: Stopped Network Time Synchronization.

Is enabling systemd-timesyncd and removing NTP, rewriting the date to what it was previously with systemd?

And now

[  OK  ] DietPi-Run_ntpd | systemctl restart systemd-timesyncd
Warning: systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.

v6.0 > v6.13
reboot, date is reset

Croot@DietPi:~# date
Thu Nov  3 17:17:02 GMT 2016
root@DietPi:~# systemctl status systemd-timesyncd -l
Warning: systemd-timesyncd.service changed on disk. Run 'systemctl da
emon-reload' to reload units.
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vend
or preset: enabled)
  Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
           └─disable-with-time-daemon.conf
   Active: inactive (dead)
     Docs: man:systemd-timesyncd.service(8)

Fourdee referenced this issue Aug 20, 2018
+General | Resolved an issue where pre v6.9 images, would roll back the clock during the 1st reboot after updating DietPi: https://github.com/Fourdee/DietPi/issues/2026#issuecomment-414475011

+ Force removal of NTP, regardless of NTPD mode set
@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 20, 2018

@MichaIng

🈯️ Time issue resolved with: Fourdee@7635d6c

Cause:

  • Removing NTP and not updating SystemD-TimeSyncD afterwards
  • Date would be rolled back after reboot
  • Sync would then fail as systemd needing daemon-reloading (probably due to NTP removal)

@Fourdee Fourdee modified the milestones: v6.14, v6.15 Aug 20, 2018
@Fourdee Fourdee changed the title Images | Update all images to resolve issues with previous NTP system Images | Update all images Aug 21, 2018
@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 21, 2018

Rock64, after PREP:

Fine until reboot after resize.

root@DietPi:~# cat /var/tmp/dietpi/logs/fs_partition_resize.log
GPT fdisk (gdisk) version 1.0.1

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help):
Expert command (? for help): Relocating backup data structures to the end of the disk

Expert command (? for help):
Command (? for help): Partition number (1-7):
Command (? for help): Partition number (7-128, default 7): First sector (34-31116254, default = 262144) or {+-}size{KMGTP}: Last sector (262144-31116254, default = 31116254) or {+-}size{KMGTP}: Current type is 'Linux filesystem'
Hex code or GUID (L to show codes, Enter = 8300): Changed type of partition to 'Linux filesystem'

Command (? for help): Partition number (1-7): Enter name:
Command (? for help):
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): OK; writing new GUID partition table (GPT) to /dev/mmcblk1.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.
Filesystem at /dev/mmcblk1p7 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/mmcblk1p7 is now 3856763 (4k) blocks long.

Fourdee referenced this issue Aug 21, 2018
+ Update resize script for Rock64:
https://github.com/Fourdee/DietPi/issues/2026#issuecomment-414503323

modified version of ayufan-rock64 resize script. I take no credit for this.
Fourdee referenced this issue Aug 21, 2018
+General | Rock64: Image has been updated to Ayufan 0.7.9. Includes fixes for kernel upgrades via APT: https://github.com/Fourdee/DietPi/issues/2026
@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 21, 2018

Note to self:
BlitterStudio/amiberry#264 (comment)

@Fourdee Fourdee mentioned this issue Aug 21, 2018
Fourdee referenced this issue Aug 21, 2018
**v6.14**
(21/08/18)

**Changes / Improvements / Optimizations:**

DietPi-Software | GLOBAL_PW: The global password used by DietPi-Software is now encrypted with AES-256, removed from '/boot/dietpi.txt' and stored securely on rootFS with root:root/700 access only: https://github.com/Fourdee/DietPi/issues/2021

DietPi-Software | FreshRSS, a self-hosted RSS feed aggregator, now available for installation. Thanks @msongz for requesting an RSS reader: https://github.com/Fourdee/DietPi/issues/1996

DietPi-Software | BruteFIR: Due to low install count (7), we have removed this software from the DietPi database, and, is no longer available for installation.

DietPi-Software | NAA Daemon: Installation updated to 3.5.4-38. Thanks Volpone for the heads up!: https://dietpi.com/phpbb/viewtopic.php?f=11&t=4420

General | '/etc/machine-id' is now unique for each DietPi installation. Regenerated during patch: https://github.com/Fourdee/DietPi/issues/2015

**Bug Fixes:**

DietPi-Drive_Manager | Resolved an issue where custom tmpfs and/or bind entries would be removed during script run: https://github.com/Fourdee/DietPi/issues/2013

DietPi-Software | NAA Daemon : Resolved an issue where this would fail to progress the installation, due to a whiptail prompt behind G_RUN_CMD.

DietPi-Survey/Bugreport | Resolved an issue with failed uploads, due to Cloudflare: https://github.com/Fourdee/DietPi/issues/2022

General | Sparky SBC: Previous patch for RTL8812AU driver support, will be reapplied, as the previous patch did not succeed.

General | Resolved an issue where pre v6.9 images, would roll back the clock during the 1st reboot after updating DietPi: https://github.com/Fourdee/DietPi/issues/2026#issuecomment-414475011

General | Rock64: Image has been updated to Ayufan 0.7.9. Includes fixes for kernel upgrades via APT: https://github.com/Fourdee/DietPi/issues/2026
@Fourdee
Copy link
Collaborator Author

Fourdee commented Aug 22, 2018

As the original issue which caused this ticket to be created, is now resolved, and, the most popular images have been updated, i'll flag this as low priority.

Fourdee referenced this issue Aug 24, 2018
+Many thanks to PINE64, for becoming our 1st Patreon Legend and supporting our project! As one of their rewards, you will see PINE64 displayed on login via the DietPi-Banner.

+General | PineA64: Image updated to v6.14, also contains the latest kernel/uboot by Ayufan (0.6.2): https://github.com/Fourdee/DietPi/issues/2026
@Millichrome
Copy link

In Issue 2020 you mention that it's possible to manually add the date (I am trying to install the 6.9 image on an ASUS tinker board). What file do I have to edit to manually set the date on the SD card?

@MichaIng MichaIng modified the milestones: v6.20, v6.21 Jan 28, 2019
@Fourdee Fourdee modified the milestones: v6.21, v6.22 Feb 7, 2019
@MichaIng
Copy link
Owner

MichaIng commented Feb 8, 2019

@Fourdee
May I add a Odroid C1 Stretch image?

  • I know this means a distro upgrade since Meveric does not offer a Stretch image. However if this can succeed, then via DietPi-PREP. But for sure requires properly cleanup and some testing, e.g. adding as testing/experimental image first and promoting this to users for testing.

More and more issues appear with Jessie not offering required library/package versions, e.g. now Emby: https://github.com/Fourdee/DietPi/issues/2521

Btw great work to update so much images to v6.20, I recognized meanwhile. That as well prevented many users from running into first run update loop due to the updater issue 👍!!

@Fourdee
Copy link
Collaborator Author

Fourdee commented Feb 8, 2019

@MichaIng

May I add a Odroid C1 Stretch image?

Please, I still unable to find mine, most likely in a toy box somewhere (kids lol).

  • I know this means a distro upgrade since Meveric does not offer a Stretch image. However if this can succeed, then via DietPi-PREP

Yep, agree Stretch is preferred. However, software from Meverics APT repo (kernel/kodi etc) may not work.

Although, if above is an issue, update to latest kernel, then remove his APT repo from /etc/apt/sources.list.d

@MichaIng
Copy link
Owner

MichaIng commented Feb 8, 2019

@Fourdee
Ah sorry, I have not Odroid C1 here either 😢. I meant adding it to the ToDo list 😉.

Hmm, kernel packages should work independently from Debian version, at least on RPi this was never an issue (Stretch kernel on Buster, and that time Jessie kernel on Stretch). But of course needs testing.
Are Meverics other repos device specific and for C1 only Jessie available? 🤔 Okay that would be indeed an issue. I mean we can anyway not support it forever, but loosing Kodi and certain media software support is quite a nasty bumper...


From what I can see here it looks fine. C1 specific packages (and kernel) do not require Jessie. All dependencies are >=, non <= where a Stretch package could be too new: http://fuzon.co.uk/meveric/dists/all/c1/binary-armhf/Packages
The software repo source can be switch from jessie to stretch. This is actually something we could/should do automatically within DietPi-PREP based on chosen distro version: https://github.com/Fourdee/DietPi/blob/master/PREP_SYSTEM_FOR_DIETPI.sh#L578

Related new issue: https://github.com/Fourdee/DietPi/issues/2561

@MichaIng
Copy link
Owner

MichaIng commented Mar 8, 2019

Other outdated images

I will do the x86_64 BIOS image the next days, UEFI is currently outside of my possibilities.

@MichaIng MichaIng modified the milestones: v6.22, v6.23 Mar 23, 2019
@MichaIng
Copy link
Owner

MichaIng commented Mar 24, 2019

@MichaIng
Copy link
Owner

MichaIng commented Apr 1, 2019

Updated VirtualBox Stretch image: https://dietpi.com/downloads/images/DietPi_VMware-x86_64-Stretch.7z

Updated VirtualBox Buster image: https://dietpi.com/downloads/images/DietPi_VMware-x86_64-Buster.7z

Links on homepage have been updated as well (manually), since old images are zip instead of 7z.

@MichaIng
Copy link
Owner

MichaIng commented Apr 6, 2019

Updated NativePC BIOS image ready for testing: https://dietpi.com/downloads/testing/DietPi_NativePC-BIOS-x86_64-Stretch.7z

@MichaIng
Copy link
Owner

MichaIng commented Apr 13, 2019

Updated NativePC BIOS image released: https://dietpi.com/downloads/images/DietPi_NativePC-BIOS-x86_64-Stretch.7z

@MichaIng
Copy link
Owner

MichaIng commented May 14, 2019

Updated RPi image ready for testing: https://dietpi.com/downloads/testing/DietPi_RPi-ARMv6-Stretch.7z

@MichaIng MichaIng modified the milestones: v6.24, v6.25 May 15, 2019
@MichaIng
Copy link
Owner

Updated RPi image with yesterday released kernel v4.19 + FIRST Raspbian Buster image available for testing: https://dietpi.com/downloads/testing/

@MichaIng MichaIng modified the milestones: v6.25, v6.26 Jun 24, 2019
@MichaIng
Copy link
Owner

I close this in favour of: #2979

@MichaIng MichaIng removed this from the v6.26 milestone Sep 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants