You are not logged in.

#1 2018-08-15 11:55

jackdanielsesq
Member
From: Phuket
Registered: 2017-12-19
Posts: 149

Linux Image - initrd.img-4.9.0-7-amd64 update

Greetings All

One week ago I updated Q4 OS 2.4 # 1, my longest running, pristine, glitch-free system and it broke
It is now useless - have tried everything ... nix .. normally fix it myself ... and zero help from this forum,
not even a suggestion or two ....

Today there's an update for Q4 OS 2.5 # 1, also initrd.img-4.9.0-7-amd64, which is my 2nd longest
running, glitch-free system - which begs the question - to update or not to update .. also why did it
arrive one week later - I have been using this OS since #1 crashed, last week

I have had several update mishaps, including TB message file corruption after updates ... yesterday I
deleted 2x Q4 OS 3.1 # 1 & # 2 - although they ran flawlessly for many months, both started to show
signs of strange behavior, their update files were also very different - more troubles in repo-land?

Yesterday I loaded a fresh instance of Q4 OS 2.5 # 3, and after a security update, TB now refuses to
load - message files are intact - they are always in a separate container - the system is now essentially
useless, even after trying all the usual Mozilla remedies ... its still no-go ...

All OS were loaded from same source ISO's, same default repos, zero non Deb/Q4 files were ever used

From 6x functional OS's, I am down to 1x - not a good omen, folks

Regards

Jack

Offline

#2 2018-08-15 12:51

Dai_trying
Member
From: UK
Registered: 2015-12-14
Posts: 2,989

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

I have had no issues like you mention here, I have already applied the kernel update and no ill effects on my machines (updated 2 machines with 3 installations in total). I have also had no problems with the previous kernel updates...

Can you provide some information for the system that is causing you these problems?

Offline

#3 2018-08-15 20:09

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,223
Website

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

@jackdanielsesq
Thank you for using Q4OS, as we can see from the OP, all your systems suffer from serious difficulties. If you want to get an effective help in such situation, you have to post some more valuable information, for example error messages and more detailed description of the particular issue. Statements like ".. started to show signs of strange behavior .." or ".. have tried everything .." are valueless and no one can deduce any clue what's going wrong with the system. Unfortunately, we are not able to reproduce such issues and the latest upgrade passed flawlessly on all of our testing machines.

As the OP looks more like a complaint, then a support request, and lacks particular information needed for help, it could be moved from the Support section of this forum. If you would want to post a complaint, please contact us at support@q4os.org .

Offline

#4 2018-08-16 06:32

jackdanielsesq
Member
From: Phuket
Registered: 2017-12-19
Posts: 149

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

What particular information do you want, what do you suggest I do with reference to the above update seeing as the same update
was invoked a week ago, and trashed an excellent system - what 'Plan B' do you have for me to recover from a second disaster ?
You had no solutions for the previous post - kindly note, all I did was methodically update my system, from your 'repos'

Jack

PS - kindly note, all systems have suffered due to various updates - they were flawless prior-to
Why is there a one-week difference in upgrade time on identical systems?
The same image upgrade on this system today is 37MB, not 18MB as was the previous update, one week prior-to


q4osteam wrote:

@jackdanielsesq
Thank you for using Q4OS, as we can see from the OP, all your systems suffer from serious difficulties. If you want to get an effective help in such situation, you have to post some more valuable information, for example error messages and more detailed description of the particular issue. Statements like ".. started to show signs of strange behavior .." or ".. have tried everything .." are valueless and no one can deduce any clue what's going wrong with the system. Unfortunately, we are not able to reproduce such issues and the latest upgrade passed flawlessly on all of our testing machines.

As the OP looks more like a complaint, then a support request, and lacks particular information needed for help, it could be moved from the Support section of this forum. If you would want to post a complaint, please contact us at support@q4os.org .

Last edited by jackdanielsesq (2018-08-16 06:44)

Offline

#5 2018-08-16 08:11

Dai_trying
Member
From: UK
Registered: 2015-12-14
Posts: 2,989

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

jackdanielsesq wrote:

What particular information do you want,

maybe output from inxi -F or some other system information (for each affected machine)

jackdanielsesq wrote:

what do you suggest I do with reference to the above update seeing as the same update was invoked a week ago, and trashed an excellent system

Probably best to wait until some information is available...

jackdanielsesq wrote:

- what 'Plan B' do you have for me to recover from a second disaster ?

Use your backup... you do have one right??

jackdanielsesq wrote:

You had no solutions for the previous post - kindly note, all I did was methodically update my system, from your 'repos'

Personally I could offer no explanation or magic cure as I have not experienced this issue and so left it for others who might be able to help to step in.


jackdanielsesq wrote:

PS - kindly note, all systems have suffered due to various updates - they were flawless prior-to

How many systems? what architecture(s) what software do you use? wine installed? samba installed? any outside repositories enabled? do you have deb-multimedia repository enabled? do you use any software from backports?

jackdanielsesq wrote:

Why is there a one-week difference in upgrade time on identical systems?

Without knowing how your system is configured etc it is only possible to speculate... maybe you don't use the system long enough for the random time to pass before the system updates the apt repository... maybe you do not have anything set-up to automatically update the repository information... maybe your internet connection is flakey...

jackdanielsesq wrote:

The same image upgrade on this system today is 37MB, not 18MB as was the previous update, one week prior-to

Again no system information means anyone can only guess... maybe one system requires firmware that is not installed on the other... maybe one system has an extra package or two installed... maybe there was an upgrade very recently uploaded to the repository...

You can always use a live-cd to access your "broken" system to obtain the relevant logs (/var/log/apt/history.log might show something regarding your updates) and to possibly restore your system but I can offer no advice that would be relevant to the description of your problem "and it broke It is now useless - have tried everything " and remember Q4OS always keeps the previous kernel available so you could choose that from the grub boot screen and it should boot using the previous "pristine, glitch-free system" kernel.

Last edited by Dai_trying (2018-08-16 08:13)

Offline

#6 2018-08-16 08:53

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,223
Website

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

@jackdanielsesq
In order to provide a support for you, we need you to follow our instructions as exact as possible. So, let's go ..

We assume you are not able to login. So, let systems (you want to rescue) boot and post kernel (or systemd) messages you see on the screen. Please post a screenshots, as they are best testifying.

We can also recommend you to follow Dai_trying's suggestions, thanks DT for your valuable help. You could start from the last point, so, attach here the '/var/log/apt/history.log' file from systems you want to rescue.

Offline

#7 2018-08-16 10:07

jackdanielsesq
Member
From: Phuket
Registered: 2017-12-19
Posts: 149

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

/var/log/apt/history.log

start-Date: 2018-08-05  11:23:20
Commandline: /usr/sbin/synaptic
Requested-By: putz (1000)
Install: libcogl20:amd64 (1.22.2-2, automatic), libclutter-1.0-0:amd64 (1.26.0+dfsg-3, automatic), libgdl-3-5:amd64 (3.22.0-1, automatic), libcogl-path20:amd64 (1.22.2-2, automatic), libgtkpod1:amd64 (2.1.5-4, automatic), vorbis-tools:amd64 (1.4.0-10+b1, automatic), libcogl-common:amd64 (1.22.2-2, automatic), id3v2:amd64 (0.1.12-2.1+b2, automatic), libcogl-pango20:amd64 (1.22.2-2, automatic), iio-sensor-proxy:amd64 (2.0-4, automatic), libgpod4:amd64 (0.8.3-8.2, automatic), libwebkitgtk-3.0-0:amd64 (2.4.11-3, automatic), geoclue-2.0:amd64 (2.4.5-1, automatic), libgeoclue-2-0:amd64 (2.4.5-1, automatic), gtkpod:amd64 (2.1.5-4), libgpod-common:amd64 (0.8.3-8.2, automatic), libgdl-3-common:amd64 (3.22.0-1, automatic), libatomicparsley0:amd64 (2.1.5-4, automatic), libanjuta-3-0:amd64 (2:3.22.0-3, automatic), libsgutils2-2:amd64 (1.42-2, automatic), libclutter-1.0-common:amd64 (1.26.0+dfsg-3, automatic), anjuta-common:amd64 (2:3.22.0-3, automatic), libjavascriptcoregtk-3.0-0:amd64 (2.4.11-3, automatic), libclutter-gtk-1.0-0:amd64 (1.8.2-2, automatic), libid3-3.8.3v5:amd64 (3.8.3-16.2+b1, automatic), gtkpod-data:amd64 (2.1.5-4, automatic)
End-Date: 2018-08-05  11:24:32

***********

Q4OS 2.4 # 1 worked perfectly after the above updates/reboot for three days …...


***********

Start-Date: 2018-08-07  02:35:15
Commandline: packagekit role='update-packages'
Requested-By: putz (1000)
Upgrade: linux-image-4.9.0-7-amd64:amd64 (4.9.110-1, 4.9.110-3+deb9u1)
End-Date: 2018-08-07  02:36:36


Q4OS 2.4 # 1 stopped working from this point forward …...

***********************

As you can see - nothing untoward here - next idea, please

Jack

Offline

#8 2018-08-16 10:11

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,223
Website

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

In addition, please provide the following one:

q4osteam wrote:

We assume you are not able to login. So, let systems (you want to rescue) boot and post kernel (or systemd) messages you see on the screen. Please post a screenshots, as they are best testifying.

Offline

#9 2018-08-16 10:23

jackdanielsesq
Member
From: Phuket
Registered: 2017-12-19
Posts: 149

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

As in the OP above - press Control-D for maintenance - no screenshots

Offline

#10 2018-08-16 10:36

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,223
Website

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

We need screenshots to be able to check all preceding, or visible, messages, please post it here, as it could be highly important. Just take a photo and attach it here, should be easy, shouldn't it ?

EDIT: You can add an attachment by 'post reply -> choose file'

Last edited by q4osteam (2018-08-16 10:48)

Offline

#11 2018-08-16 11:00

Dai_trying
Member
From: UK
Registered: 2015-12-14
Posts: 2,989

Re: Linux Image - initrd.img-4.9.0-7-amd64 update

jackdanielsesq wrote:

press Control-D for maintenance - no screenshots

Sounds like you cannot access the HDD... can you check in your BIOS/UEFI settings if there is a HDD detected and available? and if you have "SMART monitoring" in there check that too.

Offline

Board footer

Powered by FluxBB