[solved] "failed command: WRITE FPDMA QUEUED" ATA errors
Hi!
Edit: Thinking about it, this could quite well be the famous "5184 hours" bug on micron SSDs. The 3624 seconds until failure basically scream for it being that issue. I'll do a firmware update after I have performed a backup and see if that helps.
Since shortly (I do not remember it to be linked to a kernel upgrade) I keep getting these error messages after a while, with the system freezing and usually not recovering:
[ 3624.763766] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
[ 3624.763777] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3624.763786] ata1.00: cmd 61/08:00:57:a1:14/00:00:00:00:00/40 tag 0 ncq 4096 out
res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3624.763790] ata1.00: status: { DRDY }
[ 3624.764032] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3624.764035] ata1.00: cmd 61/08:f0:ff:80:46/00:00:00:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3624.764037] ata1.00: status: { DRDY }
[ 3624.764041] ata1: hard resetting link
[ 3630.100435] ata1: link is slow to respond, please be patient (ready=0)
[ 3634.796593] ata1: COMRESET failed (errno=-16)
[ 3634.796609] ata1: hard resetting link
[ 3640.133287] ata1: link is slow to respond, please be patient (ready=0)
[ 3644.829517] ata1: COMRESET failed (errno=-16)
[ 3644.829529] ata1: hard resetting link
[ 3650.166146] ata1: link is slow to respond, please be patient (ready=0)
[ 3679.894424] ata1: COMRESET failed (errno=-16)
[ 3679.894438] ata1: limiting SATA link speed to 1.5 Gbps
[ 3679.894443] ata1: hard resetting link
[ 3684.910856] ata1: COMRESET failed (errno=-16)
[ 3684.910871] ata1: reset failed, giving up
[ 3684.910875] ata1.00: disabled
[ 3684.910883] ata1.00: device reported invalid CHS sector 0
[ 3684.910888] ata1.00: device reported invalid CHS sector 0
[ 3684.910891] ata1.00: device reported invalid CHS sector 0
[ 3684.910969] ata1.00: device reported invalid CHS sector 0
[ 3684.910971] ata1.00: device reported invalid CHS sector 0
[ 3684.911077] ata1: EH complete
[ 3684.911110] sd 0:0:0:0: [sda] Unhandled error code
[ 3684.911113] sd 0:0:0:0: [sda]
[ 3684.911115] Result: hostbyte=0x04 driverbyte=0x00
[ 3684.911118] sd 0:0:0:0: [sda] CDB:
[ 3684.911120] cdb[0]=0x2a: 2a 00 00 46 80 ff 00 00 08 00
[ 3684.911129] end_request: I/O error, dev sda, sector 4620543
[ 3684.911134] Buffer I/O error on device sda1, logical block 577560
[ 3684.911143] EXT4-fs warning (device sda1): ext4_end_bio:286: I/O error writing to inode 1309793 (offset 5537792 size 4096 starting block 577568)
[ 3684.911161] sd 0:0:0:0: [sda] Unhandled error code
[ 3684.911163] sd 0:0:0:0: [sda]
[ 3684.911901] Buffer I/O error on device sda3, logical block 12682192
[ 3684.920707] systemd-journald[128]: Failed to write entry (20 items, 542 bytes), ignoring: Read-only file system
The computer is a thinkpad T410i, with this ATA controller:
» lspci |grep ATA
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06)
and this hard drive:
# smartctl -a /dev/sda |grep Model
Model Family: Crucial/Micron RealSSD m4/C400
Device Model: M4-CT128M4SSD2
Google and the error message suggest this is related to errors in the communication between the SATA controller and the hard drive. Usually things like "try another SATA cable" or "try a better power supply" are suggested, so I tried removing and re-inserting the drive into the slot; that didn't help though. What could I do now? I guess swapping the SATA cable or trying a better power supply is out of question
The disk itself seems fine to me, here's the SMART report:
# smartctl -a /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.6-2-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Crucial/Micron RealSSD m4/C400
Device Model: M4-CT128M4SSD2
Serial Number: 000000001142031CDAA0
LU WWN Device Id: 5 00a075 1031cdaa0
Firmware Version: 0009
User Capacity: 128,035,676,160 bytes [128 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: Solid State Device
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Tue Aug 20 02:16:50 2013 CEST
==> WARNING: This drive may hang after 5184 hours of power-on time:
http://www.tomshardware.com/news/Crucial-m4-Firmware-BSOD,14544.html
See the following web pages for firmware updates:
http://www.crucial.com/support/firmware.aspx
http://www.micron.com/products/solid-state-storage/client-ssd#software
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 595) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 9) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 050 Pre-fail Always - 0
5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
9 Power_On_Hours 0x0032 100 100 001 Old_age Always - 6002
12 Power_Cycle_Count 0x0032 100 100 001 Old_age Always - 2557
170 Grown_Failing_Block_Ct 0x0033 100 100 010 Pre-fail Always - 0
171 Program_Fail_Count 0x0032 100 100 001 Old_age Always - 0
172 Erase_Fail_Count 0x0032 100 100 001 Old_age Always - 0
173 Wear_Leveling_Count 0x0033 098 098 010 Pre-fail Always - 73
174 Unexpect_Power_Loss_Ct 0x0032 100 100 001 Old_age Always - 0
181 Non4k_Aligned_Access 0x0022 100 100 001 Old_age Always - 4034 1449 2584
183 SATA_Iface_Downshift 0x0032 100 100 001 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 050 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 001 Old_age Always - 0
188 Command_Timeout 0x0032 100 100 001 Old_age Always - 0
189 Factory_Bad_Block_Ct 0x000e 100 100 001 Old_age Always - 82
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 0
195 Hardware_ECC_Recovered 0x003a 100 100 001 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 100 100 001 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 001 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 001 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 100 100 001 Old_age Always - 0
202 Perc_Rated_Life_Used 0x0018 098 098 001 Old_age Offline - 2
206 Write_Error_Rate 0x000e 100 100 001 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 5684 -
# 2 Short offline Completed without error 00% 5550 -
# 3 Short offline Completed without error 00% 3843 -
# 4 Extended offline Completed without error 00% 1835 -
# 5 Short offline Completed without error 00% 1319 -
# 6 Short offline Completed without error 00% 244 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Any ideas would be very much appreciated.
Cheers,
Sven
Last edited by scummos (2013-08-23 18:44:52)
Looks like the firmware update solved it.
Similar Messages
-
Ata command READ FPDMA QUEUED on new laptop + ssd
I call on you again, fellow archers!
I have just installed Arch on a brand new laptop, but the boot process hangs a few times, with the "failed command" messages in the gist below.
excerpt from dmesg
I've searched around on the web; some say it's a hardware error, some say it's a bug.
Full disclosure: I'm running btrfs.
So can I do something about it, or should I ask the supplier for a new laptop?
Any help is much appreciated.
Last edited by Bladtman242 (2014-01-30 18:52:11)Looks like the firmware update solved it.
-
[SOLVED] SSD hard drive ata errors, system unresponsive
Hello,
I have arch installed for about 2 weeks. Since 2 or 3 days, I'm getting ata errors in dmesg.
When this happen, The HD LED is light up steady and the system is unresponsive. I have to reset the PC. It was stable before. I remember when doing a pacman -Syu, there was a kernel upgrade a couple of days ago. I'm wondering if it could be realted.
The SSD is a OCZ Vortex2, 100GB.
Any clue?
Here is the dmesg log:
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c6 b4 07 00 03 d0 00
end_request: I/O error, dev sda, sector 147239943
Buffer I/O error on device sda1, logical block 18404985
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404986
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404987
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404988
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404989
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404990
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404991
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404992
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404993
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18404994
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c e8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38594623
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c ec 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38595647
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c f0 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38596671
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c f4 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38597695
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c f8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38598719
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4c fc 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38599743
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c7 4a 07 00 04 00 00
end_request: I/O error, dev sda, sector 147278343
quiet_error: 880 callbacks suppressed
Buffer I/O error on device sda1, logical block 18409785
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409786
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409787
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409788
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409789
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409790
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409791
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409792
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409793
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18409794
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c7 4e 07 00 04 00 00
end_request: I/O error, dev sda, sector 147279367
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c7 52 07 00 04 00 00
end_request: I/O error, dev sda, sector 147280391
ata3.00: exception Emask 0x0 SAct 0x10004 SErr 0x0 action 0x6 frozen
ata3.00: failed command: WRITE FPDMA QUEUED
ata3.00: cmd 61/e0:10:c7:fc:c8/00:00:08:00:00/40 tag 2 ncq 114688 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.00: status: { DRDY }
ata3.00: failed command: WRITE FPDMA QUEUED
ata3.00: cmd 61/00:80:c7:f8:c8/04:00:08:00:00/40 tag 16 ncq 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata3.00: status: { DRDY }
ata3: hard resetting link
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: configured for UDMA/133
ata3.00: device reported invalid CHS sector 0
ata3.00: device reported invalid CHS sector 0
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c8 e4 c7 00 04 00 00
end_request: I/O error, dev sda, sector 147383495
quiet_error: 374 callbacks suppressed
Buffer I/O error on device sda1, logical block 18422929
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422930
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422931
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422932
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422933
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422934
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422935
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422936
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422937
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18422938
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c8 e8 c7 00 04 00 00
end_request: I/O error, dev sda, sector 147384519
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c8 ec c7 00 04 00 00
end_request: I/O error, dev sda, sector 147385543
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c8 f0 c7 00 04 00 00
end_request: I/O error, dev sda, sector 147386567
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 c8 f4 c7 00 04 00 00
end_request: I/O error, dev sda, sector 147387591
ata3: EH complete
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 49 10 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38342719
quiet_error: 630 callbacks suppressed
Buffer I/O error on device sda1, logical block 4792832
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792833
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792834
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792835
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792836
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792837
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792838
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792839
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792840
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4792841
lost page write due to I/O error on sda1
JBD2: Detected IO errors while flushing file data on sda1-8
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc c8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147638335
quiet_error: 118 callbacks suppressed
Buffer I/O error on device sda1, logical block 18454784
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454785
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454786
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454787
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454788
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454789
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454790
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454791
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454792
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18454793
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc cc 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147639359
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc d0 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147640383
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc d4 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147641407
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc d8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147642431
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc dc 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147643455
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc e0 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147644479
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc e4 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147645503
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc e8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147646527
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc ec 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147647551
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc f0 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147648575
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc f4 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147649599
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc f8 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147650623
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 cc fc 3f 00 04 00 00
end_request: I/O error, dev sda, sector 147651647
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 ce fc 3f 00 02 30 00
end_request: I/O error, dev sda, sector 147782719
quiet_error: 1782 callbacks suppressed
Buffer I/O error on device sda1, logical block 18472832
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472833
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472834
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472835
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472836
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472837
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472838
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472839
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472840
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18472841
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 18 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38475839
quiet_error: 60 callbacks suppressed
Buffer I/O error on device sda1, logical block 4809472
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809473
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809474
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809475
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809476
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809477
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809478
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809479
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809480
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 4809481
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 1c 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38476863
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 20 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38477887
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 24 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38478911
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 28 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38479935
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 2c 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38480959
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 30 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38481983
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 34 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38483007
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 38 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38484031
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 3c 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38485055
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 40 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38486079
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 44 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38487103
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 02 4b 48 3f 00 04 00 00
end_request: I/O error, dev sda, sector 38488127
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 71 ef 00 04 00 00
end_request: I/O error, dev sda, sector 147878383
quiet_error: 1654 callbacks suppressed
Buffer I/O error on device sda1, logical block 18484790
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484791
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484792
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484793
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484794
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484795
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484796
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484797
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484798
lost page write due to I/O error on sda1
Buffer I/O error on device sda1, logical block 18484799
lost page write due to I/O error on sda1
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 75 ef 00 04 00 00
end_request: I/O error, dev sda, sector 147879407
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 79 ef 00 04 00 00
end_request: I/O error, dev sda, sector 147880431
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 7d ef 00 04 00 00
end_request: I/O error, dev sda, sector 147881455
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 81 ef 00 04 00 00
end_request: I/O error, dev sda, sector 147882479
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 85 ef 00 04 00 00
end_request: I/O error, dev sda, sector 147883503
sd 2:0:0:0: [sda] Unhandled error code
sd 2:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x06
sd 2:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 08 d0 89 ef 00 03 30 00
end_request: I/O error, dev sda, sector 147884527
Last edited by Pitou (2011-03-09 18:51:27)litemotiv wrote:Pitou, could you place your dmesg output between code-tags please?
Or better yet, on pastebin since it's so huge -
[SOLVED] Trying to install from CD, ATA bus errors
I've been running Arch on what used to be my main computer for over a year now, and I recently built a new box. I already have Windows 8.1 installed on it. However, when I try to boot up the Arch install disk to set up a dual boot, I get the following errors:
:: Triggering uevents...
[ 1.764769] radeon 0000:01:00.0: Invalid ROM contents
[ 33.375619] ata8.00: exception Emask 0x52 SAct 0x0 SErr 0xffffffff action 0xe frozen
[ 33.375642] ata8: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 33.375682] ata8.00: failed command: IDENTIFY PACKET DEVICE
[ 33.375698] ata8.00: cmd a1/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 33.375698] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
[ 33.375736] ata8.00: status: { DRDY }
[ 33.525620] ata7.00: exception Emask 0x52 SAct 0x1 SErr 0xffffffff action 0xe frozen
[ 33.525645] ata7: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch }
[ 33.525686] ata7.00: failed command: READ FPDMA QUEUED
[ 33.525703] ata7.00: cmd 60/08:00:00:00:02/00:00:00:00:00/40 tag 0 ncq 4096 in
[ 33.525603] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
[ 33.525743] ata7.00: status: { DRDY }
After this, the cursor stops blinking and nothing else happens.
I am using UEFI, however I booted the disk using AHCI as well and got the same error, so I don't believe that its causing the problem.
I downloaded the ISO from the torrent link on the Arch downloads page, checked the "verify contents" box in Windows when I burned the disk, and tried burning the ISO on a different disk.
Any assistance would be greatly appreciated.
Last edited by Commie Pinko (2013-12-19 20:07:08)alphaniner wrote:Don't worry about the Radeon error for now. The other errors related to your drive bus are probably the problem. Normally I'd recommend checking cables and connections. But I've never seen a "SError:" line with so many 'details' and you have such errors on two ports, so it may be more complicated than that. Have you searched for info on Linux support of the controller?
Thanks for the response.
I searched for the things you wrote. By "drive bus" and "controller" do you mean the bus driver and device controller from this diagram?
http://www.linuxforu.com/wp-content/upl … 1/ldd1.jpg
Additionally, I found the following forum post while searching: http://ubuntuforums.org/showthread.php?t=2038227
Does that mean I should try reconnecting my drives to different ports on my motherboard?
Last edited by Commie Pinko (2013-12-17 22:39:41) -
[Flat File Destination [220]] Error: Failed to write out column name for column "Column 2"
I am using SSIS to extract fixed width data into a flat file destination and I keep getting below error. I have tried almost everything in this forum but still no solution. can anyone help me out to solve this problem.
[Flat File Destination [220]] Error: Failed to write out column name for column "Column 2".
[SSIS.Pipeline] Error: component "Flat File Destination" (220) failed the pre-execute phase and returned error code 0xC0202095
ThanksHi Giss68,
Could you check the Advanced tab of the Flat File Connection Manager to see whether the InputColumnWidth and the OutputColumnWidth properties of the Column2 has the same value? Please refer to the following link about the same topic:
http://stackoverflow.com/questions/10292091/how-do-i-fix-failed-to-write-error-while-exporting-data-to-ragged-right-flat-fil
If it doesn’t work, please post the sample data and the advanced settings of Column2 for further analysis.
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support -
Dmesg error.... Test WP failed, assume Write Enabled
Hi all....
there seems to be some kind of error going on. When I type
$dmesg | tail -3
[ 1398.681274] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 1398.683528] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 1398.683542] sd 4:0:0:0: [sdb] Assuming drive cache: write through
This is repeated throughout the log files. And the funny thing is I don't have anything connected i.e. no usb drives, no secondary hdds. Also,
$df -h /dev/sdb
Filesystem Size Used Avail Use% Mounted on
/dev 493M 0 493M 0% /dev
What am I missing here?
Update:
Found a similar thread : https://bbs.archlinux.org/viewtopic.php?pid=1059099
Seems like its the card reader afterall.....
Last edited by whzee (2012-02-17 10:06:28)Looks like the firmware update solved it.
-
Errors on boot - failed command: READ DMA
I've started to get failed command: READ DMA errors on boot. What do they mean? Is there any way to fix them?
[ 114.232991] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 114.233001] ata1.00: BMDMA stat 0x25
[ 114.233006] ata1.00: failed command: READ DMA
[ 114.233017] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 114.233022] ata1.00: status: { DRDY ERR }
[ 114.233026] ata1.00: error: { UNC }
[ 114.290536] ata1.00: configured for UDMA/133
[ 114.290566] sd 0:0:0:0: [sda] Unhandled sense code
[ 114.290573] sd 0:0:0:0: [sda]
[ 114.290577] Result: hostbyte=0x00 driverbyte=0x08
[ 114.290584] sd 0:0:0:0: [sda]
[ 114.290588] Sense Key : 0x3 [current] [descriptor]
[ 114.290596] Descriptor sense data with sense descriptors (in hex):
[ 114.290601] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 114.290624] 02 a6 57 02
[ 114.290636] sd 0:0:0:0: [sda]
[ 114.290640] ASC=0x11 ASCQ=0x4
[ 114.290647] sd 0:0:0:0: [sda] CDB:
[ 114.290651] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 114.290671] end_request: I/O error, dev sda, sector 44455682
[ 114.290700] ata1: EH complete
[ 115.677517] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 115.677529] ata1.00: BMDMA stat 0x25
[ 115.677538] ata1.00: failed command: READ DMA
[ 115.677555] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 115.677565] ata1.00: status: { DRDY ERR }
[ 115.677570] ata1.00: error: { UNC }
[ 115.713838] ata1.00: configured for UDMA/133
[ 115.713870] sd 0:0:0:0: [sda] Unhandled sense code
[ 115.713877] sd 0:0:0:0: [sda]
[ 115.713882] Result: hostbyte=0x00 driverbyte=0x08
[ 115.713889] sd 0:0:0:0: [sda]
[ 115.713893] Sense Key : 0x3 [current] [descriptor]
[ 115.713901] Descriptor sense data with sense descriptors (in hex):
[ 115.713905] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 115.713929] 02 a6 57 02
[ 115.713940] sd 0:0:0:0: [sda]
[ 115.713945] ASC=0x11 ASCQ=0x4
[ 115.713951] sd 0:0:0:0: [sda] CDB:
[ 115.713956] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 115.713976] end_request: I/O error, dev sda, sector 44455682
[ 115.714006] ata1: EH complete
[ 117.055388] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 117.055400] ata1.00: BMDMA stat 0x25
[ 117.055409] ata1.00: failed command: READ DMA
[ 117.055427] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 117.055436] ata1.00: status: { DRDY ERR }
[ 117.055442] ata1.00: error: { UNC }
[ 117.090462] ata1.00: configured for UDMA/133
[ 117.090494] sd 0:0:0:0: [sda] Unhandled sense code
[ 117.090501] sd 0:0:0:0: [sda]
[ 117.090506] Result: hostbyte=0x00 driverbyte=0x08
[ 117.090512] sd 0:0:0:0: [sda]
[ 117.090516] Sense Key : 0x3 [current] [descriptor]
[ 117.090524] Descriptor sense data with sense descriptors (in hex):
[ 117.090529] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 117.090552] 02 a6 57 02
[ 117.090564] sd 0:0:0:0: [sda]
[ 117.090568] ASC=0x11 ASCQ=0x4
[ 117.090575] sd 0:0:0:0: [sda] CDB:
[ 117.090579] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 117.090599] end_request: I/O error, dev sda, sector 44455682
[ 117.090648] ata1: EH complete
[ 118.344345] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 118.344356] ata1.00: BMDMA stat 0x25
[ 118.344365] ata1.00: failed command: READ DMA
[ 118.344382] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 118.344391] ata1.00: status: { DRDY ERR }
[ 118.344397] ata1.00: error: { UNC }
[ 118.427170] ata1.00: configured for UDMA/133
[ 118.427198] sd 0:0:0:0: [sda] Unhandled sense code
[ 118.427240] sd 0:0:0:0: [sda]
[ 118.427246] Result: hostbyte=0x00 driverbyte=0x08
[ 118.427252] sd 0:0:0:0: [sda]
[ 118.427257] Sense Key : 0x3 [current] [descriptor]
[ 118.427265] Descriptor sense data with sense descriptors (in hex):
[ 118.427269] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 118.427293] 02 a6 57 02
[ 118.427304] sd 0:0:0:0: [sda]
[ 118.427309] ASC=0x11 ASCQ=0x4
[ 118.427315] sd 0:0:0:0: [sda] CDB:
[ 118.427320] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 118.427340] end_request: I/O error, dev sda, sector 44455682
[ 118.430078] ata1: EH complete
[ 725.193320] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
Here's some info about the hard drive itself:
/dev/sda:
ATA device, with non-removable media
Model Number: SAMSUNG HM040HI
Serial Number: S07WJ10Y711599
Firmware Revision: YA100-02
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 0
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 78242976
LBA48 user addressable sectors: 78242976
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 38204 MBytes
device size with M = 1000*1000: 40060 MBytes (40 GB)
cache/buffer size = 8192 KBytes (type=DualPortCache)
Last edited by β ™ (2014-01-14 10:31:39)I've started to get failed command: READ DMA errors on boot. What do they mean? Is there any way to fix them?
[ 114.232991] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 114.233001] ata1.00: BMDMA stat 0x25
[ 114.233006] ata1.00: failed command: READ DMA
[ 114.233017] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 114.233022] ata1.00: status: { DRDY ERR }
[ 114.233026] ata1.00: error: { UNC }
[ 114.290536] ata1.00: configured for UDMA/133
[ 114.290566] sd 0:0:0:0: [sda] Unhandled sense code
[ 114.290573] sd 0:0:0:0: [sda]
[ 114.290577] Result: hostbyte=0x00 driverbyte=0x08
[ 114.290584] sd 0:0:0:0: [sda]
[ 114.290588] Sense Key : 0x3 [current] [descriptor]
[ 114.290596] Descriptor sense data with sense descriptors (in hex):
[ 114.290601] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 114.290624] 02 a6 57 02
[ 114.290636] sd 0:0:0:0: [sda]
[ 114.290640] ASC=0x11 ASCQ=0x4
[ 114.290647] sd 0:0:0:0: [sda] CDB:
[ 114.290651] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 114.290671] end_request: I/O error, dev sda, sector 44455682
[ 114.290700] ata1: EH complete
[ 115.677517] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 115.677529] ata1.00: BMDMA stat 0x25
[ 115.677538] ata1.00: failed command: READ DMA
[ 115.677555] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 115.677565] ata1.00: status: { DRDY ERR }
[ 115.677570] ata1.00: error: { UNC }
[ 115.713838] ata1.00: configured for UDMA/133
[ 115.713870] sd 0:0:0:0: [sda] Unhandled sense code
[ 115.713877] sd 0:0:0:0: [sda]
[ 115.713882] Result: hostbyte=0x00 driverbyte=0x08
[ 115.713889] sd 0:0:0:0: [sda]
[ 115.713893] Sense Key : 0x3 [current] [descriptor]
[ 115.713901] Descriptor sense data with sense descriptors (in hex):
[ 115.713905] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 115.713929] 02 a6 57 02
[ 115.713940] sd 0:0:0:0: [sda]
[ 115.713945] ASC=0x11 ASCQ=0x4
[ 115.713951] sd 0:0:0:0: [sda] CDB:
[ 115.713956] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 115.713976] end_request: I/O error, dev sda, sector 44455682
[ 115.714006] ata1: EH complete
[ 117.055388] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 117.055400] ata1.00: BMDMA stat 0x25
[ 117.055409] ata1.00: failed command: READ DMA
[ 117.055427] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 117.055436] ata1.00: status: { DRDY ERR }
[ 117.055442] ata1.00: error: { UNC }
[ 117.090462] ata1.00: configured for UDMA/133
[ 117.090494] sd 0:0:0:0: [sda] Unhandled sense code
[ 117.090501] sd 0:0:0:0: [sda]
[ 117.090506] Result: hostbyte=0x00 driverbyte=0x08
[ 117.090512] sd 0:0:0:0: [sda]
[ 117.090516] Sense Key : 0x3 [current] [descriptor]
[ 117.090524] Descriptor sense data with sense descriptors (in hex):
[ 117.090529] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 117.090552] 02 a6 57 02
[ 117.090564] sd 0:0:0:0: [sda]
[ 117.090568] ASC=0x11 ASCQ=0x4
[ 117.090575] sd 0:0:0:0: [sda] CDB:
[ 117.090579] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 117.090599] end_request: I/O error, dev sda, sector 44455682
[ 117.090648] ata1: EH complete
[ 118.344345] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 118.344356] ata1.00: BMDMA stat 0x25
[ 118.344365] ata1.00: failed command: READ DMA
[ 118.344382] ata1.00: cmd c8/00:08:00:57:a6/00:00:00:00:00/e2 tag 0 dma 4096 in
res 51/40:07:02:57:a6/00:00:00:00:00/e2 Emask 0x9 (media error)
[ 118.344391] ata1.00: status: { DRDY ERR }
[ 118.344397] ata1.00: error: { UNC }
[ 118.427170] ata1.00: configured for UDMA/133
[ 118.427198] sd 0:0:0:0: [sda] Unhandled sense code
[ 118.427240] sd 0:0:0:0: [sda]
[ 118.427246] Result: hostbyte=0x00 driverbyte=0x08
[ 118.427252] sd 0:0:0:0: [sda]
[ 118.427257] Sense Key : 0x3 [current] [descriptor]
[ 118.427265] Descriptor sense data with sense descriptors (in hex):
[ 118.427269] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 118.427293] 02 a6 57 02
[ 118.427304] sd 0:0:0:0: [sda]
[ 118.427309] ASC=0x11 ASCQ=0x4
[ 118.427315] sd 0:0:0:0: [sda] CDB:
[ 118.427320] cdb[0]=0x28: 28 00 02 a6 57 00 00 00 08 00
[ 118.427340] end_request: I/O error, dev sda, sector 44455682
[ 118.430078] ata1: EH complete
[ 725.193320] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
Here's some info about the hard drive itself:
/dev/sda:
ATA device, with non-removable media
Model Number: SAMSUNG HM040HI
Serial Number: S07WJ10Y711599
Firmware Revision: YA100-02
Standards:
Used: ATA/ATAPI-7 T13 1532D revision 0
Supported: 7 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 78242976
LBA48 user addressable sectors: 78242976
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 38204 MBytes
device size with M = 1000*1000: 40060 MBytes (40 GB)
cache/buffer size = 8192 KBytes (type=DualPortCache)
Last edited by β ™ (2014-01-14 10:31:39) -
Credential Roaming failed to write to the Active Directory. Error code 5 (Access is denied.)
Hi All,
I could see following error event in all client computers , Could you please some one help me on this ?
Log Name: Application
Source:
Microsoft-Windows-CertificateServicesClient-CredentialRoaming
Event ID: 1005
Level: Error
Description: Certificate Services Client: Credential Roaming failed to write to the Active Directory. Error code 5 (Access is denied.)
Regards, Srinivasu.MuchcherlaIf you are not using certificates and Credential Roaming for clients then simply ignore the error message.
If you are using certificates then you are getting access denied message when Credential Roaming is trying to write to your AD. More details about Credential Roaming here: http://blogs.technet.com/b/askds/archive/2009/01/06/certs-on-wheels-understanding-credential-roaming.aspx
http://blogs.technet.com/b/instan/archive/2009/05/26/considerations-for-implementing-credential-roaming.aspx
This is probably related to the fact that your schema version not 44 or higher: https://social.technet.microsoft.com/Forums/windowsserver/en-US/5b3a6e61-68c4-47d3-ae79-8296cb3be315/certificateservicesclientcredentialroaming-errors?forum=winserverGP
Active Directory
ObjectVersion
Windows 2000
13
Windows 2003
30
Windows 2003 R2
31
Windows 2008
44
Windows 2008 R2
47
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile -
Error message on brand new WLC2504; "Failed to write...."
Hello!
I have received a new WLC2504 for my lab, which is nice.... :-)
What's not so nice is that I get a mysterious error message on the console. It appeared when the wizard started at first boot and it apperars at every startup since.
I have gone through the wizard twice and reset to factory defaults in between but the error message persists. It looks like this :
(Cisco Controller)
Enter User Name (or 'Recover-Config' this one-time only to reset configuration to factory defaults)
User: Failed to write I2C device: Input/output error
[i2c_wr_to_wdt_timer_reg]Got error -1 during tx.
User:
Is this unit ready for RMA/DOA or can I somehow force it into normal behaviour..?.. The GUI appears to be working normally.
Best Regards
Göran Blomqvsit
SwedenI would suggest talked to TAC & RMA if that is their view on this.
Normally you should not get any errors like this on console, if it is working properly
HTH
Rasika
**** Pls rate all useful responses **** -
Using digital editions 2.0, I cannot transfer books downloaded to digital editions from the library to my nook. I get an error message: failed to write destination file. At first, this happened once in a while but now every time. Help!!!
Modern kobo books should just use regular Adobe DRM and be readable on compatible ereaders that are authorized to the correct Adobe ID.
I understand older kobo book had different DRM: but I wouldn't expect those to
When Adobe DRM book information say 'no copying', that generally means no copying outside those Adobe DRM limitations.
You should be able to copy within the restrictions. You can double-check that with the sellers (Kobo).
Just double-checking
the pocket book is Adobe DRM compatible?
that you have authorized your pocket book with your current Adobe ID?
menu/Help/Authorize Device when plugged into ADE: Library/Authorize Device if using the older more reliable ADE 1.7.2
If the pocket book is already authorized but to a different ID, you will need to deauthorize it first, ctrl-shift-E to ADE with device plugged in (or cmd-shift-E on Mac).
Be aware that will lose the ability to read DRM books authorized with the previous ID. -
Getting "file failed to write" error while syncing.
I am syncing IPADs and IPODs (big family) over USB to a windows based machine. During large syncs it often fails with a message like "file failed to write." It is random as to which file fails. In fact if I keep trying it eventually syncs everything. It's like each file has some chance of failure and I just need to try enough times. It takes forever. Please help!
Some details
- I have updated with latest iTunes
- I have tried different USB cables and USB slots on the computer
Thanks.
-- CCheck out this Apple article -> 'Disk cannot be read from or written to' when syncing iPod or 'Firmware update failure' error when updating or restoring iPod
If you have a USB hub, try removing it and connecting the iPad or iPod to the back of the computer. If it isn't caused by the USB connection, the article suggestions will be a good place to start. -
When burning my pictures to CD, a burn failed, medium write error came up.
When burning my pictures from IPhoto to a CD, a burn failed, medium write error showed up,
Like many other suggestions I found, I went ahead and purchased a lens cleaner. The CD instructions said to insert and play track 2, but my drive would just keep ejecting the CD. But it worked! That and a little compressed air.
Before using the lens cleaner and compressed air, my drive would constantly give me a medium write error and always make loud vibrating noises that sounded like my drive was about to explode. But now it writes like a charm and is completely silent! -
Ebook error message: "Fail to write destination file error"
I am attempting to transfer ebooks (checked out via my library's ebook consortium) from Adobe Digital Editions to my Nook. I have done this in the past with no issues, but recently I have been getting the following error message: "Fail to write destination file error".
I know the issue is NOT lack of space on my Nook (I cleared it of all info and still received the error message).I had this problem as well, and after doing some research via google (because I found NOTHING helpful in adobe forums), I found the problem....my Nook was full. I had no idea this was even possible! But, I borrow a lot of library books, and didn't realize that after they expire, they are still taking up space on my Nook. Here's how to check: plug your Nook into your computer, go to file manager (right-click the start button in Windows), find the Nook drive and right click, choose properties. This should show you a pie chart of used/free space on your Nook. If this is the case, you need to remove some files from your Nook. For me, I had to find the Digital Editions file and delete all the thumbnails and actual files for the library books. If it's booked you've purchased, perhaps you need to archive some books. Hope this helps!
-
Quicktime would fail to write/export to server windows share with "Error -43: file not found" errors
Summary:
With the combination of Windows 7 and Quicktime 7.x, Quicktime would fail to write/export to server windows share with "Couldn't create output movie storage" and "Error -43: file not found" errors
Steps to Reproduce:
Trying to render to Quicktime files using network shared folders as a destination:
Unable to open file. (-1610153459)
The funny thing: it only happens when there are at least two shared folders mapped on the workstation, and the destination folder used for the rendered movie is not the first one.
If we have only two mapped drives, F: and G: for example, and we try to render something to F:, everything works fine and no error is showed. But, when the destination is the G: drive, rendering never works, the error is showed, but a zero-byte file is created in F: (!!). ODD! If we remap F: drive with a different letter, but a letter BEFORE G:, the problem always happens. If we remap drive F: to any letter AFTER G:, making G: the first available network drive, rendering works. Also, simply unmapping F: and leaving G: as the only connected network folder makes render to work.
We do not have a D: drive in our Windows 7 workstations, they are all C: only.
It is a 100% reproducible problem. We tried with three different Active Directory networks and workstations. It has all of the features of a software bug.
Any help would be appreciated.
Cheers!
Expected Results:
Error -43: file not found
Actual Results:
The workaround seems to be to use the full path to the servers instead of the mapped mount point (ie //server/z/... instead of Z:/...
Regression:
All versions of quicktime 7 in combination with windows 7 client and more than one smb share point mapped in a letter.
Notes:
All software that uses quicktime movie exports showed this error.Not sure what file your are referencing? Thanks for your suggestion, however, it's not relavant.
It renders fine if you render to either the UNC path or the first mapped drive.
i.e. If you have two mapped drives G: and H:
they both point to \\fileserver\share1\folder
If you render to H: it will fail, if you render to G: it works! Same path, same user, same permissions.
The only difference is H comes after G, so it fails... BUG. If it was to do with anything else, underscores, permissions etc, it would fail on both. -
When trying to transfer a book from Adobe Digital Editions 2.0.1.78765 I get the error message E_IO_WRITE Failed to write to destination. The book shows in the Nook folder, but as 0 KB and cannot be found on the Nook device when unplugged. I don't have a problem transfering from ADE with a second Nook I own, just have a problem with this Nook.
I figured it out. I deleted the Digital Editions folder and then transferred the book without a problem. It quite possibly could have been that my daughter had exceeded the storage capacity of her Nook and there wasn't any room on there to transfer the books.
Maybe you are looking for
-
I owned an iPhone 4s a year ago before I unfortunately lost it. I have since then bought the iPhone 5 but had not plugged it in to my computer yet to download any music. I plugged in my iPhone today to my laptop and my iTunes store stated that it reg
-
Hi, Our company has a SAP Netweaver Enterprise Portal implementation. Recently we have been asked to create a Web service from a Java class in SAP Netweaver using Netweaver Developer Studio. The connection to Web service must be an https connection.
-
Java.lang.StackOverflowError reading to a variable
Hello, Below is the piece of the code used to replace all matched pattern to empty. But when executed 1. FileInputStream fis = new FileInputStream(filePath); 2. FileChannel fc = fis.getChannel(); 3. MappedByteBuffer bb = fc.map(FileChannel.MapMode.RE
-
Hi, I'm looking for some guidelines how I can add an extra instance (via Domain Manager) in the ICM. Current environment is an UCCE 8.5. Is it correct that I've to move to UCCH, when I want to have an extra (second) instance? How can I migrate to UCC
-
Firefox displays files as Media Player format
hi when i attempt to download a split file, firefox reads the split file as a media player file instead of a windows common dll. is there anyway to solve this?