Manjaro Difference between revisions of "Kernel Fails to Load (pata acpi error)"

Difference between revisions of "Kernel Fails to Load (pata acpi error)"

From Manjaro
imported>Verityproductions
(Created page with "= Overview = {{tip|Parallel ATA ('''[http://en.wikipedia.org/wiki/Parallel_ATA PATA]''') is an interface standard to connect storage devices, and the Advanced Configuration a...")
 
(replace actual guid with a placeholder)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Overview =
<languages/>
__TOC__
<translate>
= Overview = <!--T:1-->


{{tip|Parallel ATA ('''[http://en.wikipedia.org/wiki/Parallel_ATA PATA]''') is an interface standard to connect storage devices, and the Advanced Configuration and Power Interface ('''[http://en.wikipedia.org/wiki/Acpi ACPI]''') is used for device configuration and power management.}}
<!--T:2-->
{{tip|'''Parallel ATA''' ('''[http://en.wikipedia.org/wiki/Parallel_ATA PATA]''') is an interface standard to connect storage devices, and the '''Advanced Configuration and Power Interface''' ('''[http://en.wikipedia.org/wiki/Acpi ACPI]''') is used for device configuration and power management.}}




This problem may affect particular particular computer systems using the '''[http://en.wikipedia.org/wiki/JMicron JMicron PATA Controller chipset]''', which is used to control and access storage devices, such as Solid State Drives ('''[http://en.wikipedia.org/wiki/Solid-state_drive SSD]'''). More specifically, it may be due to the '''PATA ACPI''' driver being loaded by the GRUB ('''GR'''and '''U'''nified '''B'''ootloader), which has consequently resulted in a conflict with the ''JMicron'' chipset. Should this indeed be the case, then an error message similar - or identical - to the example provided below should be displayed upon attempting to boot the affected kernel version(s):
<!--T:3-->
This problem may affect particular computer systems using the '''[http://en.wikipedia.org/wiki/JMicron JMicron PATA Controller chipset]''', which is used to control and access storage devices, such as Solid State Drives ('''[http://en.wikipedia.org/wiki/Solid-state_drive SSD]'''). More specifically, it may be due to the '''PATA ACPI driver''' being loaded by the GRUB ('''GR'''and '''U'''nified '''B'''ootloader), which has consequently resulted in a conflict with the ''JMicron'' chipset. Should this indeed be the case, then an error message similar - or identical - to the example provided below should be displayed upon attempting to boot the affected kernel version(s):


  ERROR: device 'UUID=......' not found. Skipping FSCK'
  <!--T:4-->
ERROR: device 'UUID=......' not found. Skipping FSCK'
  ERROR: Unable to find root device 'UUID=......'
  ERROR: Unable to find root device 'UUID=......'
  You are being dropped to the recovery shell
  You are being dropped to the recovery shell
  Type 'exit' to try and continue booting
  Type 'exit' to try and continue booting
  sh: can't access tty: job control turned off'
  sh: can't access tty: job control turned off'
   
  [...]
.....
  mount: can't find UUID='.....'
  mount: can't find UUID='.....'
  You are now being dropped into the emergency shell.
  You are now being dropped into the emergency shell.




<!--T:5-->
If so, then the solution is to simply stop the ''PATA ACPI'' driver from being loaded in the first place. This is a simple task, undertaken by amending a single line in the '''default grub''' file.
If so, then the solution is to simply stop the ''PATA ACPI'' driver from being loaded in the first place. This is a simple task, undertaken by amending a single line in the '''default grub''' file.




= Opening the Default GRUB File =  
= Opening the Default GRUB File = <!--T:6-->


The syntax of the command to open the LXDM configuration file is:
<!--T:7-->
{{warning|'''DO NOT edit the ''grub.cfg'' file'''. This is not the same as the ''grub'' file, which does not have an extension at the end of its name.}}
sudo [text editor] /etc/lxdm/lxdm.conf




<!--T:8-->
The syntax of the command to open the grub file is:
{{UserCmd|command=sudo [text editor] /etc/default/grub}}
<!--T:9-->
For example, if you wish to edit the file within the terminal using nano (a standard terminal-based text editor) then enter:
For example, if you wish to edit the file within the terminal using nano (a standard terminal-based text editor) then enter:
{{UserCmd|command=sudo nano /etc/default/grub}}
sudo nano /etc/default/grub




Otherwise - if you have installed the full version of Manjaro (i.e. not the NET-Edition) - you may find it easier to use the pre-installed ''gedit'' text editor instead. This will open the configuration file up as a document, making it easier to read and edit. To use ''gedit'' instead, enter:
<!--T:10-->
If you have installed the full version of Manjaro, not the NET-Edition, you may find it easier to use the pre-installed ''gedit'' text editor instead. This will open the file up as a document, making it easier to read and edit. To use ''gedit'' instead, enter:
sudo gedit /etc/default/grub
{{UserCmd|command=sudo gedit /etc/default/grub}}


= Editing the Default GRUB File = <!--T:11-->


= Editing the Default GRUB File =
<!--T:12-->
 
Once the ''default grub'' file has been opened, it will be necessary to amend the '''GRUB_CMDLINE_LINUX=""''' command, which is itself located near the top of the file. An example has been provided below, with the appropriate line '''<font color="green">highlighted in green</font>''' below for illustrative purposes:
Once the ''default grub'' file has been opened, it will be necessary to amend the '''GRUB_CMDLINE_LINUX=""''' command, which is itself located near the top of the file. An example has been provided below, with the appropriate line '''<font color="green">highlighted in green</font>''' below for illustrative purposes:


  GRUB_DEFAULT=saved
  <!--T:13-->
GRUB_DEFAULT=saved
  GRUB_TIMEOUT=5
  GRUB_TIMEOUT=5
  GRUB_DISTRIBUTOR="Manjaro"
  GRUB_DISTRIBUTOR="Manjaro"
  GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/4cbb5d28-6569-4225-a5a0-adf5f6c372b0"
  GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/<some-guid>"
  <font color="green">'''GRUB_CMDLINE_LINUX=""'''</font color>
  <font color="green">'''GRUB_CMDLINE_LINUX=""'''</font color>




<!--T:14-->
To prevent the ''PATA ACPI'' driver from being loaded, '''modprobe.blacklist=pata_acpi''' must be added in between the otherwise empty speech marks. An example of the necessary amendment has been provided below, which has again been '''<font color="green">highlighted in green</font>''' for illustrative purposes:
To prevent the ''PATA ACPI'' driver from being loaded, '''modprobe.blacklist=pata_acpi''' must be added in between the otherwise empty speech marks. An example of the necessary amendment has been provided below, which has again been '''<font color="green">highlighted in green</font>''' for illustrative purposes:


  GRUB_DEFAULT=saved
  <!--T:15-->
GRUB_DEFAULT=saved
  GRUB_TIMEOUT=5
  GRUB_TIMEOUT=5
  GRUB_DISTRIBUTOR="Manjaro"
  GRUB_DISTRIBUTOR="Manjaro"
  GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/4cbb5d28-6569-4225-a5a0-adf5f6c372b0"
  GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/<some-guid>"
  '''GRUB_CMDLINE_LINUX="<font color="green">modprobe.blacklist=pata_acpi</font color>"'''
  '''GRUB_CMDLINE_LINUX="<font color="green">modprobe.blacklist=pata_acpi</font color>"'''




<!--T:16-->
Once you have completed the amendments, save the change and close the file by:
Once you have completed the amendments, save the change and close the file by:


<!--T:17-->
* '''nano''': Press CTRL and 'x' to exit, 'y' to save, and <enter> to finish, or
* '''nano''': Press CTRL and 'x' to exit, 'y' to save, and <enter> to finish, or
* '''gedit''': Select the 'save' option and then close the window.
* '''gedit''': Select the 'save' option and then close the window.




<!--T:18-->
Now all that is necessary is to '''update the GRUB''' before rebooting.
Now all that is necessary is to '''update the GRUB''' before rebooting.




= Updating the GRUB =
= Updating the GRUB = <!--T:19-->


<!--T:20-->
To update the GRUB, ensure that the terminal is open, and enter the folliwing command:
To update the GRUB, ensure that the terminal is open, and enter the folliwing command:


  sudo update-grub
  <!--T:21-->
{{UserCmd|command=sudo update-grub}}




<!--T:22-->
Once complete, reboot your system for the change to take effect.
Once complete, reboot your system for the change to take effect.
</translate>
[[Category:Contents Page{{#translation:}}]]

Latest revision as of 09:52, 9 December 2022

Other languages:
English • ‎русский

Overview

Tip
Parallel ATA (PATA) is an interface standard to connect storage devices, and the Advanced Configuration and Power Interface (ACPI) is used for device configuration and power management.


This problem may affect particular computer systems using the JMicron PATA Controller chipset, which is used to control and access storage devices, such as Solid State Drives (SSD). More specifically, it may be due to the PATA ACPI driver being loaded by the GRUB (GRand Unified Bootloader), which has consequently resulted in a conflict with the JMicron chipset. Should this indeed be the case, then an error message similar - or identical - to the example provided below should be displayed upon attempting to boot the affected kernel version(s):

ERROR: device 'UUID=......' not found. Skipping FSCK'
ERROR: Unable to find root device 'UUID=......'
You are being dropped to the recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off'
[...]
mount: can't find UUID='.....'
You are now being dropped into the emergency shell.


If so, then the solution is to simply stop the PATA ACPI driver from being loaded in the first place. This is a simple task, undertaken by amending a single line in the default grub file.


Opening the Default GRUB File

Warning
DO NOT edit the grub.cfg file. This is not the same as the grub file, which does not have an extension at the end of its name.


The syntax of the command to open the grub file is:

user $ sudo [text editor] /etc/default/grub COPY TO CLIPBOARD



For example, if you wish to edit the file within the terminal using nano (a standard terminal-based text editor) then enter:

user $ sudo nano /etc/default/grub COPY TO CLIPBOARD



If you have installed the full version of Manjaro, not the NET-Edition, you may find it easier to use the pre-installed gedit text editor instead. This will open the file up as a document, making it easier to read and edit. To use gedit instead, enter:

user $ sudo gedit /etc/default/grub COPY TO CLIPBOARD


Editing the Default GRUB File

Once the default grub file has been opened, it will be necessary to amend the GRUB_CMDLINE_LINUX="" command, which is itself located near the top of the file. An example has been provided below, with the appropriate line highlighted in green below for illustrative purposes:

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/<some-guid>"
GRUB_CMDLINE_LINUX=""


To prevent the PATA ACPI driver from being loaded, modprobe.blacklist=pata_acpi must be added in between the otherwise empty speech marks. An example of the necessary amendment has been provided below, which has again been highlighted in green for illustrative purposes:

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="GRUB_CMDLINE_LINUX_DEFAULT= resume=/dev/disk/by-uuid/<some-guid>"
GRUB_CMDLINE_LINUX="modprobe.blacklist=pata_acpi"


Once you have completed the amendments, save the change and close the file by:

  • nano: Press CTRL and 'x' to exit, 'y' to save, and <enter> to finish, or
  • gedit: Select the 'save' option and then close the window.


Now all that is necessary is to update the GRUB before rebooting.


Updating the GRUB

To update the GRUB, ensure that the terminal is open, and enter the folliwing command:

user $ sudo update-grub COPY TO CLIPBOARD



Once complete, reboot your system for the change to take effect.

Cookies help us deliver our services. By using our services, you agree to our use of cookies.