Capture Error
-
Are there any “Failed!” messages before the PartClone screen shows?
-
@Wayne-Workman https://onedrive.live.com/redir?resid=BD4D5D336B75EB86!12042&authkey=!AIebEm7G2UuGnWI&v=3&ithint=photo%2Cjpg
That message pops up briefly before receiving the following:
Thanks
-
@arduinoAndMore Thank you for the screen shots! Definitely helps, but I was asking about the things displayed before partclone even starts. Any errors there?
-
@Wayne-Workman Everything looks perfectly happy until that first screenshot in my last response. Hope that helps
-
@arduinoAndMore I’ve found some information on that error, they all refer to inconsistencies on the drive, unmounting issues, inaccurate detection of how big the drive is, or other issues related to malware/viruses.
https://sourceforge.net/p/clonezilla/discussion/Help/thread/de8ea4fe/
https://sourceforge.net/p/clonezilla/bugs/167/
http://serverfault.com/questions/438243/cloning-bitmap-free-count-err-on-proxmox-drive
http://ubuntuforums.org/showthread.php?t=2082868
http://www.saetechnologies.com/clonezilla-bitmap-error-at-group/My advise to you is to re-upload the image and try again.
Also, is this a Windows image or an OSX/Linux image? If it’s windows, do a checkdisk. OSX also has some filesystem fixing things too, just can’t remember their names.
Ah, just read this is Lubuntu.
-
@Wayne-Workman This is my golden machine, so it would take some effort to redo the image. I suppose that might be best at this point. It’s better than hacking this one into working and then spreading problems further by imaging. Thanks for the help. I’ll plan to redo the image.
-
@arduinoAndMore Well, the image doesn’t need rebuilt. I’m just suggesting doing some disk integrity checking and then re-uploading.
-
@Wayne-Workman Here’s what I did: I booted to Puppy (live) and tried to check the drive. It didn’t take more than 10 seconds and it returned nothing. I’m not sure it actually did anything useful. (Might have, just no confirmation)
I also discovered that the directory I had created to save the image to on my server (inside /images) was owned by someone besides root. I chowned it to root and tried again. The image seems to be going up just fine now. I hope this is useful to someone down the line.
sudo chown root:root /images/<imagename> -
@arduinoAndMore said in Capture Error:
I also discovered that the directory I had created to save the image to on my server (inside /images) was owned by someone besides root. I chowned it to root and tried again. The image seems to be going up just fine now. I hope this is useful to someone down the line.
It’s in our wiki already, but spamming it all over the forums is a good thing. People seem to not know how to Google search very well.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Permissions
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_NFS#PermissionsLet us know if anything changes when you try to deploy.
-
Wow! From what we see in the picture this is happening on upload/capture (source /dev/sda1)!
@arduinoAndMore Did you ever try to shrink the partitions on that disk? Possibly something went wrong there. Partition being smaller than the filesystem on it?!?
-
UPDATE: I wound up having the same issue again trying to capture an updated image under the same conditions. I set the folder permissions again and tried to capture before running a check from a live USB stick. This also failed, which means that permissions were not the problem (important, but not the cause of this issue)
I booted to Slacko Puppy Linux and ran gparted and did right-click /dev/sda1 and clicked check. It takes a few seconds and then everything works. Hope that helps.
Bottom line: Do a check on the drive from a live USB
-
@arduinoAndMore Well, something screwed up your first partition I’d say. Good to hear that you got this solved by a simple filesystem check!
