- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- StoreEasy Storage
- >
- Re: Blue screen after applying Blaster patch to NA...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-15-2003 12:36 AM
тАО08-15-2003 12:36 AM
Blue screen after applying Blaster patch to NASB2000
last attempt so far has been to boot into recovery mode of an advanced server CD and manually copy the dll's that the patch overwrites out of the uninstall directory to the winnt\system32 and winnt\system32\dllcache directory.
any more ideas out there?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2003 03:20 PM
тАО08-19-2003 03:20 PM
Re: Blue screen after applying Blaster patch to NASB2000
I have the exact same issue and I tried what you have to no avail. The paych has caused more issues then the worm could have.
I am going to ahve to reinatll windows tomorrow as I have no other solution.
If you find anything let me know and likewise,
Damien.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-19-2003 11:20 PM
тАО08-19-2003 11:20 PM
Re: Blue screen after applying Blaster patch to NASB2000
The patch creates a registry key which if you have a ERD you can repair with this. I am trying a third party product to get into the registry to remove this key and hope for the best.
Damien.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2003 12:00 AM
тАО08-20-2003 12:00 AM
Re: Blue screen after applying Blaster patch to NASB2000
The rebuild went okay, and it even automatically picked up the storage pools and virtual disks okay afterwards, only needing to run the namespace recovery on the web admin tool. The only issue left was to replace shares and permissions on 4TB of storage - looks like i'll be busy for the next month.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-18-2003 03:27 AM
тАО12-18-2003 03:27 AM
Re: Blue screen after applying Blaster patch to NASB2000
The symptoms you are reporting are consistent with having applied the blaster worm fixes (MS03-026 and MS03-039) while leaving the VR service running. These patches (as well as Service Pack 4 and others) rip the RPC service files out from under the running VR process, which can result in meta-data and data corruption. Once VR metadata is corrupted, your box will blue screen when attempting to access the storage.
There were Customer Advisories released about these two patches, documenting how to properly load and install them. These instructions need to be followed in detail, and step-by-step, or you risk having these same issues occur again.