So I set up an Ubuntu Hardy box, and have configured DRBL and Clonezilla, and I can boot over PXE and such. I have it set up as a private lan. The Ubuntu box has two ethernet cards. One connected to our network(where I work) and the other is connected to an isolated switch.
When I set clonezilla to save the image (with dcs script) and boot, I am getting errors. Basically what it comes down to is that whatever is trying to clone the hard drive is trying to clone the whole hard drive with empty sectors.
This was sort of a test. The Ubuntu computer has only an 80 gig hard drive. The laptop I was cloning also has an 80 gig.
so When I try to go in and clone it gives me the error that there is not enough space on the hard drive... (The laptop is only using ~7 gigs) When I try to clone the only option it gives me is the 80 gig. The same when I try to save only partitions. When selecting what to use, (i.e. ntfsclone, partimage, dd) I select the first (i.e what was in the previous parentheses) one.
So it seems that ntfsclone is the problem. So I booted up the laptop through the drbl server into ubuntu and ran ntfs clone there, and it worked great and created a 7 gig image.
So Am I missing something in a config somewhere, because ntfsclone is not doing its thing when going the clonezilla way.
If anyone could help I would appreciate it.
Kory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although both of them are 80 GB, but maybe it is slightly different.
Could you boot clonezilla live into command prompt, then run:
1. sudo su -
2. /sbin/parted -s /dev/sda print (or /dev/hda)
3. /sbin/parted -s /dev/sdb print (or /dev/hdb)
Then post the results ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ahhh. I see that you are misunderstanding me. (totally my fault)
No.. My problem is that ntfsclone is not working right. Instead of cloning only the ~7 gigs that are used on the partition it is trying to copy the partition like dd would (i.e. copying even empty sectors) So it always tries to create a 80 gig image (with all the empty sectors) instead of just 7 gigs of used space (which ntfsclone claims to do.)
Now I was able to run ntfsclone manually after I started the laptop in thin-client Ubuntu from the ubuntu server (the same on with clonezilla on it) and was able to only make a 7 gig image.
However, for whatever reason, when I run clonezilla (i.e from the dcs script and set it up) even though I chose the order ntfsclone, partimage, dd it still will only try and clone 80 gigs, generating the error that the folder does not have enough space for the image (because the server is also only 80 gigs) I am not worried about the space issue. I am worried that it tries to create 80 gig images instead of 7.
I hope you understand my problem now! Thanks so much for helping....
Kory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I think the problem is why clonezilla can not decide the filesystem in your partition. Could you:
1. Boot clonezilla live into command line prompt
2. sudo su -
3. cat /proc/partitions
4. /opt/drbl/sbin/ocs-get-part-info /dev/sda1 fs (replace /dev/sda1 with yours)
Please post the results of (3) and (4).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I set up an Ubuntu Hardy box, and have configured DRBL and Clonezilla, and I can boot over PXE and such. I have it set up as a private lan. The Ubuntu box has two ethernet cards. One connected to our network(where I work) and the other is connected to an isolated switch.
When I set clonezilla to save the image (with dcs script) and boot, I am getting errors. Basically what it comes down to is that whatever is trying to clone the hard drive is trying to clone the whole hard drive with empty sectors.
This was sort of a test. The Ubuntu computer has only an 80 gig hard drive. The laptop I was cloning also has an 80 gig.
so When I try to go in and clone it gives me the error that there is not enough space on the hard drive... (The laptop is only using ~7 gigs) When I try to clone the only option it gives me is the 80 gig. The same when I try to save only partitions. When selecting what to use, (i.e. ntfsclone, partimage, dd) I select the first (i.e what was in the previous parentheses) one.
So it seems that ntfsclone is the problem. So I booted up the laptop through the drbl server into ubuntu and ran ntfs clone there, and it worked great and created a 7 gig image.
So Am I missing something in a config somewhere, because ntfsclone is not doing its thing when going the clonezilla way.
If anyone could help I would appreciate it.
Kory
Although both of them are 80 GB, but maybe it is slightly different.
Could you boot clonezilla live into command prompt, then run:
1. sudo su -
2. /sbin/parted -s /dev/sda print (or /dev/hda)
3. /sbin/parted -s /dev/sdb print (or /dev/hdb)
Then post the results ?
ahhh. I see that you are misunderstanding me. (totally my fault)
No.. My problem is that ntfsclone is not working right. Instead of cloning only the ~7 gigs that are used on the partition it is trying to copy the partition like dd would (i.e. copying even empty sectors) So it always tries to create a 80 gig image (with all the empty sectors) instead of just 7 gigs of used space (which ntfsclone claims to do.)
Now I was able to run ntfsclone manually after I started the laptop in thin-client Ubuntu from the ubuntu server (the same on with clonezilla on it) and was able to only make a 7 gig image.
However, for whatever reason, when I run clonezilla (i.e from the dcs script and set it up) even though I chose the order ntfsclone, partimage, dd it still will only try and clone 80 gigs, generating the error that the folder does not have enough space for the image (because the server is also only 80 gigs) I am not worried about the space issue. I am worried that it tries to create 80 gig images instead of 7.
I hope you understand my problem now! Thanks so much for helping....
Kory
So I think the problem is why clonezilla can not decide the filesystem in your partition. Could you:
1. Boot clonezilla live into command line prompt
2. sudo su -
3. cat /proc/partitions
4. /opt/drbl/sbin/ocs-get-part-info /dev/sda1 fs (replace /dev/sda1 with yours)
Please post the results of (3) and (4).