ntfsresize & ssd Intel PRO 5400 series

[raumin]

Server

• FOG Version: latest RC (15/11/2016)
• OS: debian 8 64bits

Description

Hello,
We received new computers (dell optiplex 3240 AIO) with an SSD Intel Pro 5400 series 256GB.

i can not image the OS on it, i get error with ntfsresize:

I disabled fast reboot on Windows 10 (build 1607) and…that’s all, i dont know where to look at.

Do you have any idea ?
Thank you

[Wayne Workman]

your problem is that you cannot “capture” the image. Please do a debug capture. This is a checkbox that you tick on the capture confirmation page. When you network boot the system for capture, it’ll land at a linux shell eventually, you’ll need to press enter a few times to get to the shell to pass the informational windows.

Here, run these commands and give us the output:
lsblk
fdisk -l

From this we should be able to figure out what’s going on.

[Sebastian Roth]

Possibly this change is causing the error? https://github.com/FOGProject/fogproject/commit/e748a9da95b91103890bf5d2c126091839875c8a

[Quazz]

Looks like the same thing happening over at

https://forums.fogproject.org/topic/8961/problem-on-hp-probook-650g2/11

@Sebastian-Roth said in ntfsresize & ssd Intel PRO 5400 series:

Possibly this change is causing the error? https://github.com/FOGProject/fogproject/commit/e748a9da95b91103890bf5d2c126091839875c8a

It seems to fail before it even does a resize test or otherwise there’s no output of it, which is most strange.

[Wayne Workman]

If the code was changed back to what it was before, would the resize fail and destroy the image? That change was intended to test the disk more throughly - and prevent destroying images.

[Tom Elliott]

Just a heads up. I tested upload with working-RC-24 and 1.3.0-RC-13 and am not seeing an issue.

I can only think, possibly, the disk is setup in ‘raid’ through the bios and it’s presenter still display’s /dev/sda to the system. Another potential, I suppose, could be the disk is completely empty? I’m only guessing of course.

The change I put in for maintaining ntfsresize is still working properly from what I can see. So it’s failing, from what I can tell, appropriately. Again, I’ll need more info to more suitably help I think. I mean, this could potentially happen because it’s fragmented and can’t move data around (testing) to find the size that can shrink to.