Kernel Panic
2 Attachment(s)
Attachment 31126I have been using Zorin 9 since it became available. I have a dual boot laptop with windows 10 which I rarely use, I mainly use the computer for my PLEX media server and general web browsing, email etc. So I am not a Linux expert by any means. Anyway I went to reboot the computer yesterday and it boots to the window I have attached. I disconnected everything from the computer and tried again but it just ends up with the same display and I can't do anything with it other than power it off. The caps lock key blinks steady during this situation. Hopefully someone here can give me some assistance.
TIA tld6008 |
I added another pic to original message which had more text on the screen but it may be too blurry to read
|
The top of your first image shows you are having filesystem problems. Have you tried booting into a live USB distro and checking your file systems?
|
Quote:
|
Is zorin 9 on a separate drive from windows?
|
Quote:
Thanks |
Quote:
|
Quote:
|
sda is your first hard disk (HDD or SSD) and sda7 is the partition number 7 on this device. It looks like the filesystem on that partition is corrupted (or the device itself has gone away).
You need to boot a live CD and analyze it. But it looks like you need to learn how to do it. You can use your windows and for example this link: https://tutorials.ubuntu.com/tutoria...k-on-windows#0 (you do not need to use zorin). But you can try this too: https://www.letsinstall10.com/2018/0...in-os-usb.html |
did you happen to do a windows update just before all this happened?
|
Quote:
|
Quote:
|
We can't tell if you need to reinstall until you have helped us to determine what went wrong. Usually in Linux, you do not need to reinstall a distro. Most of what goes wrong can be corrected. If you boot from your Zorin installation disc, you can run some simple checks on that sda7 partition and hopefully find out what is wrong with it. For example, if you have an ext4 filesystem (which is probably what you have there) the e2fsck command will check it for errors and correct any that it finds. This link suggests running the badblocks and smartctl commands after receiving this "unable to read itable" error.
|
boot into a live iso open a terminal post the output of
Code:
sudo fdisk -l |
Quote:
I just rechecked the files the Rufus file is an .exe program |
All times are GMT -5. The time now is 02:42 PM. |