Re: "disk not in z/OS format"
If you don't need z/OS to access the disks, then your best bet is probably "CMS RESERVED". You would have to CMS FORMAT them and then RESERVE them before booting Linux. Given a raft of disks which have already been thusly processed, DO NOT run 'dasdfmt' on them. You don't even need 'fdasd'. Simply tell YaST to use the partition presented (which is the reserved file). -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, Feb 15, 2011 at 19:00, Daniel Tate wrote: > We are continually having a problem when it comes time in autoyast to > do a dasdfmt where it complains that the disks are not in z/OS format. > We are not using PAV (which was the prior problem). it is a mystery > to me and the mainframe guy who's been doing this for 30 years - has > anyone run into the same issue? This is urgent, so if anyone has any > insight please respond. The disks are owned to the appropriate user > (also tried system) and the cyls are formatted (also tried raw). > > Thank you very much. > > -- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: "disk not in z/OS format"
Sorry ... you did not indicate, and I failed to ask, so I presumed you're running on VM. -- R; <>< Rick Troth Velocity Software http://www.velocitysoftware.com/ On Tue, Feb 15, 2011 at 19:00, Daniel Tate wrote: > We are continually having a problem when it comes time in autoyast to > do a dasdfmt where it complains that the disks are not in z/OS format. > We are not using PAV (which was the prior problem). it is a mystery > to me and the mainframe guy who's been doing this for 30 years - has > anyone run into the same issue? This is urgent, so if anyone has any > insight please respond. The disks are owned to the appropriate user > (also tried system) and the cyls are formatted (also tried raw). > > Thank you very much. > > -- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: "disk not in z/OS format"
I've only seen that when I've attempted to do an 'fdasd -a /dev/dasdx' on a disk that didn't have dasdfmt run on it yet... I've never seen dasdfmt complain..(why would it? it's going to format the disk and doesn't care what's there) only fdasd. Are you creating a partition on the disk? Scott Rohling On Tue, Feb 15, 2011 at 5:00 PM, Daniel Tate wrote: > We are continually having a problem when it comes time in autoyast to > do a dasdfmt where it complains that the disks are not in z/OS format. > We are not using PAV (which was the prior problem). it is a mystery > to me and the mainframe guy who's been doing this for 30 years - has > anyone run into the same issue? This is urgent, so if anyone has any > insight please respond. The disks are owned to the appropriate user > (also tried system) and the cyls are formatted (also tried raw). > > Thank you very much. > > -- > 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 more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
"disk not in z/OS format"
We are continually having a problem when it comes time in autoyast to do a dasdfmt where it complains that the disks are not in z/OS format. We are not using PAV (which was the prior problem). it is a mystery to me and the mainframe guy who's been doing this for 30 years - has anyone run into the same issue? This is urgent, so if anyone has any insight please respond. The disks are owned to the appropriate user (also tried system) and the cyls are formatted (also tried raw). Thank you very much. -- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
