Latest update problems

[Ausrpned]

What is the problem with the recent update for 19?
Now cannot copy or move screen shots to a USB HDD which carries the Mint OS, don't yet know what ever other nasties are lurking in the background.
Do wish things are checked before posting, my OS has been running like a dog for some time now, regret doing updates, changed from Ubuntu because they appeared to have lost the plot, would prefer not to have to change to another OS again.

Code: Select all

data:
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.6.13_amd64.deb ...
Unpacking libapt-pkg5.0:amd64 (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up libapt-pkg5.0:amd64 (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.6.13_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up libapt-inst2.0:amd64 (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.6.13_amd64.deb ...
Unpacking apt (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up apt (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.6.13_amd64.deb ...
Unpacking apt-utils (1.6.13) over (1.6.12ubuntu0.2) ...
Preparing to unpack .../apt-transport-https_1.6.13_all.deb ...
Unpacking apt-transport-https (1.6.13) over (1.6.12ubuntu0.2) ...
Preparing to unpack .../linux-firmware_1.173.20_all.deb ...
Unpacking linux-firmware (1.173.20) over (1.173.19) ...
Preparing to unpack .../sbsigntool_0.9.2-2ubuntu1~18.04.1_amd64.deb ...
Unpacking sbsigntool (0.9.2-2ubuntu1~18.04.1) over (0.6-3.2ubuntu2) ...
Setting up apt-transport-https (1.6.13) ...
Setting up apt-utils (1.6.13) ...
Setting up sbsigntool (0.9.2-2ubuntu1~18.04.1) ...
Setting up linux-firmware (1.173.20) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-70-generic
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=9e6de72e-4cb9-44d0-a125-4070106f45ad)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-5.4.0-66-generic
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=9e6de72e-4cb9-44d0-a125-4070106f45ad)
I: Set the RESUME variable to override this.

Next attempt:
04.09@08:20 ++ Launching Update Manager
04.09@08:20 ++ Initial refresh will happen in 1 day(s), 0 hour(s) and 0 minute(s)
04.09@08:20 ++ Starting refresh (local only)
04.09@08:20 ++ Found 2 software updates
04.09@08:20 ++ Refresh finished
04.09@09:39 ++ Install requested by user
04.09@09:39 ++ Install requested by user
04.09@09:39 ++ Will install chromium-codecs-ffmpeg-extra
04.09@09:39 ++ Ready to launch synaptic

(synaptic:9890): Gtk-CRITICAL **: 09:39:41.688: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
04.09@09:40 ++ Return code:0
04.09@09:40 ++ Install finished
04.09@09:40 ++ Starting refresh (local only)
04.09@09:40 ++ Found 4 software updates
04.09@09:40 ++ Refresh finished
04.09@09:40 ++ Install requested by user
04.09@09:40 ++ Will install libapt-inst2.0
04.09@09:40 ++ Will install apt
04.09@09:40 ++ Will install libapt-pkg5.0
04.09@09:40 ++ Will install apt-utils
04.09@09:40 ++ Will install apt-transport-https
04.09@09:40 ++ Will install linux-firmware
04.09@09:40 ++ Will install sbsigntool
04.09@09:40 ++ Ready to launch synaptic

(synaptic:10037): Gtk-CRITICAL **: 09:40:39.330: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
04.09@09:52 ++ Return code:0
04.09@09:52 ++ Install finished
04.09@09:52 ++ Starting refresh (local only)
04.09@09:52 ++ Found 1 software updates
04.09@09:52 ++ Refresh finished

[Ausrpned]

What is the problem with the recent update for 19?
Now cannot copy or move screen shots to a USB HDD which carries the Mint OS, don't yet know what ever other nasties are lurking in the background.
Do wish things are checked before posting, my OS has been running like a dog for some time now, regret doing updates, changed from Ubuntu because they appeared to have lost the plot, would prefer not to have to change to another OS again.

Code: Select all

data:
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.6.13_amd64.deb ...
Unpacking libapt-pkg5.0:amd64 (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up libapt-pkg5.0:amd64 (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.6.13_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up libapt-inst2.0:amd64 (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.6.13_amd64.deb ...
Unpacking apt (1.6.13) over (1.6.12ubuntu0.2) ...
Setting up apt (1.6.13) ...
(Reading database ... 372845 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.6.13_amd64.deb ...
Unpacking apt-utils (1.6.13) over (1.6.12ubuntu0.2) ...
Preparing to unpack .../apt-transport-https_1.6.13_all.deb ...
Unpacking apt-transport-https (1.6.13) over (1.6.12ubuntu0.2) ...
Preparing to unpack .../linux-firmware_1.173.20_all.deb ...
Unpacking linux-firmware (1.173.20) over (1.173.19) ...
Preparing to unpack .../sbsigntool_0.9.2-2ubuntu1~18.04.1_amd64.deb ...
Unpacking sbsigntool (0.9.2-2ubuntu1~18.04.1) over (0.6-3.2ubuntu2) ...
Setting up apt-transport-https (1.6.13) ...
Setting up apt-utils (1.6.13) ...
Setting up sbsigntool (0.9.2-2ubuntu1~18.04.1) ...
Setting up linux-firmware (1.173.20) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-70-generic
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=9e6de72e-4cb9-44d0-a125-4070106f45ad)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-5.4.0-66-generic
W: Possible missing firmware /lib/firmware/i915/tgl_dmc_ver2_04.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/glk_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_33.0.0.bin for module i915
W: Possible missing firmware /lib/firmware/i915/icl_guc_33.0.0.bin for module i915
I: The initramfs will attempt to resume from /dev/sda5
I: (UUID=9e6de72e-4cb9-44d0-a125-4070106f45ad)
I: Set the RESUME variable to override this.

Next attempt:
04.09@08:20 ++ Launching Update Manager
04.09@08:20 ++ Initial refresh will happen in 1 day(s), 0 hour(s) and 0 minute(s)
04.09@08:20 ++ Starting refresh (local only)
04.09@08:20 ++ Found 2 software updates
04.09@08:20 ++ Refresh finished
04.09@09:39 ++ Install requested by user
04.09@09:39 ++ Install requested by user
04.09@09:39 ++ Will install chromium-codecs-ffmpeg-extra
04.09@09:39 ++ Ready to launch synaptic

(synaptic:9890): Gtk-CRITICAL **: 09:39:41.688: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
04.09@09:40 ++ Return code:0
04.09@09:40 ++ Install finished
04.09@09:40 ++ Starting refresh (local only)
04.09@09:40 ++ Found 4 software updates
04.09@09:40 ++ Refresh finished
04.09@09:40 ++ Install requested by user
04.09@09:40 ++ Will install libapt-inst2.0
04.09@09:40 ++ Will install apt
04.09@09:40 ++ Will install libapt-pkg5.0
04.09@09:40 ++ Will install apt-utils
04.09@09:40 ++ Will install apt-transport-https
04.09@09:40 ++ Will install linux-firmware
04.09@09:40 ++ Will install sbsigntool
04.09@09:40 ++ Ready to launch synaptic

(synaptic:10037): Gtk-CRITICAL **: 09:40:39.330: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed
04.09@09:52 ++ Return code:0
04.09@09:52 ++ Install finished
04.09@09:52 ++ Starting refresh (local only)
04.09@09:52 ++ Found 1 software updates
04.09@09:52 ++ Refresh finished

[Moonstone Man]

What is the problem with the recent update for 19?

What problem? If there were problems being caused by updates then the forum would be flooded with calls for help. It isn't so there aren't. On it's face, there are no issues in the wall of text you posted, so it's bewildering as to how you know the copying issue is caused by updates.

Code: Select all

(synaptic:9890): Gtk-CRITICAL **: 09:39:41.688: gtk_widget_hide: assertion 'GTK_IS_WIDGET (widget)' failed

Don't run GUI applications from the command line.

Do wish things are checked before posting,

They are.

my OS has been running like a dog for some time now

And only now you mention it after 'some time'.

regret doing updates

Your regret is highly misplaced. You should instead regret not coming here when your system first started looking like it might be "running like a dog". What has happened here is that you have allowed a deeper problem to get ever deeper, ever wider, and ever more pronounced by not attending to it promptly, and now the problem has gone so deep and wide that your system is severely unstable and is impacted by file issues. The cause here is your non-intervention. Any issues that follow are merely a symptom of your non-intervention.

changed from Ubuntu because they appeared to have lost the plot, would prefer not to have to change to another OS again.

<shrug>

We can't do anything about your personal preferences.

Nice wall of text, though. Please use code tags next time. Post the output of inxi -Fxz from a terminal and enclose it in code tags [code]output.here[/code]. You'll see the code tags icon </> when you reply.

Also post the output of dmesg --level=err, and lsblk -f, also in code tags.

The first suspect is major disk corruption. Those outputs will tell us what your machine looks like so that we can ask further questions and try to get to the root cause, and possibly a fix. However if the drive's SMART values indicate that your drive is toast or in its way to becoming toast, then the fix is a new drive and a clean install or a reimaging from a backup disk image. Determining that will come later, when we know what your machine's innards look like.

Your first course of action is to make and boot from a live LM media and then make at least one backup of your important files, and verify those backups. You should do this immediately, then attend to the requests above.

[Ausrpned]

Will need to wait a bit before I can do what you ask.

The output posted is in both cases, copy from:

Don't run GUI applications from the command line.

Are you suggesting I do not use Update Manager?

Cheers

atavar.png (3.37 KiB) Viewed 903 times

[Moonstone Man]

Don't run GUI applications from the command line.

Are you suggesting I do not use Update Manager?

No, I'm fairly certain I wrote, "don't run GUI applications from the command line." However you are only now indicating where the output came from. What you are seeing are GUI error messages that have absolutely nothing to do with failed or broken updates, and those messages are why you were told to not run GUI applications from the command line.

[Hoser Rob]

What is the problem with the recent update for 19?
Now cannot copy or move screen shots to a USB HDD which carries the Mint OS, don't yet know what ever other nasties are lurking in the background.
Do wish things are checked before posting, my OS has been running like a dog for some time now, regret doing updates, changed from Ubuntu because they appeared to have lost the plot, would prefer not to have to change to another OS again....

The problems with the update have entirely to do with your machine, not for most users.

And Ubuntu hasn't "lost the plot". Mint is Ubuntu based unless you're running LMDE. So changing from Ubuntu to Mint thinking it'll work when Ubuntu didn't is ridiculously futile.

You need to post the text output of inxi -Fxz as mentioned, how can anyone be expected to have any idea what the problem is with no system info?

The only meaningful guess I can make is that you're trying to run a Mint version that comes with too new a kernel or your video card isn't supported properly.

[Ausrpned]

Thanks for the replies.

Nice wall of text, though. Please use code tags next time. Post the output of inxi -Fxz from a terminal and enclose it in code tags

Code: Select all

output.here

. You'll see the code tags icon </> when you reply.

Also post the output of dmesg --level=err, and lsblk -f, also in code tags.

The first suspect is major disk corruption.

Checked the disk with 16.04, works OK.
Below the info requested.

Code: Select all

ausrpned@Mint193:~$ inxi -Fxz
System:
  Host: Mint193 Kernel: 5.4.0-70-generic x86_64 bits: 64 compiler: gcc 
  v: 7.5.0 Desktop: Cinnamon 4.4.8 Distro: Linux Mint 19.3 Tricia 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Laptop System: LENOVO product: 2767PJ2 v: ThinkPad T400 
  serial: <filter> 
  Mobo: LENOVO model: 2767PJ2 serial: <filter> BIOS: LENOVO 
  v: 7UET81WW (3.11 ) date: 11/26/2009 
Battery:
  ID-1: BAT0 charge: 39.9 Wh condition: 39.9/48.8 Wh (82%) 
  model: SANYO 92P1137 status: Unknown 
CPU:
  Topology: Dual Core model: Intel Core2 Duo P8700 bits: 64 type: MCP 
  arch: Penryn rev: A L2 cache: 3072 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 10107 
  Speed: 2600 MHz min/max: 800/2534 MHz Core speeds (MHz): 1: 2502 2: 2058 
Graphics:
  Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Lenovo 
  driver: i915 v: kernel bus ID: 00:02.0 
  Device-2: AMD RV620/M82 [Mobility Radeon HD 3450/3470] vendor: Lenovo 
  driver: radeon v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.8 driver: ati,modesetting,radeon 
  unloaded: fbdev,vesa resolution: 1440x900~60Hz 
  OpenGL: renderer: Mesa DRI Mobile Intel GM45 Express (CTG) 
  v: 2.1 Mesa 20.0.8 direct render: Yes 
Audio:
  Device-1: Intel 82801I HD Audio vendor: Lenovo driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k5.4.0-70-generic 
Network:
  Device-1: Intel 82567LM Gigabit Network vendor: Lenovo driver: e1000e 
  v: 3.2.6-k port: 1840 bus ID: 00:19.0 
  IF: enp0s25 state: down mac: <filter> 
  Device-2: Intel PRO/Wireless 5100 AGN [Shiloh] Network driver: iwlwifi 
  v: kernel port: 2000 bus ID: 03:00.0 
  IF: wlp3s0 state: down mac: <filter> 
  Device-3: Huawei type: USB driver: cdc_ether,usb-storage bus ID: 2-2:4 
  IF: enx0c5b8f279a64 state: up speed: N/A duplex: N/A mac: <filter> 
Drives:
  Local Storage: total: 2.73 TiB used: 503.24 GiB (18.0%) 
  ID-1: /dev/sda vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB 
  ID-2: /dev/sdb type: USB vendor: Seagate model: Expansion size: 1.82 TiB 
Partition:
  ID-1: / size: 191.15 GiB used: 43.76 GiB (22.9%) fs: ext4 dev: /dev/sda3 
  ID-2: swap-1 size: 1.90 GiB used: 97.5 MiB (5.0%) fs: swap dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 40.0 C mobo: 31.0 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 220 Uptime: 15m Memory: 1.84 GiB used: 1.18 GiB (64.0%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 
  inxi: 3.0.32 

Code: Select all

ausrpned@Mint193:~$ lsblk -f
NAME   FSTYPE   LABEL       UUID                                 MOUNTPOINT
loop0  squashfs                                                  /snap/core18/1997
loop1  squashfs                                                  /snap/core20/904
loop2  squashfs                                                  /snap/kde-frameworks-5-qt-5-14-core18/4
loop3  squashfs                                                  /snap/brave/106
loop4  squashfs                                                  /snap/kolourpaint/59
loop5  squashfs                                                  /snap/snapd/11402
loop6  squashfs                                                  /snap/core18/1988
loop7  squashfs                                                  /snap/gnome-3-34-1804/60
loop8  squashfs                                                  /snap/brave/103
loop9  squashfs                                                  /snap/kolourpaint/56
loop10 squashfs                                                  /snap/gtk-common-themes/1514
loop11 squashfs                                                  /snap/gnome-3-34-1804/66
loop12 squashfs                                                  /snap/snap-store/518
loop13 squashfs                                                  /snap/snapd/11107
loop14 squashfs                                                  /snap/core20/975
sda                                                              
├─sda1 ext4                 b6e43003-40e8-4089-8547-a3720c22c199 
├─sda2                                                           
├─sda3 ext4     Mint        cd16fa22-a7f4-497b-8a42-3d0ea372150e /
└─sda5 swap                 9e6de72e-4cb9-44d0-a125-4070106f45ad [SWAP]
sdb                                                              
├─sdb1 ntfs     NTFSXchange 8A2EEC5F2EEC4633                     /media/ausrpned/NTFSXchange1
└─sdb2 vfat     EXCHANGE1B  A21A-4049                            /media/ausrpned/EXCHANGE1B

Code: Select all

ausrpned@Mint193:~$ dmesg --level=err
[    1.748381] ima: Error Communicating to TPM chip
[    1.755532] ima: Error Communicating to TPM chip
[    1.762796] ima: Error Communicating to TPM chip
[    1.769963] ima: Error Communicating to TPM chip
[    1.776961] ima: Error Communicating to TPM chip
[    1.783818] ima: Error Communicating to TPM chip
[    1.790786] ima: Error Communicating to TPM chip
[    1.797960] ima: Error Communicating to TPM chip
[    2.230463] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 262144/32768 exceeds size of target Buffer (262144 bits) (20190816/dsopcode-203)
[    2.230497] ACPI Error: Aborting method \_SB.PCI0.VID.GETB due to previous error (AE_AML_BUFFER_LIMIT) (20190816/psparse-531)
[    2.230505] ACPI Error: Aborting method \_SB.PCI0.VID.ATRM due to previous error (AE_AML_BUFFER_LIMIT) (20190816/psparse-531)
[    3.709794] blk_update_request: critical medium error, dev sr1, sector 16368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    3.709823] Buffer I/O error on dev sr1, logical block 2046, async page read
[    3.837040] blk_update_request: critical medium error, dev sr1, sector 16360 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    3.837076] Buffer I/O error on dev sr1, logical block 2045, async page read
[    3.859438] blk_update_request: critical medium error, dev sr1, sector 16344 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    3.859469] Buffer I/O error on dev sr1, logical block 2043, async page read
[    3.895546] blk_update_request: critical medium error, dev sr1, sector 16336 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    3.895568] Buffer I/O error on dev sr1, logical block 2042, async page read
[    8.138861] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
[    8.138909] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing F9F4 (len 479, WS 0, PS 4) @ 0xFA35
[    9.735653] blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    9.763558] blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    9.763562] Buffer I/O error on dev sr0, logical block 0, async page read
[    9.770299] blk_update_request: critical medium error, dev sr1, sector 16320 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    9.770321] Buffer I/O error on dev sr1, logical block 2040, async page read
[    9.802292] blk_update_request: critical medium error, dev sr1, sector 16312 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    9.802313] Buffer I/O error on dev sr1, logical block 2039, async page read
[   21.164667] blk_update_request: critical medium error, dev sr1, sector 16296 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   21.164686] Buffer I/O error on dev sr1, logical block 2037, async page read
[   21.186548] blk_update_request: critical medium error, dev sr1, sector 16288 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   21.186566] Buffer I

Code: Select all

ausrpned@Mint193:~$ lsblk -f
NAME   FSTYPE   LABEL       UUID                                 MOUNTPOINT
loop0  squashfs                                                  /snap/core18/1997
loop1  squashfs                                                  /snap/core20/904
loop2  squashfs                                                  /snap/kde-frameworks-5-qt-5-14-core18/4
loop3  squashfs                                                  /snap/brave/106
loop4  squashfs                                                  /snap/kolourpaint/59
loop5  squashfs                                                  /snap/snapd/11402
loop6  squashfs                                                  /snap/core18/1988
loop7  squashfs                                                  /snap/gnome-3-34-1804/60
loop8  squashfs                                                  /snap/brave/103
loop9  squashfs                                                  /snap/kolourpaint/56
loop10 squashfs                                                  /snap/gtk-common-themes/1514
loop11 squashfs                                                  /snap/gnome-3-34-1804/66
loop12 squashfs                                                  /snap/snap-store/518
loop13 squashfs                                                  /snap/snapd/11107
loop14 squashfs                                                  /snap/core20/975
sda                                                              
├─sda1 ext4                 b6e43003-40e8-4089-8547-a3720c22c199 
├─sda2                                                           
├─sda3 ext4     Mint        cd16fa22-a7f4-497b-8a42-3d0ea372150e /
└─sda5 swap                 9e6de72e-4cb9-44d0-a125-4070106f45ad [SWAP]
sdb                                                              
├─sdb1 ntfs     NTFSXchange 8A2EEC5F2EEC4633                     /media/ausrpned/NTFSXchange1
└─sdb2 vfat     EXCHANGE1B  A21A-4049 

Cheers.

atavar.png (3.37 KiB) Viewed 812 times

[Ausrpned]

Just saved this page, HDD accessible again,"what gives"?

Cheers

atavar.png (3.37 KiB) Viewed 806 times

[Ausrpned]

Is this extract the problem?

Code: Select all

ausrpned@Mint193:~$ dmesg --level=err
[    2.230463] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [TBF3] at bit offset/length 262144/32768 exceeds size of target Buffer (262144 bits) (20190816/dsopcode-203)

Cheers

atavar.png (3.37 KiB) Viewed 771 times

[Ausrpned]

Posted the bug report to Github.
reply:

notifications@github.com
Re: [linuxmint/cinnamon] Bug (#10040)
reply+ATT2WMQNVQBWOY6DM5G3Q5N6PYDSNEVBNHHDF6GFNI@reply.github.com
cinnamon@noreply.github.com

This isn't a cinnamon issue.

Can only mean the BIOS is outdated, solution is no further updates to be made, unless someone can suggest how to modify the BIOS.

Cheers

atavar.png (3.37 KiB) Viewed 732 times

[spamegg]

Code: Select all

Machine:
  Type: Laptop System: LENOVO product: 2767PJ2 v: ThinkPad T400 
  serial: <filter> 
  Mobo: LENOVO model: 2767PJ2 serial: <filter> BIOS: LENOVO 
  v: 7UET81WW (3.11 ) date: 11/26/2009 

It seems that your bios is VERY OLD. It may not be able to run Mint 19, I'm not sure.
I suppose you can run Ubuntu 16.04 but don't connect to the internet! It's not safe.
You have to go to the Lenovo website and look for BIOS updates there.

I went there and it seems that even Lenovo is not supporting your PC anymore. They have a separate page for EOL (end of life) products.
https://download.lenovo.com/eol/index.html
Here you can choose "Laptops & Tablets", "Thinkpad T Series", "Thinkpad T 400" and "BIOS". It seems they have no support for Linux anyway.

[Reddog1]

It appears to be a bios problem, however, it could be the way the kernel provided by Ubuntu/Mint interacts with your bios. Try installing a 4-series kernel, and if that doesn't work, try a different distro, and not one based on Ubuntu. Maybe Sparky Linux Xfce, which is smaller and uses the 4.19 kernel.

[Ausrpned]

Mon Apr 12 spamegg and Reddog1 replied, thanks.

Yes the computer is old, will need to start looking for a later model soon.

Sparky Linux Xfce, which is smaller and uses the 4.19 kernel

Will have a look, thanks.

update Checked Sparky but the download page only shows kernel 5...
Also, ubuntu 16.04 runs Ok but the last update I did for that dropped off the ISP.

Did that some years ago as well, took me ages to work around then. Main reason for switching to Mint which had impressed me some time before the problem.

Cheers

atavar.png (3.37 KiB) Viewed 642 times