Hello,

I have moved a partition with Clonezilla to another disk on the same server so I could fix an issue with the partition table on disk sda. After this fix I restored again with Clonezilla the partition content back to /dev/sda2.

Directly booting to /dev/sda2 ended with a kernel panic (normal I think). So I booted with a Slackware DVD and tried to boot from there. Unfortunately I get as well a kernel panic.

The content is well in /dev/sda2 and I can access it.

Does someone has another idea how to fix this issue? I have a backup so worst case is to re-install and restore the backup.

Regards,
Silvio

So /dev/sda2 is the partition from which your system should boot?
What was the nature of your "fix" on sda? Could you have maybe nuked the MBR by accident?
EDIT:nevermind that wouldn't be it. Have a bump anyway!

Hello STDOUBT,
I used cfdisk to create the partitions and so the start sector was not correct. So I moved the partition with Clonezilla and created the partition with fdisk. My MBR is still ok and as you mentioned this would not impact to boot the system from a DVD.

Cheers,
Silvio

Check your partition order, maybe your root partition is no longer /dev/sda2.

And what type of kernel panic you have?
Look closely at the messages just before panic - this should help you to track problem. (Most probably: wrong partition name, wrong disk order, missing fs type [missing initrd], missing init).

Sounds like you need to run lilo on it.

Hello dive and Labinnah,

Thank you for your replies and sorry for late reply but I was out of town without access to my server that was not running ;-)

At first I tried to rerun lilo but it gave me an error message something like 'this is a binary file'. I can't remember the exact wording. Today I used again Clonezilla and I moved again the saved partition from sda4 to sda2. This time I could start up the server with the Slack14.1 DVD. After having run lilo all is working as expected. The only error done from my side that I can think of is that the first time I used the 32bit side of the Slack DVD instead 64bit. I don't know it this could be the culprit.

Tagging this thread as solved,

Cheers,
Silvio