If this were my box I think I would do the following:
If possible take a “snapshot” of your working directories by booting
into the box from a live CD or flashdrive and copying the user data (e.g.
Desktop, Documents, Pictures, etc...) to a separate drive to preserve them.
From the separate drive check the disk performance and error rate.
Replace the disk if you find it defective.
Install F21 fresh and keep a secure record of the password.
You might do well to expand upon #2. Perhaps it is time to open the box up,
blow the dust out, check the connections, and replace the CMOS battery as
those silly batteries can cause a bunch of crazy problems before you find
them. As well you might run some hardware testing software to make sure
everything in the box is working well.
.. just some thoughts ...
On Mon, Nov 23, 2015 at 4:03 AM, Frank White <mediomen27(a)gmail.com> wrote:
I tried with rd.break or init=/bin/sh but I failed with both.
rd.break boot and I have a shell but it miss the passwd command and touch.
I tried with /sysroot/bin/passwd but it lack some library.
and I tried with /sysroot/bin/touch /.autorelabel and it worked.
anyway the pc does not want to boot.
it stop when it begin to start some service like "volatile and temp
files creation" or something like that. And other service like avahi..
login... ntp.. and firewalld.
it looks there are some problems with dbus...
2015-11-03 17:06 GMT+00:00 Erick Ocrospoma <zipper1790(a)gmail.com>:
> On 3 November 2015 at 11:46, Frank White <mediomen27(a)gmail.com> wrote:
>> I am a new subscriber but an old user, especially on linux.
>> I have some problem to boot my box because I changed some files by a
>> I lost my root password so tried some old method to change it. I tried
>> to boot in single mode but it doesn't worked. After that I change the
>> passwd file removing the x character ... but this has broken my box.
> Which version of Fedora are you using ?
> I suppose single command is not working because Fedora is using systemd.
> to set 'rd.break' instead of single.
> Follow this:
> Follow the steps, specially autorelabel part, if your Fedora box has
> enabled this step is necessary.
>> I have rid of the following errors on the log:
>> Nov 3 17:40:06 localhost dbus-daemon: Could not get password database
>> information for UID of current process: User "???" unknown or no
>> memory to allocate password entry
>> Nov 3 17:40:06 localhost dbus-daemon: Unknown username "root" in
>> message bus configuration file
>> Anyone know how to fix it ?
>> Oh the last thing, my bot does not boot property, I mean it stop at
>> Network manager startup and it does not give me the login prompt on
>> gdm or console.
>> Thank you.
>> users mailing list
>> To unsubscribe or change subscription options:
>> 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
> ~ Happy install !
> IRC : zerick
> Blog : http://zerick.me
> About : http://about.me/zerick
> Linux User ID : 549567
> users mailing list
> To unsubscribe or change subscription options:
> 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
users mailing list
To unsubscribe or change subscription options:
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Have a question? Ask away: http://ask.fedoraproject.org