MB910 reports corrupted .mb files and error

Discussion in 'MultiBeast Bug Reports' started by Oclair, May 3, 2017.

  1. Oclair

    Oclair

    Joined:
    Jun 17, 2011
    Messages:
    44
    Motherboard:
    ga-z68ap-d3_f8
    CPU:
    i5 2400
    Graphics:
    AMD Radeon HD 6670
    Mac:
    MacBook Pro
    Classic Mac:
    iBook, iMac, LC, Performa, Power Mac, PowerBook
    Mobile Phone:
    iOS
    May 3, 2017 at 8:56 PM #1
    Oclair

    Oclair

    Joined:
    Jun 17, 2011
    Messages:
    44
    Motherboard:
    ga-z68ap-d3_f8
    CPU:
    i5 2400
    Graphics:
    AMD Radeon HD 6670
    Mac:
    MacBook Pro
    Classic Mac:
    iBook, iMac, LC, Performa, Power Mac, PowerBook
    Mobile Phone:
    iOS
    Current Hardware/Status:
    ga-z87n-wifi
    i5 4670k
    16GB DDR3
    Samsung EVO 840 1TB SSD
    Audio: Yes
    Ethernet Nic: Yes
    Trim: Yes
    Wifi: Yes
    Bluetooth: Yes
    Facetime,iMessenger: don't know/care
    iCloud: OFF
    Little Snitch: Yes
    All via a happily running system setup with MultiBeast 901
    Screen Shot 2017-05-03 at 21.29.17.jpg

    Aah its a new MultiBeast with lots of new goodies!
    Let's give it a Spin, shall we?

    Enter the Warrior Tom Sawyer Multibeast 9.1.0
    Screen Shot 2017-05-03 at 21.44.53.jpg
    Seems that there is a problem with backwards compatibility with previous or current MultiBeast Config files incorporating configurations no longer required/need etc...
    Is this popping up an error the working as intended?
    Note to self: I think not...

    Ok no problem, should be kinda simple these days to roll one of my own ;)


    Screen Shot 2017-05-03 at 21.28.26.jpg
    When run produced almost immediately this result
    Screen Shot 2017-05-03 at 21.12.32.jpg
    hmm thats new, lets Check and see

    Screen Shot 2017-05-03 at 21.23.37.jpg
    Ah, figures a search my Mother would only love!

    Q: do we have a path for MultiBeast.log?
    A: Yes in console where system logs normally live.
    But I am not sure everyone else who gets this error knows this?
    Note to self: Maybe better to let em know where it lives!


    ~/Library/Logs/MultiBeast.log

    05/03/17 21:11:03 - Starting MultiBeast 9.1.0-20170501
    05/03/17 21:11:25 - Failed to find node with path 'Drivers > Audio > Realtek ALCxxx > Optional HD 4600 HDMI Audio'
    05/03/17 21:11:53 - Failed to find node with path 'Drivers > Audio > Realtek ALCxxx > Optional HD 4600 HDMI Audio'
    05/03/17 21:12:22 - Installing 'Bootloaders > Clover v2.4k r4063 UEFI Boot Mode'
    05/03/17 21:12:27 - Installing 'BootVolume'
    05/03/17 21:12:27 - Mounting EFI
    05/03/17 21:12:27 - Mounting EFI failed. Exiting.
    05/03/17 21:21:51 - Failed to find node with path 'Drivers > Audio > Realtek ALCxxx > Optional HD 4600 HDMI Audio'
    05/03/17 21:23:11 - Installing 'Bootloaders > Clover v2.4k r4063 UEFI Boot Mode'
    05/03/17 21:23:17 - Installing 'BootVolume'
    05/03/17 21:23:17 - Mounting EFI
    05/03/17 21:23:17 - Mounting EFI failed. Exiting.

    Thanks for the Excellent work everyone!
    Best Regards,
    Oclair
     
    Last edited by a moderator: May 3, 2017
  2. MacMan

    MacMan Administrator Staff Member

    Joined:
    Feb 2, 2010
    Messages:
    8,082
    Motherboard:
    GA-Z270X-Ultra Gaming - F8 - UEFI
    CPU:
    i7-7700K
    Graphics:
    GTX 1070
    Mac:
    MacBook Pro, Mac Pro
    Classic Mac:
    Power Mac, PowerBook
    Mobile Phone:
    iOS
    May 3, 2017 at 9:46 PM #2
    MacMan

    MacMan Administrator Staff Member

    Joined:
    Feb 2, 2010
    Messages:
    8,082
    Motherboard:
    GA-Z270X-Ultra Gaming - F8 - UEFI
    CPU:
    i7-7700K
    Graphics:
    GTX 1070
    Mac:
    MacBook Pro, Mac Pro
    Classic Mac:
    Power Mac, PowerBook
    Mobile Phone:
    iOS
    The reason for the failure in backwards compatibility is the removal of "Drivers > Audio > Realtek ALCxxx > Optional HD 4600 HDMI Audio" as seen in line 2 of the MultiBeast.log.

    The reason for the other failure can be seen in the last line of the log.
     
  3. Oclair

    Oclair

    Joined:
    Jun 17, 2011
    Messages:
    44
    Motherboard:
    ga-z68ap-d3_f8
    CPU:
    i5 2400
    Graphics:
    AMD Radeon HD 6670
    Mac:
    MacBook Pro
    Classic Mac:
    iBook, iMac, LC, Performa, Power Mac, PowerBook
    Mobile Phone:
    iOS
    May 7, 2017 at 7:16 AM #3
    Oclair

    Oclair

    Joined:
    Jun 17, 2011
    Messages:
    44
    Motherboard:
    ga-z68ap-d3_f8
    CPU:
    i5 2400
    Graphics:
    AMD Radeon HD 6670
    Mac:
    MacBook Pro
    Classic Mac:
    iBook, iMac, LC, Performa, Power Mac, PowerBook
    Mobile Phone:
    iOS
    I was able to get MB910 to complete a successful install but for some reason the system was not performing well, especially in the Video Game performance aspects as well as general system stability. I used my usb unibeast boot and returned to MB901 and the system returned to a more suitable state. Hopefully this will get ironed out, it always does ;) Great work!
     
  4. piupiu

    piupiu

    Joined:
    Mar 26, 2013
    Messages:
    9
    Motherboard:
    GA-Z87MX-D3H
    CPU:
    i7-4770K
    Graphics:
    NVIDIA GTX 950 2GB
    Mac:
    iMac
    Jul 26, 2017 at 7:22 AM #4
    piupiu

    piupiu

    Joined:
    Mar 26, 2013
    Messages:
    9
    Motherboard:
    GA-Z87MX-D3H
    CPU:
    i7-4770K
    Graphics:
    NVIDIA GTX 950 2GB
    Mac:
    iMac
    I also get the same corrupted configuration message each and every time. I get it even when I create the config file using the same MultiBeast 9.1 app. So, this is not backwards compatibility issue. I simply cannot load back any .mb file at all.
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice