LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-22-2019, 10:03 AM   #61
tld6008
Member
 
Registered: Mar 2014
Location: Pensacola
Distribution: Zorin
Posts: 48

Original Poster
Rep: Reputation: Disabled

Quote:
Originally Posted by colorpurple21859 View Post
boot into the live iso from the file manager you should be able to access the zorin partition and your windows partition, copy the items you want to save and/or your home directory to your windows partition.
I just tried to reboot the system normally and the startup screen (blue with the pulsing Z) was taking too long so I walked away for a couple minutes and when I got back there was this, not the kernel panic that had been being produced repeatedly. Don't know it this indicates anything usable?
Attached Thumbnails
Click image for larger version

Name:	SAM_1504.jpg
Views:	2
Size:	49.4 KB
ID:	31185  
 
Old 08-22-2019, 10:36 AM   #62
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,844

Rep: Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478
The initrd is corrupted.

One of the things missing/damaged is the udev/eudev to scan for devices and build /dev.

You can sometimes work around this by booting live system, but specify the kernel "root=" for it to mount.

This will use the initrd from live CD/DVD/USB device to initialize the device, and then redirect it to using the target disk for root.

If that works then you might try recreating the initrd (mkinitrd), but there could be other damage on the filesystem. It never hurts to try it, as it may fix everything. Be sure the initrd you create will be the one used on the next default boot or you get the same error.
 
Old 08-22-2019, 10:40 AM   #63
jpollard
Senior Member
 
Registered: Dec 2012
Location: Washington DC area
Distribution: Fedora, CentOS, Slackware
Posts: 4,844

Rep: Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478Reputation: 1478
The initrd is corrupted.

One of the things missing/damaged is the udev/eudev to scan for devices and build /dev.

You can sometimes work around this by booting live system, but specify the kernel "root=" for it to mount.

This will use the initrd from live CD/DVD/USB device to initialize the device, and then redirect it to using the target disk for root.

If that works then you might try recreating the initrd (mkinitrd), but there could be other damage on the filesystem. It never hurts to try it, as it may fix everything. Be sure the initrd you create will be the one used on the next default boot or you get the same error.

If the mkinitrd fails, you definitely are right up to a reinstall.

The reinstall is faster than trying to reinstall the various packages independantly - I've done that once, and won't do it again as for me it tool almost all day. What slows it down is the allocation/deallocation of every file being reinstalled. And then the corruption may extend to the installation tools on the disk...

sorry for the double post.
 
Old 08-22-2019, 10:59 AM   #64
tld6008
Member
 
Registered: Mar 2014
Location: Pensacola
Distribution: Zorin
Posts: 48

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by jpollard View Post
The initrd is corrupted.

One of the things missing/damaged is the udev/eudev to scan for devices and build /dev.

You can sometimes work around this by booting live system, but specify the kernel "root=" for it to mount.

This will use the initrd from live CD/DVD/USB device to initialize the device, and then redirect it to using the target disk for root.

If that works then you might try recreating the initrd (mkinitrd), but there could be other damage on the filesystem. It never hurts to try it, as it may fix everything. Be sure the initrd you create will be the one used on the next default boot or you get the same error.

If the mkinitrd fails, you definitely are right up to a reinstall.

The reinstall is faster than trying to reinstall the various packages independantly - I've done that once, and won't do it again as for me it tool almost all day. What slows it down is the allocation/deallocation of every file being reinstalled. And then the corruption may extend to the installation tools on the disk...

sorry for the double post.
Thanks for you help, sounds like a new install is the way to go. I definitely need to take the easiest path.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Determining cause of Linux kernel panic "Kernel panic - not syncing: Fatal exception" gladman002 Linux - Kernel 1 09-07-2015 09:04 PM
PANIC! KERNEL panic.... Solean Slackware 2 05-03-2003 01:27 AM
Kernel Panic Kernel Panic!!! aditya Linux - Newbie 5 09-09-2002 12:46 AM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 04:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 01:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration