Update from 6.1 to 6.2 on headless Ryzen PC down now

[NanoPat]

DietPI 6.1 was installed on an AMD Ryzen PC.
The update to 6.2 is completed with an error in diet-process-tool, the rest seemed ok.
However, the /DietPI folder is empty and at login (by SSH) have the following error:
-bash: /DietPi/dietpi/login: No such file or directory
-bash: /DietPi/dietpi/func/dietpi-globals: No such file or directory

All is broken now

[NanoPat]

In addition, the filesystem seems in readonly now:
$ apt-get update
Ign:4 https://deb.debian.org/debian stretch-backports InRelease
Err:5 https://deb.debian.org/debian stretch Release
Could not open file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_stretch_Release - open (30: Read-only file system)

[Fourdee]

In addition, the filesystem seems in readonly now:
$ apt-get update
Ign:4 https://deb.debian.org/debian stretch-backports InRelease
Err:5 https://deb.debian.org/debian stretch Release
Could not open file /var/lib/apt/lists/partial/deb.debian.org_debian_dists_stretch_Release - open (30: Read-only file system)

Check dmesg for filesystem errors. Most likely drive is mounted read only due to failure.

[NanoPat]

Is there a way to fix the upgrade issue ? Since the upgrade to 6.2, diet-xxx commands are no longer available.
Don't know how to retrieve a stable system. All application I've installed are down.

[Fourdee]

Is there a way to fix the upgrade issue ? Since the upgrade to 6.2, diet-xxx commands are no longer available.
Don't know how to retrieve a stable system. All application I've installed are down.

Hi,

The issue is with a read only filesystem. The kernel will automatically set Read only, if it encounters issues with the drive/filesystem.

We need to check kernel + fstab.
Please send us a bug report, and reply with the unique reference code after running the below command:

Code: Select all

dietpi-bugreport

[NanoPat]

Hi Foudee, I'd like to send a bug-report but since the upgrade to 6.2, the folder /DietPi is empty, so I don't know where to find the diet-bugreport command.
I've remounted the filesystem un read-write mode now with the command:
$ mount -o remount,rw /dev/nvme0n1p2 /

I tried an apt-get update but I guess it is not like this I'll can complete the unfinished job of the diet-update command that failed earlier.

root@DietPi:~# apt-get update
Ign:1 https://cdn-aws.deb.debian.org/debian stretch InRelease
Get:2 https://cdn-aws.deb.debian.org/debian stretch-updates InRelease [91.0 kB]
Get:3 https://cdn-aws.deb.debian.org/debian-security stretch/updates InRelease [63.0 kB]
Get:4 https://cdn-aws.deb.debian.org/debian stretch-backports InRelease [91.8 kB]
Hit:5 https://cdn-aws.deb.debian.org/debian stretch Release
Get:7 https://cdn-aws.deb.debian.org/debian-security stretch/updates/main Translation-en [145 kB]
Get:8 https://cdn-aws.deb.debian.org/debian stretch-backports/main amd64 Packages.diff/Index [27.8 kB]
Get:9 https://cdn-aws.deb.debian.org/debian stretch-backports/main i386 Packages.diff/Index [27.8 kB]
Get:10 https://cdn-aws.deb.debian.org/debian stretch-backports/main amd64 Packages 2018-02-23-1422.59.pdiff [802 B]
Get:11 https://cdn-aws.deb.debian.org/debian stretch-backports/main amd64 Packages 2018-02-24-0221.26.pdiff [547 B]
Get:12 https://cdn-aws.deb.debian.org/debian stretch-backports/main amd64 Packages 2018-02-24-0821.34.pdiff [292 B]
Get:12 https://cdn-aws.deb.debian.org/debian stretch-backports/main amd64 Packages 2018-02-24-0821.34.pdiff [292 B]
Get:13 https://cdn-aws.deb.debian.org/debian stretch-backports/main i386 Packages 2018-02-23-2021.17.pdiff [803 B]
Get:14 https://cdn-aws.deb.debian.org/debian stretch-backports/main i386 Packages 2018-02-24-0221.26.pdiff [544 B]
Get:15 https://cdn-aws.deb.debian.org/debian stretch-backports/main i386 Packages 2018-02-24-0821.34.pdiff [294 B]
Get:15 https://cdn-aws.deb.debian.org/debian stretch-backports/main i386 Packages 2018-02-24-0821.34.pdiff [294 B]
Fetched 450 kB in 1s (365 kB/s)
Reading package lists... Done

[Fourdee]

Code: Select all

mount -o remount,rw /dev/nvme0n1p2 /
systemctl start dietpi-ramdisk
systemctl status dietpi-ramdisk -l

If no errors, try sending bug report:

Code: Select all

dietpi-bugreport

[NanoPat]

Thanks, please see result below:
root@DietPi:~# systemctl start dietpi-ramdisk
root@DietPi:~# ls -l /DietPi/
total 16
-rwxr-xr-x 1 root root 2052 Feb 24 16:13 config.txt
drwxr-xr-x 5 root root 1020 Feb 24 16:13 dietpi
-rwxr-xr-x 1 root root 10307 Feb 24 16:13 dietpi.txt
root@DietPi:~# systemctl status dietpi-ramdisk -l
● dietpi-ramdisk.service - DietPi-RAMdisk
Loaded: loaded (/etc/systemd/system/dietpi-ramdisk.service; enabled; vendor preset: enabled)
Active: active (exited) since Sat 2018-02-24 16:13:29 CET; 22s ago
Process: 20707 ExecStart=/bin/bash -c /boot/dietpi/dietpi-ramdisk 0 &>> /var/tmp/dietpi/logs/dietpi-ramdisk.log (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/dietpi-ramdisk.service

Feb 24 16:13:29 DietPi systemd[1]: Starting DietPi-RAMdisk...
Feb 24 16:13:29 DietPi systemd[1]: Started DietPi-RAMdisk.

I've launched dietpi-bugreport:
Reference CODE: 2e7a54e6-263c-4a91-8039-de4f393e8e61-0

[NanoPat]

The splash screen tell me to update from 6.2 to 6.1.
Do you recommend me to downgrade the system ?
Reference CODE: 2e7a54e6-263c-4a91-8039-de4f393e8e61-0

[NanoPat]

Hello, any update ?
Did you receive my submitted logs ?
Thanks.