0

Linux is continuously throwing these error logs:

XFS: metadata I/O error in "xfs_trans_read_buf_map" at daddr ... len 32 error 5

XFS: xfs_imap_to_bp: xfs_trans_read_buf() returned error -5

The laptop is slow and opening a web browser takes minutes. What could be the cause?

Screenshot

Update

Also, there is a Windows virtual machine which is showing BSoD consistently at boot time. Maybe it's a related problem:

https://superuser.com/q/1692804/571029

Megidd
  • 1,519
  • 3
  • 32
  • 44
  • Related: https://unix.stackexchange.com/q/607162/158683 – Megidd Dec 14 '21 at 08:27
  • 4
    this looks very much like a faulty drive, you can't fix filesystems on faulty drives, you have to ddrescue first then hope for the best – frostschutz Dec 14 '21 at 08:35
  • @frostschutz Thanks. Also, my Windows 10 virtual machine is showing blue-screen-of-death at boot time consistently. I'm not sure, but maybe that's a related problem. – Megidd Dec 14 '21 at 08:40
  • 1
    Maybe the read errors in the faulty drive are all in the sectors occupied by the VM virtual hard disk. Check badblocks and SMART – golimar Dec 15 '21 at 09:22
  • @golimar Thanks. I will try `badblocks` and `SMART` – Megidd Dec 15 '21 at 12:01
  • I will have to back up the data and replace the hard disk: https://unix.stackexchange.com/q/683313/158683 – Megidd Dec 21 '21 at 12:10
  • I will have to back up the data and replace the hard disk: https://unix.stackexchange.com/q/683313/158683 – Megidd Dec 21 '21 at 12:10

2 Answers2

0

I just powered off the Linux laptop for a few hours and the XFS errors got resolved.

However, as soon as I start a Windows virtual machine inside Linux laptop, I receive some kernel errors. Not exactly the XFS errors, but some errors like:

blk_update_request: I/O error, dev sda, sector 1654298024 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0

ata1.00: exception Emask 0x0 SAct 0x80000000 SErr 0x40000 action 0x0

ata1.00: irq_stat 0x40000008

ata1: SError: { CommWake }

ata1.00: failed command: READ FPDMA QUEUED

ata1.00: cmd 60/08:f8:a8:95:9a/00:00:62:00:00/40 tag 31 ncq dma 4096 in res 41/40:08:a8:95:9a/00:00:62:00:00/40 Emask 0x409 (media error)

ata1.00: status: { DRDY ERR }

ata1.00: error: { UNC }

Screenshot

The virtual machine takes forever to boot. It doesn't boot. Just an empty screen is shown:

Virtual machine screenshot

Megidd
  • 1,519
  • 3
  • 32
  • 44
0

Conclusion

I will have to back up the data and replace the hard disk:

What does command do: `badblocks -svn /dev/sda`? does it just report the bad blocks?

Tried

I just used badblocks -svn /dev/sda command to handle the bad blocks of the hard disk. As suggested here. It took almost two days to finish!

Screenshot

Megidd
  • 1,519
  • 3
  • 32
  • 44