Yes, we used the Load Driver tool to install the RAID drivers and then didn't inject drivers into the restore. One little tick box screwed up the restore, with each restore attempt taking 1-2 hours, so it took us 8 hours to have the server back up and running as we didn't know it was the driver injection that was causing thisDima P. wrote:Indeed pcw.sys BCOD is usually caused by driver conflicts, so you should not inject drivers from recovery media or you might want to add any customer drivers to the recovery media and install them prior running recovery via Load Driver tool. Anyway, glad you nailed it!
The server was only built a week ago but Microsoft patches have come out since then, which may have changed multiple drivers. Is there a way to automate the creation of the recovery media? I'm thinking some sort of command line call from Task Scheduler? The recovery media is kept on all the USB Backup drives and on an internal drive, usually the R Drive (R for Recovery, hehe), and it would be nice to create an ISO recovery media every so often so we don't get caught with our pants down again.Mike Resseler wrote:A good practice is always to quickly make a new recovery media.
it's not "just" an issue with having changed drivers between creation etc.. as nothing was changed in our tests.
Users browsing this forum: Yahoo [Bot] and 6 guests