Меню Рубрики

Установка mac os waiting root device

Это видео недоступно.

Очередь просмотра

Очередь

YouTube Premium

Hackintosh-still-waiting-for-root-device/

Хотите сохраните это видео?

Пожаловаться на видео?

Выполните вход, чтобы сообщить о неприемлемом контенте.

Понравилось видео?

Не понравилось?

Текст видео

Hackintosh or Macintosh installation shows this error: still waiting for root device while installation, here you can fix this problem 100%.
with refrence of
https://www.hackintosh.computer/59/ha.
What does “Still waiting for root device” means ?
Its very simple, it means that the source from which you’re booting is not detected properly in other way
it can be explained as the operating system was not able to locate a driver/kext for your Hard disk/DvD Drive/USB

The OS X Comes with the latest drivers that supports SATA out of the box
but you may face this issue

If you’re using an old motherboard
if you have a PATA ( Parallel ATA ) Port
If you have a Gigabyte Motherboard.
If you’re using a USB-Hard disk/ USB DvD Rom/ PenDrive to Boot
This problem occurs before/after the installation but it depends on the Boot Media
In This Article i will explain them by dividing the problem types in to three cases
Case:- 1

You May be trying to Install Mac OS X Using a Bootable USB .
This occurs when Your USB Port is not recognized by Mac OS X & In some LGA 1156 motherboards they need to use some additional kexts to Make USB Work Properly.

How Can You Fix It? (Solutions)

Try to boot with the kernel flag USBBusFix=Yes this usually triggers All The USB Ports & Fix all usb related issues
LGA 1156 motherboard Users Install Zenith432’s GenericUSBXHCI.kext into the Bootable USB ( /Extra/Extensions ) Using Kext Wizard / Transmac (If you’re using windows)
Try to Enable/Disable Legacy USB in Bios
Case:- 2
You May be trying to Install Mac OS X Using a DvD
This occurs when Your DvD Drive is not recognized by Mac OS X ( Unless if you’re using a USB DvD Drive Check The Solutions of Case 1 )

How Can You Fix It? (Solutions)
This is a problematic case as you can’t modify the DvD All you can try are the Bios Settings

Try to Set SATA as AHCI on Bios
Try to Change SATA Ports
Connect DvD to Primary SATA/PATA Port
If these doesn’t help stop trying its unworthy to try in this case

Case:- 3
You May be Trying to Boot/Install Mac OS X Using a Hard-disk (SATA/PATA) (Unless if you’re using a USB Hard Disk Check The Solutions of Case 1 )

Try to Boot with USBBusFix=Yes
Try to Boot with ahc >Check Your Bios Settings Set AHCI as SATA
Connect Hard disk to Primary SATA /PATA Port
Installing These Chipset Kexts to /System/Library/Extensions Most of The Systems Including Gigabyte MotherBoard with Jmicron Chipset.

other data from tonymacx86.com
— Changed my USB drive to a different port.
— Used the following BOOT Flags: npci=x2000 -v -x UseKernelCache=No

Note: — Be sure to check that your SATA drive is not connected to a 6gb/s port.

After doing this, I was successfully able to install ML, but after reboot, I couldnt get into Mountain Lion as it kept getting stuck at various parts. I fixed this by using the following boot flags: cpus=1 npci=x2000 -v -x UseKernelCache=No (All of these may not be needed but this is what worked for me).

Note: — I read that using cpus=1 flag for the boot loader would help smooth out the rendering if you are seeing UI Lag and have an jumpy/unresponsive mouse.

источник

Установка mac os waiting root device

Краткая поэтапная инструкция по установке 10.12 Sierra.

Установка принципиально не отличается от установки El Capitan.
Обязательно добавляйте в загрузочные аргументы(бутарги, Boot Arguments) -v debug=0x100 для отлова паники.
Если этого сделано не было, вопросы и просьбы о помощи типа:» у меня идет установка, а потом перечеркнутый круг что мне делать?» или «идет установка, а потом перезагрузка, помогите», будут игнорироваться. Помогайте себе сами.
Конфиг (config.plist) Clover в большинстве случаев годится от El Capitan.

2. Копируем FakeSMC.kext и др. в /EFI/EFI/CLOVER/kexts/10.12(создать папку 10.12) или в /EFI/EFI/CLOVER/kexts/Other
Install.APP в программы
Очень рекомендуется, при первой установке, никаких других кекстов в папки 10.12 и Other не копировать.
FakeSMC.kext копируем чистый, без датчиков.
Можно добавить кекст на сеть, хотя из-за него тоже можно словить панику, к тому же это можно сделать после установки.
2.1. Установка поверх или на другой диск — запустить Install.APP
2.2. Для новой установки изготовить флэшку команндой от Apple:
sudo /Applications/Install\ 10.12\ Developer\ Preview.app/Contents/Resources/createinstallmedia —volume /Volumes/ИМЯФЛЕШКИ —applicationpath /Applications/Install\ 10.12\ Developer\ Preview.app

3. Видео
3.1. Nvidia:
а) Либо пользуемся официальным драйвером, если поддерживает видеокарта.
б) Либо добавляем в бутаргументы nv_disable=1, ставим в VESA режиме, первый запуск так же с ключем и установка вебдрайверов, в аргументы nvda_drv=1 и перезагрузка в штатном режиме.

Читайте также:  Установка балюстрады из бетона

3.2. AMD77xx — легась verge паникует. Пропишите изменения прямо в плист AMDRadeonX4000.kext
ati-personality.pl

4. Звук
4.1. В большинстве случаев достаточно VoodooHDA.kext

5. Настройки
Установка прог со сторонних источников —
sudo spctl —master-disable

6. Клавиатура PS2 (непроверенно)

Нет решений:
Прекращена поддержка процессоров не имеющих инструкции SSE4.
Проверить наличие инструкций ( в другой макоси) в терминале вот так: sysctl -a machdep.cpu.features
===========================================================================
Многие проблемы с установкой и первичной настройкой такие же как в осях 10.8—10.11

Установка по методу ГЫКа с правками xite666 (видео):

источник

[Solved] Still waiting for root device

Roargasm

I am trying to install Sierra on my recently built PC, and I’m running into problems.

So far, this is what I have done:

  1. Adjust all BIOS settings to the recommended settings, except SATA mode, which I keep as Intel Rapid Storage Technology since I have a RAID array configured. Regardless, any drives not in the RAID array (the drive I want to install to is not in the RAID array) are supposed to default to AHCI (relevant to step 3)
  2. Use unibeast to create a bootable Sierra USB
  3. Add AHCIPortInjector.kext to the bootable USB, since for some reason the installer wouldn’t detect any SATA drives without it
  4. Boot the Sierra install partition from Clover on that USB, use fake cpu id 0x0506E3
  5. Install Sierra to internal drive
  6. Boot the newly installed Sierra OS from Clover on the USB, still using fake cpu id
  7. Run multibeast and only do quick start for UEFI, no other changes
  8. Attempt to boot Sierra OS from Clover on the internal drive, still using fake cpu id

At this point, verbose mode ends up at the prohibited symbol, and says «Still waiting for root device» on the last line of the verbose mode output.

Have I done something wrong?

P1LGRIM

Moderator

«Still waiting for root device» when installing this means that your USB flash drive cannot be found.
This is usually because the flash drive is in a USB3 port.
If this is the case move it to a USB2 port, if it is already in a USB2 port move it to another and try again.
Repeat until you have tried all USB ports.
Use a USB2 flash drive.
If it still doesn’t work you could try another flash drive.
You might also try enabling Legacy on your USB3 ports in your BIOS settings.
If you only have USB3 ports try with your USB flash drive in a USB2 hub.

For your GTX 1070 you should boot with nv_disable=1 until you have installed the operating system and web drivers.

Roargasm

I do not think that the flash drive should have anything to do with it at this point. I am not utilizing the flash drive at all in the final step that is causing the «still waiting for root device» issue. I am booting to the Clover bootloader located on my internal SATA drive, and then attempting to boot my Sierra OS, also located on my internal SATA drive. This issue occurs even if there is no USB flash drive plugged in to the computer.

Previously, I did have this issue, which was caused by using a USB 3 flash drive, but I switched to a USB 2 flash drive and the issue was resolved. Now, I am having the same issue again, but with no USB involved whatsoever.

I am booting with the default boot arguments of «dart=0 nv_disable=1», and nothing else is changed besides using the fake cpu id.

P1LGRIM

Moderator

Roargasm

What’s odd is that the issue also occurs now when I boot to the Clover bootloader on the flash drive, and then boot the Sierra OS on the internal SATA drive from there. This worked fine before I did the quick start installs in multibeast.

So, previously it would boot fine going Clover on USB -> Sierra on internal SATA drive. Then, I did the quickstart installs for UEFI in multibeast. Now, Neither Clover on USB -> Sierra on internal SATA drive nor Clover on internal SATA drive -> Sierra on internal SATA drive will finish booting. This makes it seem like something might have gone wrong with the actual Sierra install to cause this issue, but maybe that is not a possibility?

Where would I find a specific driver for my SATA controller? How do I even know what SATA controller I have exactly? Any why would this make any difference if the SATA controller previously worked fine when I first booted the Sierra install via Clover on USB -> Sierra on internal SATA drive?

Читайте также:  Установка лопастей в ласты

Gigamaxx

Moderator

If you ran Multibeast (correctly) the USB is not needed. Remove USB installer so it defaults to Multibeast Clover EFI.

If it persists with same message, hit space bar once at clover menu screen and select: verbose, single user, don’t reboot on panic, keep symbols, and debug kexts.

It should stop at root# type in «mount -uw» hit enter

Root# type in «Fsck -fy» hit enter

Wait, wait, wait, root# type «exit»

All of these without the » » marks.

It should either boot or finish with a black screen, wait a little it may be loading up for the final sign in and account settings if it’s a fresh install. If nothing happens after 5 min then reboot.

For reboot let it boot normally.

Roargasm

cmn699

  • I think Gigamaxx was asking you to run a System file check and fix any errors found automatically using the commands he had listed.. That makes use of the Built- in tool called «fsck» which unlike the diskutility is able to check for errors and if errors are found try to fix the file system errors. Disk Utility can only check and find errors and will ask you to fix it by running in Recovery Mode by rebooting.
  • I believe his rationale for that is a suspicion that your hard disk has many corrupted system files causing that strange error «still waiting for root device» or the «No Entry Sign» for the bootloalder to make a handshake with the Kernel; file corruption making it impossible for Clover bootloader to pass the control to the Operating System (Kernel) to continue the boot process to its destination . the Login Screen . Desktop.
  • The only way you can run system file checker is to boot from Clover Boot Manager screen in the «Single User Mode» with a Boot flag (s) at Clover Boot Manager>Options.Boot Args:- -s -v ( to make it verbose)[ENTER] ESC> Clover Boot Manager Screen> Your Sierra System Disk >Enter . wait for . Shell command prompt to show up for you to type and execute the commands listed by Gigamaax.
  • Please Run Gigamaxx given two commands at the Shell Prompt:.
  • The first one instructs to «mount» the disk and permit to write
  • Thew second one instructs to run on the mounted disk fsck and if errors are found fix them without stopping and asking you to say «yes» or «no» to fix each and very bit of error!
  • Since it is hard disk of some size, it can take a while . hence :wait . wait wait.
  • Since he is expecting a corrupt disk and if repair is done, you will see «FILE SYSTEM WAS MODIFIED”.
  • At that time you type «exit» to get out and then reboot
  • Back in CBM >Options>Boot Args : your usual flags; but add v also to make it verbose to make it readable rather than the Apple logo that covers up problem.

If you have done the above and still facing the problem , the HDD has a bigger problem and you may need to look for another disk.

While considering that, you can try a CMOS Reset just in case the problem is from a corrupt CMOS feeding wrong instruction to Boot loader. That must be easy for you.

источник

[Solved] First hackintosh, “still waiting for root device” and prohibitory sign

sean101v

Hi, I’m trying to get my hackintosh working on my computer. I made a Sierra Hackintosh USB with UniBeast choosing “Legacy”, and “Inject ATI”.

My computer specs are as follows:

Intel Core 2 Duo E8400 3.00GHz
8GB DDR2 RAM
256GB SSD (completely empty)
AMD Radeon R7 240 GPU
PCI Wireless card (I checked, it works with OSX)
The computer itself is an HP Compaq DC7900 SFF

I boot the USB, choose Sierra in Clover, w/out verbose the loading line gets 2/3rds of the way through before prohibitory sign, with verbose the following screen appears:

It’s really hard to read and it’s all jumbled for some reason. I’m able to make out the last line as “still waiting for root device”

Flags I’ve tried:
-v
-x
USBBusFix=Yes
-s
rd=diskXsY
(disk and partition)

The following boot args were already added by default:
dart=0
nv_disable=1

Other things I’ve tried:
Adding this kext and modifying config.plst

Читайте также:  Установка бытового электросчетчика в квартире

Here is my list of Kext files:

BECAUSE THE MACHINE IM USING TO MAKE THE USB IS A 2017 MACBOOK PRO, THE LOWEST OS I CAN GET FROM THE MAC APP STORE FOR UNIBEAST IS SIERRA. I have an older MBP somewhere, I can use that if necessary.

All help appreciated, please note that I’m new so I apologize if there’s something I don’t understand.

P1LGRIM

Moderator

You should read and comply with the rules, in particular the one regarding profiles.

There is no requirement to host your images / files on third party sites — You may attach them to your posts here.

sean101v

You should read and comply with the rules, in particular the one regarding profiles.

There is no requirement to host your images / files on third party sites — You may attach them to your posts here.

I don’t understand what you mean. In my post I gave my computer specifications, and you can find them here:

My computer specs are as follows:

Intel Core 2 Duo E8400 3.00GHz
8GB DDR2 RAM
256GB SSD (completely empty)
AMD Radeon R7 240 GPU
PCI Wireless card (I checked, it works with OSX)
The computer itself is an HP Compaq DC7900 SFF

And I do not understand what you mean by «there is no requirement to host your images / files on third party sites. Are you saying that it’s not allowed to use third party sites to attach my images? If so, I can fix that.

P1LGRIM

Moderator

Use your Profile not your Signature.
Just three items — Motherboard (or prebuilt system), Processor (CPU) and Graphics.

sean101v

Use your Profile not your Signature.
Just three items — Motherboard (or prebuilt system), Processor (CPU) and Graphics.

P1LGRIM

Moderator

sean101v

P1LGRIM

Moderator

«Still waiting for root device».
When booting from USB means that there is a problem finding a valid System folder to start up from on your USB flash drive.
This is usually because the flash drive is in a USB3 port.
If this is the case move it to a USB2 port, if it is already in a USB2 port move it to another and try again.
Repeat until you have tried all USB ports.
Use a USB2 flash drive.
If it still doesn’t work you could try another flash drive.
Try connecting your USB flash drive using a USB2 hub.
You might also try enabling Legacy on your USB3 ports in your BIOS settings.
Set XHCI Handoff to Enabled in your BIOS settings.
Ensure that Fast Boot is not enabled in your BIOS settings.
macOS High Sierra 10.13.6 requires a new USB Port Limit patch.

With the DC7900 you must boot with -f UseKernelCache=No or you will lose access to your USB ports and network.

sean101v

«Still waiting for root device».
When booting from USB means that there is a problem finding a valid System folder to start up from on your USB flash drive.
This is usually because the flash drive is in a USB3 port.
If this is the case move it to a USB2 port, if it is already in a USB2 port move it to another and try again.
Repeat until you have tried all USB ports.
Use a USB2 flash drive.
If it still doesn’t work you could try another flash drive.
Try connecting your USB flash drive using a USB2 hub.
You might also try enabling Legacy on your USB3 ports in your BIOS settings.
Set XHCI Handoff to Enabled in your BIOS settings.
Ensure that Fast Boot is not enabled in your BIOS settings.
macOS High Sierra 10.13.6 requires a new USB Port Limit patch.

With the DC7900 you must boot with -f UseKernelCache=No or you will lose access to your USB ports and network.

Thank you for the several suggestions. I would love to try them but now I’m running into a new issue.

Now, the computer does not want to boot from the USB. I’m not sure why, as it was able to boot just a few minutes ago. I made no changes at all, and now when I select «boot from USB» all I get is a blinking cursor. This is the same USB that worked before and I haven’t made a single change, so I have no clue what happened. I tried different USB ports, making the USB again with UniBeast, and resetting my BIOS, but it’s still not working. I plugged it into another computer I had and Clover works with no problems.

источник