Booting problem

AmandaONeill · September 11, 2021, 4:58pm

Sep 11 18:36:23 honnoji kernel: blk_update_request: critical medium error, dev sr1, sector 145368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Sep 11 18:36:23 honnoji kernel: blk_update_request: critical medium error, dev sr1, sector 143872 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0
Sep 11 18:36:23 honnoji kernel: blk_update_request: critical medium error, dev sr1, sector 144112 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Sep 11 18:36:23 honnoji kernel: blk_update_request: critical medium error, dev sr1, sector 143872 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Sep 11 18:36:23 honnoji kernel: Buffer I/O error on dev sr1, logical block 17984, async page read
Sep 11 18:36:23 honnoji kernel: blk_update_request: critical medium error, dev sr1, sector 145360 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Sep 11 18:36:23 honnoji kernel: Buffer I/O error on dev sr1, logical block 17984, async page read
Sep 11 18:36:26 honnoji wpa_supplicant[678]: Using interface wlan0 with hwaddr 94:b8:6d:8b:b9:d3 and ssid “honnoji temple”
Sep 11 18:36:29 honnoji pulseaudio[1166]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.
Sep 11 18:45:51 honnoji dolphin[11882]: kf.jobwidgets: Couldn’t start kuiserver from org.kde.kuiserver.service: QDBusError(“org.freedesktop.DBus.Error.ServiceUnknown”, “The name org.kde.kuiserver was not provided by any .service files”)

Sep 11 17:54:27 honnoji kernel: x86/cpu: SGX disabled by BIOS.

Kresimir · September 11, 2021, 5:00pm

otherbarry · September 11, 2021, 5:05pm

Those errors indicate your drive may be failing.

You may want to fsck that drive first.

More info on that message.

https://bbs.archlinux.org/viewtopic.php?id=269249

Seems benign enough.

Keep going back (ie -2, -3, -4, -5 … etc) and see if you can find the first failed reboot, or even the boot cycle that orginally hung.

Otherwise it could be your hdd on the way out.

Either way I’d backup what you have, just in case.

keybreak · September 11, 2021, 5:11pm

It’s not just drive, i think it’s CD/DVD drive

@AmandaONeill
Show us

lsblk -o TRAN,ROTA,GROUP,MODEL,NAME,SIZE,FSTYPE,MOUNTPOINTS,FSUSE%,FSUSED,FSAVAIL,SCHED,HOTPLUG,OWNER,MODE

If that’s indeed CD/DVD drive first of all disconnect it and see if everything is fine, then inspect if maybe it’s cables SATA / power is intact - if it is intact, then inspect the drive itself - perhaps it’s dead…

AmandaONeill · September 11, 2021, 5:31pm

well, thats daunting

fsck from util-linux 2.37.2
e2fsck 1.46.4 (18-Aug-2021)
/dev/sda2 is mounted.
WARNING!!! The filesystem is mounted. If you continue you WILL
cause SEVERE filesystem damage.

i think its

– Journal begins at Wed 2021-09-01 04:41:06 CEST, ends at Sat 2021-09-11 19:29:59 CEST. –
Sep 01 04:41:06 honnoji kernel: x86/cpu: SGX disabled by BIOS.
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Wrong diagnostic page; asked for 1 got 8
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Failed to get diagnostic page 0x1
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Failed to bind enclosure -19
Sep 01 04:46:32 honnoji systemd-coredump[8137]: Failed to connect to coredump service: Connection refused
Sep 01 04:46:33 honnoji kernel: watchdog: watchdog0: watchdog did not stop!

its barely a few years old, i never really did anything to cause such early ssd failure

TRAN ROTA GROUP MODEL NAME SIZE FSTYPE MOUNTPOINTS FSUSE% FSUSED FSAVAIL SCHED HOTPLUG OWNER MODE
sata 0 disk SanDi sda 119,2G mq-deadline 0 root brw-rw----
0 disk ├─sda1
│ 512M vfat /boot/efi 0% 296K 510,7M mq-deadline 0 root brw-rw----
0 disk └─sda2
118,7G ext4 / 22% 25,2G 85,1G mq-deadline 0 root brw-rw----
sata 0 disk SanDi sdb 931,5G mq-deadline 0 root brw-rw----
0 disk └─sdb1
931,5G ext4 mq-deadline 0 root brw-rw----
usb 0 disk Samsu sdc 931,5G mq-deadline 1 root brw-rw----
0 disk └─sdc1
931,5G ext4 mq-deadline 1 root brw-rw----
usb 0 disk SanDi sdd 931,5G mq-deadline 1 root brw-rw----
0 disk └─sdd1
931,5G exfat /run/media/honnoji/external 95% 886,1G 45,4G mq-deadline 1 root brw-rw----
usb 1 disk TF CA sde 0B mq-deadline 1 root brw-rw----
sata 1 optic PLDS sr0 1024M mq-deadline 1 root brw-rw----
usb 1 optic Mass sr1 71M iso966 mq-deadline 1 root brw-rw----

keybreak · September 11, 2021, 5:34pm

So it’s your USB optical drive which gave that errors…?
Disconnect it, check usb connection, check if it can actually work / can read stuff from disc

It looks to me that this can be easily caused by some failure connected to that sr1 drive:

– Journal begins at Wed 2021-09-01 04:41:06 CEST, ends at Sat 2021-09-11 19:29:59 CEST. –
Sep 01 04:41:06 honnoji kernel: x86/cpu: SGX disabled by BIOS.
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Wrong diagnostic page; asked for 1 got 8
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Failed to get diagnostic page 0x1
Sep 01 04:41:07 honnoji kernel: scsi 7:0:0:1: Failed to bind enclosure -19
Sep 01 04:46:32 honnoji systemd-coredump[8137]: Failed to connect to coredump service: Connection refused
Sep 01 04:46:33 honnoji kernel: watchdog: watchdog0: watchdog did not stop!

otherbarry · September 11, 2021, 5:46pm

Be careful using fsck. Do a dry run first.

Make sure the file system you are checking is not mounted, if that is a root partition then this has to be done from another system or live environment.

May not be the ssd.

Still, a good time to do backups, just in case.

AmandaONeill · September 11, 2021, 6:00pm

well, this is all not only daunting but frankly i do not know whats going on anymore, in the way that i never fully understood the fsck disk command nor hwo to use it
or the fact i basically never use this drive
i also keep an img file of the boot drive

and lastly i do plan on getting a new pc with a certain influx of money happening sometime thie month so either here is hoping drives are okay until that moment, and even if they arent i should be able to change it out if worse comes to worse

joekamprad · September 11, 2021, 6:31pm

A full boot log would give some more complete information:
journalctl -b -0 | eos-sendlog

AmandaONeill · September 11, 2021, 7:03pm

https://clbin.com/wYcmX

joekamprad · September 11, 2021, 7:52pm

Login Manage (LightDM) failed:

Sep 11 18:36:22 honnoji systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Sep 11 18:36:22 honnoji systemd[1]: lightdm.service: Failed with result 'exit-code'.
Sep 11 18:36:22 honnoji audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lightdm comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Nvidia Driver used // what card?

Sep 11 18:36:22 honnoji kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 20:44:16 UTC 2021
Sep 11 18:36:22 honnoji kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  470.63.01  Tue Aug  3 20:30:55 UTC 2021
Sep 11 18:36:22 honnoji kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Sep 11 18:36:22 honnoji kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1

pcieport errors… can be loose card, failing hardware or missconfiguration…

Sep 11 18:36:26 honnoji kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
Sep 11 18:36:26 honnoji kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Sep 11 18:36:26 honnoji kernel: pcieport 0000:00:1c.0:   device [8086:a33d] error status/mask=00000001/00002000
Sep 11 18:36:26 honnoji kernel: pcieport 0000:00:1c.0:    [ 0] RxErr                  (First)

BIOS O3QKT16A 11/06/2018 outdated?
check here:
https://pcsupport.lenovo.com/de/de/products/desktops-and-all-in-ones/500-series/510-15icb/90hu/90hu002qge/downloads/driver-list/component?name=BIOS

Sep 11 18:36:21 honnoji kernel: efi: EFI v2.60 by American Megatrends
Sep 11 18:36:21 honnoji kernel: efi: ACPI 2.0=0x7aebc000 ACPI=0x7aebc000 TPMFinalLog=0x7b362000 SMBIOS=0x7b8bf000 SMBIOS 3.0=0x7b8be000 ESRT=0x77847418 MEMATTR=0x77828018 
Sep 11 18:36:21 honnoji kernel: SMBIOS 3.1.1 present.
Sep 11 18:36:21 honnoji kernel: DMI: LENOVO 90HU002QGE/36EB, BIOS O3QKT16A 11/06/2018

Please give:
inxi -G | eos-sendlog
for info about GPU
Reinstall Nvidia Drivers:
sudo nvidia-installer-dkms
Try reverting to Nouveau:
sudo nvidia-installer-dkms -n
Try updating BIOS/Firmware

AmandaONeill · September 11, 2021, 8:39pm

https://clbin.com/Cbf4W

i always found to have hardware acceleration problems with the installer, so i installed it manually “through yay” and i had no problems until today

never ever had to do so in my entire life, i would have no idea honestly how i would do so thanks to that

ricklinux · September 11, 2021, 8:56pm

Did you happen to have an audio cd in the drive on boot?

joekamprad · September 11, 2021, 9:28pm

could be the first time now But it is a known fact that it is good to have the latest firmware if using Linux, also we all know it is troublesome to update firmware in cases where producer only have windows apps to do that…
A si can see same for your device Lenovo provides only a windows exe file you can run from WIndows 10…

There are ways to run these files also without windows… like using hiren BootCD or similar… but the adventure is preprogrammed

AmandaONeill · September 12, 2021, 3:38am

the last time i used the cd drive was last year to copy some files from an audio cd

i have sworn myself off from windows only after a few months after i got into linux

i assume something like wine wont work?

system · September 14, 2021, 3:39am

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