- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Installing new driver with old firmware
Disk Enclosures
1753851
Members
7236
Online
108807
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
09-26-2001 04:00 PM
09-26-2001 04:00 PM
Installing new driver with old firmware
Just an FYI, something that I haven't seen mentioned elsewhere: When updating the SMART driver for NT to v4.24 to allow installation of the MS01-044 security roll-up, I had a problem with some of my older servers. So far, all I know for sure is that a SMART-2DH with v2.08 firmware will blue screen on boot with a BOOT_DEVICE_INACCESSIBLE message after the driver update.
I tried upgrading to 4.48b first, which didn't work, but luckily I had read the thread about firmware downgrades, and so I knew not to reboot! Installing v2.14 worked, and fixed the problem (although I'd kinda like to be able to install the latest one...). Another server took the 4.48b upgrade on the first try, which also worked fine. So v2.14 seems to be the minimum firmware level required, at least on a SMART-2DH.
I tried upgrading to 4.48b first, which didn't work, but luckily I had read the thread about firmware downgrades, and so I knew not to reboot! Installing v2.14 worked, and fixed the problem (although I'd kinda like to be able to install the latest one...). Another server took the 4.48b upgrade on the first try, which also worked fine. So v2.14 seems to be the minimum firmware level required, at least on a SMART-2DH.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP