Problem using Clone Zilla

[george_toolan]

It shows in red color a warning that disk failure is imminent, but nothing of that sort has happened so far, it works well.

You should check the smart values of the Samsung drive and maybe run a (long) self test.

smartctl -a /dev/sda

You might run into read errors later when you try to copy the drive ;-)

[tech291083]

Originally Posted by stevea

156301488 - 156299375 = 2113 sectors.
2113 sectors * 512 bytes/ector = 1081856bytes = 1056.5 KiB = 1.031738281 MiB.

Great. I did the same. Thanks.

gparted doesn't handle LVMs wrt resizing

Yes, right.

Use the system-config-lvm command (package is the same name IIRC).

This is for the logical volume manager. I have never used this but since its GUI, it should not be too difficult for someone like me. Let me try it out. Thanks.

---------- Post added at 04:39 AM ---------- Previous post was at 04:37 AM ----------

Originally Posted by george_toolan

You should check the smart values of the Samsung drive and maybe run

You might run into read errors later when you try to copy the drive ;-)

I have done all of this tests as recommended by forum members here only. But I was also told that the errors might not be there and the results might be a false alarm. I do not doubt your abilities I must say. Thanks.


Another thread of mine dealing with this drive failure imminent issue.

http://forums.fedoraforum.org/showthread.php?t=283188

---------- Post added at 04:47 AM ---------- Previous post was at 04:39 AM ----------

Ok,

I have done some searching on the net today and found this. It looks interesting enough for me to do manually via a terminal. Wish me luck though. This is a thread on this forum only.


http://forums.fedoraforum.org/showthread.php?t=250423

LVM physical volumes contain logical volumes, and logical volumes contain filesystems. So to shrink a partition with an LVM physical volume, you first have to shrink a filesystem, then shrink its logical volume, then shrink the physical volume, then shrink the partition, and then you will have unallocated space that you can use to make a new partition.

You can try the LVM utility found in the panel menu somewhere or start it in a terminal with system-config-lvm. It's a GUI applet for managing logical volumes. I've never used it, but you supposedly can use it to resize things. Matter of fact, I don't use LVM in my own systems, but I've played around with it enough to know how to shrink a PV. If you get nowhere with system-config-lvm, then you can do all of the steps manually in a terminal.

When shrinking the manual procedure will go something like this (off the top of my head):

umount and shrink the file system
shrink the LV
shrink the VG
shrink the PV
shrink the DOS partition (assuming you made your PV on a standard partition)

---------- Post added at 04:59 AM ---------- Previous post was at 04:47 AM ----------

Looking at the screenshot of an app called Disk Utility as submitted by me in post no 11 of this thread, I conclude the following.

There are basically 3 partitions in my system.

sda1 = BIOS boot partition = 1.0 MB

sda2 = EFI system partition/boot partition = 524 MB

sda3 = Physical volume = 79 GB = contains /home/, /root and swap partitions as logical volume in a volume group called VolGroup.

In order to reduce the overall size of these 3 partitions that I intend to clone, I have to shrink one of these 3 partitions and I have to shrink the last one ie the Physical volume 79 GB, containing logical volumes /root, /home and swap. Root is the biggest with 45.94 GB, so I want to shrink this one only to 40 GB. So an extra space/free space of 5.94 GB will be created within physical volume. Even this free space will be cloned to the destination drive if I choose the disk-disk method as told by Chilly Willy. I am not very sure about this though. But if this is the case, then I will have to choose partition-partition method of cloning and I will not clone the free space if that is possible, but this is just a guesss.

To do so, I will follow the steps given at the url below.

http://forums.fedoraforum.org/showthread.php?t=250423

umount and shrink the file system
shrink the LV
shrink the VG
shrink the PV
shrink the DOS partition (assuming you made your PV on a standard partition)

But i do not understand the last step ie the one which says shrink the DOS partition. In my case it will be sda3. Please guide me. Thanks.

[tech291083]

I have tried to use the GUI - system-config-lvm and here is the efforts I have made so far. Please see the attached screenshots and guide me. I need to shrink a root lvm. Thanks.

[Chilly Willy]

I was beginning to wonder if that drive you are using for a target was really any good, (had any issues) and from post #11 it appears that it may not be, at least for THIS.

Yes you are correct, whatever is on the one will be duplicated to the other. (in disk to disk) So your target HAS to be the same size or bigger. (physical size of the source disk) Now if the target is bigger, that extra space CAN be recaptured.

Given that according to post #11 that you are getting error, those bad blocks (usually associated with disk failure) will be locked out of usage, actually making your HD smaller. I suspect THAT is why it IS smaller.

My suggestion would be to get another HD for THIS & use THAT ["bad"] one for general playing, IOW to put stuff on that when it DOES go, you won't lose anything important. - btw: I've seen such drives run for a LONG time - IF the bad block count remains steady, there shouldn't be anything to worry about at all. But if it starts CLIMBING, then it's definitely time to consider replacing it. (FYI - I'm assuming this is NOT a solid state disk)

As stated by others, there ARE ways to make the one you have work, but from what you have been posting, I really don't think you want to "jump through hoops" to get what you want, thus the suggestion.

[tech291083]

I have this GParted install on my system and here is a screenshot of the same. Unfortunately I can't use this to shrink the root lvm within my volume group on sda3 partition. I need to somehow shrink it to get where I want to. I need some step by step instruction. I am waiting for a good reply from someone senior. Thanks.

[tech291083]

Originally Posted by Chilly Willy

I was beginning to wonder if that drive you are using for a target was really any good, (had any issues) and from post #11 it appears that it may not be, at least for THIS.

in post #11, the screenshot I have attached is that of my source disk (not target disk) as seen in an app called Disk Utility. It shows in red color a warning that disk failure is imminent, but nothing of that sort has happened so far, it works well.

My target disk works well and has no problems whatsoever.

Given that according to post #11 that you are getting error, those bad blocks (usually associated with disk failure) will be locked out of usage, actually making your HD smaller. I suspect THAT is why it IS smaller.

Good if the bad blocks are separated from usage. But again this is my source drive and not the target drive.

I have bought a new 500 GB drive already but I can't use it as it is for another important pc of mine. but as I have mentioned earlier despite the bad sector and the warning in red color, the drive seems to be working well since August this year, when I first discovered the error. I have a friend who has same error, but his drive has been working well for the last 12 months or so. I am no expert, but just trying to tell you what I have seen in real life.

Thanks.

[Chilly Willy]

OK - my bad... sorry, getting a bit confused... But the info is still good.

This is getting to the "HAIRY" point & I'm afraid I'm just not of much help now, probably just making it worse. So I may have to bail on you. Hope someone else can take it from here. I'll try to help if need be, but I don't see ME as a good guide at THIS point. & the last thing I want is to mess you up &/or make things worse.

[tech291083]

Originally Posted by Chilly Willy

OK - my bad... sorry, getting a bit confused...

No need to say sorry, its ok. Even I am a bit confused and frustrated as I am still waiting for someone to guide me through. This is really silly that despite both the drives being of equal size ie 80 GB, just a silly difference of 1.03 MB is causing such a mess.

This is getting to the "HAIRY" point & I'm afraid I'm just not of much help now, probably just making it worse. So I may have to bail on you. Hope someone else can take it from here. I'll try to help if need be, but I don't see ME as a good guide at THIS point. & the last thing I want is to mess you up &/or make things worse.

All of you inlcluding Chilly Willy have tried to help me and I really appreciate that. Then how do people clone drives of equal size from two difference makes as in my case the source is Samsung and destination is Seagate. I do not want to run a campaign against these 2 makes but just letting you know the bare facts as they are. Thanks.