centos_not_booting
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
centos_not_booting [2021/04/21 17:49] – walkeradmin | centos_not_booting [2023/03/09 22:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 5: | Line 5: | ||
**<color # | **<color # | ||
---- | ---- | ||
+ | ==== Introduction ==== | ||
\\ | \\ | ||
This has been listed under IPHE, not because it is specific to IPHE (because it is not) but because it was on an IPHE system that I first observed this phenomenon. | This has been listed under IPHE, not because it is specific to IPHE (because it is not) but because it was on an IPHE system that I first observed this phenomenon. | ||
Line 10: | Line 11: | ||
\\ | \\ | ||
After a server was rebooted (and I cannot say whether this was a reboot from a command line, a server crash, someone pulling out the power cables, a power cut etc) the end result is that the server will not fully boot up, instead we end up in <color # | After a server was rebooted (and I cannot say whether this was a reboot from a command line, a server crash, someone pulling out the power cables, a power cut etc) the end result is that the server will not fully boot up, instead we end up in <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | When logging in to the server from command KVM or from BMC (or whatever remote management is present) we can see the following tell tale screen: | ||
+ | \\ | ||
+ | \\ | ||
+ | {{ : | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | ==== The Cause ==== | ||
+ | To move past this page you have to enter <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | On my system this file was 30,888 lines long, so hundreds of pages long. After searching through it though I did find this section: | ||
+ | \\ | ||
+ | < | ||
+ | -- The start-up result is done. | ||
+ | Apr 20 17:04:10 k8master1 kernel: power_meter ACPI000D: | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | Apr 20 17:04:10 k8master1 systemd[1]: Started File System Check on / | ||
+ | -- Subject: Unit systemd-fsck@dev-mapper-vg_main\x2dlv_var.service has finished start-up | ||
+ | </ | ||
+ | \\ | ||
+ | The important parts are: | ||
+ | \\ | ||
+ | \\ | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | \\ | ||
+ | \\ | ||
+ | The partition <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | The other important part is: | ||
+ | \\ | ||
+ | \\ | ||
+ | Apr 20 17:04:10 k8master1 systemd-fsck[19721]: | ||
+ | \\ | ||
+ | \\ | ||
+ | So <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Each time the server boots, this discrepancy causes the server to go in to <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== The Remedy ==== | ||
+ | \\ | ||
+ | We need to tell the system to not perform the <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Open the file in a text editor by using <color # | ||
+ | \\ | ||
+ | < | ||
+ | # | ||
+ | # /etc/fstab | ||
+ | # Created by anaconda on Thu Nov 5 18:45:24 2020 | ||
+ | # | ||
+ | # Accessible filesystems, | ||
+ | # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info | ||
+ | # | ||
+ | / | ||
+ | UUID=ce253ff9-86ee-480b-87b3-7efa803bedda /boot | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | </ | ||
+ | Above we see the contents of the <color # | ||
+ | \\ | ||
+ | \\ | ||
+ | Each entry in the fstab file has six fields: | ||
+ | < | ||
+ | 1 2 | ||
+ | |||
+ | / | ||
+ | </ | ||
+ | \\ | ||
+ | It is the last number we want to change, and we will change this to a zero, this will mark this partition (and only this partition) to ignore fsck at boot. | ||
+ | \\ | ||
+ | < | ||
+ | So we will change: | ||
+ | |||
+ | / | ||
+ | |||
+ | to | ||
+ | |||
+ | / | ||
+ | </ | ||
+ | Save this file, and now you should be able to do a test reboot, and the system should boot normally to user login page rather than emergency mode. | ||
+ | \\ | ||
+ | \\ | ||
+ | \\ | ||
+ |
centos_not_booting.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1