Mac Still Waiting For Root
Evangelino Cousteau
I found this kernel for 10.12.5. I added the kext and kernel to the USB Installer. With this kernel I got past the plus line in clover by adding NullCPUPowerManagement. When I boot with cpus=1 and -v I get to FakeSMC Successfully initialized and then there are errors about USB XHCI. When I add GenericUSBXHCI I get the following output and then it freezes.
I have been able to boot further by using cpus=1 and the clover OsxAptioFixDrv driver. Now I am stuck at a prohibited symbol with garbled text. At the bottom, Still waiting for root device can be seen. I am trying to install from my USB2.0 stick in a USB2.0 port on my laptop. I have tried Rehabman's USBInjectAll (with and without the limit patch) and I have tried GenericUSBXHCI kext without any luck. I have tried clover's fix usb patch and I havee tried to use clover's inject usb and usb ownership options. My BIOS does not have a legacy USB option (although legacy booting is disabled.) I am out of ideas. How do I get the USB ports to work?
My system will not boot past the white screen with the apple logo and a spinning wheel and after a while the apple logo turns into a O with a \ through the middle. I tried to start the system in safe mode, os x recovery system, target disk mode, and all no gos. When I started in Verbose mode it gives the same O with the \ in the middle and gives the statement "still waiting for root device" over and over and will not start and gets really hot on the bottom. What can I do about this issue? Really need to get my data off the harddrive!! Please Help!!
Putting drive in an enclosure worked great for me. I really thought I lost all data but it's still there. This does mean I have an other problem at hand. I tried every single boot key combination nothing worked all I got was the "waiting for root device" error. Other error I get is "SATA WARNING: Enable auto-activate failed". So took the hdd out again hooked it up to my imac and ran disk utility. Got several errors repaired disk. Back in macbook pro but nothing happened. Still same errors. Anybody have any idea what to try next?
Seen the document. Haven't run through all the options yet. ? I tried to boot it in target disk mode on my imac yesterday and that worked fine. So I think it's not a HDD problem but rather logic board or cables even. Don't know if I feel like taking it to Apple store again. Took it to a "Genius" bar the first time but they booted it and send me of with an external HDD to do the backup at home. After which I said "what if it doesn't boot when I am home?". On which they said "Don't worry it will". The next is history. Back at home it didn't boot and I fixed it myself, that is too say I removed the HDD and put it in an enclosure.
So when I have ran through the whole document and I still don't have a result only THEN will I go back to Apple. Do you know if they still have the flat rate plan? I have read about it but not sure if it truly exists.
Im using Clover (BootDiskUtility) and bootpack macOS Sierra 10.12 for Hp430, but when i try boot Mac Os Sierra in my hp 430 i have an error "waiting for root devices" then the system crash like "graphic glitch" and stop sign.
Hello! I came back again with good news I finally started Mac OS, the problem was that I used 2 USB, the solution was to put the operating system and clover boot loader in the same "key" or usb, I am now trying to install the audio kext. .. When I install everything I will upload the "bootpack" here, thanks a lot for the answers
Edit: I plugged mouse back and tried again. Maybe the issue isn't the crng itself. Without mouse, it hands a few secs on the waiting root device message and passes. With mouse this msg doesn't hang, after it I get a msg about low-speed USB device, then a msg about optical mouse, then hid-generic. All of them should be about the mouse. Then the crng msg back and hang.
If you partition the disk first you will probably have a uuid mismatch as shown as the second to the last line. OpenWrt is not fully booted and usable because root did not mount. This might be fixed by editing the grub2 config to match the actual root uuid.
Yes I see new high speed USB device, presumably that is the drive. (High speed means USB2). That message should be followed though by usb-storage detecting the partitions on the drive, and ext4 mounting it.
I followed -developer/quickstart-build-images to make a custom build, it's currently compiling and haven't got any error. But it's only for learning, I looked around on makeconfig and couldn't find where to enable NVMe driver.
OpenWrt on x86 hardware aka PC or Servers OpenWrt can of course run in normal PC or server hardware, and take advantage of the much more powerful hardware the x86 (Intel/AMD) architecture can offer. Note: For UEFI bootable OpenWrt image see OpenWrt...
Can you give a bit of background? Are you attempting multiboot? Are there other operating systems on your NVMe drive? Why are you partitioning manually? Since you used the img file before, I'm assuming you have just OpenWrt on the NVMe drive for now but you probably resized the rootfs after installation? If you did so, it might just be that your rootfs has a differend UUID now (do check that!). If so, you need to modify your /boot/grub/grub.cfg to use the new UUID.
I have a custom designed AM3352 board that uses a micro SD card on MMC0 as it's main storage. On about 1 out of 6 boots the system will get stuck at the "Waiting for root device /dev/mmcblk0p2... " phase and will need a reset or power cycle to recover. Does anyone know exactly what this indicates and how to fix it?
-EINVAL doesn't disable CD. Rather, it indicates that something other than GPIO is used for CD (ie, doesn't apply to your situation). As Mario indicated in the other thread, am335x_mmc[0].nonremovable = true disables CD.
Today I experimented with setting nonremovable to true and specifying the GPIO for the CD signal. I monitored the CD signal on the scope and it looks fine (inverse logic). I tried adding debug printks to omap_hsmmc_card_detect and omap_hsmmc_get_cover_state in omap_hsmmc.c but it looks like in my case they are never reached. Note that on my hardware I have 10K pullup resistors on all the lines to the SD card, as well as pull-ups defined in the pinmux, not sure if that's a problem?
I doubt the combination of the resistor and the mux pull-up is a problem. The EVM board does the same thing except that it uses a 470k resistor. A short to ground within the connector should have no problem overcoming both.
All I can suggest is to add some reading of the GPIO registers in some appropriate init code (at mount wait?) to see what the processor believes is the state of the line and the GPIO configuration. And likely read the associated control register to verify that the mux settings didn't get changed by another driver after the omap_hsmmc_gpio_init() code ran.
This indicates to me that there's some type of corruption reading the card. I've tried multiple cards, fscked the file system on each, and tried different boards but the problem still remains. Most of the time the board boots OK but sometimes it will display the above log messages and hang. How can I get this working reliably?
I did some further testing and the problem stems from the mmc_decode_scr function in drivers/mmc/core/sd.c in the kernel. The code is reading scr_struct as non zero sometimes, which is causing the function below to return -EINVAL. The actual value returned is not consistent when it's non zero either. If I remove this check and let the system continue to boot it still boots and runs successfully. But I would like to know why the SCR on the SD card is sometimes returning non zero.
ROM and UBoot do not require this line since they use a lower level driver. However once the linux kernel decompressed and went to mount the second partition it would use the more advanced linux mmc driver which checks for the Card detect.
The only thing I can do is recover from backup, which dates back almost a year (I know, I know,...), so any re-application of updates now involves a basket of 150 packages. (I do not remember how recent the "killer" update may have been.)
I have multiple instances of the Orange Pi hardware; they all exhibit the same problem. Multiple uSD cards; same problem still. And at least two different machine identities share this grief. I simply cannot apply any updates since my backups were taken, without killing things.
If you mean "a fresh install" from distro, no, I haven't done that. I'm trying to rescue the existing machines. I have two separate machine identities (which do have a common ancestor, if we were to go back far enough), having their own backups each. I have restored the two backups multiple times, tried something, applied updates, and then hit the brick wall in both cases, every time.
Getting a full boot log to a serial console is a great idea, and I've been working on doing that, but haven't quite figured it out yet. I have verbosity=7 and console=both in /boot/armbianEnv.txt, and have a serial dongle, but have not yet gotten any traffic into a Putty session. Obviously doing something wrong, and need to play with that more.
May be a question, but have you tried each of the three baud rates that getty is configured to use? Those being 115200, 38400 and 9600? I've had a few cases where for some reason the default baud rate was not being used and had to get putty to try the latter two baud rates to be able to get output from the board and be able to login and issue commands.
7fc3f7cf58