Re: During rescue startup boot process halts with "cannot open access to console, the root account is locked"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 6, 2016 at 6:07 AM, Jobst Schmalenbach <jobst@xxxxxxxxxxxxxx> wrote:
> Fedora-Live-Workstation-x86_64-23-10.iso
> USB based DVD
> Lenovo Yoga
>
> Description of problem:
> Originally I tried to boot to rescue mode on a Lenovo Yoga that has Ubuntu installed. I wanted to start rescue mode, then wipe the ubuntu install by formatting the partitions (/ and boot using mkfs.ext4) and replace Ubuntu with Fedora 23.

You're best off letting the installer delete these partitions because
it'll do a proper teardown and wipe all the signatures for each layer.
Leaving these signatures around can cause problems later.

>
> So I inserted the Fedora 23 DVD, wait for the bios boot menu to appear, select the DVD drive with inserted Fedora 23 and boot to that. When the grub menu appears I select tab and change the kernel line to have "rescue" at the end, delete the "quiet" so I can see what is going on and add "vag=771".
>
> Just after the "Started D-Bus System Message Bus" it stops:
>
> "Cannot open access to console, the root account is locked. See sulogin(8) man page for more details.
>
> As this is "rescue mode" and the idea of rescue mode is to be able to access anything that is on the computer even with a messed up password it is tricky.

There is a Troubleshooting submenu, and an option Rescue a Fedora
installation. Pick that. And then when you get to the text menu, just
don't have it assemble whatever it finds, and you'll get to a shell
prompt instead. I have no idea what vag=771 means...



>
> How reproducible:
> I have tried this on three computers:
>  1: a beefy, selfmade workstation that has Fedora 22 installed on the local hard drive
>  2: a Dell XPS 13, that has Windows installed (but UEFI disabled)
>  3: Lenovo Yoga that has Ubuntu 16.04 installed (UEFI disabled)
> all of them have the same issue
>
> Additional info:
> It does not matter what setting UEFI boot is set to, I tried this with every possible setting in the BIOS that was given to me by the different manufacturers, I could not get pass the "root account is locked"

I would start by not including vag=771 as a boot parameter.

-- 
Chris Murphy
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux