Doing dasdfmt against the partition (dasdf1), and not the whole device (dasdf) is not going to give good results. I don't know if it will fix your problem completely or not, but give this a try: dasdfmt -b 4096 -v -f /dev/dasdf
After some experimentation, I think Mark's right: I shot myself in the foot by trying to work with a partition, not the whole disk.
DETACHing and re-LINKing the disk seems to help; it clears out whatever state data there was about the devices.
dasdfmt is happily running.
Also, with this level of s390-tools, the CMS format step seems to be optional.
Mark Post
Nick
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
