Ntfs-problems with scripted installation after upgrading to 3.6
We are having strange problems after 3.6 with our scripted installation and not quite sure if they are K2000 related or not. Hardware is HP Z420 with Intel 180GB SSD and at least 3/4 that we have installed have had NTFS-errors after the deployment. The fact that the problem has been on multiple identical computers would suggest it is not a hardware problem. I have checked both BIOS and SSD firmware and they were up-to-date. There wasnt any problems with similar computer before the upgrade, but this might be a coincidence.
The problem is very frustrating and I feel im running out of ideas where to look. Anyone else have ideas?
1 Comment
[ + ] Show comment
-
Exactly what sort of scripted install are you deploying? Is this an application or operating system install? Are you able to try a system with a SATA hard disk in place of the SSD? It's just a guess but since SSDs have internal logic that moves data around to equalise the wear on the storage cells, anything that deploys to absolute block addresses might be tangling with the SSD internal management. Trying with a normal hard disk will quickly show if this is an SSD issue. - EdT 9 years ago
Answers (1)
Please log in to answer
Posted by:
mikesharp1
9 years ago
Kemu79
Good Afternoon.
I so this alot after upgrading myself what I had to do was recreate my KBE's using the K2000 Media Manager. You are probably better off downloading a new copy from your K2 and creating a new KBE from that. It doesn't take very long and you shouldn't have anyother issues unless your drivers are cache for the KBE under \\yourk2ipaddress\drivers\kbe_windows...
Hope that helps.
