[SOLVED] Can't boot Tara after kernel update: can't restore via Timeshift

[PerpetualNewbie]

Hi,

I suspect that a recent system update has made my operating system no longer compatible with my HP laptop hp elitebook 1030-gi. Suspect a kernel upgrade is the culprit, but I am not sure.

I can no longer boot up the computer, but hardware tests are ok and I can see the operating system is still installed on the system, but can't restore it. When booting from BOIS get message:
[1.609901] Couldn't get size: 0x00000000000000e
[3.205962] sd 2:0:0:0: [sbd] no caching mode page found
[3.205964] sd 2:0:0:0 [sbd] assuming drive cache: write through

I was able to use a USB ISO and can boot up in Compatibility mode. From there, I tried using Time Shift, but it did not automatically re-boot and the restore did not return the OS to normal. I tried a couple different saved versions I had available in Time Shift but they did not work.

I have seen several other posts with a similar theme, do the new kernels require newer hardware or is usable hardware more limited since the newer kernels?

Is there a way for me to update the kernel without being able to boot?

I have been a happy user for so many years, this is the first real trouble I have run into.

Any insight welcome.

[SMG]

I was able to use a USB ISO and can boot up in Compatibility mode.

In compatibility mode, can you provide the inxi -Fxxxrz information requested in Section 5 of READ: How To Get Help! ?

[PerpetualNewbie]

Thanks, here is the output.

Code: Select all

mint@mint:~$ inxi -Fxxxrz
System:    Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm
           Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: HP product: HP EliteBook 1030 G1 serial: N/A
           Mobo: HP model: 80FB v: KBC Version 14.36 serial: N/A
           UEFI: HP v: N86 Ver. 01.05 date: 11/01/2016
           Chassis: type: 10 serial: N/A
Battery    BAT0: charge: 23.0 Wh 64.1% condition: 35.9/35.9 Wh (100%)
           volts: 7.6/7.6
           model: Hewlett-Packard Primary Li-ion serial: <filter>status: Discharging cycles: 0
CPU:       Dual core Intel Core m5-6Y54 (-MT-MCP-)
           arch: Skylake rev.3 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6048
           clock speeds: min/max: 400/2700 MHz 1: 500 MHz 2: 500 MHz
           3: 500 MHz 4: 500 MHz
Graphics:  Card: Intel HD Graphics 515 bus-ID: 00:02.0 chip-ID: 8086:191e
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@59.93hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 515 (Skylake GT2)
           version: 4.5 Mesa 18.0.0-rc5 (compat-v: 3.0) Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d70
           Sound: Advanced Linux Sound Architecture v: k4.15.0-20-generic
Network:   Card-1: Intel Ethernet Connection I219-LM
           driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 chip-ID: 8086:156f
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel Wireless 8260
           driver: iwlwifi bus-ID: 01:00.0 chip-ID: 8086:24f3
           IF: wlp1s0 state: down mac: <filter>
Drives:    HDD Total Size: 287.1GB (2.8% used)
           ID-1: /dev/sda model: SanDisk_SD8SN8U size: 256.1GB
           serial: <filter> temp: 30C
           ID-2: USB /dev/sdb model: USB_DISK_3.0 size: 31.0GB
           serial: <filter> temp: 0C
Partition: ID-1: / size: 3.9G used: 35M (1%) fs: overlay dev: N/A
           ID-2: swap-1 size: 8.46GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda3
RAID:      System: supported: N/A
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 34.5C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb cdrom:[Linux Mint 19 _Tara_ - Release amd64 20180717]/ bionic contrib main non-free
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com tara main upstream import backport #id:linuxmint_main
           deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ bionic partner
Info:      Processes: 191 Uptime: 1 min Memory: 591.6/7858.1MB
           Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191 running in gnome-terminal-) inxi: 2.3.56

[SMG]

I was able to use a USB ISO and can boot up in Compatibility mode.

I assumed this meant you booted the ISO in Compatibility Mode, but usually that disables the graphics driver and that is not what the data you posted shows. Is that what you meant when you said you can boot up in Compatibility Mode?

I do not have any ideas of what may be happening at this point. Usually, if one kernel is a problem, booting into a prior kernel should work. This post indicates a couple of bugs with 4.15.0-151, but neither sound exactly like what you have described.

Maybe someone else will have ideas.

[mikeflan]

I tried using Time Shift, but it did not automatically re-boot and the restore did not return the OS to normal. I tried a couple different saved versions I had available in Time Shift but they did not work.

Wow, a nightmare scenario. Very surprising. If you have the disk space it's always nice if you have some disk images to fall back on. I hope you don't have to start over.

Did Timeshift hang while doing the first restore? I have never seen it do that, but I am in fear of it every time I do a restore.

Maybe I should start backing up my snapshots. I don't do that except for the disk image I take every 2-3 months. Backing up snapshots would not be too difficult for me, but it seems like overkill.

[PerpetualNewbie]

Hi SMG: I collected data again for inxi. This time, instead of Compatibility, I chose the first menu option that says Linux Mint 19. The graphics card data is in this one as well.

The problematic kernel would be more recent than 4.15.0-151. I think 4.15.0-151 is in the ISO image, and the kernel that caused my system to choke is a more recent release.

Here is the inxi from the first menu option, which is labelled Linux Mint 19.

Code: Select all

mint@mint:~$ inxi -Fxxxrz
System:    Host: mint Kernel: 4.15.0-20-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.8 (Gtk 3.22.30-1ubuntu1) dm: lightdm
           Distro: Linux Mint 19 Tara
Machine:   Device: laptop System: HP product: HP EliteBook 1030 G1 serial: N/A
           Mobo: HP model: 80FB v: KBC Version 14.36 serial: N/A
           UEFI: HP v: N86 Ver. 01.05 date: 11/01/2016
           Chassis: type: 10 serial: N/A
Battery    BAT0: charge: 18.8 Wh 51.5% condition: 36.5/36.5 Wh (100%)
           volts: 7.5/7.6
           model: Hewlett-Packard Primary Li-ion serial: <filter>status: Discharging cycles: 0
CPU:       Dual core Intel Core m5-6Y54 (-MT-MCP-)
           arch: Skylake rev.3 cache: 4096 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 6048
           clock speeds: min/max: 400/2700 MHz 1: 500 MHz 2: 500 MHz
           3: 500 MHz 4: 500 MHz
Graphics:  Card: Intel HD Graphics 515 bus-ID: 00:02.0 chip-ID: 8086:191e
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@59.93hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 515 (Skylake GT2)
           version: 4.5 Mesa 18.0.0-rc5 (compat-v: 3.0) Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3 chip-ID: 8086:9d70
           Sound: Advanced Linux Sound Architecture v: k4.15.0-20-generic
Network:   Card-1: Intel Ethernet Connection I219-LM
           driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 chip-ID: 8086:156f
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel Wireless 8260
           driver: iwlwifi bus-ID: 01:00.0 chip-ID: 8086:24f3
           IF: wlp1s0 state: down mac: <filter>
Drives:    HDD Total Size: 287.1GB (2.8% used)
           ID-1: /dev/sda model: SanDisk_SD8SN8U size: 256.1GB
           serial: <filter> temp: 31C
           ID-2: USB /dev/sdb model: USB_DISK_3.0 size: 31.0GB
           serial: <filter> temp: 0C
Partition: ID-1: / size: 3.9G used: 35M (1%) fs: overlay dev: N/A
           ID-2: swap-1 size: 8.46GB used: 0.00GB (0%)
           fs: swap dev: /dev/sda3
RAID:      System: supported: N/A
           No RAID devices: /proc/mdstat, md_mod kernel module present
           Unused Devices: none
Sensors:   System Temperatures: cpu: 35.5C mobo: 0.0C
           Fan Speeds (in rpm): cpu: N/A
Repos:     Active apt sources in file: /etc/apt/sources.list
           deb cdrom:[Linux Mint 19 _Tara_ - Release amd64 20180717]/ bionic contrib main non-free
           Active apt sources in file: /etc/apt/sources.list.d/official-package-repositories.list
           deb http://packages.linuxmint.com tara main upstream import backport #id:linuxmint_main
           deb http://archive.ubuntu.com/ubuntu bionic main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse
           deb http://archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse
           deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse
           deb http://archive.canonical.com/ubuntu/ bionic partner
Info:      Processes: 191 Uptime: 1 min Memory: 567.7/7858.1MB
           Init: systemd v: 237 runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191 running in gnome-terminal-) inxi: 2.3.56

Mikeflan: Time Shift did not give any response the first attempt at Restore. On subsequent attempts, it does give feedback that I can see in terminal, but no screens or GUI feedback. Backups are super important, but sometimes your number is up the chute just doesn't open.

[SMG]

The problematic kernel would be more recent than 4.15.0-151. I think 4.15.0-151 is in the ISO image, and the kernel that caused my system to choke is a more recent release.

The iso image is the one in your data which is showing 4.15.0-20. Going from -20 to -151 means the one I listed is much, much newer.

Did you maybe upgrade to the 5.4 kernel? I did not think those with Tara did that, but maybe you did? That would be a newer kernel than 4.15.

Your data lists an sba and sbb, but the error was sbd. What is sbd? Do you have something else attached to the computer (such as maybe a card or disc)?
Drives:
HDD Total Size: 287.1GB (2.8% used)
ID-1: /dev/sda model: SanDisk_SD8SN8U size: 256.1GB
serial: <filter> temp: 31C
ID-2: USB /dev/sdb model: USB_DISK_3.0 size: 31.0GB
serial: <filter> temp: 0C

[PerpetualNewbie]

I am wondering is it possible that when running updates, I somehow managed to get a the 5.4 kernel? I didn't do anything fancy, I just run updates whenever the icon on my system tray tells me new stuff is waiting to update.

The only thing attached to the computer was the USB stick, so I am guessing that the sbd is from the USB.

[SMG]

I am wondering is it possible that when running updates, I somehow managed to get a the 5.4 kernel? I didn't do anything fancy, I just run updates whenever the icon on my system tray tells me new stuff is waiting to update.

The 4.15 kernel is the LTS (long-term-support) kernel for LM19, so I would not think it would automatically upgrade you since 4.15 is still supported (and thus no reason to change).

The only thing attached to the computer was the USB stick, so I am guessing that the sbd is from the USB.

You had your usb stick attached when you got the messages you put in your first post? I thought those messages happened when you booted from the hard drive (before trying the live session with the usb stick).

(The 32GB usb drive you used to boot the live session of Tara shows on the data I posted as sdb.)

[PerpetualNewbie]

Yes, that is what appeared in the first post. it is a 32 GB stick (USB), not a hard drive. I have been using it to boot up from the ISO image.

Is it possible that the kernel was made available in the update by accident? For whatever reason, it was allowed to be seen by my system, downloaded and then installed during the normal update process?

[SMG]

Yes, that is what appeared in the first post. it is a 32 GB stick (USB), not a hard drive. I have been using it to boot up from the ISO image.

You have permanent install of Tara on a 32 GB usb stick? Or are you booting a Tara ISO from a usb stick? (Or maybe you are doing both.) Where exactly is the install which is having problems?

This is the part of the first post I am referencing:

I can no longer boot up the computer, but hardware tests are ok and I can see the operating system is still installed on the system, but can't restore it. When booting from BOIS get message:
[1.609901] Couldn't get size: 0x00000000000000e
[3.205962] sd 2:0:0:0: [sbd] no caching mode page found
[3.205964] sd 2:0:0:0 [sbd] assuming drive cache: write through

What is giving those errors? Is it the BIOS itself or is it the operating system?

[PerpetualNewbie]

Just to review, I am not having trouble with an install, I am trying to restore Tara 19.

I used an ISO on the 32GB USB stick in order to re-boot and access Time Shift in an effort to restore the OS.

The clipped text shows the message I get when trying to boot up the machine without the USB: this is what I see when trying to boot up, as one normally would, by turning the computer on. I think this is an error message from the BIOS, not the OS, but I am not sure.
"I can no longer boot up the computer, but hardware tests are ok and I can see the operating system is still installed on the system, but can't restore it. When booting from BOIS get message:
[1.609901] Couldn't get size: 0x00000000000000e
[3.205962] sd 2:0:0:0: [sbd] no caching mode page found
[3.205964] sd 2:0:0:0 [sbd] assuming drive cache: write through"

[SMG]

Just to review, I am not having trouble with an install, I am trying to restore Tara 19.

If you are not having trouble with an install, then why are you trying to restore Tara? Just for practice?

Your thread title seems to indicate there are problems booting an install.

The clipped text shows the message I get when trying to boot up the machine without the USB: this is what I see when trying to boot up, as one normally would, by turning the computer on. I think this is an error message from the BIOS, not the OS, but I am not sure.

The first number within the brackets appears to be timestamps from the operating system booting up. My guess is they are from the operating system.

[3.205962] sd 2:0:0:0: [sbd] no caching mode page found
[3.205964] sd 2:0:0:0 [sbd] assuming drive cache: write through"

This part seems to be similar to what is posted in this thread “No caching mode page present” when USB flash disk attached.

[PerpetualNewbie]

To recap: My system failed to boot, so I tried to restore using Time Shift and that failed, so I posted to this forum, hoping for guidance on how to restore.

I suspect the problem was caused by a kernel update, that got installed as a routine update.

I would like to know if there is a way to restore that I haven't tried or if there is a way to reverse the kernel back to an earlier one so that I can restore.

[SMG]

I would like to know if there is a way to restore that I haven't tried or if there is a way to reverse the kernel back to an earlier one so that I can restore.

One either boots through recovery mode to get to Timeshift and restore or one boots to a live session of Mint and uses Timeshift on it to restore to a snapshot on the hard drive.

If one only suspects a kernel is the issue, one can boot into grub, select advanced options, and select an older kernel to boot.

Your computer has UEFI and not the older BIOS technology. Can you boot into UEFI? It may be that something happened to your EFI partition. It may be helpful to boot into a live session of Mint and open GParted to see if the partitions look correct.

[mikeflan]

I suspect the problem was caused by a kernel update, that got installed as a routine update.

Lets see if we can check that.

If you can start Update Manager, then select 'View' - 'History of updates'.
Find the updates you did. Are there any kernel updates in there?

If you can't start Update Manager, but can get to a terminal:

Look at recent updates:

Code: Select all

cat /var/log/apt/history.log

Go back a little further on the updates log:

Code: Select all

zcat /var/log/apt/history.log.1*

STOP HERE. NO NEED TO DO ALL THIS STUFF:

How many lines in '/var/log/apt/history.log' have 'Install.*5.4.0' in them:

Code: Select all

grep "Install.*5.4.0" /var/log/apt/h* | wc -l

For me it is 1 time. For you I suspect it is zero.

How many lines in '/var/log/apt/history.log' have 'Upgrade.*5.4.0' in them:

Code: Select all

grep "Upgrade.*5.4.0" /var/log/apt/h* | wc -l

For me it is 1 time. For you I suspect it is zero.

Then do the same for '4.15.0':

How many lines in '/var/log/apt/history.log' have 'Install.*4.15.0' in them:

Code: Select all

grep "Install.*4.15.0" /var/log/apt/h* | wc -l

For me it is 1 time. For you - I don't know.

How many lines in '/var/log/apt/history.log' have 'Upgrade.*4.15.0' in them:

Code: Select all

grep "Upgrade.*4.15.0" /var/log/apt/h* | wc -l

For me it is 1 time. For you - I don't know.

Are these even the same as kernel updates? I don't know.
To see the lines instead of the number of lines remove the " | wc -l" off the end of the commands above.
To see older history files change "grep" to "zgrep".

[Jo-con-Ël]

Taken into account the problem with that 4.15.0-151 kernel update would left root partition in a read-only state (it happens to me) and this would explain why PerpetualNewbie can't restore Timeshft snapshot.

I think, first of all , you will need to check root partition's filesystem to be sure. It is worth you boot Linux Mint live and run disks (Menu>Accessories>Disks> Select disk on the left and the root partition on the right. Then click on wheels icon downside>Check filesystem,

Screenshot from 2021-07-29 10-26-50.png (26.96 KiB) Viewed 776 times

Confirm to check when asked.

a)if file system is undamaged, shutdown, extract/unplug Linux Mint live USB and do as indicated by SMG (in GRUB menu>choose Advanced Option press Enter scroll down to the previous kernel 4.15.0-147 (w/o recovery option) and press Enter to boot.

Then you can remove the problematic kernel in Update Manager>View>Linux Kernel... 4.15 on the left and select 4.14.0-151 on the right>Remove.

Reboot when finished and wait 'till kernel 4.15.0-153 will be released and available in Update manager.

b)If files system is damage and need to repaired, then click on wheels icon again and choose >Repair filesystem. When cleaned do as indicated in a)

c)If something goes wrong on repairing take a snapshot and post back or open a terminal (Alt+Ćtrl+T)

run

Code: Select all

sudo fdisk -l

and then(replace sdxy with the real one as per previous sudo fdisk -l

Code: Select all

sudo fsck -y /dev/sdxy 

Post back codes result.

[PerpetualNewbie]

Thanks for the leads! Here is what gparted looked like:


Does that look right or am I in real trouble?

[PerpetualNewbie]

Hi Jo-con-Ël,

Partition1 on the left looks ok, no damage detected.



Partition 3 does not allow me to run a check.



Does this mean that partition3 is out of commission and is what is causing the trouble or am I clear to try to get into GRUB?

[SMG]

Thanks for the leads! Here is what gparted looked like:

Does that look right or am I in real trouble?

There are others on the forum with more experience than me on this issue, but that looks correct to me. The boot flag is on your EFI partition.

Swap is locked because it is in use. (Mint live session will mount and use swap partitions it finds.)