System starts in emergency mode...how do I recover ?? (as a newbie)

[Tod Merley]

If in a terminal you type "man fsck" you get a simple manual for the fsck
command. "fsck tutorial" at the Google search prompt should yield good info
soon.

 If you open a terminal and do a "cd /var/log" and then an "ls -l" you will
see the system log files.

 A good place to poke around for hints to what is wrong.

 Often people find hints looking at:

 dmesg

 syslog

 Xorg.0.log

 using such commands as:

 tail dmesg #prints the last ten lines of dmesg

 less dmesg #prints several lines of dmesg with response to up/down arrow
to see the whole file - q to end

 cat dmesg #prints the whole dmesg file to the screen all at once

 In your situation I would tend to boot in to the box with a live CD - grab
what was in my Desktop, Documents, Downloads(if not too large), Pictures
directories (under /home/<yourUserName> - onto a flash drive or external
USB drive for example) and then re-load Linux fresh. If you have a disk
failing perhaps time to consider getting and using an SSD (they are
wonderfully fast).

 Also you might look into using Clonezilla to make bare metal backups for
yourself. Saved my bottom many times working with a new SSD (many years
ago) which had a bad habit of loosing it's directory structure about every
6 weeks to three months - apparently a video vs disk hardware bus conflict.
Went away with a bios upgrade.


On Sun, Aug 24, 2014 at 3:28 PM, antonio <antonio.montagnani at gmail.com>
wrote:

> Ed Greshko ha scritto / said the following    il giorno/on 25/08/2014
> 00:22:
>
>  On 08/25/14 06:10, antonio montagnani wrote:
>>
>>> Suddenly my laptop when rebooted doesn't start in the usual way After
>>> six months of hard work) but it stops when bootib with this message
>>> drm:cpt-serr_int_handler ERROR PCH transcoder a FIFO underrun
>>> and the appears some lines with request for password for maintenance
>>> mode or CTRL-D option...
>>>
>>> If I open journalctl -xb I see some errors in particular saying that
>>> fsck failed with error code 4 on dev/mapper/fedora and suggestint to use
>>> fsck.
>>>
>>> How do I revover from this situation?? (I am writing from this machine
>>> started with CTRL-D option)
>>>
>>
>> Did you then run fsck manually?  Error code 4 means ...  "Filesystem
>> errors left uncorrected".  Sounds like a disk may be dying.
>>
>> The PCH transcoder error, on googling, seems to be related to Intel
>> graphics and not a fatal error.
>>
>>
> how do I run fsck manually?? surprised to hear that a disk may be dying as
> the system is six months old .....
>
>
> --
> Antonio M
> Skype: amontag52
>
> Linux Fedora F20 (Heisenbug)
> on Fujitsu Lifebook A512
>
> http://lugsaronno.altervista.org
> http://www.campingmonterosa.com
>
>
>
>
> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140824/caa86369/attachment.html>