How to - How to reaccess a DASD in accepted state

#cat /proc/dasd/devices

If you see "accepted" in the output the corresponding DASD is disabled and not available for use. You can re-enable the DASD with the command:

#echo 'set <devno [-devno]> on '>/proc/dasd/devices

where <devno> is the device number of the DASD you want to enable. Example:

#cat /proc/dasd/devices 0700(ECKD)at (94:0)is dasda:active at blocksize:4096,601020 blocks,2347MB 0800(ECKD)at (94:4)is dasdb:active at blocksize:4096,601020 blocks,2347MB 0900(ECKD)at (94:8)is dasdc:accepted

Disk 900 is in the accepted state and cannot be formatted with the dasdfmt command.

#echo 'set 900 on'>/proc/dasd/devices

enables the disk and changes its state to "active, not formatted".

#cat /proc/dasd/devices 0700(ECKD)at (94:0)is dasda:active at blocksize:4096,601020 blocks,2347MB 0800(ECKD)at (94:4)is dasdb:active at blocksize:4096,601020 blocks,2347MB 0900(ECKD)at (94:8)is dasdc:active n/f #

You now will be able to format the DASD.

How to - How to solve install problems related to the network adapter on a MP3000?

How to - How to set up a cross build environment?

In the following it is assumed that all archives (*.tar.gz) and all patches (*.diff) are located in your home directory (~). The version numbers are exemplary only. You should replace them by the version number of the packages you are using. Note also that some of the patches may have an additional versioning position as compared to the original packages. This was done to distinguish different patch revisions to be applied to the same original package version. e.g., binutils-2.9.1.2.diff.tar.gz contains our third patch revision to be applied to the binutils-2.9.1 package.

How to - How to avoid problems running in LPAR mode?

LINUX for S/390 runs in either environment, native, in LPAR, and as a guest under VM/ESA. Running LINUX for S/390 in an LPAR environment you should follow the following configuration guidelines :

While OS/390 or VSE/ESA have configuration scripts telling the OS which devices to regard or disregard, LINUX does not. All it has is the kernel parameter list or the parameters passed to a driver with insmod. Unless configured otherwise, LINUX for S/390 will try to autosense all the devices accessible. While this is usually the desired behavior when running native or as guest under VM/ESA it might not be desirable when running in a LPAR environment with shared CHPIDs. This behavior may lead to sharing problems. This is not specific to LINUX, but is also the case with misconfigured OS/390, VM/ESA, and VSE/ESA systems. However, it might become more quickly visible with LINUX's autosensing mode.

If you have a LPAR environment with shared CHPIDs there are two possible approaches possible to avoid sharing problems:

Please follow either of the two configuration methods to assure that LINUX for S/390 cannot disturb a production environment residing in another LPAR.

Performance hints and tips

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.