Return to MDL Home Page

DSD Driver

PROBLEMS AND SOLUTIONS

Symptom:
"Permission Denied" Error

Possible Causes:
/etc/mdl_dsdd doesn't load when the system boots. Check the /etc/bcheckrc file to ensure the command /etc/mdl_dsdd appears after the final "fi" at the end of the eisa config section.

The license string was mistyped in the /etc/mdl_dsd_licenses file. Check the file to ensure the license was entered and entered correctly.

Major numbers assigned to the DSD Driver (block and/or character device numbers) had previously been assigned to other device drivers. Check the /etc/master file to verify unique assignment of these numbers.

The /dev/dsd_info file was created incorrectly. "ls-1" the /dev/dsd_info file to ensure it was created with the correct major number and the minor number chosen reflects a valid partition on the disk you are accessing with the DSD Driver.

Symptom:
The DSD Driver won't load.

Possible Cause:
A major number was assigned to the DSD Driver which had already been assigned to another driver in the file /etc/master.

Symptom:
dsd_format ran for twelve hours and never finished. dmesg logged a "Medium Error."

Possible Cause:
Bad disk drive. dsd_format should take approximately 2.5 hours on a 9 Gig drive.

Symptom:
mediainit failed on a 9 Gig drive.

Possible Cause:
mediainit will always time out on a 9 Gig drive. Must run the dsd_format program on the /dev/rdsk/xxxxxxxx, where xxxxxxxx is the device file (partition 0) of the disk being formatted.

Symptom:
The error message "Invalid Argument" is displayed when make_part is invoked.

Possible Cause:
Major number 47 was assigned to the driver, but 47 is used by the system and is assigned in the file /etc/master.

Symptom:
makepart does not find the disk being partitioned.

Possible Cause:
The minor number assigned to the file /dev/dsd_info was incorrect. It must be the device of a valid DSD partition on that system.

Symptom:
The system reports the DSD partitioned disk as unformatted, even though dsd_format had been run.

Possible Cause:
An incorrect major number was used in the dsd_format command. The major number assigned to the DSD Driver must be used in the format command.

Symptom:
tar command hangs when run against a DSD partitioned drive.

Possible Cause:
Wrong version of the DSD Driver. User had HP-UX version 9.05, but was using version 1P of the DSD Driver which is compatible with 9.03. The DSD Driver 1R is compatible with 9.05.

Symptom:
Errors are displayed during HP-UX 9.05 kernel rebuild.

Possible Causes:
Used version 1P of the DSD Driver rather than 1R.
 
There were spelling errors in dfile.

Symptom:
The DSD partitioned disk is not fsck'd during bootup.

Possible Cause:
The /etc/checklist entries for those partitions directed the system to skip the fsck during bootup.

Symptom:
DSD partitions won't mount.

Possible Causes:
/dev/dsd_info file was made with wrong major and minor numbers
 
Disk partitions were created manually, as opposed to using make_part. and the numeral 1 was placed before the LUN designator rather than the letter l.

Symptom:
DSD Driver doesn't recognize a second 9 Gig drive on the same system.

Possible Causes:
Wrong version of the DSD Driver. User had HP-UX version 9.05, but was using version 1I of the DSD Driver. The DSD Driver compatible with 9.05 is version 1R.

The proper SCSI patches for HP-UX version 9.05 needed installation.

Symptom:
System hangs and generates a C700 error when a second 9 Gig drive is present.

Possible Causes:
One or both 9 Gig drives is terminated.

Installation of OS Patches is required.

Symptom:
A RAID consisting of fourteen 9 Gig drives can't be partitioned into more than 64 Gigs.

Possible Cause:
The customer needs to manually configure the array, allocating as many as 8 LUNs per RAID. However, this can only be done by connecting a terminal to the serial port of the RAID and using the "manual configuration" option.

Symptom:
CRD RAID Controller hangs when manipulating files of 120 MB or larger.

Possible Cause:
Wrong version of the DSD Driver for HP-UX 9.05. The correct driver version is 1R.

Symptom:
Permission Denied error when DSD Driver was used to partition a RAID attached to a FAWs card.

Possible Cause:
The problem was due to the ordering of the FAWs and DSD daemon commands in /etc/bcheckrc. The command /etc/mdl_fawsd must appear before the command /etc/mds_dsdd, otherwise the system won't see the disk referenced by /dev/dsd_info.

Symptom:
Could not do a mkfs on a RAID attached to a FAWs card and being partitioned with the DSD Driver. mkfs would fail on LUN 1, hanging the process. make_part reported the size of LUN 1 as -1, though correctly reported the size of LUN 0.

Possible Causes:
No HP-UX SCSI OS patches had been installed.

Using older version of FAWs driver.

New FAWs firmware required.

Symptom:
A RAID shared by two systems only mounts on the first system to boot. This symptom appeared when the RAID was upgraded to Fast Wide Differential.

Possible Causes:
The upgrade to Fast Wide Differential was not a factor in this problem: however, the OS had been upgraded to HP-UX 9.05 from 9.03 without upgrading to the DSD Driver to 1R.
 
The SCSI patches to HP-UX 9.05 had to be installed.

Return to MDL Technical Support Page

Return to MDL Home Page

For more information, contact MDL Corporation. Website information.
Copyright ©1999 by MDL Corporation. All rights reserved.