Extremely slow for kernel install

I had a couple problem with the suspend on 5.3.18 (eol). I decide to reboot on 4.19.91. All disk operations were extremely slow, Then I decided to install 5.4, it's been running for 3 hours! It's stuck at:

Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img

Any idea on what I should do?

Here's the journalctl:

$ journalctl -p 3 --since=today
-- Logs begin at Fri 2019-11-22 10:25:52 PST, end at Thu 2020-01-02 10:35:36 PST. --
Jan 02 06:40:10 ethelbert systemd-udevd[283]: GOTO 'libsane_rules_end' has no matching label in: '/etc/udev/rules.d/40-libsane.rules'
Jan 02 06:40:12 ethelbert systemd-udevd[283]: GOTO 'libsane_rules_end' has no matching label in: '/etc/udev/rules.d/S99-2000S1.rules'
Jan 02 06:40:25 ethelbert NetworkManager[575]: <error> [1577976025.7076] device (enp4s0): addrconf6: failed to start neighbor discovery: failure creating libndp socket: Ad>
Jan 02 06:48:51 ethelbert kernel: print_req_error: I/O error, dev sdg, sector 0
Jan 02 06:52:18 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:52:18 ethelbert kernel:       Not tainted 4.19.91-1-MANJARO #1
Jan 02 06:52:18 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:54:21 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:54:21 ethelbert kernel:       Not tainted 4.19.91-1-MANJARO #1
Jan 02 06:54:21 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:54:36 ethelbert kernel: EXT4-fs error (device sdg1): __ext4_get_inode_loc:4695: inode #2: block 1027: comm mc: unable to read itable block
Jan 02 06:54:36 ethelbert kernel: EXT4-fs error (device sdg1) in ext4_reserve_inode_write:5909: IO failure
Jan 02 06:54:41 ethelbert kernel: Buffer I/O error on dev sdg1, logical block 1545, lost sync page write
Jan 02 06:54:41 ethelbert kernel: JBD2: Error -5 detected when updating journal superblock for sdg1-8.
Jan 02 06:54:41 ethelbert kernel: Aborting journal on device sdg1-8.
Jan 02 06:54:41 ethelbert kernel: Buffer I/O error on dev sdg1, logical block 1545, lost sync page write
Jan 02 06:54:41 ethelbert kernel: JBD2: Error -5 detected when updating journal superblock for sdg1-8.
Jan 02 06:56:24 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:56:24 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 06:56:24 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:58:27 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:58:27 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 06:58:27 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:00:30 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:00:30 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 07:00:30 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:02:33 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:02:33 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 07:02:33 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:04:36 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
...skipping...
-- Logs begin at Fri 2019-11-22 10:25:52 PST, end at Thu 2020-01-02 10:35:36 PST. --
Jan 02 06:40:10 ethelbert systemd-udevd[283]: GOTO 'libsane_rules_end' has no matching label in: '/etc/udev/rules.d/40-libsane.rules'
Jan 02 06:40:12 ethelbert systemd-udevd[283]: GOTO 'libsane_rules_end' has no matching label in: '/etc/udev/rules.d/S99-2000S1.rules'
Jan 02 06:40:25 ethelbert NetworkManager[575]: <error> [1577976025.7076] device (enp4s0): addrconf6: failed to start neighbor discovery: failure creating libndp socket: Ad>
Jan 02 06:48:51 ethelbert kernel: print_req_error: I/O error, dev sdg, sector 0
Jan 02 06:52:18 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:52:18 ethelbert kernel:       Not tainted 4.19.91-1-MANJARO #1
Jan 02 06:52:18 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:54:21 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:54:21 ethelbert kernel:       Not tainted 4.19.91-1-MANJARO #1
Jan 02 06:54:21 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:54:36 ethelbert kernel: EXT4-fs error (device sdg1): __ext4_get_inode_loc:4695: inode #2: block 1027: comm mc: unable to read itable block
Jan 02 06:54:36 ethelbert kernel: EXT4-fs error (device sdg1) in ext4_reserve_inode_write:5909: IO failure
Jan 02 06:54:41 ethelbert kernel: Buffer I/O error on dev sdg1, logical block 1545, lost sync page write
Jan 02 06:54:41 ethelbert kernel: JBD2: Error -5 detected when updating journal superblock for sdg1-8.
Jan 02 06:54:41 ethelbert kernel: Aborting journal on device sdg1-8.
Jan 02 06:54:41 ethelbert kernel: Buffer I/O error on dev sdg1, logical block 1545, lost sync page write
Jan 02 06:54:41 ethelbert kernel: JBD2: Error -5 detected when updating journal superblock for sdg1-8.
Jan 02 06:56:24 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:56:24 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 06:56:24 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 06:58:27 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 06:58:27 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 06:58:27 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:00:30 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:00:30 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 07:00:30 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:02:33 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:02:33 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 07:02:33 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:04:36 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:04:36 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1
Jan 02 07:04:36 ethelbert kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 02 07:06:39 ethelbert kernel: INFO: task udisksd:710 blocked for more than 120 seconds.
Jan 02 07:06:39 ethelbert kernel:       Tainted: G        W         4.19.91-1-MANJARO #1

and here's my inxi

$ inxi -Fxxxz
System:    Host: ethelbert Kernel: 4.19.91-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: KDE Plasma 5.17.4 
           tk: Qt 5.14.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: MSI model: 970A-G46 (MS-7693) v: 2.0 serial: <filter> BIOS: American Megatrends v: 2.8 
           date: 01/08/2016 
CPU:       Topology: 8-Core model: AMD FX-8350 bits: 64 type: MCP arch: Bulldozer L2 cache: 2048 KiB 
           flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 64001 
           Speed: 3944 MHz min/max: 1400/4000 MHz boost: enabled Core speeds (MHz): 1: 3944 2: 3286 3: 3578 4: 3145 5: 2764 
           6: 3841 7: 3930 8: 3717 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] 
           vendor: Micro-Star MSI driver: amdgpu v: kernel bus ID: 01:00.0 chip ID: 1002:67df 
           Display: x11 server: X.Org 1.20.6 driver: amdgpu unloaded: modesetting alternate: ati,fbdev,vesa 
           compositor: kwin_x11 resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: Radeon RX 570 Series (POLARIS10 DRM 3.27.0 4.19.91-1-MANJARO LLVM 9.0.0) v: 4.5 Mesa 19.3.1 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] SBx00 Azalia vendor: Micro-Star MSI driver: snd_hda_intel v: kernel 
           bus ID: 00:14.2 chip ID: 1002:4383 
           Device-2: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] vendor: Micro-Star MSI driver: snd_hda_intel 
           v: kernel bus ID: 01:00.1 chip ID: 1002:aaf0 
           Sound Server: ALSA v: k4.19.91-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel 
           port: d000 bus ID: 04:00.0 chip ID: 10ec:8168 
           IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 5.46 TiB used: 2.99 TiB (54.8%) 
           ID-1: /dev/sda vendor: Western Digital model: WD30EFRX-68EUZN0 size: 2.73 TiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0A82 scheme: GPT 
           ID-2: /dev/sdb vendor: Western Digital model: WD30EFRX-68EUZN0 size: 2.73 TiB speed: 6.0 Gb/s rotation: 5400 rpm 
           serial: <filter> rev: 0A82 scheme: GPT 
Partition: ID-1: / size: 491.15 GiB used: 12.81 GiB (2.6%) fs: ext4 dev: /dev/sda2 
           ID-2: /boot size: 999.7 MiB used: 139.3 MiB (13.9%) fs: vfat dev: /dev/sda1 
           ID-3: /home size: 2.19 TiB used: 502.01 GiB (22.4%) fs: ext4 dev: /dev/sda3 
           ID-4: swap-1 size: 13.67 GiB used: 29.2 MiB (0.2%) fs: swap dev: /dev/sda4 
Sensors:   System Temperatures: cpu: 22.9 C mobo: N/A gpu: amdgpu temp: 28 C 
           Fan Speeds (RPM): N/A gpu: amdgpu fan: 1026 
Info:      Processes: 244 Uptime: 4h 02m Memory: 11.68 GiB used: 1.88 GiB (16.1%) Init: systemd v: 242 Compilers: gcc: 9.2.0 
           Shell: bash v: 5.0.11 running in: konsole inxi: 3.0.37 

Thanks

From the looks of it, you've either got a damaged root filesystem ─ possibly the result of an unclean shutdown ─ or you've got a failing drive. :thinking:

You can try to check the filesystem with the live system of the USB stick containing Manjaro.

1 Like

check state of your disk /dev/sdg
something go wrong also udev with new systemd

1 Like

BTW I was doing backups this morning

$ lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0  2.7T  0 disk 
├─sda1   8:1    0 1000M  0 part /boot
├─sda2   8:2    0  500G  0 part /
├─sda3   8:3    0  2.2T  0 part /home
└─sda4   8:4    0 13.7G  0 part [SWAP]
sdb      8:16   0  2.7T  0 disk 
└─sdb1   8:17   0  2.7T  0 part /drive-b
sr0     11:0    1 1024M  0 rom  
  1. How do I found out which partition is having problems?
  2. Is it related to the tainted kernel?
  3. Can I interrupt the mkinitcpio?

Thanks

/dev/sdg was a usb hard drive that I used for doing my backups. Not plugged in anymore.

Thanks

Well, the one that had problems isn't shown in your list, because you've already stated in a later post that it's a USB drive. But apparently that drive is faulty nevertheless.

No. A tainted kernel is a kernel that has a proprietary driver module loaded into it. Given that proprietary software cannot be debugged and that kernel modules all run within the same address space, a kernel like that is considered "tainted" because the developers wouldn't be able to debug it, and they will thus reject any bug reports filed against a kernel like that.

I'm not sure what you mean by that. You probably mean the initramfsmkinitcpio is a script for creating an initramfs.

You cannot interrupt its execution "as such", but you can boot to a rescue shell in the initramfs. But this would have to be chosen from the boot loader screen, by supplying the option "rescue". You cannot interrupt the boot process once it is ongoing, because userspace hasn't been initialized yet.


Was it plugged in when you tried to boot?

No it was not

Thanks

i think it could come from theses bug on disconnect disks ( USB -- kernel 5.4.7 )
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.7
search for disconnect

Have you updated your bios to the most recent version because I'm pretty sure your MSI mobo had the same USB issues as my 970a Gigabyte mobo.

I have to use the "iommu=soft" kernel boot parameter on my mobo or it has major USB problems. I think the MSI boards had a bios update released to correct the issue. The Gigabyte mobos never did get an update.

As your computer is a little older I would also try kernel 4.14.I have found I/O errors occur on the newer kernels sometimes, but 4.14 is fine.

I also have an older mobo that is experiencing issues on any of the newer kernels except the real time kernels. So it pays to test quite a few different kernels.

1 Like

The last bios update from msi is Sep-2018 which I did.

I have not tested 4.14 yet.

I had to alt-sysrq-reisub to restart and right now it's back to "normal".

Thanks

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by