Score:0

Linux console is not prompting for root p/w after detecting "RUN fsck MANUALLY" - how to proceed?

gb flag

Last night our datacenter host had issues filling up their storage (again!!!) and caused all our VMs to drop to r/o. After the admins allocated some more storage, a simple reboot on most of our VMs cleared their filesystem errors with the usual automatic fsck, but a few required it to run manually, halting the boot after the message "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY". After that, all the VMs except one presented the prompt: "Give root password for maintenance (or type Control-D to continue)" and I could do so, and did, and it all worked great.

My issue is that one VM asks for the manual fsck, but never "finishes" and prompts for the root password! It just sits there. Rebooting merely runs the same fsck -f, tells me to run it manually, and doesn't fix anything. I imagine I'll have to boot with some rescue disk, but figured I'd ask if anyone knew of a control character to break out of this, or hit one of the other consoles, or if anyone has seen this before and knows why it's happening.

VMs are all RHEL/CentOS of the 5 and 7 variety - I believe this failing one is actually CentOS7.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.