Mark, We did have it in our parmfile, however we went back to the manual and put only the parms that they had in it ( this is our 3'rd boot tape and we have collected a bunch of parms). We put the dasd parm as the first parm and it is now able to see our dasd. Thanks for the help, I'm sure you and the group will be hearing from us soon.....
-----Original Message----- From: Post, Mark K [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 10:04 PM To: [EMAIL PROTECTED] Subject: Re: DASDFMT PROBLEM Thomas, Yes, you didn't specify a "dasd=" parameter in your parmfile, hence the DASD device driver is not allowing access to the devices it detects. I would recommend paring down the amount of DASD available to that LPAR to only those DASD volumes you want Linux/390 to be able to use. Since there is no mechanism to ensure data integrity between Linux/390 and any other operating system, data loss is only a finger check away. Further, although you didn't ask about this, I would recommend that you only use the Marist file system for initial "feeling around" purposes. If you intend to go farther than that, think seriously about downloading one of the fully supported distributions that are available. Check out the main page on http://linuxvm.org for those. Mark Post -----Original Message----- From: Marsh, Thomas [mailto:[EMAIL PROTECTED]] Sent: Monday, March 18, 2002 6:22 PM To: [EMAIL PROTECTED] Subject: DASDFMT PROBLEM I am new to the Group, and I am trying to get Linux up in it's own LPAR. I downloaded all the files from the Marist site and created the BootTape. When I IPL the dasd seems to be known but I get the message : 6>dasd:0D50 not enabled due to probeonly mode <6>dasd:0D51 not enabled due to probeonly mode <6>dasd:0D52 not enabled due to probeonly mode <6>dasd:0D53 not enabled due to probeonly mode <6>dasd:0D54 not enabled due to probeonly mode <6>dasd:0D55 not enabled due to probeonly mode <6>dasd:0D56 not enabled due to probeonly mode <6>dasd:0D57 not enabled due to probeonly mode <6>dasd:0D58 not enabled due to probeonly mode <6>dasd:0D59 not enabled due to probeonly mode <6>dasd:0D5A not enabled due to probeonly mode <6>dasd:0D5B not enabled due to probeonly mode <6>dasd:0D5C not enabled due to probeonly mode <6>dasd:0D5D not enabled due to probeonly mode <6>dasd:0D5E not enabled due to probeonly mode <6>dasd:0D5F not enabled due to probeonly mode <6>channel: no Channel devices recognized I have checked and I see the devices built in the /dev directory for the dasda,dasda1......dasdh,dasdh1. When I try and do the lowlevel format I get different results : [root@linux01 /sbin]# dasdfmt -v -b 4096 /dev/dasdg dasdfmt: device to format not specified [root@linux01 /sbin]# dasdfmt -v -b 4096 /dev/dasda -n 0d50 dasdfmt: failed to find device in the /proc filesystem (are you sure to have th) When I look in /proc/dasd/devices all I see is the header. I tried to put my dasd in the file but kept on getting I/O errors. I guess I cannot write to that file. Has anyone fought this dragon before, I am at a loss as how to get the dasd formated and partitioned, so I can get this system up possibly show some of our people that the Mainframe isn't dead it is just taking on a new improved form. *************************************************************** This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message. *************************************************************** This message and any attachments is solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.
