On 03.02.2024 09:13, -pj via openSUSE Users wrote:
Thinkcentre-M57p:/usr/share/susepaste> ls -l /sys/block total 0 lrwxrwxrwx 1 root root 0 Feb 2 16:33 dm-0 -> ../devices/virtual/block/dm-0 lrwxrwxrwx 1 root root 0 Feb 2 17:10 dm-1 -> ../devices/virtual/block/dm-1 lrwxrwxrwx 1 root root 0 Feb 2 17:10 dm-2 -> ../devices/virtual/block/dm-2 lrwxrwxrwx 1 root root 0 Feb 2 17:19 dm-3 -> ../devices/virtual/block/dm-3 lrwxrwxrwx 1 root root 0 Feb 2 16:33 fd0 -> ../devices/platform/floppy.0/block/fd0 lrwxrwxrwx 1 root root 0 Feb 2 17:10 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Feb 2 17:16 sdc -> ../devices/pci0000:00/0000:00:1d.7/usb3/3-6/3-6:1.0/host5/target5:0:0/5:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Feb 2 16:33 sr0 -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0 Thinkcentre-M57p:/usr/share/susepaste>
On 02-03-2024 12:07AM, Andrei Borzenkov wrote:
ls -l /sys/block
OK, so messages are apparently 7 hours old and refer to the device that is no more present on your system. Nothing can be guessed about them now. You can run "journalctl -b" and investigate when sdb appeared and disappeared. But messages themselves are not direct indications of any hardware failure. They may be consequences of hardware failure, but for this you need to look in logs for earlier errors.