I moved a pair of 500 GB HDDs from onboard raid controller to another raid card (Marvell). The drives were setup in Raid1 configuration before the migration, and have now been set in the same configuration. However, when I try to restore the image created earlier by Clonezilla Live, I get an error message as below:
Destination disk is too small !!
Destination disk size: 976609280 sectors (500.0 GB) <<-- (This is correct)
Source disk size from the image: 976766976 sectors (500.1 GB) <<-- (This can't be true)
Program terminated !!
PLEASE HELP !!! I WILL BE IN BIG TROUBLE IF I CAN'T RESTORE
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My bad bad again.
Now I understand your system is firmware RAID.
Therefore please also run this command, too:
parted -s /dev/md126 print
then post the results, too.
Thanks.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please see attached pictures for the requested output.
Note: the volume shows up as /dev/md126 when connected to the onboard SATA controllers. And, the image starts to restore successfully when intended change is rolled back i.e. I connect the HDDs back to the onboard SATA.
The issue duplicates as soon as I go back to the Marvel RAID controller as seen in the pictures attached here.
/dev/md126 not available when using the Marvel RAID
At this time I am rolling my changes back. Going back to onboard Intel Matrix Raid and restoring the image, which appears to initiate without any trouble. Will report back in any problem persists with restored MBR or partition tables. I am hoping all goes fine.
Thanks for attempting to help !!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I moved a pair of 500 GB HDDs from onboard raid controller to another raid card (Marvell). The drives were setup in Raid1 configuration before the migration, and have now been set in the same configuration. However, when I try to restore the image created earlier by Clonezilla Live, I get an error message as below:
Destination disk is too small !!
Destination disk size: 976609280 sectors (500.0 GB) <<-- (This is correct)
Source disk size from the image: 976766976 sectors (500.1 GB) <<-- (This can't be true)
Program terminated !!
PLEASE HELP !!! I WILL BE IN BIG TROUBLE IF I CAN'T RESTORE
So what's the size of your source disk?
Steven.
Thanks for trying to help Steven !!
The image is stored on a 1 TB external USB drive with almost 725 GB available.
So could you please run the following commands in the Clonezilla live command prompt:
(replace /dev/sda with your source disk name)
Then post the results of (2) and (3).
Steven.
I am sorry, unable to share the output from the PC in trouble. However, I have attached the below link for you to access the "screenshot".
https://www.flickr.com/gp/ssaluja/sDq1f2
/dev/sdc1 is the source drive which contains the disk image
Oops... My bad, for (3) the correct command should be:
parted -s /dev/sdc print
(I missed the "print")
Please run it again and show us the results.
Steven.
My bad bad again.
Now I understand your system is firmware RAID.
Therefore please also run this command, too:
parted -s /dev/md126 print
then post the results, too.
Thanks.
Steven.
Please see attached pictures for the requested output.
Note: the volume shows up as /dev/md126 when connected to the onboard SATA controllers. And, the image starts to restore successfully when intended change is rolled back i.e. I connect the HDDs back to the onboard SATA.
The issue duplicates as soon as I go back to the Marvel RAID controller as seen in the pictures attached here.
I do not see the results of
parted -s /dev/md126 print
BTW, which version of Clonezilla live did you use?
Steven.
Using version 2.3.1-18-amd64
/dev/md126 not available when using the Marvel RAID
At this time I am rolling my changes back. Going back to onboard Intel Matrix Raid and restoring the image, which appears to initiate without any trouble. Will report back in any problem persists with restored MBR or partition tables. I am hoping all goes fine.
Thanks for attempting to help !!