search for: sact

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { U...

Hi, My xen guest stopped booting suddenly and giving me the below error message. Any idea what is going wrong here? DOM 0 boots OK though. ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 ata5.00: irq_stat 0x40000008 ata5.00: failed command: READ FPDMA QUEUED ata5.00: cmd 60/00:00:cd:ee:36/02:00:09:00:00/40 tag 0 ncq 262144 in res 51/40:72:5b:f0:36/d9:00:09:00:00/40 Emask 0x409 (media error) <F> ata5.00: status: { DRDY ERR } ata5.00: error: { U...

...ay to prevent them? My configuration: - 2 Hitachi SATA 120 GB Harddisks - Intel P4 3GHz - Tyan Tomcat i875p motherboard - 1 GB ECC RAM - 2 Intel Gb NICs - 1 Intel 10/100 NIC Error message follows: --------------------------------------------------------------------- ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0...

...TA 120 GB Harddisks (first generation, no NCQ) - Intel P4 3GHz - Tyan Tomcat i875p motherboard, Intel ICH5 disk controler - 1 GB ECC RAM - 2 Intel Gb NICs - 1 Intel 10/100 NIC Error message follows: --------------------------------------------------------------------- ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0...

Hi, I have some errors in dmesg: [ 542.255788] ata1.00: exception Emask 0x0 SAct 0xffffff SErr 0x0 action 0x0 [ 542.255797] ata1.00: irq_stat 0x40000008 [ 542.255805] ata1.00: failed command: READ FPDMA QUEUED [ 542.255821] ata1.00: cmd 60/00:00:1a:b7:7a/04:00:1d:00:00/40 tag 0 ncq 524288 in [ 542.255824] res 41/40:00:a0:b7:7a/00:00:1d:00:00/40 Emask 0x409 (media e...

...R09: 0000000000000006 > [ 26.755144] R10: 000000000089fc18 R11: 0000000000000246 R12: 00007ffef0289ea8 > [ 26.755853] R13: 000000000043a5f0 R14: 0000000000000000 R15: 0000000000000000 > [ 26.756560] ---[ end trace 23cc3e9021358587 ]--- > [ 26.778034] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 > [ 26.778690] ata2.00: failed command: READ DMA > [ 26.779131] ata2.00: cmd c8/00:e8:92:ad:00/00:00:00:00:00/e0 tag 0 dma 118784 in > [ 26.779131] res 50/00:00:0a:80:03/00:00:00:00:00/a0 Emask 0x40 (internal error) > [ 26.780691] ata2.00: status...

I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of my Ubuntu machines without success. It keeps giving errors like this: [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 frozen [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED [ 9.115556] ata9.00: cmd 60/04:00: d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in [ 9.115557] res 40/00:18:d3:82:85/00:00:1f:00:00/40 Emask 0x4 (timeout) [ 9.115560] ata9.00: status: { DRDY...

...ght after booting, when harddisks plays smoothly. the I/O errors apear only after few hours-days. Is it a known problem? (Already two posts regarding this)? Any solution or at least a way to check it? (I'm using CentOS5 with the latest updates) =============== ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 0x51 err 0x4 (device error) ata1: EH complete ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0...

...SCSI error decoding tool to tell normal people what cmd and res are about.) [ 157.732885] device label srv devid 4 transid 11292 /dev/sdf [ 157.733201] btrfs: disk space caching is enabled [ 172.936515] device label srv devid 4 transid 11292 /dev/sdf [44106.091461] ata4.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [44106.091470] ata4.01: BMDMA stat 0x64 [44106.091478] ata4.01: failed command: READ DMA EXT [44106.091492] ata4.01: cmd 25/00:08:a0:ca:72/00:00:4f:00:00/f0 tag 0 dma 4096 in [44106.091495] res 51/40:00:a3:ca:72/40:00:4f:00:00/f0 Emask 0x9 (media error) [44106.09150...

...been seeing disk errors in the syslog every seven days. Until today it always happens Sunday morning at 8:13 AM, plus or minus a minute or two. Yesterday it happened at 1:13 AM. Here are the pertinent log entries for the latest occurrence: Jan 6 01:12:29 g2 kernel: ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jan 6 01:12:29 g2 kernel: ata9.00: BMDMA stat 0x64 Jan 6 01:12:29 g2 kernel: ata9.00: failed command: READ DMA EXT Jan 6 01:12:29 g2 kernel: ata9.00: cmd 25/00:00:00:fe:d5/00:02:04:00:00/e0 tag 0 dma 262144 in Jan 6 01:12:29 g2 kernel: res 51/40:00:19:ff:d5/40:00...

...5357] ata2.00: qc timeout (cmd 0xa0) [ 19.859931] ata2.00: TEST_UNIT_READY failed (err_mask=0x4) [ 19.865765] ata2.00: disabled [ 19.869676] ata2: soft resetting link [ 20.056857] ata2: EH complete [ 35.712153] ata1: lost interrupt (Status 0x50) [ 35.722381] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 35.735437] ata1.00: failed command: READ DMA [ 35.745912] ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 35.745913] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 35.777373] ata1.00: status: { DRDY } [ 35.78570...

...by_channel: session 0 channel 0 > debug1: session_input_channel_req: session 0 req subsystem > debug2: subsystem request for sftp by user m61586 > debug1: subsystem: exec() /usr/libexec/openssh/sftp-server > Starting session: forced-command (key-option) '/opt/app/workload/secgov/opt/sact-central/bin/receive.ksh' for m61586 from 135.99.45.25 port 49734 id 0 Well, I'll be ... Looks like the server side recognizes the forced-command setup, but honors the SFTP subsystem request by exec()ing that nonetheless ... ! Kind regards, -- Jochen Bern Systemingenieur Binect GmbH --...

On my C5 machine (a Dell XPS420) I have a 500Gb disk on the internal SATA controller. I also have a SiI3132 dual-port multi-device eSATA card. This is connected to an external SATA array of disks. Now occasionally I see something like this in my logs ata7.01: exception Emask 0x0 SAct 0x0 SErr 0x0 a ction 0x0 ata7.01: irq_stat 0x00060002, device error via D 2H FIS ata7.01: cmd 25/00:08:47:1c:92/00:00:6c:00:00/e0 tag 0 dma 4096 in res 51/40:00:4e:1c:92/00:00:6c:00:00/00 Emask 0x9 (media error) ata7.01: status: { DRDY ERR } ata7.01: error: { UNC } ata7.01: configured for...

...ch I could apply to salvage my data while ignoring media errors ? logs/OOPS at the end of this mail, please let me know if more information is needed, Best regards, Vincent ----------------------------------------------------------------------- [ 129.241636] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 129.241640] ata6.00: BMDMA stat 0x24 [ 129.241643] ata6.00: failed command: READ DMA EXT [ 129.241649] ata6.00: cmd 25/00:08:5f:dc:2f/00:00:70:00:00/e0 tag 0 dma 4096 in [ 129.241651] res 51/40:00:61:dc:2f/40:00:70:00:00/e0 Emask 0x9 (m...

On 30/06/2023 09:56, Damien Miller wrote: > It's very hard to figure out what is happening here without a debug log. > > You can get one by stopping the listening sshd and running it manually > in debug mode, e.g. "/usr/sbin/sshd -ddd" Or starting one in debug mode on a different port, e.g. "-p99 -ddd"

Hello, I was wondering if anyone could point me in the right direction? I am receiving these in my log file and do not know what they mean or what to look for; Mar 8 04:03:56 bms kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 8 04:03:56 bms kernel: ata3.00: cmd 25/00:28:42:d3:37/00:00:13:00:00/e0 tag 0 cdb 0x0 data 20480 in Mar 8 04:03:56 bms kernel: res 51/40:22:64:d3:37/40:00:13:00:00/e0 Emask 0x9 (media error) Mar 8 04:03:56 bms kernel: ata3.00: configured for UDMA/133 Mar...

...0 > > debug1: session_input_channel_req: session 0 req subsystem > > debug2: subsystem request for sftp by user m61586 > > debug1: subsystem: exec() /usr/libexec/openssh/sftp-server > > Starting session: forced-command (key-option) > > '/opt/app/workload/secgov/opt/sact-central/bin/receive.ksh' for m61586 from > > 135.99.45.25 port 49734 id 0 > > Well, I'll be ... Looks like the server side recognizes the forced-command > setup, but honors the SFTP subsystem request by exec()ing that nonetheless ... no, that's the log message being mis...

...to provide extra SATA ports to a raid system. The HD's are all "WD2003FYYS" and so run at 3Gbps on the 6Gbps controller. However I am seeing lots of instances of errors like this ----------------------------------------- Jun 22 03:13:23 viz1 kernel: ata13.00: exception Emask 0x10 SAct 0x4 SErr 0x400000 action 0x6 frozen Jun 22 03:13:23 viz1 kernel: ata13.00: irq_stat 0x08000000, interface fatal error Jun 22 03:13:23 viz1 kernel: ata13: SError: { Handshk } Jun 22 03:13:23 viz1 kernel: ata13.00: failed command: WRITE FPDMA QUEUED Jun 22 03:13:23 viz1 kernel: ata13.00: cmd 61/e8...

On Fri, 2013-09-06 at 16:39 +0200, Alessandro Vesely wrote: Both sets of log contain stuff like: > Sep 6 15:22:53 pcale kernel: [ 126.828195] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x80000 action 0x6 frozen > Sep 6 15:22:53 pcale kernel: [ 126.828199] ata4: SError: { 10B8B } > Sep 6 15:22:53 pcale kernel: [ 126.828201] ata4.00: failed command: SMART > Sep 6 15:22:53 pcale kernel: [ 126.828205] ata4.00: cmd b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0 >...

On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M