SunVTS 2.0 Test Reference Manual
  Search only this book
Download this book in PDF

disktest

7

The disktest verifies the functionality of hard disk drives and floppy drives using two subtests. Most disk drives, such as SCSI disks, native or SCSI floppy disks, IPI, and so on, are supported. The type of drive being tested is displayed on the top of the option menu. The media subtest verifies disk media by writing data to and reading data from the disk. The media subtest treats a disk as one large chunk of contiguous data. The File System subtest verifies the disk system's integrity.
Initially, disktest probes the disks under /dev/rdsk. It checks all of the partitions of each disk. If any partition has a file system not yet mounted, disktest pre-mounts these partitions for the File System subtest. The pre-mount point bears the name of the disk partition appended with a system-wide unique number. For example, if the disk name is /dev/dsk/c0t3d0, disktest mounts it as superuser under the name /c0t3d0.XXXXXX. Where XXXXXX is a six-digit system-wide number. The option menu shows all partitions available for testing. The File System subtest can only be run if the selected partition is mounted. The Write option of the Media subtest is allowed only if selected partition is not mounted.
The disktest tests the floppy drive regardless of whether or not the Volume Management software is running.
  • If the Volume Management software is running, disktest tests the disk drive with the mount point name in the /etc/mnttab file.

CAUTION Caution - If a power failure occurs while the Media subtest is being run in write mode, disk data will be destroyed.

  • If the Volume Management software is not running, disktest tests the disk drive with the device name dev=/dev/diskette. Do not edit the /etc/vold.conf file to change the floppy drives. Currently, the sunvts software is hard-coded to use these path names as the default logic name.
The disktest performs a random seek check followed by a read test or a read after write test. The Media subtest is a scalable test; so you can run multiple copies of it in read/write mode on the same disk partition. To avoid data corruption, all simultaneous instances of disktest communicate through a shared memory service. This ensures that different copies of the Media subtest do not overlay the same disk block at the same time.
The File System subtest exercises the partition being tested determine if it is mounted. If the partition is not already mounted or pre-mounted, then the test is blocked.

disktest Test Options

Graphic

Figure 7-1 disktest

The disktest has different option menus for different test modes.
Partition: The partitions for the Media subtest are displayed. If a partition is mounted, it's mount point is appended after the partition number, such as 1(/usr). Where 1 is the partition number, and /usr is the mount point.
Test Media: Enable or Disable of Media subtest.
Mode: Read only or Rad after write with/without backup.
Media Coverage(%): Percentages of partition will be tested.
Media Transfer Size: Transfer size of Media subtest.
Test File System: Enable or Disable of File System subtest File System File Size: Size of files created for testing.
File System Transfer Size: Transfer size of File System subtest File System Test Pattern: Test pattern of File System subtest.
Connectivity Mode Option Menu for hard disk partition: 0 - 7 [default]
Test Media: [Enable~](fixed to Enable)
Test Mode: [ReadOnly~](fixed to Readonly)
Media Coverage(%): [1](default - can be changed)
Media Transfer Size: [2KB]
Test File System: [Disable~]..(fixed to Disable)
Online Mode On-line Mode for hard disk partition: 0 - 7 [default]
Test Media: [Enable]<- [Disable]
Test Mode: [Readonly~]....(fixed to Readonly)
Media Coverage(%): [10]
Media Transfer Size: [2KB]         [10KB] [20KB] <- [40KB] [60KB]
Test File System: [Disable~]       (fixed to Disable)

Offline Mode for hard disk (under SCSI-devices group): partition: 0 - 7 [default]
Test Media: [Enable]<- [Disable]
Mode: [ReadOnly]<- [BackupWriteRead] [NoBackupWriteRead]
Media Coverage(%): [30]
Media Transfer Size: [2KB]         [10KB] [20KB] <- [40KB] [60KB]
Test File System: [Enable]   [Disable] <-
File System File Size:[512KB]<-    [2MB]    [8MB] [20MB]      [100MB] [200MB]
File System Transfer Size:[512B]<- [1024B] [10KB] [40KB]      [100KB]

File System Test Pattern:[sequential] [0x00000000] [0xffffffff] [0x5aa55aa5] [0xdb6db6db] [random]
Offline Mode for floppy disk (under Other-Devices group): partition: 0 - 7 [default]
Test Media: [Enable]<- [Disable]
Mode: [ReadOnly]<- [BackupWriteRead] [NoBackupWriteRead]
Media Coverage(%): [30]
Media Transfer Size: [2KB]<- [10KB] [20KB]
Test File System: [Enable]  [Disable] <-
File System File Size:[512KB]<-    [2MB]    [8MB] [20MB]      [100MB] [200MB]
File System Transfer Size:[512B]<-  [1024B] [10KB]

File System Test Pattern:[sequential] [0x00000000] [0xffffffff] [0x5aa55aa5] [0xdb6db6db] [random]

Note - Only the offline mode test is allowed on floppy disktest.

disktest Test Modes

The disktest supports all three modes. It performs different test schemes on the network device, according to the mode you select.
Connectivity Mode This mode is only available for the hard disk test. There is no Connectivity Mode for floppy driver test. Only one instance of disktest is allowed for each disk device. A disktest monitors UNIX error messages. The disktest displays messages and reports errors. The test also opens the hard disk, checks the disk configuration, reads a few blocks, and then closes the hard disk. No File System subtest will be run. No Write option is available in Connectivity Mode.
Online Mode The Online Mode is only available for the hard disk test. There is no Online Mode for the floppy driver test. Only one instance of disktest is allowed for each disk device. A disktest monitors UNIX error messages. disktest displays messages and reports errors.
In this mode, disktest also opens the hard disk, checks the disk configuration, and executes the Media subtest. Next, disktest performs some random seek checks. Only Read Only mode is allowed. The default coverage is 10%. No File System subtest will be run. When the test finishes, disktest closes the disk device being tested. No Write option is available in Online Mode.
Offline Mode More than one instance of disktest is allowed for one disk device. Both File system subtest and Media subtest can be run in Offline mode. The disktest does not monitor UNIX error messages in this mode. Floppy test can be run in Off-line mode.

disktest Command Line Syntax

/opt/SUNWvts/bin/disktest standard_arguments -o p=n,-i=n,
-w=n,dev=<device_name>,partition=<0-7>,rawsub=E/D,rawrw=,
rawcover=,rawiosize=,fssub=,fssize=,fsiosize=,fspattern=,

ArgumentExplanation
p=numberSets the number of passes for the test to run; default is 1.
i=numberSets the number of total instances for the test; default is 1.
w=numberDetermines which instance this test is assigned; default is 0.
dev=<device_name>Specifies the name of the disk to be tested, such as c0t3d0.
partition=<0-7>Specifies the partition number to test as partition=6(/export/s6) if mounted on partition 6.
rawsub=Enable/DisableEnables or disables the media subtest.
rawrw=

Readonly

BackupWriteRead NoBackupWriteRead

Specifies the Media subtest read/write mode: Read Only

Write, read then backup

Write, read without backup

rawcover=Specifies media coverage from 0-100% of the partition, such as 70526f..
rawiosize=<2KB,10KB
20KB,40KB,60KB>
Specified the media size to transfer.
fssub=Enable/DisableEnables or disables the file system subtest.
fspattern=<data
pattern>
Specifies the file system data pattern as sequential or
random. {seq(uential)/0x0(0000000)/0xf(fffffff)/0xa
(5a5a5a5)/0x5(a5a5a5a)/ran(dom)/0xd(b6db6db)}.
fssize=<file system
size>
Indicates the file system subtest size in kilobytes or
megabytes:
K/k/KB/kb:kilobytes, M/m/MB/mb: megabytes
fsiosize=<file system I/O transfer size>Indicates the size of the file system subtest I/O transfer in bytes or kilobytes:

{512B/1024B/10KB/40KB/100KB}.

disktest Error Messages

6000 Re-reading and recomparing block <number> on <name>.

Probable_Cause(s):
a. Media error b. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6002 Error on recomparing block <number> on <name>.

Probable_Cause(s):
a. Media error b. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6004 <name> failed on <name> '<name>', blk <number>:
<error_message>.

Probable_Cause(s):
a. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6006 Compare error on <name> <name>, block <number>, offset
<number>.

Probable_Cause(s):
a. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6008 Compare error: Block <number> on <name> was written
with a repeating hex pattern of '<number>'.

Probable_Cause(s):
a. Media error b. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6010 TIME OUT!

Probable_Cause(s):
a. System too busy b. Disk Faulty Cable/Disk
Recommended_Action(s):
a. Reduce system load
6012 Couldn't close <name>.

Probable_Cause(s):
a. System error
6014 <name> read failed on disk, in-between blocks <number>
and <number>: <name>.

Probable_Cause(s):
a. Media error b. Faulty cable/disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6016 <name> read failed due to unexpected end of media:\

6018 <name> write failed on disk, in-between blocks
<number> and <number>: <name>.

Probable_Cause(s):
a. Media error b. Faulty disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6020 <name> write failed due to unexpected end of media:

6022 <name> compare failed on '<name>', block <number>,
offset <number>

Probable_Cause(s):
a. Media error b. Faulty disk/controller
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6024 Couldn't close <name>.

Probable_Cause(s):
a. Faulty disk/controller b. system error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
6026 failed automount <name> onto <name>:<error_message>

Probable_Cause(s):
a. Un-supported file system b. System error
Recommended_Action(s):
a. Disable the file system subtest b. Disable the file system subtest
c. If the problem persists, call your authorized Sun service provider.
6028 <error_message>
8000 File system subtest only allow to run on off-line mode

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. re-enter command line correctly
8002 malloc() failed

Probable_Cause(s):
a. System load too heavy b. System error
8006 File operation error: Couldn't <name> file '<name>' on
<name>: <error_message>.

Probable_Cause(s):
a. Lack of system resource b. Permission error
c. System error
Recommended_Action(s):
a. Reduce the system load b. Check directory/file permission
c. If the problem persists, call your authorized Sun service provider.
8008 Not enough free blocks on <name> (partition <number>)

Recommended_Action(s):
a. Try another partition or delete some files which no more needed
8010 No writable partition on <name>.

Recommended_Action(s):
a. Try another partition
8012 No file system on device: <name>.

Recommended_Action(s):
a. Use 'newfs' to create file system b. Disable the file system subtest
8014 Couldn't run fstest on any partition of device:
<name>(except 2)

Probable_Cause(s):
a. File system not supported b. System error
Recommended_Action(s):
a. Disable the file system subtest b. If the problem persists, call your authorized Sun service provider.
8016 Cannot open device: <name>.

Probable_Cause(s):
a. Parameter error b. System error
Recommended_Action(s):
a. Enter the correct name of disk as dev=c0t3d0 b. If the problem persists, call your authorized Sun service provider.
8018 Couldn't mount /dev/dsk/<name>

Probable_Cause(s):
a. Parameter error b. System error
Recommended_Action(s):
a. Enter the correct name of disk as dev=c0t3d0 b. If the problem persists, call your authorized Sun service provider.
8020 Couldn't remove temporary dir '<name>':
<error_message>.

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8022 fail get semaphore: <error_message>

Probable_Cause(s):
a. Lack of system resource b. System error
Recommended_Action(s):
a. Please reduce system load b. If the problem persists, call your authorized Sun service provider.
8024 fail lock mtab semaphore: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8026 fail unlock mtab semaphore: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8028 failed get_volmgr_name()
8030 Couldn't open <name>: <error_message>

Probable_Cause(s):
a. Cable loose or disconnected b. Device off-line or missing
c. Device not configured
Recommended_Action(s):
a. Check cable b. Check device on-line
c. Configure device
8032 Get file state <name> failed: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8034 Couldn't open <name>

a. Probable_Cause(s):
Permission error
a. System error
Recommended_Action(s):
a. Check permission b. If the problem persists, call your authorized Sun service provider.
8036 failed putmntent(): <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8038 fail rename file

Probable_Cause(s):
a. Permission error b. System error
Recommended_Action(s):
a. Check permission b. If the problem persists, call your authorized Sun service provider.
8040 Couldn't get mount table entry for <name>.

8042 Invalid device name in <name>

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. Enter the correct name of disk as dev=c0t3d0
8044 Message table overflow on device <name>

Probable_Cause(s):
a. Parameter error b. System error
c. Program error
Recommended_Action(s):
a. Enter the correct name of disk as dev=c0t3d0 b. If the problem persists, call your authorized Sun service provider.
8046 Invalid controller id <name> for <name>

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. re-enter command line correctly
8048 <name>, disk DKIOCINFO ioctl: <name>

Probable_Cause(s):
a. Controller is not supported b. System error
Recommended_Action(s):
a. Disable the file system subtest
b. If the problem persists, call your authorized Sun service provider.
8050 failed getting shared memory for monitor <number>:
<error_message>:

Probable_Cause(s):
a. Lack of system resource b. System error
Recommended_Action(s):
a. Please reduce system load b. If the problem persists, call your authorized Sun service provider.
8052 failed attaching monitor shared memory:<error_message>

Probable_Cause(s):
a. Lack of system resource b. System error
Recommended_Action(s):
a. Please reduce system load b. If the problem persists, call your authorized Sun service provider.
8053 failed create monitor shared memory <number>:
<error_message>

Probable_Cause(s):
a. Lack of system resource b. System error
Recommended_Action(s):
a. Please reduce system load b. If the problem persists, call your authorized Sun service provider.
8054 Shm remove error: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8056 New error messages in system log. Extracted
below:<error_message>

Probable_Cause(s):
a. Faulty cable/disk/controller
Recommended_Action(s):
a. See /var/adm/messages for more information b. If the problem persists, consult your authorized Sun service provider.
8060 fails to open any partition of <name>

Probable_Cause(s):
a. File system not mounted
Recommended_Action(s):
a. Please mount the file system then run the test b. Disable the file system subtest
c. If the problem persists, call your authorized Sun service provider.
8060 failed getting semaphore: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8062 failed getting shared memory: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8064 failed attaching shared memory:<error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8068 failed unlocking semaphore: <error_message>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8070 fail open floppy disk

Probable_Cause(s):
a. No Floppy Disk in Drive
Recommended_Action(s):
a. Check the Floppy
8072 failed FDIOGCHAR on floppy ioctl

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8074 ioctl DKIOCGGEOM failed

Probable_Cause(s):
a. File system not supported b. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8074 ioctl DKIOCGAPART failed

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8076 fail initialize shared memory

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8078 Illegal parameters on Online Mode

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. Re-enter the correct option
8080 Illegal parameters on Conn. Mode

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. Re-enter the correct option
8082 failed get_volmgr_name()

Probable_Cause(s):
a. No Floppy Disk in Drive
Recommended_Action(s):
a. Check the Floppy
8084 Mounted file system on device!

Probable_Cause(s):
a. Not enough disk space b. Permission error
c. System error
Recommended_Action(s):
a. Reduce the system load b. Check directory/file permission
c. If the problem persists, call your authorized Sun service provider.
8086 Invalid controller id <number> from <name>

Probable_Cause(s):
a. Parameter error
Recommended_Action(s):
a. Enter the correct name of disk as dev=c0t3d0
8088 Couldn't get file system information on <name>
errno=<number>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8090 ioctl() failed on <name>: <name>.

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.
8092 Fail to get disk information

Probable_Cause(s):
a. No supported disk b. Too heavy load system
Recommended_Action(s):
a. No UNIX message monitor feature in this disk(2) b. Reduce system load
8094 Failed to create a message base for controller
<number>

Probable_Cause(s):
a. No disk under this controller
Recommended_Action(s):
a. connect disk driver then run test again
8096 fail to make directory <name>

Probable_Cause(s):
a. Lack of system resource b. Permission error
c. System error
Recommended_Action(s):
a. Reduce the system load b. Check directory/file permission
c. If the problem persists, call your authorized Sun service provider.
8098 Failed to mount partition

Probable_Cause(s):
a. Does this disk only have partition 2
Recommended_Action(s):
a. Partition 2 must be manually mounted
8010 r/w is on /dev/r<name>

Probable_Cause(s):
a. System error
Recommended_Action(s):
a. If the problem persists, call your authorized Sun service provider.