computer boot (some times) in emergency mode.

[Angelo Moreschini]

Hi,

my computer often (not all the time) has problem at booting ...

When it happen, it boot to emergency mode...

(after I install new updates, then this problem occurs regularly)

The message that I get, when the problem come, are (approximately):

========================
Welcome to emergency mode! after logging in , type "journalctl -xb" to view
system log .......

SError: {RecovRecovCom PHYRdyChg CommWake 10B8B DevExch }

failed commend : READ DMA

.......

exception Emask 0x10 SAct 0x0 Serr 0x40d0002 action 0x0 frozen

SError: {RecovCom PHYRdyCh CommWake 10808 DevExch}

status: {DRY}

exception Emask 0x10 SAct 0x0 Serr 0x40d0002 action 0x0 frozen

...........

status {Busy}

.............

failed command : READ DMA

....

Status {DRY}

========================

In this link

http://ubuntuforums.org/archive/index.php/t-1034762.html

I read that this problem happen frequently; and it is not sure if is a HD
problem or a SW problem...

Someone suggest to disable the ports of all bus not SATA in the bios...

In this other link:

http://ubuntuforums.org/showthread.php?t=1034762

someone said that, on Ubuntu, he was able to solve the problem changing
options in the file /etc/modprobe.d/options

= = = = =
It's Kernel bug on ata acpi
Put "options libata noacpi=1" on /etc/modprobe.d/options

= = = = =

In my case surly the problem  is connected with the HD; this because,
trying to change HD, the problem disappeared only re-plugging the caves of
the HD.

- - - - - - - - -

I would like have some suggestion about this problem

thank you

regard

Angelo

[Chris Murphy]

On Wed, Feb 25, 2015 at 1:53 AM, Angelo Moreschini <
[e-mail]> wrote:
> Hi,
>
> my computer often (not all the time) has problem at booting ...
>
> When it happen, it boot to emergency mode...
>
> (after I install new updates, then this problem occurs regularly)
>
> The message that I get, when the problem come, are (approximately):
>
> ========================
> Welcome to emergency mode! after logging in , type "journalctl -xb" to
> view system log .......
>
> SError: {RecovRecovCom PHYRdyChg CommWake 10B8B DevExch }
>
> failed commend : READ DMA

Please don't trim the messages to tidy them, include the entire thing, or
post the rdsosreport.txt if one was generated.

Statistically speaking, the errors you post are probably due to a failed
read on a critical sector that the system simply can't proceed without
reading, so it waits for the drive to recover, and hits the kernel SCSI
command timer limit which is 30 seconds.

If that's true, you might be able to fix the problem by booting with
parameter rd.break=cmdline which gets you to a command line before anything
is mounted (not even read only). And then do:
# echo 120 > /sys/block/sda/device/timeout

This will change the command timer, allowing the drive to do a long
recovery and possibly enabling the bad sector to be read. I would do an
e2fsck -f (assuming it's an ext fs). If it's a bad sector, and if file
system metadata is on it, there's a possibility it can be fixed. Any writes
to this bad sector will solve the problem, either by refreshing the
existing sector's data or by remapping it if it's persistently failing
writes too. You'll see all of this in dmesg.

If there are no errors in dmesg or fsck, then it's not fs metadata that's
affected, it's data (binaries most likely). And that's slightly more
difficult to fix. But if you just use
# exit
 that will continue with the startup process from the break. And the
command timer change might allow the drive to recover this data. If not, at
the very least, again if it's a bad sector, you'll get something in dmesg
that's explicitly a read error and will have an LBA associated with it. Now
you can find out what file's data is on that LBA using debugfs and
reinstall that binary (hopefully) which causes the problem to be fixed also.

[Angelo Moreschini]

Hi Chris,

I would be more inclined to to think about a electrical problem, since the
only rep-plugging of the connectors of the HD solves the problem ..
In any case I think the control of the HD  is appropriate, so I would ask
you in detail how to do this operation:

This is what I get with the command blkid (the output concern only the
partition where is the OS Fedora):

/dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
PARTUUID="0008635c-01"
/dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K" TYPE="LVM2_member"
PARTUUID="0008635c-02"
/dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
TYPE="ext4"
/dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
TYPE="swap"

so I should do :
e2fsck -f /dev/sdc1
and after
e2fsck -f /dev/sdc2

This is enough ?

After I did I'll ask you more..

I am sorry about the message... I would include a photo of the output but
the administrator of the mail list didn't do it because the message had a
size too much big..

thank you
Angelo

[Chris Murphy]

On Thu, Feb 26, 2015 at 5:22 AM, Angelo Moreschini
 wrote:
> Hi Chris,
>
> I would be more inclined to to think about a electrical problem, since the
> only rep-plugging of the connectors of the HD solves the problem ..

Cable connectors are often a source of problems.
> This is what I get with the command blkid (the output concern only the
> partition where is the OS Fedora):
>
> /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> PARTUUID="0008635c-01"
> /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K" TYPE="LVM2_member"
> PARTUUID="0008635c-02"
> /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> TYPE="ext4"
> /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> TYPE="swap"
>
> so I should do :
> e2fsck -f /dev/sdc1
> and after
> e2fsck -f /dev/sdc2

Yes for sdc1, but not for sdc2 which is an LVM PV. You need to do
e2fsck -f /dev/mapper/fedora/root

Thing is, at the rd break, it might not be active. Check with blkid.
If not, then
vgchange -ay

[Angelo Moreschini]

Hi

I tried with e2fsck -f /dev/sdc1
but I got the message:

WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.

Of curse I didn't continue...

How I have to do this test ?
Have I to boot the computer using some utility that didn't need the hard
disk ?

On Thu, Feb 26, 2015 at 6:35 PM, Chris Murphy 
wrote:
> On Thu, Feb 26, 2015 at 5:22 AM, Angelo Moreschini
>  wrote:
> > Hi Chris,
> >
> > I would be more inclined to to think about a electrical problem, since
>
> the
> > only rep-plugging of the connectors of the HD solves the problem ..
>
> Cable connectors are often a source of problems.
> > This is what I get with the command blkid (the output concern only the
> > partition where is the OS Fedora):
> >
> > /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> > PARTUUID="0008635c-01"
> > /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K"
>
> TYPE="LVM2_member"
> > PARTUUID="0008635c-02"
> > /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> > TYPE="ext4"
> > /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> > TYPE="swap"
> >
> > so I should do :
> > e2fsck -f /dev/sdc1
> > and after
> > e2fsck -f /dev/sdc2
>
> Yes for sdc1, but not for sdc2 which is an LVM PV. You need to do
> e2fsck -f /dev/mapper/fedora/root
>
> Thing is, at the rd break, it might not be active. Check with blkid.
> If not, then
> vgchange -ay
>
> --
> Chris Murphy
> --
> users mailing list
> [e-mail]
> 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

[Chris Murphy]

On Feb 28, 2015 3:37 AM, "Angelo Moreschini" 
wrote:
> Hi
>
> I tried with e2fsck -f /dev/sdc1
> but I got the message:

Buried in my long first reply:
"booting with parameter rd.break=cmdline"

Chances are it's not sdc1 damaged. It's lv-root.
> WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
> cause ***SEVERE*** filesystem damage.
>
> Of curse I didn't continue...
>
> How I have to do this test ?
> Have I to boot the computer using some utility that didn't need the hard

disk ?
> On Thu, Feb 26, 2015 at 6:35 PM, Chris Murphy

wrote:
> > On Thu, Feb 26, 2015 at 5:22 AM, Angelo Moreschini
> >  wrote:
> > > Hi Chris,
> > >
> > > I would be more inclined to to think about a electrical problem, since

the
> > > only rep-plugging of the connectors of the HD solves the problem ..
> >
> > Cable connectors are often a source of problems.
> > > This is what I get with the command blkid (the output concern only the
> > > partition where is the OS Fedora):
> > >
> > > /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> > > PARTUUID="0008635c-01"
> > > /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K"

TYPE="LVM2_member"
> > > PARTUUID="0008635c-02"
> > > /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> > > TYPE="ext4"
> > > /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> > > TYPE="swap"
> > >
> > > so I should do :
> > > e2fsck -f /dev/sdc1
> > > and after
> > > e2fsck -f /dev/sdc2
> >
> > Yes for sdc1, but not for sdc2 which is an LVM PV. You need to do
> > e2fsck -f /dev/mapper/fedora/root
> >
> > Thing is, at the rd break, it might not be active. Check with blkid.
> > If not, then
> > vgchange -ay
> >
> > --
> > Chris Murphy
> > --
> > users mailing list
> > [e-mail]
> > 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
>
> --
> users mailing list
> [e-mail]
> 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

[Chris Murphy]

On Sat, Feb 28, 2015 at 4:12 AM, Chris Murphy  wrote:
> On Feb 28, 2015 3:37 AM, "Angelo Moreschini" 
> wrote:
> > Hi
> >
> > I tried with e2fsck -f /dev/sdc1
> > but I got the message:
>
> Buried in my long first reply:
> "booting with parameter rd.break=cmdline"
>
> Chances are it's not sdc1 damaged. It's lv-root.
> > WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
> > cause ***SEVERE*** filesystem damage.
> >
> > Of curse I didn't continue...
> >
> > How I have to do this test ?
> > Have I to boot the computer using some utility that didn't need the hard
> > disk ?
> >
> > On Thu, Feb 26, 2015 at 6:35 PM, Chris Murphy 
> > wrote:
> > > On Thu, Feb 26, 2015 at 5:22 AM, Angelo Moreschini
> > >  wrote:
> > > > Hi Chris,
> > > >
> > > > I would be more inclined to to think about a electrical problem, since
> > > > the
> > > > only rep-plugging of the connectors of the HD solves the problem ..
> > >
> > > Cable connectors are often a source of problems.
> > > > This is what I get with the command blkid (the output concern only the
> > > > partition where is the OS Fedora):
> > > >
> > > > /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> > > > PARTUUID="0008635c-01"
> > > > /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K"
> > > > TYPE="LVM2_member"
> > > > PARTUUID="0008635c-02"
> > > > /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> > > > TYPE="ext4"
> > > > /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> > > > TYPE="swap"
> > > >
> > > > so I should do :
> > > > e2fsck -f /dev/sdc1
> > > > and after
> > > > e2fsck -f /dev/sdc2
> > >
> > > Yes for sdc1, but not for sdc2 which is an LVM PV. You need to do
> > > e2fsck -f /dev/mapper/fedora/root

So I just had to do this, and LVM isn't activate this early in the
boot process using cmdline. Adding this to the end of the GRUB boot
entry linux line (after rhgb quiet) works:
rd.break=pre-mount
And then F10 or cntrl-x to boot. And then at the prompt:
e2fsck -f /dev/mapper/VG-root   ##assumes ext file system

[Doug]

On 02/28/2015 05:36 AM, Angelo Moreschini wrote:
> Hi
>
> I tried with e2fsck -f /dev/sdc1
> but I got the message:
>
> WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
> cause ***SEVERE*** filesystem damage.
>
> Of curse I didn't continue...
>
> How I have to do this test ?
> Have I to boot the computer using some utility that didn't need the hard disk ?

Before you try to run e2fsck on /dev/sdc1, simply give the command:

umount /dev/sdc1

This will unmount the partition, and then you can do a file check without
destroying it. Note that there is only ONE "n" in the umount command!

--doug

[Robin Laing]

On 2015-02-26 05:22, Angelo Moreschini wrote:
> Hi Chris,
>
> I would be more inclined to to think about a electrical problem, since the
> only rep-plugging of the connectors of the HD solves the problem ..
> In any case I think the control of the HD  is appropriate, so I would ask
> you in detail how to do this operation:
>
> This is what I get with the command blkid (the output concern only the
> partition where is the OS Fedora):
>
> /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> PARTUUID="0008635c-01"
> /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K" TYPE="LVM2_member"
> PARTUUID="0008635c-02"
> /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> TYPE="ext4"
> /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> TYPE="swap"
>
> so I should do :
> e2fsck -f /dev/sdc1
> and after
> e2fsck -f /dev/sdc2
>
> This is enough ?
>
> After I did I'll ask you more..
>
> I am sorry about the message... I would include a photo of the output but
> the administrator of the mail list didn't do it because the message had a
> size too much big..
>
> thank you
> Angelo

I had some strange issues on a computer and it turned out to be the 
power supply.  A known issue with the 5V rail on the supply not 
regulating properly.  Especially under load.  I have a stack of DVD's of 
backups of data that are almost coasters due to this issue.

If you can, setup up lm_sensors and monitor your system voltages.

Also check the drive for issues as it could be failing.

[Angelo Moreschini]

Hi

I had serious problems.

Because I didn't  check immediately the hard disk with the bad sector,  the
time of booting stretched at every subsequent  opening; and, at last, I was
not able anymore  to start Fedora  ..

So I had to make the restore of my installation, using a clone that I took
before, by Clonezilla.. (luckily).

Now I  want only to check why a HD, 'Western Digital with only a few months
of life, has gone faulty ..

I know there are programs, made by the manufacturers of HD, that allow you
to make these types of control

On Mon, Mar 2, 2015 at 5:54 AM, Robin Laing  wrote:
> On 2015-02-26 05:22, Angelo Moreschini wrote:
> > Hi Chris,
> >
> > I would be more inclined to to think about a electrical problem, since the
> > only rep-plugging of the connectors of the HD solves the problem ..
> > In any case I think the control of the HD  is appropriate, so I would ask
> > you in detail how to do this operation:
> >
> > This is what I get with the command blkid (the output concern only the
> > partition where is the OS Fedora):
> >
> > /dev/sdc1: UUID="4b1e5e09-306b-4c17-8c2f-653b32e1b956" TYPE="ext4"
> > PARTUUID="0008635c-01"
> > /dev/sdc2: UUID="Vtbdeq-eq6H-sbMY-Mpme-UyFk-jx77-I5Z20K"
> > TYPE="LVM2_member"
> > PARTUUID="0008635c-02"
> > /dev/mapper/fedora-root: UUID="2d224b16-d37f-4eee-820a-dfcd5929e05e"
> > TYPE="ext4"
> > /dev/mapper/fedora-swap: UUID="54d55595-8c35-4e84-8566-89d8b6f340e8"
> > TYPE="swap"
> >
> > so I should do :
> > e2fsck -f /dev/sdc1
> > and after
> > e2fsck -f /dev/sdc2
> >
> > This is enough ?
> >
> > After I did I'll ask you more..
> >
> > I am sorry about the message... I would include a photo of the output but
> > the administrator of the mail list didn't do it because the message had a
> > size too much big..
> >
> > thank you
> > Angelo
>
> I had some strange issues on a computer and it turned out to be the power
> supply.  A known issue with the 5V rail on the supply not regulating
> properly.  Especially under load.  I have a stack of DVD's of backups of
> data that are almost coasters due to this issue.
>
> If you can, setup up lm_sensors and monitor your system voltages.
>
> Also check the drive for issues as it could be failing.
>
> --
> users mailing list
> [e-mail]
> 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

[Patrick O'Callaghan]

On Wed, 2015-03-04 at 15:56 +0200, Angelo Moreschini wrote:
> Now I  want only to check why a HD, 'Western Digital with only a few
> months
> of life, has gone faulty ..
>
> I know there are programs, made by the manufacturers of HD, that allow
> you
> to make these types of control

man smartd

poc