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)
Tnx
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.
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 .....
On 08/25/14 06:28, antonio 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 .....
fsck dev/mapper/fedora
should be sufficient to see if there are error. Others may suggest you run "fsck -y dev/mapper/fedora" to have it try and fix problems automatically.
Disks do die early from time to time.
Ed Greshko ha scritto / said the following il giorno/on 25/08/2014 00:53:
On 08/25/14 06:28, antonio 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 .....
fsck dev/mapper/fedora
should be sufficient to see if there are error. Others may suggest you run "fsck -y dev/mapper/fedora" to have it try and fix problems automatically.
Disks do die early from time to time.
recovered using a Live Fedora and run a fsck on /dev/sda. Run a smartctl test with no errors. Any idea what could have caused it??
Tnx to all
On 08/25/14 12:59, antonio wrote:
recovered using a Live Fedora and run a fsck on /dev/sda. Run a smartctl test with no errors. Any idea what could have caused it??
Good..... Possible caused by improper power down....
I would also run...
smartctl --all /dev/sda | grep Real
To see if any badspots have been reallocated.
Ed Greshko ha scritto / said the following il giorno/on 25/08/2014 07:06:
On 08/25/14 12:59, antonio wrote:
recovered using a Live Fedora and run a fsck on /dev/sda. Run a smartctl test with no errors. Any idea what could have caused it??
Good..... Possible caused by improper power down....
I would also run...
smartctl --all /dev/sda | grep Real
To see if any badspots have been reallocated.
smartctl --all /dev/sda | grep Real 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
can you explain???
On 08/25/14 13:13, antonio montagnani wrote:
smartctl --all /dev/sda | grep Real 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
Yes, the 0 at the end of each line is good. :-)
http://www.dlaube.com/2010/04/how-to-determine-if-a-sata-drive-is-failing/
Is one source that can be found by doing just a bit of googling.
Ed Greshko ha scritto / said the following il giorno/on 25/08/2014 08:57:
On 08/25/14 13:13, antonio montagnani wrote:
smartctl --all /dev/sda | grep Real 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
Yes, the 0 at the end of each line is good. :-)
http://www.dlaube.com/2010/04/how-to-determine-if-a-sata-drive-is-failing/
Is one source that can be found by doing just a bit of googling.
tnx for the link: and tnx for the help!!! I have learnt more that I could have expected from this inconvenient
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@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@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
On 8-24-14 16:05:05 Tod Merley wrote:
using such commands as:
tail dmesg #prints the last ten lines of dmesg
Not here:
$ tail dmesg tail: cannot open ‘dmesg’ for reading: No such file or directory $
less dmesg #prints several lines of dmesg with response to up/down arrow to see the whole file - q to end
$ less dmesg dmesg: No such file or directory $
cat dmesg #prints the whole dmesg file to the screen all at once
So stop this silliness. Read the manual page for dmesg(1). And try running commands you post before posting them.
NAME dmesg - print or control the kernel ring buffer
The dmesg command writes to stdout.
Allegedly, on or about 24 August 2014, Tod Merley sent several major syntax errors:
tail dmesg #prints the last ten lines of dmesg
You mean:
dmesg|tail
You have to pipe the output of dmesg through the tail command, to do what you want to do.
less dmesg #prints several lines of dmesg with response to up/down arrow to see the whole file - q to end
Likewise, you really mean:
dmesg|less
To pipe the output of the dmesg command through the less command, to allow paging through it.
cat dmesg #prints the whole dmesg file to the screen all at once
Also, wrong, and another completely unnecessary use of a cat. Just use the dmesg command, by itself, and you'll see the whole output dumped to screen.
Thanks for the reminder to delete my original message.
But did not include in the message about the exact things you mention:
"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. "
Which was part of the message you mention.
thanks - and take care
On Mon, Aug 25, 2014 at 9:46 AM, Tim ignored_mailbox@yahoo.com.au wrote:
Allegedly, on or about 24 August 2014, Tod Merley sent several major syntax errors:
tail dmesg #prints the last ten lines of dmesg
You mean:
dmesg|tail
You have to pipe the output of dmesg through the tail command, to do what you want to do.
less dmesg #prints several lines of dmesg with response to up/down arrow to see the whole file - q to end
Likewise, you really mean:
dmesg|less
To pipe the output of the dmesg command through the less command, to allow paging through it.
cat dmesg #prints the whole dmesg file to the screen all at once
Also, wrong, and another completely unnecessary use of a cat. Just use the dmesg command, by itself, and you'll see the whole output dumped to screen.
-- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists.
George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments.
ZNQR LBH YBBX
-- users mailing list users@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
On Mon, Aug 25, 2014 at 00:10:09 +0200, antonio montagnani antonio.montagnani@alice.it 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...
Was there a kernel update betwen reboots? If so, try booting the previous kernel.
So the following might well prove themselves useful to find the source of a problem which resulted in a resucue mode:
$ journalctl | grep fail
$ journalctl | grep error
$ journalctl | grep disk
$ dmesg | tail -n 30
$ dmesg | less
of course the outputs of the fail, error, disk lines above as well as journalctl and dmesg alone can be redirected to a text file and observed with a text editor with search facilities.
e.g. $ journalctl | grep fail > journalctlFail.txt
On Sun, Aug 24, 2014 at 3:10 PM, antonio montagnani < antonio.montagnani@alice.it> 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)
Tnx
Antonio M Skype: amontag52
Linux Fedora F20 (Heisenbug) on Fujitsu Lifebook A512
http://lugsaronno.altervista.org http://www.campingmonterosa.com
-- users mailing list users@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
-
Antonio M -
antonio montagnani -
Bruno Wolff III -
Ed Greshko -
Garry Williams -
Tim -
Tod Merley