issues after upgrade

[timl]

Hi, I have a Raspberry Pi 3 which was running stretch until yesterday. I modified source.lis and raspi.lis to reference buster rather than stretch then

Code: Select all

apt-get update
apt-get dist-upgrade 

Ever since the upgrade I have experienced problems. I run a number of programs headlessly, eg.

Code: Select all

 ssh -f -X -l pi 10.1.1.91 "midori &" 

. These programs keep crashing. All at the same time. I thought this might be an SSH thing (no problems with headless operation before) and was advised to add a couple of lines to my ssh config file

Code: Select all

ForwardX11Timeout 0
ServerAliveInterval 15

. These haven't made a difference. The programs were running all day today while I was out at work but crashed not long after I started using the Pi again.

I came across this in /var/log/messages

Code: Select all

Sep 30 15:39:47 buzz kernel: [   14.632305] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
Sep 30 15:39:47 buzz kernel: [   15.353613] sd 1:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
Sep 30 15:39:47 buzz kernel: [   15.867742] EXT4-fs (sda2): recovery complete
Sep 30 15:39:47 buzz kernel: [   16.409011] EXT4-fs (sdb1): recovery complete
Sep 30 15:43:51 buzz kernel: [    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Sep 30 15:43:51 buzz kernel: [    0.926480] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem
Sep 30 15:43:51 buzz kernel: [    0.926490] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
Sep 30 15:43:51 buzz kernel: [    1.633309] EXT4-fs (mmcblk0p2): recovery complete

Funnily enough when I copied this block of the text the jobs all crashed out again. Note the Pi doesn't crash, just the connection.

The disks in question are these

Code: Select all

/dev/sda2       4.6T  2.6T  1.8T  60% /mnt/extend
/dev/sdb1       4.6T  2.6T  1.8T  59% /mnt/downloads

I wasn't getting these messages before the upgrade and I wasn't experiencing any issues with SSH either. Just wondering whether there are any further tasks I need to perform after the upgrade (being a fedora user I am more used to upgrades being installed while the PC is not available)

TIA

[PeterO]

Hi, I have a Raspberry Pi 3 which was running stretch until yesterday. I modified source.lis and raspi.lis to reference buster rather than stretch then

Code: Select all

apt-get update
apt-get dist-upgrade 

Major release upgrades like that are not recommended. It's better to just get a new SD card and start fresh with a clean install of the new release.
User files and config can then be copied across (eg via a USB stick).

PeterO

[pcmanbob]

Updating from stretch to buster in that way is not recommend as it often leads to problems or a failure to boot after the update,

the recommanded way is to flash a new image on to the SD card and start over.

As ever with major version changes, our recommendation is that you download a new clean image from the usual place on our site – this will ensure that you are starting from a clean, working Buster system.

We do not recommend upgrading an existing Stretch (or earlier) system to Buster – we can’t know what changes everyone has made to their system, and so have no idea what may break when you move to Buster. However, we have tested the following procedure for upgrading, and it works on a clean version of the last Stretch image we released. That does not guarantee it will work on your system, and we cannot provide support (or be held responsible) for any problems that arise if you try it. You have been warned – make a backup!

https://www.raspberrypi.org/blog/buster ... -raspbian/

So as it says you are on you own as there is no way to know what software you have installed and how it has affected the update.

[timl]

Thanks for the responses. I did think this upgrade path was too good to be true. I already downloaded buster so I'll get a new sd card and install this.

[bjtheone]

Hi, I have a Raspberry Pi 3 which was running stretch until yesterday. I modified source.lis and raspi.lis to reference buster rather than stretch then

Code: Select all

apt-get update
apt-get dist-upgrade 

Major release upgrades like that are not recommended. It's better to just get a new SD card and start fresh with a clean install of the new release.
User files and config can then be copied across (eg via a USB stick).

PeterO

Further to what Peter said, if you start with a new card (they are CHEAP, compared to the potential hassle factor and time wasted) you will have your current working SD card as a backup, with all your data files safe and sound. Install Buster on the new card, and then you can easily put the old card in a USB reader and copy whatever across. Can also browse config files, etc.

[emma1997]

I had all versions but never tried to upgrade from one to the other. My 'issues' with upgrade almost all stemmed from it's nasty habit of changing the resolution.

[timl]

Hi All, sorted. I did the right thing and bought a new SD card. With the backups on my main PC it took next to no time to get back online. Thanks for all the help