1 Suggested Answer

Hi,
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!

Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.

You can download and install the drviers that are available from the website of your computer manufacturer. Please check the computer manufacturer and browse in their websites and download the required drivers that suits for your computer Model.

Windows 7 is bundled with all the required drivers for any computer. Every Hardware device will get the required drivers installed while installing the Windows 7 Operating System. These Drivers drivers are assigned by the Microsoft. However, Unassigned drivers can be downloaded depending on the computer Model.

If you have internet connection in the computer that has the issue, then you can run the Windows update to keep your computer upto date.

You have not provided much to go on here. Is the system up and running or do you have only a single drive? You should be able to do a "SHO ERR" and see any errors logged to the errlog that will indicate the hardware issue. Using "anal/err" or Clue, you should get the error details. Please post what you find here and I'll provide suggestions.

the Only VMS post on fixya ever.
wow. from the dark ages of DEC. VMS. OS.
sounds like bad drive if it can not be mounted.(or disk bad)
sounds like you are 42 years behind the upgrade curve too...
i used to work on all DEC systems. so know that . 1975
the DS10, is now 18 years old.

Version 7.1-2 is an older version of the OS. I will have to check, but I think that V7.2 will resolve this. What version of TCP/IP are you using? Back in the day when I supported TCP and VMS, there were some timing issues that causes odd behavior. If you can provide the details about your configuration, I can check and get back to you. If necessary, an examination of a forced crashdump may be needed.

As has been remarked before, "SCSI is a collection of optionally implemented -- or optionally misimplemented -- features", and the other classic remark, "None of the S's in SCSI are Standard".

There is typically no requirement for what some platforms might call a low-level format for SCSI disk devices accessed by OpenVMS.

The volume-level format -- the file structure -- is established with the OpenVMS INITIALIZE command.

There is apparently a configuration-level or hardware-level SCSI incompatibility here. That the console can identify the device means that some simple operations have succeeded -- that the console has identified the device does not imply that the device will operate, nor that the device will operate under any particular I/O load.

Please contact your hardware support vendor or storage vendor for assistance with the requisite integration and testing, and please also see the OpenVMS FAQ for related discussions of third-party hardware issues, requirements, testing, and support considerations.

The effort involved in qualification of peripheral devices is large, and involves detecting, isolating and resolving obvious functional incompatibilities and obvious errors within the host, controller or drive interfaces, as well as more subtle considerations such as ensuring that the particular device thermal-cooling and other environmental requirements are met. Acquisition of a supported device is often far cheaper than performing a local qualification, and particularly when -- such as is the case here -- errors are encountered. Additionally, if operational problems should arise, then the supported configurations will typically see the necessary remediation work.

The device support effort involved can range from trivially simple to what is effectively cost-prohibitive, and the particular results and which extreme might be involved are not entirely clear at the onset of the testing and support effort. Put another way, there is definite value in the supported device configurations.

Additionall, your OpenVMS version is outdated, and in need of an upgrade. While the OpenVMS Wizard is entirely unfamiliar with the rated capacity of this Seagate device, the Wizard will also call your attention to the maximum disk capacity and storage-ECO-related information in the OpenVMS FAQ. If you cannot upgrade from V7.1-2, please make certain that you have all current ECO kits applied.

The OpenVMS Wizard is not in a position to provide device qualification and device integration assistance at no cost -- having been involved in this, this effort can involve weeks or months of technical effort; far beyond what the OpenVMS Wizard can offer. Again, please contact your hardware support or storage vendor for this assistance, or please then expect to become of a subject matter expert for SCSI.