Problem resolved. I didn't follow my procedures. I evidently forgot to do a DIRECTXA command under VM and when I attached the volume to Linux it saw tracks 0 thru 10016. The VM directory only presents tracks 1 thru 10016.
Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott Rohling Sent: Wednesday, April 01, 2009 9:51 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Formatting 3390-9 problem with RedHat Are you dedicating/attaching volumes to this guest? If they are minidisks, then you've been given full pack minidisks which include cylinder 0 (note the 10017 size) .. and Linux is formatting the dasd label.. If they are dedicated volumes - then I'm not sure how it's going to act from a z/VM point of view in terms of a valid VTOC. Scott On Wed, Apr 1, 2009 at 7:40 AM, Bauer, Bobby (NIH/CIT) [E] < baue...@mail.nih.gov> wrote: > Suddenly this morning I'm having trouble formatting a 3390-9 in > compatibility mode. After formatting the device under VM with cpfmtxa and > examining the vtoc with IEHLIST, it is as expected, it tells me there is a > permanent I/O error. > > > > > > Attaching the device to a guest and formatting with: > > > > dasdfmt -v -b 4096 -d cdl -f /dev/dasdg -l ncial5 > > Retrieving disk geometry... > > Drive Geometry: 10017 Cylinders * 15 Heads = 150255 Tracks > > > > I am going to format the device /dev/dasdg in the following way: > > Device number of device : 0x204 > > Labelling device : yes > > Disk label : VOL1 > > Disk identifier : NCIAL5 > > Extent start (trk no) : 0 > > Extent end (trk no) : 150254 > > Compatible Disk Layout : yes > > Blocksize : 4096 > > > > --->> ATTENTION! <<--- > > All data of that device will be lost. > > Type "yes" to continue, no will leave the disk untouched: yes > > Formatting the device. This may take a while (get yourself a coffee). > > Detaching the device... > > Invalidate first track... > > formatting tracks complete... > > Revalidate first track... > > Re-accessing the device... > > Finished formatting the device. > > Retrieving dasd information... ok > > Writing empty bootstrap... > > Writing label... > > Writing VTOC... ok > > Rereading the partition table... ok > > > > Re-examining the vtoc I now see valid allocation which from experience > tells me a volume restore will not result in a valid volume. > > > > I've used these procedures maybe 100 times. Any ideas? > > > > > > Bobby Bauer > > Center for Information Technology > > National Institutes of Health > > Bethesda, MD 20892-5628 > > 301-594-7474 > > > > > > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
