I've successfully created a disk image using CloneZilla from a SATA disk partitioned as below:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 38913 312464250 8e Linux LVM
I restored to a factory new SATA disk (not previously formatted or partitioned) and left the options on the defaults (letting it create the partitions etc.). I've attempted to test the new drive, disconnecting the old one and connecting the new on it's cable. I get Kernel panics and messages saying no volume could be found.
I'm running CentOS5 and I believe using LVM2 (as running the following command returns the ID of the device-mapper module which I understand is only present in LVM2?)
Normally the step you did should work, no extra post config you have to do.
When you mentioned about "get Kernel panics and messages saying no volume could be found", could you show more details about the error messages ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Steven, thanks for your reply. This is the message I get when the new drive is used in place of the old drive:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
ACAPI: Getting cpuindex for acpiid 0x2
ACAPI: Getting cpuindex for acpiid 0x3
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
Mount: could not find filesystem '/dev/root'
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Switchroot: mount failed: No such file or directory
Kernel panic - not synching: Attempted to kill init!
ernel alive
Kernel direct mapping tables up to 100000000 @ 8000-d000
If it has any impact, the new drive is 640GB while the cloned drive is only 320GB. The backup and restore from CloneZilla was made directly to the new drive without performing any initialisation or partitioning beforehand. I don't think that CloneZilla attempted to resize the partitions to fill the unused space - I just went with the default settings all the way.
Thanks,
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you boot your new disk with clonezilla live, then in command prompt, run:
0. sudo su -
1. /opt/drbl/sbin/ocs-lvm2-start
2. pvscan
3. vgscan
4. lvscan
Then post the results of 2-4.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't think there were any errors the first time I tried the restore. I tried the restore operation again this weekend and it worked. I'm pretty sure I used the same (default) options this time around, the only possible difference I can think of is that I booted from the cloned drive while it was still attached by the external e-sata cable, but I think I tried that last time too.
Anyway, seems to be working now, thanks for your help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am getting the same error while booting the restored image.
I created a image of red hat linux 5 on 20gb hard drive and restored the image on a 500 gb hard drive.
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
ACAPI: Getting cpuindex for acpiid 0x2
ACAPI: Getting cpuindex for acpiid 0x3
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
Mount: could not find filesystem '/dev/root'
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Switchroot: mount failed: No such file or directory
Kernel panic - not synching: Attempted to kill init!
ernel alive
I am using clonezilla live clonezilla-live-1.2.1-23.
Thanks,
Vijay
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am able to restore the same image on a intel p4 40 gb hd.
But when I restored the image on a sunfire x2100 amd ,500 gb drive getting boot errors as mentioned above.
Please help.
--Vijay.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there any resolution anyone has found for this? I am having the same problem with restoring as well, same error. Any suggestions or workarounds greatly appreciated!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Emperorzombie,
Not sure... I can not reproduce the problem here...
The source disk is installed with CentOS ? How did you install that ? How about the partition table and LVM layout ? Could you please list them as detail as possible so that it's easier for us to duplicate the environment and reproduce the problem here ?
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I've successfully created a disk image using CloneZilla from a SATA disk partitioned as below:
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 38913 312464250 8e Linux LVM
I restored to a factory new SATA disk (not previously formatted or partitioned) and left the options on the defaults (letting it create the partitions etc.). I've attempted to test the new drive, disconnecting the old one and connecting the new on it's cable. I get Kernel panics and messages saying no volume could be found.
I'm running CentOS5 and I believe using LVM2 (as running the following command returns the ID of the device-mapper module which I understand is only present in LVM2?)
cat /proc/misc | grep device-mapper | awk '{print $1}'
Is there some post config I need to do to get the cloned disk's LVM partition recognised and the system booted?
Thanks for your help.
Normally the step you did should work, no extra post config you have to do.
When you mentioned about "get Kernel panics and messages saying no volume could be found", could you show more details about the error messages ?
Hi Steven, thanks for your reply. This is the message I get when the new drive is used in place of the old drive:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
ACAPI: Getting cpuindex for acpiid 0x2
ACAPI: Getting cpuindex for acpiid 0x3
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
Mount: could not find filesystem '/dev/root'
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Switchroot: mount failed: No such file or directory
Kernel panic - not synching: Attempted to kill init!
ernel alive
Kernel direct mapping tables up to 100000000 @ 8000-d000
If it has any impact, the new drive is 640GB while the cloned drive is only 320GB. The backup and restore from CloneZilla was made directly to the new drive without performing any initialisation or partitioning beforehand. I don't think that CloneZilla attempted to resize the partitions to fill the unused space - I just went with the default settings all the way.
Thanks,
Scott
Could you boot your new disk with clonezilla live, then in command prompt, run:
0. sudo su -
1. /opt/drbl/sbin/ocs-lvm2-start
2. pvscan
3. vgscan
4. lvscan
Then post the results of 2-4.
I think the clone was not finished correctly. Did you see any error messages when you restore the image ?
Hi Steven,
I don't think there were any errors the first time I tried the restore. I tried the restore operation again this weekend and it worked. I'm pretty sure I used the same (default) options this time around, the only possible difference I can think of is that I booted from the cloned drive while it was still attached by the external e-sata cable, but I think I tried that last time too.
Anyway, seems to be working now, thanks for your help!
Scott,
OK, no problem.
If you find the problem is reproducible, please let us know.
Steven.
Hi Steven,
The results I get are:
1: /opt/drb1/ocs-lvm2-start
Setting up the Logical Volume Manager
No volume groups found
No volume groups found
2: pvscan
No matching physical volumes found
3: vgscan
No volume groups found
4: lvscan
No volume groups found
Not looking too flash then :o
Hi Steven,
I am getting the same error while booting the restored image.
I created a image of red hat linux 5 on 20gb hard drive and restored the image on a 500 gb hard drive.
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
ACAPI: Getting cpuindex for acpiid 0x2
ACAPI: Getting cpuindex for acpiid 0x3
Red Hat nash version 5.1.19.6 starting
Reading all physical volumes. This may take a while...
No volume groups found
Volume group "VolGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
Mount: could not find filesystem '/dev/root'
Setuproot: moving /dev failed: No such file or directory
Setuproot: error mounting /proc: No such file or directory
Setuproot: error mounting /sys: No such file or directory
Switchroot: mount failed: No such file or directory
Kernel panic - not synching: Attempted to kill init!
ernel alive
I am using clonezilla live clonezilla-live-1.2.1-23.
Thanks,
Vijay
Vijay,
How about Clonezilla live 1.2.1-39 ? Same problem ?
Steven.
Hi Steven,
I am able to restore the same image on a intel p4 40 gb hd.
But when I restored the image on a sunfire x2100 amd ,500 gb drive getting boot errors as mentioned above.
Please help.
--Vijay.
Hi Steven,
Yeah same problem with Clonezilla live 1.2.1-39 too.
--Vijay
Is there any resolution anyone has found for this? I am having the same problem with restoring as well, same error. Any suggestions or workarounds greatly appreciated!
Emperorzombie,
Not sure... I can not reproduce the problem here...
The source disk is installed with CentOS ? How did you install that ? How about the partition table and LVM layout ? Could you please list them as detail as possible so that it's easier for us to duplicate the environment and reproduce the problem here ?
Steven.