[SOLVED] Kernel Panic

tld6008 · 08-22-2019, 09:03 AM

Quote:

Originally Posted by colorpurple21859

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?

jpollard · 08-22-2019, 09:36 AM

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.

jpollard · 08-22-2019, 09:40 AM

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.

tld6008 · 08-22-2019, 09:59 AM

Quote:

Originally Posted by jpollard

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.