- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Autoloader 448 and Windows Server 2003
StoreEver Tape Storage
1752766
Members
5243
Online
108789
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
04-08-2006 02:56 AM
04-08-2006 02:56 AM
Autoloader 448 and Windows Server 2003
I am having some trouble getting my server to see the Autoloader 448 backup device. If I run the Adaptec diagnostic program during boot, the Adaptec card sees the HP Autoloader 448 device correctly. But, when Windows boots, it does not see the device. I cannot see the device in device settins, in HP LT&T, or in Veritas. I think I have installed the correct driver, but it still does not work. Can anybody offer me some help in regards to where I can look for this problem?
I am running a DL140 with Windows Server 2003 32-bit version. I have an Adaptec SCSI RAID 2120S card.
Thanks for any help you can offer me.
Jeff
I am running a DL140 with Windows Server 2003 32-bit version. I have an Adaptec SCSI RAID 2120S card.
Thanks for any help you can offer me.
Jeff
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2006 03:35 AM
04-10-2006 03:35 AM
Re: Autoloader 448 and Windows Server 2003
There is no "448" autoloader but there is a 418 , a 4048, and several autoloaders with 448 drives. They are quite a bit different so exactly which autoloader you have is important.
I would guess that you have an autoloader with a 448 drive.
The autoloader is very likely using LUN mode. I don't have the specs on that card but most RAID cards I have worked with do not support LUN mode. In that case you should see the drive but not the library.
Your comment sounds like maybe you don't see the drive or the library. Drivers don't effect whether a device is seen in device manager, only where. If you don't see the device at all you have a connection problem of some kind. HBA, HBA bios, HBA driver, cable, terminator, SCSI ID conflict, etc.
Seeing something during the boot but not after Windows is running sound like a windows HBA driver problem or possibly a SCSI ID conflict. Sometimes one SCSI device will respond faster than another and show during an initial scan but later neither device will show.
I would guess that you have an autoloader with a 448 drive.
The autoloader is very likely using LUN mode. I don't have the specs on that card but most RAID cards I have worked with do not support LUN mode. In that case you should see the drive but not the library.
Your comment sounds like maybe you don't see the drive or the library. Drivers don't effect whether a device is seen in device manager, only where. If you don't see the device at all you have a connection problem of some kind. HBA, HBA bios, HBA driver, cable, terminator, SCSI ID conflict, etc.
Seeing something during the boot but not after Windows is running sound like a windows HBA driver problem or possibly a SCSI ID conflict. Sometimes one SCSI device will respond faster than another and show during an initial scan but later neither device will show.
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