there was no error using
/bin/rpi-sysup-online.sh -R downgrade
or
/bin/rpi-sysup-online.sh -R current
now I tried the force command and got:
1 Like
ok thanks... i'll think about whats going on there an improve things...
use old school...
cd /tmp
wget https://rpi4.wulfy23.info/builds/devel/rpi-4_snapshot_3.5.99-25_r17795_extra/rpi4.64-snapshot-26935-3.5.99-25-r17795-ext4-sys.img.gz
sysupgrade -R rpi4.64-snapshot-26935-3.5.99-25-r17795-ext4-sys.img.gz
its still not expanded If I am interpreting the output correctly, right?
1 Like
looks that way... it prints some (debug) messages on a monitor or console if it does not want to do it...
it seems to have worked for most people... i wonder if there is something about your disk thats throwing it off... like sector size or something...
it is ok for me to redo the formatting I am just looking for the correct way to do it - what would you do if it was your device?
i would work with the developer to identify where things are breaking down...
i am ready to do that, how can I proceed?
1 Like
great! it's 3:45am here... you'll have to excuse me for being so slow
- with a keyboard and monitor connected on upgrade you will see the upgrade messages
specifically a line like;
Writing image-partition:1 to /dev/mmcblk0p1... start:8192 size:786432
Writing image-partition:2 to /dev/mmcblk0p2... start:802816 size:1966080
LONG PAUSE
Writing previous PARTUUID[02070430] to /dev/mmcblk0... IMG[10261703]
Tue Oct 26 07:02:46 UTC 2021 upgrade: rootfs:mmcblk0p2 noresize: rootfsexpand[off] [ok: cnt:mmcblk0(2) LABEL=rootfs sz:196608]
Tue Oct 26 07:02:46 UTC 2021 upgrade: 02070430 [ptuuid-ok]
...
Rebooting system
you might have to be ready with your smart phone to take a shot
if you see this text;
noresize
it means it's something with the logic and what follows says why...
now to answer your alternate query... under the hood all it runs is;
parted /dev/${diskdev} resizepart 2 100%
BUT if your /boot/cmdline.txt root= is still set to PARTUUID it wont boot if you try to do that manually... change root= back to root=/dev/mmcblk0p1 if you are feeling like attempting this...
gee... you are quick!
your disk has 3 partitions... so we can't expand it as it's been modified...
if you use sysupgrade -R -p imagename it may work...
im not sure I understand what you are trying to convey x) - what can I do to fix it?
you added a partition in the past?
im not 100% sure to be honest, i had to do a lot of installs and reinstalls until i finally had it working - how can I get this setup cleanly without losing my entire configuration for wifi/ethernet etc?
1 Like
try what I suggested...
winner like a chicken dinner 
2 Likes
thanks man really appreciate the help, even though it was so late - maybe you can leave a note about this command in the readme, im sure it would help others in eventual similar situations, sleep well 
1 Like
Hello all !!
I want to know if there is some limitation to crontab on the build ?
i'm trying to insert the following command on system>scheduled tasks:
1 */2 * * * /mnt/sda2/zspotify-main/zspotify-ls.sh
the script content is just this:
python zspotify -ls
i've already chmod +x it.
it should run every 2hours and 1 minute a python script that downloads some musics from my account on spotify to the external hard drive connected to the pi.
when i check with crontab -l i can see the new line.
When i ssh and go to the folder and type python zspotify it works fine, it downloads without a problem.
But after i restart the pi, and wait for 2,3 or 4 hours, nothing happens.
any advice ?
sounds like just a normal 'env/shebang' or whatever issue ( aka you've done all tests yet its not running from the cron context )...
tips
quite a few threads on forum about tracking down / debugging this type of thing... maybe start with just
/usr/bin/python /path/to/zspotify -ls 2>&1 | /usr/bin/logger
in crontab
ouch! when testing... please change the interval to every minute or two!