Post-Merger Integration Blog

De-risk PMI technology projects and increase certainty for your M&A deal.

Tech Brief - Upgrading a Windows Server 2003 and RAID disk drivers (Part 3)

Posted by Dave Refault on 16-Jul-2015 19:00:00


INTRODUCTION:

In the first two articles in this series we covered some general considerations when upgrading Windows Server 2003 in-place to Windows 2008 and some specific requirements when upgrading to a VM hosted on Hyper-V.

Upgrading an Operating System is no small task, just think about all the processes that have to occur in order for the setup software to successfully update to a newer version.   This is why we shouldn’t be too hard on the pre-installation setup checks as its impossible to get it 100% correct.

CustomerUptheLadder


So what is this LSICSB6.SYS that caused us such a big headache?  LSICSB6.SYS is a RAID driver, however it is a driver that is wholly incompatible with Windows 2008.   Like before – this is not something you will be warned about and setup will happily continue until it completes its final installation phase where the machine will simply refuse to boot.   There are no errors or warnings – just a black screen.

Most sensible Sys Admins will then resort to hammering F8 and attempting a Safe Mode boot only to discover something similar to the following:-

Loaded:\windows\System32\Drivers\Fs_Rec.sys
Loaded:\windows\System32\drivers\ndis.sys
Loaded:\windows\System32\drivers\mfehidk.sys
Loaded:\windows\System32\Drivers\ksecdd.sys
Loaded:\windows\System32\drivers\tcpip.sys
Loaded:\windows\System32\drivers\fwpkclnt.sys
Loaded:\windows\System32\drivers\storflt.sys
Loaded:\windows\System32\drivers\Ntfs.sys
Loaded:\windows\System32\drivers\volsnap.sys
Loaded:\windows\System32\Drivers\spldr.sys
Loaded:\windows\System32\Drivers\mup.sys
Loaded:\windows\System32\Drivers\hpqilo2.sys
Loaded:\windows\System32\Drivers\disk.sys
Loaded:\windows\System32\Drivers\CLASSPNP.sys
Loaded:\windows\System32\Drivers\crcdisk.sys
please wait………

And that’s as far as you will get.   You might then spend hours researching CRCDISK.sys only to finally realise it’s not the problem driver…   No it is LSICSB6.SYS which is causing it.  Its worth mentioning that this issue primarily affects HP servers.

Starting in recovery mode

So what do you need to do?  Start from scratch?  Fortunately not.   Simply boot the server from the Windows 2008 installation media (or attached ISO) and choose ‘Recovery mode’:-

systemrecvoery


Removing LSICSB6.SYS

Choose ‘Command Prompt’ and then remove lsicsb6.sys from the server by either removing the lsicsb6.sys file from the \windows\system32\drivers directory or removing any INF files that reference the lsicsb6 driver.

Reboot the server and you’ll find that the final phase of the setup process completes without error.

That’s it for this series.  Check back soon for more tips and tricks when upgrading from Windows 2003 to Windows 2008 in-place.

why to migrate to windows server 2003


 

Topics: #WS2003EOL, #WindowsServer, #WS2003, Windows Server 2003 End of Life