Contribute
Register

[Solved] Still waiting for root device

Status
Not open for further replies.
I understand what Gigamaxx was telling me to do. The issue is that I cannot do it. How do I run fsck when I am unable to boot into single user mode?
The issue is that I cannot do it. How do I run fsck when I am unable to boot into single user mode?

I am trying to find out why you are unable to reach the Command Prompt in Single User Mode Boot:

  • Can you reach Clover Boot Manager Screen (CBM for short from now on) if you boot with your Sierra System Hard disk?

  • If you can see your Sierra System Disk icon on the CBM , does it stay long enough for you to navigate to Options>Boot Args?
  • If you get the chance to type in the flags -v and -s and then return to CBM and click the icon of your System Hard Disk what is the next thing you see on the screen? Does the system crash suddenly with no display on screen?
A series of screen shots will clarify what you are trying to convey before I can say with certainty , the next best option for you is to create a new Installer and start all over again.
 
  • Can you reach Clover Boot Manager Screen (CBM for short from now on) if you boot with your Sierra System Hard disk?
Yes.
  • If you can see your Sierra System Disk icon on the CBM , does it stay long enough for you to navigate to Options>Boot Args?
Yes.
  • If you get the chance to type in the flags -v and -s and then return to CBM and click the icon of your System Hard Disk what is the next thing you see on the screen? Does the system crash suddenly with no display on screen?
Look below for an explanation.
Is this the message? Does it happen right away?

Still waiting on root device
*************************************************
Yes, that is the message, no it does not happen right away. When I select my Sierra install from CBM with verbose mode enabled, it scrolls a bunch of log messages, and seems to be doing early boot process stuff, but then after a second or two it stops, and gets stuck waiting on something. Another 10-20 seconds later, the prohibited sign shows up, and the text on the screen gets all garbled graphically, but I can still recognize the final line on the output as "Still waiting on root device."
On clover menu screen scroll to options and select, then check the ACPI section and look for DSDT fixes. For Skylake and for Kaby lake Systems you should select zero options or no fixes. Check this out because a standard clover install default loads a large number of fixes which aren't needed for these builds.
I checked the ACPI section and the DSDT fix mask is 0x00000000. When I look at which options are enabled, none are checked.
Also, if you could mount the EFI partition of the SSD and post your config.plist that may have something that stands out.
I have attached my config.plist file for y'all to check out. This is from the EFI partition on my internal SATA drive.

I don't have any screenshots of what is happening (if necessary I can take some pictures later), but it's basically the exact same thing seen here. The only difference is that when all the debug options are enabled, lots of brightly colored output is interleaved between the usual verbose mode output, but the end result is the same.

I really appreciate all the help y'all!
 

Attachments

  • config.plist
    4.6 KB · Views: 337
Now when I attempt to boot, it tells me "This version of Mac OS X is not supported on this platform!"

I assume this is due to elements of the SMBIOS section in the config.plist file that you provided? What should I try next?
 
Now when I attempt to boot, it tells me "This version of Mac OS X is not supported on this platform!"

I assume this is due to elements of the SMBIOS section in the config.plist file that you provided? What should I try next?

Strange, I used the latest version of Clover Configurator and set Symbios to iMac 18.3 it has Kaby Lake i7 7700k as CPU.
Normally that happens when you have an older config. That is no longer supported.
Hang on I'll try imac 17.1 and send again.config.plist 2.zip
 

Attachments

  • config.plist 2.zip
    2.3 KB · Views: 232
Last edited:
Strange, I used the latest version of Clover Configurator and set Symbios to iMac 18.3 it has Kaby Lake i7 7700k as CPU.
Normally that happens when you have an older config. That is no longer supported.
Hang on I'll try imac 17.1 and send again.config.plist 2.zip
Now I am back to my original problem. Exactly the same as before, I end up at the prohibited symbol with "Still waiting for root device" as the last line on the verbose output.
 
Yes.

Yes.

Look below for an explanation.

Yes, that is the message, no it does not happen right away. When I select my Sierra install from CBM with verbose mode enabled, it scrolls a bunch of log messages, and seems to be doing early boot process stuff, but then after a second or two it stops, and gets stuck waiting on something. Another 10-20 seconds later, the prohibited sign shows up, and the text on the screen gets all garbled graphically, but I can still recognize the final line on the output as "Still waiting on root device."

I checked the ACPI section and the DSDT fix mask is 0x00000000. When I look at which options are enabled, none are checked.

I have attached my config.plist file for y'all to check out. This is from the EFI partition on my internal SATA drive.

I don't have any screenshots of what is happening (if necessary I can take some pictures later), but it's basically the exact same thing seen here. The only difference is that when all the debug options are enabled, lots of brightly colored output is interleaved between the usual verbose mode output, but the end result is the same.

I really appreciate all the help y'all!
  • I just came back and read the back and forth message exchanges up to your last post following the use of second edited config.plist ending in the same error of "still waiting on root device"
  • I have also reviewed your uploaded config.plist from your Sierra System disk. I have made some comments about the config.plist for your consideration.
You posted
Yes, that is the message, no it does not happen right away. When I select my Sierra install from CBM with verbose mode enabled, it scrolls a bunch of log messages, and seems to be doing early boot process stuff, but then after a second or two it stops, and gets stuck waiting on something. Another 10-20 seconds later, the prohibited sign shows up, and the text on the screen gets all garbled graphically, but I can still recognize the final line on the output as "Still waiting on root device."

  • In your config.plist Boot section, you have only dart=0 as boot arg[ See my edited image from your c.plist Boot section]
  • In your above message, you just say
    I select my Sierra install from CBM with verbose mode enabled, it scrolls a bunch of log messages, ....."Still waiting on root device."
    • Did you not add -s to Boot Arg: to enable booting in Single User Mode?
  • I noted in the Gui section of your config.plist you have [√] Legacy.
    • Isn't your Sierra System installation in UEFI mode?
    • Do you have any other disks attached to the Motherboard in Legacy mode for Clover Bootloader to Scan?
  • Graphics section of Config shows [√] Inject Intel [See image]
    • Your hardware list shows ASUS GeForce GTX 1070 Strix as your Graphics Card
    • Your post so far does not mention about your graphics card used and Display monitor Connection for the GPU and BIOS Options chosen.
    • Are you using the Integrated Intel HD Graphics?
      • Your current error does not seem to be directly related to the Graphics.
  • Rt Variables in config.plist shows CsrActiveConfig=0x3 [See image]
    • Until the system is fully setup with required kext install , better to have that value at 0x67
  • SMBIOS is blank. No System Definitions :
    • This is a significant issue but cannot explain current error
 

Attachments

  • 1.Configplist_Boot.png
    1.Configplist_Boot.png
    355.9 KB · Views: 525
  • 2.ConfigPlist_GUI.png
    2.ConfigPlist_GUI.png
    314.9 KB · Views: 515
  • 3.config-Graphics.png
    3.config-Graphics.png
    243.2 KB · Views: 500
  • 4.Configplist_Rt Variables_CsrActiveConfig.png
    4.Configplist_Rt Variables_CsrActiveConfig.png
    223.8 KB · Views: 509
  • 5.BlankSMBIOS.png
    5.BlankSMBIOS.png
    228.4 KB · Views: 471
  • 6.Configplist_System Parameters.png
    6.Configplist_System Parameters.png
    200.7 KB · Views: 461
  • I just came back and read the back and forth message exchanges up to your last post following the use of second edited config.plist ending in the same error of "still waiting on root device"
  • I have also reviewed your uploaded config.plist from your Sierra System disk. I have made some comments about the config.plist for your consideration.
You posted

  • In your config.plist Boot section, you have only dart=0 as boot arg[ See my edited image from your c.plist Boot section]
  • In your above message, you just say
    • Did you not add -s to Boot Arg: to enable booting in Single User Mode?
  • I noted in the Gui section of your config.plist you have [√] Legacy.
    • Isn't your Sierra System installation in UEFI mode?
    • Do you have any other disks attached to the Motherboard in Legacy mode for Clover Bootloader to Scan?
  • Graphics section of Config shows [√] Inject Intel [See image]
    • Your hardware list shows ASUS GeForce GTX 1070 Strix as your Graphics Card
    • Your post so far does not mention about your graphics card used and Display monitor Connection for the GPU and BIOS Options chosen.
    • Are you using the Integrated Intel HD Graphics?
      • Your current error does not seem to be directly related to the Graphics.
  • Rt Variables in config.plist shows CsrActiveConfig=0x3 [See image]
    • Until the system is fully setup with required kext install , better to have that value at 0x67
  • SMBIOS is blank. No System Definitions :
    • This is a significant issue but cannot explain current error

The config.plist I uploaded is exactly what multibeast created automatically when I used quick start for UEFI installations.

When I was attempting to boot into single user mode, I simply enabled -s and any other options Gigamaxx mentioned by hitting the space bar with my Sierra install selected at CBM, and checking off the options I was told to use. I have never manually edited the config.plist file.
 
Now I am back to my original problem. Exactly the same as before, I end up at the prohibited symbol with "Still waiting for root device" as the last line on the verbose output.

Google Clover configurator, it free and will allow you to edit the config.plist, I didn't catch the 1070, you could leave that out and get it working with Hd 630 first then install and download the web drivers.

To use clover configurator open it and when the option to mount EFI comes up select no. Then go to the menu bar on the left and select "mount EFI". It will list all EFI partitions, select the one for Sierra disk. Close Clover configurator, and open the EFI folder that appeared on the desktop, select Clover folder. This should be the sierra disk, right click on the config.plist and select open with "Clover configurator". You will be able to edit it and then after finished close clover app and hit OK prompt. Reboot and try with new Symbios iMac 14.2, Mac Pro etc...
 
Ok, so I did a reinstall, and I tried doing a few things differently.

I followed the same procedure I described in my first post, up until running multibeast. This time, when I ran multibeast, I did more than just the quick start for UEFI. I did the quickstart UEFI, plus 200 series audio, intel mausi ethernet, Intel 6xx graphics, iMac14,2 profile, and I think a couple of other things. Anyway, I looked over my Clover config in Clover Configurator, and everything looked appropriate. I'll attach the new plist.

So, after all of that, I attempted to boot via Clover on internal SATA drive (the one with all the configurations applied) -> Sierra on internal SATA drive, and I get the same result! The same exact thing. It does not make sense to me that prior to running multibeast, booting my Sierra install works fine, but afterwards, it consistently causes this error.
 

Attachments

  • config.plist
    5.6 KB · Views: 354
Status
Not open for further replies.
Back
Top