hexagon logo
Register Sign in
  • State Not Answered
  • Replies 6 replies
  • Subscribers 4 subscribers
  • Views 150 views
  • Users 0 members are here
Options
Related

USER FATAL MESSAGE 1250 (BIOWRT) No space left on device (errno = 28)

Viplava
 *** USER FATAL MESSAGE 1250 (BIOWRT)
   STATUS =      28, FILX =  5, LOGNAME = SCR300 , NSBUF3 =  65536
   FILE = /scratch/system/D200131_XLR-KB_FE_DFEM_MODEL_MR_v5.T8595_10.SCR300
   BLKNBR =   573571
   ERROR MESSAGE IS --
   No space left on device (errno = 28)
   BIOMSG: ERROR  1039 HAS OCCURRED IN ROUTINE BP_BIO , FILE INDEX =      5.
   LOGICAL NAME IS SCR300 
 
 *** SYSTEM FATAL MESSAGE 4276 (BP_BIO)
   ERROR CODE   1039 PID=  0
 *** USER INFORMATION MESSAGE 4276 (BP_BIO)
   THE DIAG 44 RELATED A NASTRAN DUMP IS SENT TO LOG FILE.
   USER ACTION: THIS INFORMATION MAY BE USEFUL TO MSC FOR DEBUGGING YOUR PROBLEM.
         PLEASE CONTACT MSC CLIENT SUPPORT.
  • 0
    Hi Hrishikesh,
     
    I attached the F04 and Log files.
    After running for a while, the F06 has this final message:
     
     *** USER FATAL MESSAGE 1250 (BIOWRT)
       STATUS =      28, FILX =  5, LOGNAME = SCR300 , NSBUF3 =  65536
       FILE = /scratch/system/D200131_XLR_nas19.T11492_55.SCR300
       BLKNBR =   948936
       ERROR MESSAGE IS --
       No space left on device (errno = 28)
  • 0
    nastran D200131_XLR_nas19.bdfi mode=i8 sscr=1000gb sdball=1000gb mem=96gb bpool=30gb
     
    Please use above settings to fire job...
    Also your f04 last line at which it got stuck
    13:51:57  112:56   1538.2G    2.0   5743.0    0.2  SEKR0  102   MCE2  BEGN 
     
    This suggest you have a very large RBE type element which is creating a dense matrix. Try using the Lagr formulation when you give a run.
     
    SOL XXX
    CEND
    RIGID=LAGR
     
    Let me know how it goes.
     
  • 0
    Hi Hrishikesh,
     
    I specified all parameters as you requested. The job ran for sometime and gave Fatal messages in F06:
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003011 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003016 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003018 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003020 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003057 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003058 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
     *** USER FATAL MESSAGE 5459 (MDG2RG)
       DEPENDENT GRID ID =10003059 IS DEFINED ON MULTIPLE RIGID ELEMENTS.
    0FATAL ERROR
    1                    * * * END OF JOB * * *
     
  • 0
    There are modeling issues with your RBE elements. This makes the solver running in loop and finally running out of space with rigid=linear or with rigid=lagr its gives a more appropriate error message.
     
    I would suggest fixing all the issues with the RBE elements. Job will not run until we fix these issues.
     
    Now you already have all the nodes in the error message which are creating violations. Also your pre-processor might have some tools to model check the RBE's.
     
    In Nastran we have FEMCHECK=ALL in case control. Please refer QRG for more information on it.
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement