Resizing issue maybe?
-
Oh, I think the most up to date is in GIT. I never set that up yet. I can do that and see what happens. Off to the fog wiki!
-
@adame GIT and SVN are EQUAL. Always. When the @Developers push changes, they push them to GitHub and SourceForge simultaneously.
With GIT, go to your fogproject directory and
git pull -
YOu’re dealing with a moron. I ran the SVN earlier today but didn’t bother doing the ./installfog.sh . Wow. Well since you confirmed that resizing is working with this build I’ll give it a shot once it’s done installing. Sorry guys.
-
@adame You’re not a moron, you’re just new to this technology. You’ll be onboarded in no time.
-
@adame lol, we’re all morons sometimes.
-
@Wayne-Workman Haha. I’m a linux noob so I’m relying heavily on the fog wiki.
I have it up-to-date now and rerunning the capture. Then I’ll deploy to the new SSD. If it still doesn’t work not sure what I may be doing wrong or if it’s just a toughbook issue. I’ll get back to you either way. -
If it doesn’t work…
@Wayne-Workman said in Resizing issue maybe?:
Also - your second picture in your OP, we need to see the error on the PartClone screen to help further! All we see now is the error after PartClone closes!
-
@Wayne-Workman Ok sounds good. I’ll try to catch it. It happens pretty quick. Haha.
-
if it fails, run the task again as a debug task. that will make it easier to see where exactly it fails
-
Caught it. Seems like the first process went through but when it started with the second I get this.
https://gyazo.com/b59cbfae543cc106d8ef2ec1da0d0e5cMaybe resizing just isn’t going to work with this unless I have some 512GB SSDs? think there are technically 3 partitions. Maybe that’s what the mess is. I don’t think it cared about the 100meg partition that windows creates but I think these toughbooks have an image of Windows storage in another one too so if I wanted to format I don’t need a disc/usb.
I just feel like I didn’t have this problem before when I did the same process.
-
@adame Do not give up… you only JUST gave us an error we can work with! And of course we can get this working! We are here to help, and the fog community is responsive!
I’m asking @Sebastian-Roth for his opinion, he is our resident HDD expert.
-
@Wayne-Workman Oh, I don’t plan to. I’ll still be looking at things on my end to see if anything pops out at me. I’m just hoping it’s not because of that one partition that has the windows image itself on it. Haha.
-
How much data was on the 500GB HDD?
-
@Quazz Actually I was wrong with one of the partitions. It’s a 24gb partition but has nothing in it. Only dedicated to recovery I guess. Here’s what that drive has in total.
24GB partition 100% free space
300MB partition 100% free space
441GB partition 95% free spaceSo all in all it’s only really has like 20GB total being used.
-
Maybe it will work if I just remove the 24gb partition? I’ll wait on what you all have to say :).
-
i would take a backup of the drive with clonezilla and play around with removing/resizing the wasted space partitions with gparted
-
@Junkhacker Alright. I can do that. I’ll give you all an update once I’ve done that.
-
@adame You might be able to get this fixed by shuffling around with your partitions but we also might be able to get this fixed from our side as well - not promising anything but we might be able.
Please run a debug upload job from the old HDD (schedule a normal upload but just before you click “CREATE UPLOAD TASK” there is a checkbox for debug). The client boots up and drops you to a shell. Run
sfdisk -d /dev/sda. Please take a picture an upload it here.[edit] Just a blind shot: Edit /images/<image-name>/d1.fixed_size_partitions file. I guess it reads
1:right now. Make it1:2and try deploying again to the SSD.[/edit] -
@Sebastian-Roth Ok I’ll give that a shot.
-
Sorry. Had to put out some fires, haha. So far I got this part done. I’ll do the other thing after I put out another fire.