Any time you run a drive mounting command, you're just running diskpart in the background.
Get into WinPE, and open a command prompt and see if you can run diskpart commands manually. Run these commands:
This will show you all disks that the machine recognizes. It's common to have a driver issue, and the hard drive may not show up at all. If this is the case, you'll want to look at this document:
Thanks for the info, but I'm doing the deployment on the same machine over and over again without changing anything.
I dont' think than it can be a driver problem.
1 of 1 people found this helpful
Maybe it's not a driver problem. However, if you run the diskpart commands that are the equivalent of what the script is doing (mounting the C: drive), maybe you'll get an error message.
Even if the error is not meaningful, it would certainly tell you whether or not it's a LANDesk provisioning issue or something else.
True, but the problem remains :-(...
Example first image good, second bad, third good, fourth bad, 5e good, 6e good, 7e good, 8e bad 9e good.
This all on the same machine with the same hardware and the some software.
Doing everytime the same thing :-(.
Is it possible that we have some corruption on the database?
Has there ever been a resolution on this? I'm having the same issue. I've ran the diskpart command and I do see Disk 0 which is online.
Hi Paul and the remaining error-victims,
this is the same here for me.
Manually I've run diskpart.exe and listed the disk and mounted it to C:
The error occurs on WinPE-Imaging als well as on Provisioning.
In Provisioning we've solved it temporarily with SLEEP and REPS.
Whats bothering me ist the fact, the error occurs not every time. Instead
this happens not periodically, so random.
Let's hope on the future,
A few pieces of commentary, which I hope will help a little at least.
* The issue should NOT be related to corruption in the DB. If there were a problem with the data in the DB in this regard, the problem would be consistently happening all the time.
* At the moment, the (well - my, I should say) guess is that there's a timing issue involved, individual to the PC + bootups (i.e. - it's still busy trying to load X or Y), so adding a few delays as Norbert did is a good thing - gives the PC in question time to finish doing what it's supposed to be doing, and then accept this.
There's still a fair bit of fog around this (specifically BECAUSE it only happens "some of the time") and we're not having any luck to reproduce this behaviour either (especially consistently - I've seen it once, and that's it), which makes it frustrating to say the least to try and debug or resolve.
So at the moment it's still in a bit of a phase where we're trying to narrow down things by trying to find recipies that work / don't work and hopefully get an insipration from that as to the combination of things that could be causing it.
Unfortunately, not a very clear cut problem this .
LANDesk EMEA Technical Lead
for my case I added a sleep about 30 seconds,
a mount, again a sleep 30 sec and another mount. Til now
If the first mount fails do you have it selected to continue on?
Do you use the WinPE image that comes with LANDesk 8.7 or 8.8? I don't know what changed exactly, but the 8.7 PE is much, much more reliable (read: no unexplainable errors at all) whereas the 8.8 PE is very unreliable...
I have this Problem consistanly. I also did what Norbert did and unchecked stop if fails and i am able to image.
Anyone ever have any luck with this issue? We are experiencing the same error.