LinuxQuestions.org
Page 2 of 5 1 2 34 Last »
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Kernel Panic (https://www.linuxquestions.org/questions/linux-newbie-8/kernel-panic-4175659204/)

tld6008 08-16-2019 02:42 PM
Quote:
Originally Posted by colorpurple21859 (Post 6025759)
boot into a live iso open a terminal post the output of
Code:
sudo fdisk -l
that is a lower case L
below is what was returned

grub> sudo fdisk -l
error: can't find command 'sudo'
grub>

tld6008 08-16-2019 04:25 PM
Quote:
Originally Posted by hazel (Post 6025755)
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.
What I ended up doing was creating a bootable USB with the latest Zorin distro (15) and was able to boot it up the computer. I could not get it to boot with the original USB with Zorin 12 on it, it just went into the same screen I posted. Anyway I opened Gparted and did a check on the sda7 and it did some type of repair. I then tried to reboot to the original Zorin but the same problem appears.

tld6008 08-16-2019 04:31 PM
2 Attachment(s)
Quote:
Originally Posted by colorpurple21859 (Post 6025759)
boot into a live iso open a terminal post the output of
Code:
sudo fdisk -l
that is a lower case L
I was able to input your suggestion in the terminal window when I booted up with a new Zorin 15 distro, it did not have the grub> on the command line and I received a different result with is attached in 2 attachments. Hopefully this shows something usefull.

tld6008 08-16-2019 05:58 PM
Quote:
Originally Posted by pan64 (Post 6025744)
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
I have taken the advice you gave in step 2 and have a bootable usb but still do not know how to do specific analyzing

pan64 08-17-2019 01:41 AM
good, that was the first step. The next one is to boot from that usb and identify your sda7 (probably it has now a different name, like sdb7).
at the console you can execute fsck /dev/sda7. see some additional info here: https://www.maketecheasier.com/check...em-fsck-linux/.

tld6008 08-17-2019 11:28 AM
Quote:
Originally Posted by pan64 (Post 6026008)
good, that was the first step. The next one is to boot from that usb and identify your sda7 (probably it has now a different name, like sdb7).
at the console you can execute fsck /dev/sda7. see some additional info here: https://www.maketecheasier.com/check...em-fsck-linux/.
This is what came back:

fsck from util-linux 2.31.1
e2fck 1.44.1 (24-Mar-2018)
/dev/sda7: clean, 876658/28549120 files, 8821966/114176000 blocks

Am I right in assuming there is no problem ?

pan64 08-17-2019 12:23 PM
make sure this /dev/sda is the same device. you can try fdisk -l to see your partitions, compare it to the result posted earlier.

colorpurple21859 08-17-2019 02:53 PM
use the bootinfo script for more information on your system. https://help.ubuntu.com/community/Boot-Info

tld6008 08-17-2019 08:02 PM
Quote:
Originally Posted by pan64 (Post 6026157)
make sure this /dev/sda is the same device. you can try fdisk -l to see your partitions, compare it to the result posted earlier.
What do you mean by Same Device? What other device would it be? I can see it with Gparted but will try the command you suggested.

pan64 08-18-2019 02:52 AM
/dev/sda /dev/sdb and similars are generated during boot. These logical names do not belong to any real device, but will be attached dynamically as kernel detects the hardware. usually /dev/sda is the first detected device, /dev/sdb is the second one. Usually the first one (sda) contains the boot - but all of these may depend on the actual configuration/system/kernel/whatever. gparted is ok, you can check if that /dev/sda7 is exactly the same when you boot from usb.

The ext4-fs error was reported by fsck, so most probably you will get the same error on the same device (if that was not already fixed somehow, but in that case the normal boot should work too).

tld6008 08-19-2019 11:08 AM
Quote:
Originally Posted by colorpurple21859 (Post 6026204)
use the bootinfo script for more information on your system. https://help.ubuntu.com/community/Boot-Info
Will one or many of you look at the following report? So far all the tests I have done as recommended above have not indicated a remedy to my problem and I still can't load Zorin. I am not at all certain how to decipher the report but it appears there may be some issues.


https://paste.ubuntu.com/p/n9TKJnxtXs/

tld6008 08-19-2019 04:48 PM
1 Attachment(s)
I am not giving up! I notice that the report I am able to see(attached) is somewhat different now. When I start the computer the boot option for Zorin include an option for a safe mode When I boot like that it still panics but the log is slowly generated and it ends up with more on the screen when it locks up. Do you know of anyway to fully view or save the log?

colorpurple21859 08-19-2019 06:36 PM
is legacy boot disabled in the bios?
boot the usb, open a terminal
post the ouput of the following
Code:
sudo mkdir /mnt/sda7
sudo mount /dev/sda7 /mnt/sda7
cat /mnt/sda7/etc/fstab

pan64 08-20-2019 03:43 AM
it looks like there was no /dev/sda7 related filesystem error (at least on the picture I can't find any). But there is something else, which may cause filesystem corruption and that may lead to the error mentioned earlier - at the next boot.
What I see now: the init process was died but I don't know why.

jpollard 08-20-2019 06:45 AM
There could be some data corruption in the boot file itself.

It could be masked by previous repair passes that made the filesystem itself consistent, but leave the files with bad data.

I'm not sure as this particular problem would appear to be in the initrd as I don't see any message about switching to sda7 as the real root.

Normally, I would have expected the unpacking of the initrd itself failed for such corruption.

Note: it DID mount sda7, and start looking for processing scripts, but the message for switch root isn't present before the crash.

I'm not familiar with this particular boot sequence though. The corrupted file could be on sda7 and I just overlooked the switch to sda7 as root.


All times are GMT -5. The time now is 05:59 PM.
Page 2 of 5 1 2 34 Last »
Show 50 post(s) from this thread on one page