Odroid C2 update (from V126 to V127)

[4bob]

Hi Fourdee,

don't remove the #bob lines

Darn! I thought so, too.

Maybe you are disappointed but under /boot is no ramdisk
I use your vm image as well same result here.

Code: Select all

root@C2:/boot# ls -a
.   boot.ini         config.txt  dietpi.txt  initrd.img-3.14.65+   README.md            uInitrd           uInitrd-3.14.65+
..  config-3.14.65+  dietpi      Image       meson64_odroidc2.dtb  System.map-3.14.65+  uInitrd-3.14.29+  vmlinuz-3.14.65+

In any case, I’ll send you the bug report [Reference CODE: 4bob-4bob+randomizing]

Thank you so much.
Bob

[Fourdee]

Hi Bob,

[Reference CODE: 4bob-4bob+randomizing

Nice Thanks for sending.

Maybe you are disappointed but under /boot is no ramdisk

Yep, it should only exist in /DietPi/.ramdisk

Ok, cant see anything ovbious in the report so far.

Please can you run the following command and print results:

Code: Select all

echo 1 > /DietPi/dietpi/bobs_test_file_dietpi.test
/DietPi/dietpi/dietpi-ramdisk 1 # Stop ramdisk

echo 1 > /boot/dietpi/bobs_test_file_boot.test
/DietPi/dietpi/dietpi-ramdisk 0 #Start ramdisk

ls /boot/dietpi/bobs_test_file_boot.test
ls /DietPi/dietpi/bobs_test_file_dietpi.test

rm /boot/dietpi/bobs_test_file_boot.test
rm /DietPi/dietpi/bobs_test_file_dietpi.test

[4bob]

Hi Fourdee,

There you are!

Code: Select all

root@C2:~# echo 1 > /DietPi/dietpi/bobs_test_file_dietpi.test

Code: Select all

root@C2:~# /DietPi/dietpi/dietpi-ramdisk 1
DietPi-Ramdisk: Stopping
DietPi-Ramdisk: Completed

Code: Select all

root@C2:~# echo 1 > /boot/dietpi/bobs_test_file_boot.test

Code: Select all

root@C2:~# /DietPi/dietpi/dietpi-ramdisk 0
DietPi-Ramdisk: Starting
cp: cannot stat ‘/boot/uEnv.txt’: No such file or directory
sed: can't read /DietPi/uEnv.txt: No such file or directory
DietPi-Ramdisk: Completed

Code: Select all

root@C2:~# ls /boot/dietpi/bobs_test_file_boot.test
/boot/dietpi/bobs_test_file_boot.test

Code: Select all

root@C2:~# ls /DietPi/dietpi/bobs_test_file_dietpi.test
/DietPi/dietpi/bobs_test_file_dietpi.test

[Fourdee]

Thanks Bob,

Looks good.

Following are fine, Pine A64 only.

Code: Select all

cp: cannot stat ‘/boot/uEnv.txt’: No such file or directory
sed: can't read /DietPi/uEnv.txt: No such file or directory

So lets try updating again, but instead of rebooting, lets check version is applied to filesystem:


Please do the following:
Update DietPi:

Code: Select all

dietpi-update

Instead of rebooting, restart dietpi-service:

Code: Select all

systemctl stop dietpi-service.service
systemctl start dietpi-service.service

Now check version is updated on filesystem

Code: Select all

cat /boot/dietpi/.version

If version code is v129, try reboot and check it matches these outputs:

Code: Select all

cat /boot/dietpi/.version
cat /DietPi/dietpi/.version

[4bob]

Sorry Fourdee,

still the same .. V126

Code: Select all

- DietPi Update Completed.

- Current Version : 129
- Server Version  : 129

- Please reboot your system now, using the command reboot
root@C2:~# systemctl stop dietpi-service.service
root@C2:~# systemctl start dietpi-service.service
root@C2:~# cat /boot/dietpi/.version
126

Code: Select all

root@C2:~# reboot

Code: Select all

root@C2:~# cat /boot/dietpi/.version
126
root@C2:~# cat /DietPi/dietpi/.version
126

There is no possibility to start a trace or a debug mode for your update service ?

Bob

[Fourdee]

Sorry Fourdee,

still the same .. V126
There is no possibility to start a trace or a debug mode for your update service ?

Bob

Hi Bob,

I'll need to code some extra debugging into the script, leave it with me and i'll let you know when its ready.