Welcome! Log In Create A New Profile

Advanced

Upgrading to Debian stretch and buster

Posted by bodhi 
Re: Upgrading to Debian stretch
January 30, 2018 01:50PM
Now I have set the label as told to rootfs correctly.

root@debian:~# e2label /dev/sdb1
rootfs
root@debian:~#

But still I have no luck. :( The kernel failed to run. The LED color is still amber.

Yes, I don't have a serial console with a physical cable attached. At the moment I can only use the netconsole as mentioned in the other thread.

Any chance to get it work? :)

Tom
Re: Upgrading to Debian stretch
January 30, 2018 04:27PM
Tom,

> Yes, I don't have a serial console with a physical
> cable attached. At the moment I can only use the
> netconsole as mentioned in the other thread.
>
> Any chance to get it work? :)

It is quite easy to run a new rootfs using Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 from the release thread:
https://forum.doozan.com/read.php?2,12096

Your current rootfs must have something wrong that we cannot see easily without serial console. So if you need to keep your current rootfs and only upgrade, I think you should connect serial console. After that, this problem can be solved in a few minutes.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Upgrading to Debian stretch
January 31, 2018 04:48PM
Strange....

The Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi is also not working. Same behavior as before with the other kernel.

Maybe still an incorrect environment var?

arcNumber=2097
baudrate=115200
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=00:10:75:1A:B8:8D
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
if_netconsole=ping $serverip
ipaddr=192.168.0.16
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
ncip=192.168.0.1
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=1
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.0.1
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Environment size: 2839/131068 bytes
u-boot>>
Tom
Re: Upgrading to Debian stretch
January 31, 2018 05:53PM
Tom,

We are going way off topic here. So please create a new thread for this booting problem and post the complete boot log of your attempt to boot Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Upgrading to Debian stretch
September 05, 2019 09:08PM
Not sure if this will help anyone but putting it out there, running Pogoplug pro v3 effectively with Debian 10 Buster, all I did was changed the etc/apt/sources.list with the following:

deb http://deb.debian.org/debian/ stable main contrib non-free
deb-src http://deb.debian.org/debian/ stable main contrib non-free

deb http://deb.debian.org/debian/ stable-updates main contrib non-free
deb-src http://deb.debian.org/debian/ stable-updates main contrib non-free

then run

apt-get update
apt-get dist-upgrade

have had no issues for the last month and switched it to my main machine after testing.
I also took a stab at testing Debian 11 Bullseye on my test machine after that and it works well thus far but it is still in the test phase so I would not recommend using it on a production machine.

learning is living! Echowarrior108
Re: Upgrading to Debian stretch
September 21, 2019 05:57PM
Just an update both my plugs are doing great with the upgrades, have had no issues at all.... Nice to just post without needing help this time:)m

learning is living! Echowarrior108



Edited 1 time(s). Last edit at 10/24/2019 10:42PM by echowarrior108.
Nuno
Re: Upgrading to Debian stretch and buster
October 12, 2019 12:33PM
While trying to update to buster, I followed the instructions in this thread and tried to use the "slow" approach:

apt-get update
apt-get upgrade

After a reboot everything seemed fine (except maybe samba, but I planned to address that later)
Then I tried to complete the upgrade:

apt-get update
apt-get dist-upgrade

This seemed to complete without any error, but after issuing a reboot command, my GoFlex Home seems not to boot. It is not accessible via the usual SSH connection and I can't ping it, even though the led is a solid green color...
These last commands, which seemed to run ok and rather fast, gave the following output:

root@Cypher:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  gnupg-agent libavcodec57 libavformat57 libavutil55 libbind9-140 libbluray1
  libcurl3-gnutls libdns-export162 libdns162 libevent-2.0-5 libf2fs0
  libfile-copy-recursive-perl libgdbm3 libicu57 libidn11 libisc-export160
  libisc160 libisccc140 libisccfg140 liblwres141 libminiupnpc10 libntfs-3g871
  libperl5.24 libprocps6 libssl1.0.2 libswresample2 libunistring0
  libustr-1.0-1 libva-drm1 libva-x11-1 libva1 libvpx4 libwebpmux2 libx264-148
  libx265-95 update-inetd
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  liblzma2 libtirpc1
The following NEW packages will be installed:
  libtirpc-common libtirpc3
The following packages will be upgraded:
  liblzma5 nfs-common nfs-kernel-server rpcbind
4 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 598 kB of archives.
After this operation, 394 kB disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://ftp.us.debian.org/debian buster/main armel rpcbind armel 1.2.5-0.3 [41.2 kB]
Get:2 http://ftp.us.debian.org/debian buster/main armel nfs-kernel-server armel 1:1.3.4-2.5 [109 kB]
Get:3 http://ftp.us.debian.org/debian buster/main armel nfs-common armel 1:1.3.4-2.5 [207 kB]
Get:4 http://ftp.us.debian.org/debian buster/main armel libtirpc-common all 1.1.4-0.4 [16.7 kB]
Get:5 http://ftp.us.debian.org/debian buster/main armel libtirpc3 armel 1.1.4-0.4 [79.4 kB]
Get:6 http://ftp.us.debian.org/debian buster/main armel liblzma5 armel 5.2.4-1 [144 kB]
Fetched 598 kB in 1s (579 kB/s)
(Reading database ... 24827 files and directories currently installed.)
Removing liblzma2 (5.0.0-2) ...
(Reading database ... 24817 files and directories currently installed.)
Preparing to unpack .../rpcbind_1.2.5-0.3_armel.deb ...
[ ok ] Stopping RPC port mapper daemon: rpcbind.
Unpacking rpcbind (1.2.5-0.3) over (0.2.3-0.6) ...
Preparing to unpack .../nfs-kernel-server_1%3a1.3.4-2.5_armel.deb ...
Unpacking nfs-kernel-server (1:1.3.4-2.5) over (1:1.3.4-2.1) ...
Preparing to unpack .../nfs-common_1%3a1.3.4-2.5_armel.deb ...
Unpacking nfs-common (1:1.3.4-2.5) over (1:1.3.4-2.1) ...
(Reading database ... 24813 files and directories currently installed.)
Removing libtirpc1:armel (0.2.5-1.2+deb9u1) ...
Selecting previously unselected package libtirpc-common.
(Reading database ... 24806 files and directories currently installed.)
Preparing to unpack .../libtirpc-common_1.1.4-0.4_all.deb ...
Unpacking libtirpc-common (1.1.4-0.4) ...
Selecting previously unselected package libtirpc3:armel.
Preparing to unpack .../libtirpc3_1.1.4-0.4_armel.deb ...
Unpacking libtirpc3:armel (1.1.4-0.4) ...
Preparing to unpack .../liblzma5_5.2.4-1_armel.deb ...
Unpacking liblzma5:armel (5.2.4-1) over (5.2.2-1.2+b1) ...
Setting up liblzma5:armel (5.2.4-1) ...
Setting up libtirpc-common (1.1.4-0.4) ...
Setting up libtirpc3:armel (1.1.4-0.4) ...
Setting up rpcbind (1.2.5-0.3) ...
Installing new version of config file /etc/init.d/rpcbind ...
Removing obsolete conffile /etc/init/portmap-wait.conf ...
Removing obsolete conffile /etc/init/rpcbind.conf ...
Removing obsolete conffile /etc/init/rpcbind-boot.conf ...
[ ok ] Stopping RPC port mapper daemon: rpcbind.
[ ok ] Starting RPC port mapper daemon: rpcbind.
Setting up nfs-common (1:1.3.4-2.5) ...
insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `nfs-common' overrides LSB defaults (S).
[ ok ] Stopping NFS common utilities: idmapd statd.
[ ok ] Starting NFS common utilities: statd idmapd.
Setting up nfs-kernel-server (1:1.3.4-2.5) ...
[ ok ] Stopping NFS kernel daemon: mountd nfsd.
[ ok ] Unexporting directories for NFS kernel daemon....
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for libc-bin (2.28-10) ...
root@Cypher:~#

Thanks!...
Re: Upgrading to Debian stretch and buster
October 12, 2019 05:48PM
Nuno,

Do you have serial console? or did you set up netconsole? which version of u-boot is on this box?


Quote

This seemed to complete without any error, but after issuing a reboot command, my GoFlex Home seems not to boot. It is not accessible via the usual SSH connection and I can't ping it, even though the led is a solid green color...

Try pinging the GoFlex Home before power up. Let it ping a long period like 5 minutes, and observe the ping response and the LED behavior during that time.

ping Cypher.local

or if you have setup static IP for this box
ping <IP address>

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Upgrading to Debian stretch and buster
October 12, 2019 09:02PM
Just wait a little longer, sometimes it might take more than 30 minutes to boot.... You have solid green and it's a good sign.

I did some research on these and it seems the system was running fsck at that time.

And since goflex home / net has failed RTC due to bad battery, the fsck might be often. :P
Nuno
Re: Upgrading to Debian stretch and buster
October 14, 2019 11:33AM
When I made the previous post I had already restored a previous working backup.
After you (@bodhi) posted your attempt at helping me (thanks!) I tried to replicate the problem and couldn't. What I did differently was (I think) just upgrade to liblzma5 and reboot before running the "dist-upgrade". After the "dist-upgrade" I though I wouldn't be able to reboot but everything was fine! Go figure!...

I do have the serial console enabled and working just fine (I didn't remember to check it before posting, sorry...) and I am using the latest uBoot. If the problems returns, I'll post any findings...

@daviddyer: You may be right, although I waited for what seemed to be quite a lot of time. Maybe I didn't wait enough...
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: