Update - Possible causes: Corrupted zFS aggregate – The OMVS root filesystem dataset may be damaged.
Incompatible zFS version – The root file system may have been created with a different version of zFS and is not compatible with your current z/OS or zFS levels. Maybe this ? Dataset is not accessible – It might not be cataloged, not SMS-managed, or not in the right volume. Mount options are incorrect – Check your BPXPRMxx PARMLIB member. ChatGPT says: Meaning of the Message BPXF029E: This message indicates that the root file system for z/OS UNIX could not be mounted. OMVS.SSAT.R31.ROOT: This is the dataset name being used as the zFS or HFS root file system. Return Code = 00000081: This is typically a decimal 129, which translates to EFAULT — a bad address passed to the mount system call. Reason Code = EF096055: EF09xxxx indicates a zFS internal error. 6055 is more specific to zFS and generally indicates a problem with the aggregate or its compatibility. Maybe it has something to do with its compatibility. Thanks -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Manoj Bandi Sent: Wednesday, June 11, 2025 11:38 AM To: [email protected] Subject: Re: BPXF029E ROOT FILE SYSTEM ! CAUTION! EXTERNAL SENDER! STOP, ASSESS, AND VERIFY Do you know this person? Were you expecting this email? If not, report it using the Report Phishing Button! It's ZFS file. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Wednesday, June 11, 2025 9:08 PM To: [email protected] Subject: Re: BPXF029E ROOT FILE SYSTEM Sent by an external sender. Please be cautious about clicking on links and opening attachments. ---------------------------------------------------------------------------------------------------------------- A new root filesystem (defined as a ZFS) should have been built as part of the 3.1 install. You need to go back to the install and see what was created. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Farley, Peter Sent: Wednesday, June 11, 2025 10:23 AM To: [email protected] Subject: [EXTERNAL] Re: BPXF029E ROOT FILE SYSTEM Looks pretty plain to me – your ROOT file system is still HFS and not ZFS: OMVS BPXF287I HFS file system no longer supported How to fix that is beyond my skill set. Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Manoj Bandi Sent: Wednesday, June 11, 2025 11:17 AM To: [email protected] Subject: BPXF029E ROOT FILE SYSTEM Hi Team, Today, am going to upgrade the z/OS 3.1 in one LPAR. I got the below issue. Any help on this ? ROOT not mounted: 05.15.18 SSAT *BPXF029E ROOT FILE SYSTEM OMVS.SSAT.R31.ROOT *WAS NOT MOUNTED. RETURN CODE = 00000081, REASON CODE = EF096055 As per my research in the log i found below msg: "OMVS IEF196I IAR065I JOB IS NOT ELIGIBLE FOR DEDICATED MEMORY" OMVS IEF403I OMVS - STARTED - TIME=05.14.53 OMVS IEF196I IAR065I JOB IS NOT ELIGIBLE FOR DEDICATED MEMORY. OMVS IEF196I IEFA111I OMVS IS USING THE FOLLOWING JOB RELATED SETTINGS: OMVS IEF196I SWA=BELOW,TIOT SIZE=64K,DSENQSHR=DISALLOW,GDGBIAS=JOB OMVS IEE252I MEMBER CTIBPX00 FOUND IN SYS1.IBM.PARMLIB OMVS IEF196I IEF285I SYSTEM.PARMLIB KEPT OMVS IEF196I IEF285I VOL SER NOS= ZSSTR1. OMVS IEF196I IEF285I CPAC.PARMLIB KEPT OMVS IEF196I IEF285I VOL SER NOS= R31RES. OMVS IEF196I IEF285I SYS1.PARMLIB KEPT OMVS IEF196I IEF285I VOL SER NOS= R31RES. OMVS IEF196I IEF285I SYS1.IBM.PARMLIB KEPT OMVS IEF196I IEF285I VOL SER NOS= R31RES. OMVS BPXF287I HFS file system no longer supported OMVS BPXTF012I GLOBAL SETTINGS: fsfull(99,5) ea 0 em 0 OMVS BPXF029E ROOT FILE SYSTEM OMVS.SSAT.R31.ROOT OMVS WAS NOT MOUNTED. RETURN CODE = 00000081, REASON CODE = EF096055 Thanks Manoj -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
