Good morning.
Thank You.
I did understand
a lot of the system is destroyed.
Is hardware destroyed?
Is software destroyed?
Can Debian repair it?
Can Knoppix repair it?
Its a Desktop PC.
Made for WIN.
But we did only install Debian.
Before we used avidemux
but to often the update crashed.
Regards
Sophie
________________________________
Von: Hans <hans.ullr...@loop.de>
Gesendet: Montag, 25. April 2022 07:07
An: Debian-user List Debian <debian-user@lists.debian.org>
Cc: Schwibinger Michael <h...@hotmail.com>
Betreff: Re: AW: Here Newbie---Amateur in Linus...Problem: Debian LXDE cannot
boot
Am Sonntag, 24. April 2022, 18:53:44 CEST schrieb Schwibinger Michael:
Hello,
first of all, I believe, your hardddrive is corrupt. You should do a filesystem
check, maybe withj a livefile system like Knoppix or similar.
>From the log:
________________________________
Apr 24 17:02:52 ah kernel: [40646.269895] sdb: sdb1
Apr 24 17:02:52 ah kernel: [40646.274262] sd 4:0:0:0: [sdb] Attached SCSI
removable disk
Apr 24 17:02:52 ah kernel: [40646.718406] FAT-fs (sdb1): Volume was not
properly unmounted. Some data may be corrupt. Please run fsck.
Apr 24 17:04:14 ah kernel: [40728.467209] sd 4:0:0:0: [sdb] tag#0 FAILED
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 24 17:04:14 ah kernel: [40728.467221] sd 4:0:0:0: [sdb] tag#0 Sense Key :
Not Ready [current]
Apr 24 17:04:14 ah kernel: [40728.467228] sd 4:0:0:0: [sdb] tag#0 Add. Sense:
Medium not present
Apr 24 17:04:14 ah kernel: [40728.467240] sd 4:0:0:0: [sdb] tag#0 CDB: Read(10)
28 00 00 00 04 20 00 00 08 00
Apr 24 17:04:14 ah kernel: [40728.467243] blk_update_request: I/O error, dev
sdb, sector 1056
Apr 24 17:04:14 ah kernel: [40728.507341] sd 4:0:0:0: [sdb] tag#0 FAILED
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 24 17:04:14 ah kernel: [40728.507352] sd 4:0:0:0: [sdb] tag#0 Sense Key :
Not Ready [current]
Apr 24 17:04:14 ah kernel: [40728.507364] sd 4:0:0:0: [sdb] tag#0 Add. Sense:
Medium not present
Apr 24 17:04:14 ah kernel: [40728.507368] sd 4:0:0:0: [sdb] tag#0 CDB: Read(10)
28 00 00 00 04 20 00 00 08 00
Apr 24 17:04:14 ah kernel: [40728.507371] blk_update_request: I/O error, dev
sdb, sector 1056
Apr 24 17:04:14 ah kernel: [40728.507374] Buffer I/O error on dev sdb1, logical
block 128, async page read
Apr 24 17:04:29 ah kernel: [40743.517610] usb 4-4: USB disconnect, device
number 4
and this:
Apr 24 21:57:43 ah kernel: [58337.363585] sd 4:0:0:0: [sdb] Attached SCSI
removable disk
Apr 24 21:57:43 ah kernel: [58337.638502] FAT-fs (sdb1): Volume was not
properly unmounted. Some data may be corrupt. Please run fsck.
Apr 24 22:02:24 ah kernel: [58618.435420] sd 4:0:0:0: [sdb] tag#0 FAILED
Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 24 22:02:24 ah kernel: [58618.435432] sd 4:0:0:0: [sdb] tag#0 Sense Key :
Not Ready [current]
Apr 24 22:02:24 ah kernel: [58618.435439] sd 4:0:0:0: [sdb] tag#0 Add. Sense:
Medium not present
________________________________
Secondary, I believe, youre hardware is a netbook. Your harddrive is only 64GB
and this line (but here I am really not sure):
Apr 24 19:26:13 ah kernel: [49247.171760] [drm:intel_pipe_update_end [i915]]
*ERROR* Atomic update failure on pipe A (start=2954506 end=2954507) time 180
us, min 1017, max 1023, scanline start 1014, end 1026
Atomic sounds like Intel Atomic CPU.
________________________________
Further investigation shows, you have an Intel hardware, and your graphics card
is an I915 chip by Intel. This is supported by the kernel itself, but as far as
I remember, you need the package "xserver-xorg-intel".
________________________________
However, the main reason, why it may crash, might be the corrupted harddrive.
This would be the first point, I would fix.
Download some livelinux image like Knoppix, TRK, GRML, R.I.P. or Debian Live,
whatever, create a bootable device and boot from it.
Then you can filescheck your harddrive.
________________________________
Another thing, I wondered: Do you have two harddrives in your computer? The log
shows sdb, but the first drive should be sda.
Also it shows, that the filesystem is FAT, but should be ext2, ext3 or ext4.
Please recheck.
________________________________
Can not say any more at the moment, maybe it helps either.
Good luck!
Hans
