Problems with second 7970 Lightning Card?

Hello
I purchased the MSI 7970 Lightning in May of last year as part of a new build. The other components of the build that affect the running of the machine are:
Asus P8Z77 WS Motherboard
Intel i7 3770K CPU
16GB Mushkin Ram (991991)
Noctua NH-U12P SE2 Cooler
Samsung 830 SSD x2
Samsung Spinpoint F2 1TB HD
Corsair AX850 PSU
Windows 7 Home Premium
USB 3.0 PCIe card with 2 internal and 2 external sockets
Sony CD Drive
With buying such high end products I thought I would have an easy hassle free build as I have built computers before with only one problem build that resulted from a faulty stick of memory. I didn't intend to overclock at all initially and intended but wanted the option to if I needed to in the future.
How wrong was I? The first Lightning card was faulty and would crash before it finished the Kombuster benchmark. The system also suffered from continual 'AMD Driver has stopped responding and has recovered' stutters and occasional crashes even on the desktop. I contacted the merchant I purchased it from and arranged a return. It took a few weeks but I did eventually receive a replacement card through MSI.
Excuse the pun, but Lightning couldn't strike twice I thought, and the next card would work. However, I still got the 'AMD Driver has stopped responding and has recovered' reports and the occasional crashes. This card did at least complete the benchmark so I kept it and put it down to driver issues.
In my quest to resolve the issue I have tried the following:
I trawled the internet looking for probable causes and have tweaked the motherboard bios according to what was recommended on Asus forums to no avail.
I have downloaded the latest bios for the motherboard
I have used the most stable settings recommended in bios so as to cause least stress on a non-overclocked CPU
I have set up my SSD's in non-raid as I read Lucid Virtu MVP doesn't like that
I have done a fresh install of Windows 7 each time I downloaded new drivers for the graphics card so that there could be no old files affecting the driver's operation
I have used graphics drivers from the MSI site for the 7970 and also from AMD without success
I have run Memtest which came up with no errors.
I have also tried using just 8GB of the RAM in various configurations on the off-chance it was a faulty stick despite the Memtest result.
I don't have limitless hours to spend trying to rectify problems with my computer. I tend to work on it when I take a holiday but, again, I can't continually take up all of my holiday time trying to sort this out. Unfortunately many moons later I have still not got a stable computer that is usable (it is intended for my work primarily so i do need it to be stable. I can't afford a crash in the middle of doing my work).
I'd like to get this rig working before the build becomes obsolete. I have built several computers before but would not consider myself an expert so please don't get too technical with the jargon.
I would welcome any suggestions even if it is to arrange another RMA for the 7970.
Thanks in advance
Trevellion.

Ok, I did a fresh install. At first I thought it had been the Lucid MVP software which was causing conflicts because the system appeared stable. The computer would even recover from sleep mode (the stage where the fans stop) without mishap which had never been able to before. Unfortunately, shortly afterwards I got the dreaded hang and the message 'AMD driver stopped responding and has recovered'. It now seems to do this every time I switch the computer on now. I just don't feel I can use this computer in it's current state for work as it's too unreliable. Once the problems start they become much more frequent.
When I enter the Action Center, click 'Maintenance' and check under 'Review your computer's reliability and problem history', I can see multiple reports of 'Video Hardware Error'
Clicking on the report gives this message:
Description
A problem with your video hardware caused Windows to stop working correctly.
Problem signature
Problem Event Name:   LiveKernelEvent
OS Version:   6.1.7601.2.1.0.768.3
Locale ID:   2057
Files that help describe the problem
WD-20130102-0601.dmp
sysdata.xml
WERInternalMetadata.xml
View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.
Extra information about the problem
BCCode:   117
BCP1:   FFFFFA800B88A4E0
BCP2:   FFFFF8800596CDB8
BCP3:   0000000000000000
BCP4:   0000000000000000
OS Version:   6_1_7601
Service Pack:   1_0
Product:   768_1
When I request Windows to check for a solution it comes up with nothing.
- Is there anything in this message that gives useful info to pinpoint the problem? I'd be grateful for any more advice on this.
Regards
Trevellion

Similar Messages

Problem with SB1240 USB sound card

I'm pulling hair here! I've just bought a SB240. Windows (XP Pro, SP3) detected it and I can select it fine for listening. But when I open Sound and Audio Device Properties and select Sound Recording/Volume, I see the Capture panel with the three inputs, but all the controls are greyed out and immovable. I also use the application "Total Recorder" by High Criteria, in which I can select the SB240 device but the only input line it sees is SPDIF Interface.
I'm stumped. Can anyone help?
John?

&Re: Problem with SB240 USB sound card
Thank you. I did a complete uninstall, including the device itself (from Device Manager) as well as all drivers and any SB related software. As recommended by Creative, I had previously installed the driver software from the supplied CD and that seems to have been the problem.
I let Windows re-detect the SB, but? got a "problem ... device may not work correctly.." during the detection, so I was not hopeful (this had not happened the first time I installed the device).
Nevertheless it now does work fully and is properly configured in "Total Recorder" too.
So I would suggest not using the supplied drivers and software - at least not in WinXP. But it's not very confidence inspiring.
John

Problem with my amd graphic card

Hi.. I have a problem with my amd graphic card.. The card is amd radeon 6770m.. I did format on my laptop and when I tried to install the catalyst center which includes the driver, it displays a message which say that catalyst center stop working... I have downloaded all the versions of the driver since 2011 when I bought the laptop... But I have the same problem whichever version I try.. I also have updated the bios to the last version but nothing happens..I think maybe graphic card is broken.. Thanks for reading..

Hi @Lefteris93 ,
Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your I would uninstall all the software and drivers for AMD High-Definition (HD) Graphics Driver and Catalyst Control from the control panel and the Device manager. Restart the notebook and download from here.
Here is a link to the HP Support Assistant if you need it. Just download and run the application and it will help with the software and drivers on your system at the time of purchase. This will help update the drivers that have been installed on the Notebook. If you graphics card was damaged or not functioning you would have a black or blank screen.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Problems with msi r6970 lightning

Hey guys I am having big issues with my 6970 lightning. Ok first I got this card to replace a second sapphire 6970 that I was running in xfire with another sapphire 6970. I since gave one of the sapphires to a relative. When I first got the lightning all went smooth benched it in a single card config then added my other sapphire 6970. No issues. Out of nowhere things rapidly went downhill. I first received a crash in grfs as I loaded shattered mountain. Froze with a sound loop then the screen turned black with a continued sound loop that eventually stopped. Reset the machine figuring it was the OC. On the lighting I had it set as 985/1400 fan 80% voltage @ 1.300 vlts. Prior to the crash I used a combo of heaven 3.0, kombustor and 3dmark 11 all passed numerous loops without issues. Again thinking it was the oc I down clocked to stock then fired up grfs multiplayer which crashed n froze on the main menu. I then ran heaven and after 10 min a solid black screen that eventually recovered throwing a display driver has stopped responding but has recovered. Now I knew something was up.
I then ran kombustor same issues black screens sometimes a 8bit Nintendo looking screen when u need to blow in the cartridge. After countless hours of stress testing my CPU with prime, memtest, and Intel burn, I ruled out my other hardware as being the cause. I ran 2 hours of prime, Intel burn passed the maximum stress test, memtest passed until about 500% on each iteration (7 to be exact) windows version. This both with my OC and at stock. Here's for the finale I have a second machine (ill include both machines at the bottom of this post) I installed the lightening in the second rig not one single issue no black screen, no 8bit Nintendo crashes nada. Again I've tried every fix known to no prevail. Reinstalled drivers 12.10 rolled back to 12.8 used driver fusion to clear out the old remnants, swapping cards and systems. The lightning ran flawless in the old rig for hours. Now the sapphire card runs all the gpu stress tests I've tried flawlessly in the main rig at stock and OC. so I assumed the lightning was dying. But I tried the lightning in my second AMD pc (with a MSI mobo coincidentally) and it ran heaven, kombuster, and games without a single crash.
The only option I didn't try was taking the PSU out of the main pc and using it in the older pc to rule out the psu. But that still don't explain why the sapphire card works perfectly in the main rig and not the lightning. The second fix I didn't try was updating the mobo bios I'm using the f3 gigabyte has up to the f6 but I never had issues b4 and my sapphire 6970 and when I had two in xfire, ran perfect in the main pc with stock and oc settings, with the current PSU and bios. Food for though, gpu temps sapphire 45c to 50c idle 75c to 80c load. Lightning 41c idle 70c to 74c load. Right where they need to be. Another thing to add I originally had a gigabyte Odin 1200 PSU that got ... Well let's say replaced (garbage of a PSU) the HX750 meets AMD requirements for xfire 6970s this almost rules out everything except BIOS or worst case the lightning just ain't compatible with the gigabyte mobo. Any ideas how to get this card to work after all the testing I know its not defective. Sry for the long post.
Main rig
AMD PII X6 1090t @4.0 with H50 push/pull 19c idle 35c load
Gigabyte 890FX UD5 ver 2.0 bios
8GB, 2GBX1 G.Skill DDR3 1600@ 1800 9.9.9.12
1X sapphire 6970 reference and MSI R6970 lightning 900/1400- 985/1400
X-fi fatal1ty
LG bluray drive, Samsung ssdx 60gb, velci rap 150gb, WD Blk1tb, Hitachi deskstar 250 gb
Cooler master Haf X, with 4 220mm fans, vista ultimate 6
Corsair HX750 watt PSU
2nd rig
PII x4 940 blk @3.6 cooler master hyper 212 dual fan 40c idle
MSI DKA790GXM Platinum
4gb ddr2 kingston hyper x 800@960
Asus dvd burner
X-fi titanium PCI-e
2x WD raptors 150gb raid 0, WD Blk 1tb, Hitachi deskstar 250gb
Sapphire 5830 extreme @ 950/1100 1.200 vlts
Pc power n cooling 650 watt PSU
Silverstone gaming case
Windows 7 64bit

I also use cpuid hwmonitor to check temps n volts 12 vlt rail is at 12.05 during load. The gpu load temps on the lightning nvr exceed 72c at stock and 76c with the oc. Should I get a new mobo? Compatibility issue? I was looking at a asrock 990fx extreme 3 as this would allow me to upgrade my CPU later if I choose. I am on my current main pc bc bulldozer didn't grab me. Some benches r less than the x6s, my two 6970s perform btr than a single 7970 for my needs and the only increase I would see is if I got two 7970s that's way to much coin n would be bottlenecked by my current CPU I'm sure. Any ideas? I'm at a loss

[SOLVED] Problem with second SATA drive

My laptop has two hard drive bays, and just recently I added a second SATA drive (moved it from my old laptop) to the extra bay.
Now, anytime the second hard drive /dev/sdb has any heavy disk activity, it appears to cause a shutdown of the SATA port for the first drive (/dev/sda)! Though the second drive is still fine, and I can still write to it until the system crashes from the root drive (on /dev/sda) being shutdown.
If I don't mount and use the second drive, the first drive works just fine, and I can pound it with traffic without issue.
I can reproduce this problem by copying large amounts of data to drive 2.
This is when I get in my dmesg when the first SATA drive shuts down:
[ 3013.249525] ata1.00: exception Emask 0x0 SAct 0x7ff SErr 0x0 action 0x6 frozen
[ 3013.249532] ata1.00: failed command: READ FPDMA QUEUED
[ 3013.249539] ata1.00: cmd 60/08:00:78:b8:ba/00:00:24:00:00/40 tag 0 ncq 4096 in
[ 3013.249539] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3013.249543] ata1.00: status: { DRDY }
[ 3013.249545] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249559] ata1.00: cmd 61/08:08:b8:60:7b/00:00:29:00:00/40 tag 1 ncq 4096 out
[ 3013.249559] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249562] ata1.00: status: { DRDY }
[ 3013.249564] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249568] ata1.00: cmd 61/08:10:c0:60:7b/00:00:29:00:00/40 tag 2 ncq 4096 out
[ 3013.249568] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249570] ata1.00: status: { DRDY }
[ 3013.249572] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249576] ata1.00: cmd 61/08:18:c8:60:7b/00:00:29:00:00/40 tag 3 ncq 4096 out
[ 3013.249576] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249578] ata1.00: status: { DRDY }
[ 3013.249580] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249585] ata1.00: cmd 61/08:20:48:12:d7/00:00:18:00:00/40 tag 4 ncq 4096 out
[ 3013.249585] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249587] ata1.00: status: { DRDY }
[ 3013.249589] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249593] ata1.00: cmd 61/08:28:28:63:38/00:00:19:00:00/40 tag 5 ncq 4096 out
[ 3013.249593] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249595] ata1.00: status: { DRDY }
[ 3013.249597] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249601] ata1.00: cmd 61/08:30:28:6f:38/00:00:19:00:00/40 tag 6 ncq 4096 out
[ 3013.249601] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249603] ata1.00: status: { DRDY }
[ 3013.249605] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249609] ata1.00: cmd 61/08:38:28:98:ae/00:00:25:00:00/40 tag 7 ncq 4096 out
[ 3013.249609] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249611] ata1.00: status: { DRDY }
[ 3013.249613] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249617] ata1.00: cmd 61/08:40:d8:79:3b/00:00:25:00:00/40 tag 8 ncq 4096 out
[ 3013.249617] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249619] ata1.00: status: { DRDY }
[ 3013.249621] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249625] ata1.00: cmd 61/08:48:08:98:b6/00:00:18:00:00/40 tag 9 ncq 4096 out
[ 3013.249625] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249627] ata1.00: status: { DRDY }
[ 3013.249629] ata1.00: failed command: WRITE FPDMA QUEUED
[ 3013.249633] ata1.00: cmd 61/08:50:10:98:36/00:00:19:00:00/40 tag 10 ncq 4096 out
[ 3013.249633] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3013.249636] ata1.00: status: { DRDY }
[ 3013.249640] ata1: hard resetting link
[ 3013.575549] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3013.576784] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578334] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3013.578588] ata1.00: configured for UDMA/133
[ 3013.592223] ata1.00: device reported invalid CHS sector 0
[ 3013.592233] ata1.00: device reported invalid CHS sector 0
[ 3013.592238] ata1.00: device reported invalid CHS sector 0
[ 3013.592242] ata1.00: device reported invalid CHS sector 0
[ 3013.592246] ata1.00: device reported invalid CHS sector 0
[ 3013.592250] ata1.00: device reported invalid CHS sector 0
[ 3013.592254] ata1.00: device reported invalid CHS sector 0
[ 3013.592258] ata1.00: device reported invalid CHS sector 0
[ 3013.592263] ata1.00: device reported invalid CHS sector 0
[ 3013.592267] ata1.00: device reported invalid CHS sector 0
[ 3013.592271] ata1.00: device reported invalid CHS sector 0
[ 3013.592302] sd 0:0:0:0: [sda]
[ 3013.592306] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592310] sd 0:0:0:0: [sda]
[ 3013.592313] Sense Key : 0xb [current] [descriptor]
[ 3013.592320] Descriptor sense data with sense descriptors (in hex):
[ 3013.592323] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592342] 00 00 00 00
[ 3013.592351] sd 0:0:0:0: [sda]
[ 3013.592353] ASC=0x0 ASCQ=0x0
[ 3013.592358] sd 0:0:0:0: [sda] CDB:
[ 3013.592361] cdb[0]=0x28: 28 00 24 ba b8 78 00 00 08 00
[ 3013.592376] end_request: I/O error, dev sda, sector 616216696
[ 3013.592414] sd 0:0:0:0: [sda]
[ 3013.592417] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592421] sd 0:0:0:0: [sda]
[ 3013.592423] Sense Key : 0xb [current] [descriptor]
[ 3013.592428] Descriptor sense data with sense descriptors (in hex):
[ 3013.592431] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592449] 00 00 00 00
[ 3013.592458] sd 0:0:0:0: [sda]
[ 3013.592460] ASC=0x0 ASCQ=0x0
[ 3013.592465] sd 0:0:0:0: [sda] CDB:
[ 3013.592467] cdb[0]=0x2a: 2a 00 29 7b 60 b8 00 00 08 00
[ 3013.592482] end_request: I/O error, dev sda, sector 695951544
[ 3013.592505] sd 0:0:0:0: [sda]
[ 3013.592508] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592512] sd 0:0:0:0: [sda]
[ 3013.592514] Sense Key : 0xb [current] [descriptor]
[ 3013.592519] Descriptor sense data with sense descriptors (in hex):
[ 3013.592522] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592540] 00 00 00 00
[ 3013.592549] sd 0:0:0:0: [sda]
[ 3013.592551] ASC=0x0 ASCQ=0x0
[ 3013.592556] sd 0:0:0:0: [sda] CDB:
[ 3013.592558] cdb[0]=0x2a: 2a 00 29 7b 60 c0 00 00 08 00
[ 3013.592572] end_request: I/O error, dev sda, sector 695951552
[ 3013.592583] sd 0:0:0:0: [sda]
[ 3013.592586] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592589] sd 0:0:0:0: [sda]
[ 3013.592592] Sense Key : 0xb [current] [descriptor]
[ 3013.592597] Descriptor sense data with sense descriptors (in hex):
[ 3013.592599] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592618] 00 00 00 00
[ 3013.592626] sd 0:0:0:0: [sda]
[ 3013.592628] ASC=0x0 ASCQ=0x0
[ 3013.592632] sd 0:0:0:0: [sda] CDB:
[ 3013.592635] cdb[0]=0x2a: 2a 00 29 7b 60 c8 00 00 08 00
[ 3013.592649] end_request: I/O error, dev sda, sector 695951560
[ 3013.592665] sd 0:0:0:0: [sda]
[ 3013.592668] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592671] sd 0:0:0:0: [sda]
[ 3013.592673] Sense Key : 0xb [current] [descriptor]
[ 3013.592678] Descriptor sense data with sense descriptors (in hex):
[ 3013.592684] Aborting journal on device dm-0-8.
[ 3013.592701] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.592687] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592723] 00 00 00 00
[ 3013.592729] sd 0:0:0:0: [sda]
[ 3013.592730] ASC=0x0 ASCQ=0x0
[ 3013.592733] sd 0:0:0:0: [sda] CDB:
[ 3013.592735] cdb[0]=0x2a: 2a 00 18 d7 12 48 00 00 08 00
[ 3013.592744] end_request: I/O error, dev sda, sector 416748104
[ 3013.592752] Buffer I/O error on device dm-0, logical block 266057
[ 3013.592760] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902184 (offset 258048 size 4096 starting block 266057)
[ 3013.592766] sd 0:0:0:0: [sda]
[ 3013.592768] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592771] sd 0:0:0:0: [sda]
[ 3013.592772] Sense Key : 0xb [current] [descriptor]
[ 3013.592776] Descriptor sense data with sense descriptors (in hex):
[ 3013.592778] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592790] 00 00 00 00
[ 3013.592795] sd 0:0:0:0: [sda]
[ 3013.592797] ASC=0x0 ASCQ=0x0
[ 3013.592800] sd 0:0:0:0: [sda] CDB:
[ 3013.592801] cdb[0]=0x2a: 2a 00 19 38 63 28 00 00 08 00
[ 3013.592811] end_request: I/O error, dev sda, sector 423125800
[ 3013.592817] Buffer I/O error on device dm-0, logical block 1063269
[ 3013.592822] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5898577 (offset 970752 size 4096 starting block 1063269)
[ 3013.592842] sd 0:0:0:0: [sda]
[ 3013.592845] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592849] sd 0:0:0:0: [sda]
[ 3013.592851] Sense Key : 0xb [current] [descriptor]
[ 3013.592856] Descriptor sense data with sense descriptors (in hex):
[ 3013.592859] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592877] 00 00 00 00
[ 3013.592885] sd 0:0:0:0: [sda]
[ 3013.592887] ASC=0x0 ASCQ=0x0
[ 3013.592892] sd 0:0:0:0: [sda] CDB:
[ 3013.592894] cdb[0]=0x2a: 2a 00 19 38 6f 28 00 00 08 00
[ 3013.592908] end_request: I/O error, dev sda, sector 423128872
[ 3013.592915] Buffer I/O error on device dm-0, logical block 1063653
[ 3013.592922] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 5902187 (offset 1171456 size 4096 starting block 1063653)
[ 3013.592931] sd 0:0:0:0: [sda]
[ 3013.592934] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.592937] sd 0:0:0:0: [sda]
[ 3013.592940] Sense Key : 0xb [current] [descriptor]
[ 3013.592945] Descriptor sense data with sense descriptors (in hex):
[ 3013.592947] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.592966] 00 00 00 00
[ 3013.592974] sd 0:0:0:0: [sda]
[ 3013.592976] ASC=0x0 ASCQ=0x0
[ 3013.592980] sd 0:0:0:0: [sda] CDB:
[ 3013.592983] cdb[0]=0x2a: 2a 00 25 ae 98 28 00 00 08 00
[ 3013.592997] end_request: I/O error, dev sda, sector 632199208
[ 3013.593006] Buffer I/O error on device dm-0, logical block 27197445
[ 3013.593018] EXT4-fs warning (device dm-0): ext4_end_bio:250: I/O error writing to inode 6425165 (offset 151552 size 4096 starting block 27197445)
[ 3013.593028] sd 0:0:0:0: [sda]
[ 3013.593031] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593034] sd 0:0:0:0: [sda]
[ 3013.593037] Sense Key : 0xb [current] [descriptor]
[ 3013.593042] Descriptor sense data with sense descriptors (in hex):
[ 3013.593045] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593063] 00 00 00 00
[ 3013.593071] sd 0:0:0:0: [sda]
[ 3013.593073] ASC=0x0 ASCQ=0x0
[ 3013.593078] sd 0:0:0:0: [sda] CDB:
[ 3013.593085] EXT4-fs error (device dm-0) in ext4_reserve_inode_write:4476: Journal has aborted
[ 3013.593089] cdb[0]=0x2a: 2a 00 25 3b 79 d8 00 00 08 00
[ 3013.593104] end_request: I/O error, dev sda, sector 624654808
[ 3013.593111] Buffer I/O error on device dm-0, logical block 26254395
[ 3013.593115] lost page write due to I/O error on dm-0
[ 3013.593126] sd 0:0:0:0: [sda]
[ 3013.593129] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593132] sd 0:0:0:0: [sda]
[ 3013.593135] Sense Key : 0xb [current] [descriptor]
[ 3013.593140] Descriptor sense data with sense descriptors (in hex):
[ 3013.593142] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593161] 00 00 00 00
[ 3013.593169] sd 0:0:0:0: [sda]
[ 3013.593171] ASC=0x0 ASCQ=0x0
[ 3013.593175] sd 0:0:0:0: [sda] CDB:
[ 3013.593178] cdb[0]=0x2a: 2a 00 18 b6 98 08 00 00 08 00
[ 3013.593192] end_request: I/O error, dev sda, sector 414619656
[ 3013.593198] Buffer I/O error on device dm-0, logical block 1
[ 3013.593201] lost page write due to I/O error on dm-0
[ 3013.593211] sd 0:0:0:0: [sda]
[ 3013.593213] Result: hostbyte=0x00 driverbyte=0x08
[ 3013.593217] sd 0:0:0:0: [sda]
[ 3013.593219] Sense Key : 0xb [current] [descriptor]
[ 3013.593224] Descriptor sense data with sense descriptors (in hex):
[ 3013.593227] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3013.593245] 00 00 00 00
[ 3013.593253] sd 0:0:0:0: [sda]
[ 3013.593256] ASC=0x0 ASCQ=0x0
[ 3013.593260] sd 0:0:0:0: [sda] CDB:
[ 3013.593262] cdb[0]=0x2a: 2a 00 19 36 98 10 00 00 08 00
[ 3013.593277] end_request: I/O error, dev sda, sector 423008272
[ 3013.593283] Buffer I/O error on device dm-0, logical block 1048578
[ 3013.593286] lost page write due to I/O error on dm-0
[ 3013.593298] ata1: EH complete
[ 3013.595707] EXT4-fs error (device dm-0) in ext4_dirty_inode:4603: Journal has aborted
[ 3013.596581] EXT4-fs error (device dm-0): ext4_journal_start_sb:370: Detected aborted journal
[ 3013.596591] EXT4-fs (dm-0): Remounting filesystem read-only
[ 3020.421558] journal commit I/O error
[ 3020.421570] journal commit I/O error
[ 3020.421574] journal commit I/O error
[ 3020.421578] journal commit I/O error
[ 3020.421581] journal commit I/O error
[ 3147.052191] ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[ 3147.052197] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052209] ata1.00: cmd 60/50:00:d0:48:99/00:00:1c:00:00/40 tag 0 ncq 40960 in
[ 3147.052209] res 40/00:00:00:4f:c2/00:00:00:00:00/40 Emask 0x4 (timeout)
[ 3147.052212] ata1.00: status: { DRDY }
[ 3147.052213] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052218] ata1.00: cmd 60/18:08:28:49:99/00:00:1c:00:00/40 tag 1 ncq 12288 in
[ 3147.052218] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052220] ata1.00: status: { DRDY }
[ 3147.052221] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052226] ata1.00: cmd 60/88:10:48:49:99/00:00:1c:00:00/40 tag 2 ncq 69632 in
[ 3147.052226] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052228] ata1.00: status: { DRDY }
[ 3147.052229] ata1.00: failed command: READ FPDMA QUEUED
[ 3147.052234] ata1.00: cmd 60/20:18:00:a4:ba/00:00:24:00:00/40 tag 3 ncq 16384 in
[ 3147.052234] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 3147.052236] ata1.00: status: { DRDY }
[ 3147.052239] ata1: hard resetting link
[ 3147.378368] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3148.066853] ata1.00: ACPI cmd ef/5a:00:00:00:00:a0 (SET FEATURES) succeeded
[ 3148.069139] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
[ 3148.069393] ata1.00: configured for UDMA/133
[ 3148.080059] ata1.00: device reported invalid CHS sector 0
[ 3148.080066] ata1.00: device reported invalid CHS sector 0
[ 3148.080071] ata1.00: device reported invalid CHS sector 0
[ 3148.080075] ata1.00: device reported invalid CHS sector 0
[ 3148.080112] sd 0:0:0:0: [sda]
[ 3148.080114] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080117] sd 0:0:0:0: [sda]
[ 3148.080118] Sense Key : 0xb [current] [descriptor]
[ 3148.080123] Descriptor sense data with sense descriptors (in hex):
[ 3148.080125] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080136] 00 00 00 00
[ 3148.080140] sd 0:0:0:0: [sda]
[ 3148.080142] ASC=0x0 ASCQ=0x0
[ 3148.080145] sd 0:0:0:0: [sda] CDB:
[ 3148.080146] cdb[0]=0x28: 28 00 1c 99 48 d0 00 00 50 00
[ 3148.080156] end_request: I/O error, dev sda, sector 479807696
[ 3148.080170] sd 0:0:0:0: [sda]
[ 3148.080171] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080173] sd 0:0:0:0: [sda]
[ 3148.080175] Sense Key : 0xb [current] [descriptor]
[ 3148.080178] Descriptor sense data with sense descriptors (in hex):
[ 3148.080180] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080190] 00 00 00 00
[ 3148.080195] sd 0:0:0:0: [sda]
[ 3148.080196] ASC=0x0 ASCQ=0x0
[ 3148.080199] sd 0:0:0:0: [sda] CDB:
[ 3148.080200] cdb[0]=0x28: 28 00 1c 99 49 28 00 00 18 00
[ 3148.080209] end_request: I/O error, dev sda, sector 479807784
[ 3148.080216] sd 0:0:0:0: [sda]
[ 3148.080218] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080220] sd 0:0:0:0: [sda]
[ 3148.080221] Sense Key : 0xb [current] [descriptor]
[ 3148.080224] Descriptor sense data with sense descriptors (in hex):
[ 3148.080225] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080236] 00 00 00 00
[ 3148.080241] sd 0:0:0:0: [sda]
[ 3148.080242] ASC=0x0 ASCQ=0x0
[ 3148.080245] sd 0:0:0:0: [sda] CDB:
[ 3148.080246] cdb[0]=0x28: 28 00 1c 99 49 48 00 00 88 00
[ 3148.080254] end_request: I/O error, dev sda, sector 479807816
[ 3148.080267] sd 0:0:0:0: [sda]
[ 3148.080268] Result: hostbyte=0x00 driverbyte=0x08
[ 3148.080270] sd 0:0:0:0: [sda]
[ 3148.080272] Sense Key : 0xb [current] [descriptor]
[ 3148.080274] Descriptor sense data with sense descriptors (in hex):
[ 3148.080276] 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 3148.080287] 00 00 00 00
[ 3148.080291] sd 0:0:0:0: [sda]
[ 3148.080293] ASC=0x0 ASCQ=0x0
[ 3148.080295] sd 0:0:0:0: [sda] CDB:
[ 3148.080296] cdb[0]=0x28: 28 00 24 ba a4 00 00 00 20 00
[ 3148.080305] end_request: I/O error, dev sda, sector 616211456
[ 3148.080315] ata1: EH complete
I have experimented, and found that if I turn off NCQ on the kernel command line in my bootloader (libata.force=noncq), that it takes longer before the problem occurs. Though, if I write enough to the second drive, it does still happen after a while, just greatly reduced its chances of happening.
Is it possible that the old drive (sdb) is causing the problem? I noticed that it is much noisier than I remember when the drive head moves around.
Another curiosity while I was trying to duplicate the problem:
- I start a large file copy from sda -> sdb
- At the same time in another terminal, I do "find / -print"
- When I hear the drive 2 head moving, it pauses the output of the "find" command.
Every time I hear the head move, I see the find output pause. Its almost like the drive seek on drive 2 causes the whole Sata controller to pause while the head moves. Very odd!
Anyone have any ideas? I think the next thing I will try is borrow a drive from another machine, and do the big write to it to see if I get the same results.
If it is of any help, here is some more info on the laptop:
lspci:
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1251 (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1)
07:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0)
0d:00.0 Network controller: Intel Corporation Centrino Advanced-N + WiMAX 6250 (rev 5e)
13:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
13:00.1 SD Host controller: Realtek Semiconductor Co., Ltd. RTS5209 PCI Express Card Reader (rev 01)
19:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
cat /proc/interrupts:
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
0: 50 0 0 0 0 0 0 0 IO-APIC-edge timer
1: 958 0 0 0 0 0 0 0 IO-APIC-edge i8042
8: 1 0 0 0 0 0 0 0 IO-APIC-edge rtc0
9: 1675 0 0 0 0 0 0 0 IO-APIC-fasteoi acpi
12: 12257 0 0 0 0 0 0 0 IO-APIC-edge i8042
16: 24769 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb1, mmc0, nvidia
17: 142 0 0 0 0 0 0 0 IO-APIC-fasteoi snd_hda_intel
19: 0 0 0 0 0 0 0 0 IO-APIC-fasteoi rts_pstor
23: 1937 0 0 0 0 0 0 0 IO-APIC-fasteoi ehci_hcd:usb4
41: 1 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
42: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
43: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
44: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
45: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
46: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
47: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
48: 0 0 0 0 0 0 0 0 PCI-MSI-edge xhci_hcd
49: 19406 0 0 0 0 0 0 0 PCI-MSI-edge iwlwifi
50: 36099 0 0 0 0 0 0 0 PCI-MSI-edge ahci
51: 14 0 0 0 0 0 0 0 PCI-MSI-edge mei
52: 386378 0 0 0 0 0 0 0 PCI-MSI-edge snd_hda_intel
53: 56803 0 0 0 0 0 0 0 PCI-MSI-edge eth0
NMI: 34 5 19 5 18 4 13 4 Non-maskable interrupts
LOC: 77964 17705 161241 14302 187823 16150 56845 12750 Local timer interrupts
SPU: 0 0 0 0 0 0 0 0 Spurious interrupts
PMI: 34 5 19 5 18 4 13 4 Performance monitoring interrupts
IWI: 0 0 0 0 0 0 0 0 IRQ work interrupts
RTR: 7 0 0 0 0 0 0 0 APIC ICR read retries
RES: 13721 7023 304 110 175 110 213 123 Rescheduling interrupts
CAL: 6941 7677 2774 7670 5804 7568 7655 7673 Function call interrupts
TLB: 366 545 268 179 310 272 212 166 TLB shootdowns
TRM: 0 0 0 0 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 0 0 0 0 Machine check exceptions
MCP: 29 29 29 29 29 29 29 29 Machine check polls
ERR: 0
MIS: 0
smartctl --all /dev/sda
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: ST9500423AS
Serial Number: 5WS354LM
LU WWN Device Id: 5 000c50 044bb741b
Firmware Version: 0005DEM1
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Thu Sep 13 15:26:14 2012 CDT
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 0) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No 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: ( 105) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 54715920
3 Spin_Up_Time 0x0003 098 098 085 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1114
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 069 060 030 Pre-fail Always - 10214892
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2030
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 559
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 100 098 000 Old_age Always - 8590065667
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 053 049 045 Old_age Always - 47 (Min/Max 47/51)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 17
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 871
193 Load_Cycle_Count 0x0032 039 039 000 Old_age Always - 122293
194 Temperature_Celsius 0x0022 047 051 000 Old_age Always - 47 (0 17 0 0 0)
195 Hardware_ECC_Recovered 0x001a 113 099 000 Old_age Always - 54715920
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 67229123085518
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1947733828
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2798982459
254 Free_Fall_Sensor 0x0032 001 001 000 Old_age Always - 899
SMART Error Log Version: 1
ATA Error Count: 8 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 8 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
Error 7 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:21:04.438 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:21:04.124 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
Error 6 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
Error 5 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
ec 00 00 00 00 00 a0 00 05:20:59.118 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 05:20:58.805 NOP [Abort queued commands]
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
Error 4 occurred at disk power-on lifetime: 2017 hours (84 days + 1 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
04 71 09 a9 00 80 e0 Device Fault; Error: ABRT
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
a1 00 00 00 00 00 a0 00 05:20:58.761 IDENTIFY PACKET DEVICE
ec 00 00 00 00 00 a0 00 05:20:58.725 IDENTIFY DEVICE
2f 00 01 10 00 00 a0 00 05:20:58.724 READ LOG EXT
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
61 00 08 ff ff ff 4f 00 05:20:58.724 WRITE FPDMA QUEUED
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% 6 -
# 2 Short offline Aborted by host 90% 1 -
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.
smartctl --all /dev/sdb
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.3-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M6
Device Model: SAMSUNG HM320JI
Serial Number: S16LJF0QB02815
LU WWN Device Id: 5 0f0000 001202815
Firmware Version: 2SS00_01
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 0
Local Time is: Thu Sep 13 15:27:10 2012 CDT
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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
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: ( 110) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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: ( 110) minutes.
SCT capabilities: (0x003f) 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 0x000f 100 100 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0007 252 252 025 Pre-fail Always - 2562
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 810
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 4842
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 440
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 154
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 71
194 Temperature_Celsius 0x0022 073 073 000 Old_age Always - 55 (Min/Max 17/55)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 1
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 252 252 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x0032 252 252 000 Old_age Always - 0
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 534
225 Load_Cycle_Count 0x0032 077 077 000 Old_age Always - 236803
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
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.
Last edited by johni (2012-09-16 00:46:54)

It appears my drive one really is failing. It was the first drive and not the second making the loud head seek sound. I borrowed another drive from a friend, and copied my drive one to it. No problems with the new drive in place.

Problems with build in wifi card in DV6-2190us.

Hi am trying to see if someone can help me out with a problem am having with my WIFI and also LAN on my laptop.
The problems am having is with connectivity and speed on WIFI and also problems connecting to a network with a Ethernet cable.
The problem am having with my wifi is when trying to connect to a network it takes me about 5 to 10 minutes just to try to connect to the network and once connected it will continue to say unidentified network and it will take 5 to 10 minutes to connect to the internet. Once connected to the network and the internet the connection will start fast and slow down to a crawl even do am 10 to 20 feet away from the wireless router and I have full bars. After the connection slows down I will get disconnected from the network and it will take me 10 to 20 minutes to get back on it.
Also when I try to connect to the network using a Ethernet cable I will get connected but if I unplug the cable and try to connected again I won't be able to connect to the network or the internet and I would have to restart the laptop with the cable plugged in.
All of the drivers on the laptop are up to date and also windows is up to date I really don't know what's going on.
I have formatted and installed Widows 7 done all of the updates I have also updated all of the drivers for the laptop but the problem continues to come up.
After talking to some of my IT friends we removed the build in wifi card from the inside of the laptop and changed it with a wifi card of a same model laptop to rule out problems with the card, but the problem continues to happen with the new card installed on the laptop. The card that came out of the laptop with the wifi problems was installed to the second laptop and the wifi problems came up but after installing the original wifi card the problems went away.
The thing that trying to figure out is why the card that came out of the working laptop won't work correctly on the laptop that's having problem with.
If anyone has any ideas on what maybe causing the problems please reply to this post I really need to have this problem fix before I start taking online classes.
Thank you for taking the time to read this post.
Laptop information.
DV6-2190us
Windows 7 64bit Home SP1
i7 1.60
Ram 8gb
AVG Pro 2012

You are posting on an iMac forum. I'd recommend posting a MBA forum, however I think you best bet is taking it into your local Apple store or AASP to determine if the Wi-Fi adapter is damaged and if it is then checking to see what options you have.

Problem with second display in premiere CS5

Hi. I have a problem with external device, I have Mac Pro with ATI radeon HD 5770 and two displays 24 LED display that is primary and second 27 LED cinema display, in Premiere on external device only none and DV 720 576 and no second display.

That's the thing, Steve. Using the secondary monitor for playback, it should not be able to show any part of the desktop at any time. It should show only black if nothing is playing, or it should show what is playing in one of Premiere Pro's monitors. But never the desktop.

Problems with Second level drop downs

Hi, I'm having problems with the second level of my drop down
menu. It's showing up when you hit the first level. Any ideas what
I'm doing wrong?
http://www.graphicvisionsinc.com/test/

Solved it!
For info, updating from FCS 1.1 to FCS 1.1.1 solved this problem!

Problems with Lexar USH-1 cards?

I have a problem using my new Lexar SDHC USH-I 600x 16GB card. Formatted and used with Nikon D800.
The card seems to work apparently properly in the cam. Inserted in the internal SD-slot of my MacBookPro (purchased March 2012, OS-X 10.8.2) the files can be imported easily and fast using the Finder. Using Lightroom 4.1, however, is inacceptable: If Lightroom does anything at all it takes up to 1 hour to import ONE pic. With my older SD-cards everything works fine - even Lightroom ;-) Does anybody know whats wrong?

Hi wolfgangvogt,
On behalf of Lexar, we are sorry to hear that you are having problems with your new Professional 600x SDHC memory card. Our support team would be happy to help you resolve your issue. Please email [email protected] or call the appropriate phone number:
1-877-747-4031
(US and Canada)
1-208-363-5862
(Outside US and Canada)
Thanks so much!
Best,
The Lexar Team

Cold boot problem with X-FI Fata1ty card... Need serious help!

Hey guys:
I just finished upgrading my computer. Realized that I have a cold boot problem. In order to identify the source of problem. I began the following test.
. Remove everything except, cpu, heatsink, ram, video card. Tried to boot with those devices. => No cold boot problem.
2. Install the rest of the ram sticks (I have 4 x 52 in total). => No cold boot problem.
3. Install the other video card (my setup is 7900gtx in SLI) => No cold boot problem.
4. Install the Creative X-FI Fataty card. => COLD BOOT PROBLEM
Once the computer is shut down via the front power switch on the case, the computer will not boot again. To boot the computer, I need to switch off the main power switch on the back of the psu and switch it back on; then turn on the computer via the front power switch on the case. I tried the problem with and without the sound card. Whenever the sound card is installed. There is the problem. If there is no that sound card in my rig, then there won't be any cold-boot problem.
My rig specs:
DFI Lanparty nF4 SLI-DR Venus
AMD Opteron 65 CCBE 609 - Stock speed
4 x 52 MB G.Skill Samsung TCCD LE 2.85V DDR 400
CPU Cooling - Tuniq tower 20
2 x EVGA 7900 GTX Stock - SLI
3 x WD Raptor 74G RAID-0 SATA (-3) 0000 rpm (System)
x Seagate Barracuda 7200.7 60Gb 7200RPM NCQ SATA - 4 (Backup)
Pioneer Black DVR 0 DVD+/-RW - IDE /0
Lian-li PC-V 200B Plus-2 with little case mod
OCZ GameXstream 600W
Creative Fatalty Sound Card w/ Front Panel
Logitech Z5500 5. speakers
I need serious help. This problem is so annoying.
Tnanks and will greatly appreciate it.Message Edited by White_Hair on 0-27-200605:4 PM

The onboard sound is disabled. Unfortunately I sold the Seasonic PSU to my friend. The OCZ GameXStream is suppose to be the higher grade psu than Seasonic PSU. Also, the cold boot problem only exists if the sound card is plugged to the motherboard. I tried change different pci slot. It doesn't seem to help the problem. Thanks for the reply Message Edited by White_Hair on 2-02-200606:07 AM

UNRECONIZED PROBLEM WITH SB AUDIGY SOUND CARD

Hi, you all. Pls help me with this problem of my SB Audigy Platinum (SB0060). In Windows XP or even Windows Vista, they can find out my sound card as an Multimedia new hard ware, but when I install sound card driver from CD (original CD driver) fail to install and a message like this: "we cannot find any support products in this computer, pls make sure that is is plugged in your computer already...". I am very disappointed with this 'cause i really like the quality of this Creative sound source. Pls help me. Thanks a lot! Pls answer me : [color="#000099">[email protected](PS: THIS CD DRIVER COMES WITH THIS SOUND CARD BOX, AND I TRY TO INSTALL A NEW FRESH WINDOWS WITH STANDING ALONE SOUND CARD WITH NO CONFLICT TO OTHER PCI CARD, STILL FAILED)

. A friend of mine who also has this soundcard, claims he has a Decoder tab in his device controls in audiohq.. But I dont?!?

That is quite odd. Your Audio HQ should look like this: http://img23.echo.cx/img23/8494/hqdecode7kl.jpg. If not, then you should uninstall you drivers (using the CTZAPXX.exe app on the CD) and reinstall them.
2. When I choose to calibrate my speakers -> basic, FL, FR, RL, RR, C plays ok BUT after that a low freq sound plays for 3 secs then my SL and SR starts to play a high freq beeps respecti'vely...
The program does the same thing on my old T5400 and my current Cambridge MegaWorks 550. My brother has the Audigy 2 ZS also and his Logitech Z-5300s do it as well. I think the program is funky, not your speakers.
3. Since I want to enjoy DTS, I downloaded Windvd, cofigured it to 8 channels (7.). But the SL and SR wont play anything... So I tried Windvds test and all goes well until it is SL and SR turn, they dont play anything... Almost the same as the speaker calibration app. BUT note that in the Creative THX setup console everything works well...

Go into the Options for your DVD software (this applies to any player, not just WinDVD) and set it to S/PDIF Passthrough. This will send the digital signal to your card, which will see it and decode it. Setting WinDVD to 7. mode will try to have the CPU decode the signal. If it doesn't work with WinDVD, then try using Media Player Classic 6.4.x.x and setting the decoder settings to Digital Passthrough. Note that you need to make sure the that decoders are enabled in the Audio HQ (for which you may need to reinstall your drivers.
Note: DTS-ES supports 6.. Dolby Digital EX supports 7., I think.

A problem with ALL creative sound cards i am hav

All creative sound cards that i've used, three i think in the past year. SB Li've, SB Audigy 2 ZS, and the Audigy 2 Zs Platinum Pro. Every time i connect speakers or headphones to the jack, i get really REALLY low sound output, also before windows loads or shuts down i hear a "bump" coming from my speakers/headphones.... I have no idea whats going on....
Specs are:
p4. 3.0
DFI Lanparty 875 rev. B
gig corsair pc4000 dual channel
2x raptor raid 0
SB Audigy 2 ZS Platinum Pro
ATI Radeon x800pro
Headphones i use are bose acoustic 2 headphones
Speakers are logitech x-530
If anyone has had this happen to them before or if anyone has any possible remedies for this I would really appreciate, if this doesnt help im done with creative sound cards =/
[edit]: forgot to mention this is only for the audio jacks on the sound card itself, on the ZS platinum pro, when i connect to the jack on the hub, the sound is alrightMessage Edited by mrkuku on 06-2-2005 06:36 AM

figured out my problem, my built in sound card drivers were conflicting with the creative drivers. Thought that if i turned off the built in sound card from bios that i wouldn't need to delete the drivers also. Thanks for any that read this and tried to figure it out. Now its working like a charm.

Weired problem with second X session with the latest Xorg

Hi all,
I'm having a weird problem with the latest Xorg. Normally I have two X sessions open, the second with startx : --1. It used to work with previous version of Xorg. However, with the last update, it's broken. The second X session behaves very strangely: it's like the whole screen is divided vertically into 2 pieces and the right hand piece is moved to the left. As a result, mouse pointer doesn't work. I've tried different WM, DE with the same result?
Anybody encountered this?
Thanks,

Yes'sssss I found the problem. Is a conflict with Mirra Backup Server Software? What I did is that I sync my Aperture Library to my MacMini with Mirra then the problem was the same on the Mini. Then I say let me do a test so I uninstall Mirra and Walaaaaa the problem was Mirra. Now AP is working nice and cool. So I did the same with my MacPro and is working nice and cool. I love Aperture it has very nice tools to work with photos. Know the thing is which program haves the problem Aperture or Mirra. So know I will do a report of this to Aperture Team and Mirra Team. I will be doing some testing on this to see what is the conflict.
Hope this is helpful if somebody haves the same problem.
boricua-macpro

Problems with second standby database

Hello All,
I have oracle 10gr1. 1 primary db and 2 physical standby and 1 is in the same network with the primary and the other is on a remote network. The primary and the standby on the same network is working perfectly well. My problem is with the remote standby. Some log are not being archived. See output below
SEQUENCE# ARC APP
1755 YES NO
1761 YES NO
1772 YES NO
1774 YES NO
1782 YES NO
1789 YES NO
I get this error RFS[10]: "Possible network disconnect with primary database". I think it has something to do with the network connectivity of my second standby and the master db. What parameters should I tweak to avoid this?
Another thing is arhived logs from seq 1728 were not being applied. I tried manually recovering the archive log from 1728 but it says there is an error in the log. I tried getting the specified archive log from the master db and tried recovering it manually but still the same. How would I solve tjhis problem? Would rebuilding the second standby do the trick? Help needed badly.
Thanks in advanced.

Hi,
About seq 1728, if the archive has been lost or alterred, you'll have to rebuild the standby. At least take a backup of the first standby and restore the datafiles at the second standby.
About network connectivity, are you using DataGuard? If so, did you setup the FAL (Failed Archive Logs) server/client parameters on your standby? You can even set your fal_server as being both the primary and first standby..
You should investigate the network connectivity problem with your network administrator. Check alert log and trace files plus sqlnet logs to see when/where/why the communication with distant site fails sometimes.
HTH,
Yoann.

Problems with second hard drive

I bought my PowerMac G5 new in 2005 and about two years after I got it, I installed a second internal hard drive. I didn't have any problems with the drive until about six months ago (which was when I moved, but I'm not sure if that has anything to do with it). Around that point, I started hearing a single, loud click followed by a slight winding down noise. Then, my computer would almost completely freeze. After a few moments, I would hear a bunch of soft clicks and my computer would go back to normal. I figured that it was a problem with one of the hard drives, but I wasn't sure what to do.
Later on, the problem got more severe, lasting more like 30 seconds. When my second drive unmounted during one of these episodes, I shut my computer down, opened the case, took both plugs out of the second hard drive, put them back in, and started up my computer again. After that, my computer was running great again. But, a few weeks later, the symptoms started up again.
So, I've gone through the same cable un-plug and re-plug process whenever the drive unmounts. Sometimes it helps and sometimes it doesn't seem to help at all. Altogether, I think that the second drive has unmounted about five or six times. I haven't had this problem at all with the original hard drive and I haven't noticed any other problems with my computer. (Well, okay, there's the rare occasion when, instead of going to sleep, it turns the screen black and puts the fans on full blast.)
Could the drive itself be going bad and it has nothing to do with the cables? I have a utility installed that always monitors the SMART status and it hasn't reported any problems. Are there any other troubleshooting steps I should take? Any advice would be appreciated. Thanks!

Before I bought DiskWarrior, I thought I'd try some troubleshooting with the software I have on hand. But while I was doing that, the problem got worse. Now, I'm having major problems just getting the computer to boot. I'll give you the rundown on what's happened. It goes through a few boneheaded twists and turns and goes on at great length, but I thought I'd relate it all in the hopes that someone can see a likely pattern.
My first thought was the Apple hardware test, which I had thought was on the Mac OS 10.5 install DVD. So naturally, I didn't see the hardware test listed under Utilities. But while I had it up, I used Disk Utility to do repairs on both hard drives (checking both the disk and permissions). It found no problems on the 2nd hard drive, but found a few errors with "leaves" on the booting drive. It also found a bunch of issues with the permissions, but I don't think it was anything out of the ordinary.
Just for the heck of it, I asked it to run the repairs again. Not long into that, I got what I think is a kernel panic (overlaid message saying I needed to restart my computer in a few languages). It also sped up the fans.
I pushed the power button to shut it down, then started it up again. I heard the startup chime, then nothing but a black screen and the ol' hyperactive fans. I went through that several times before I was finally able to boot from the DVD again. Then, I changed the startup disk back to my usual boot volume and restarted. I had to go through the black screen and insane fans several more times before I could boot normally.
Next, I thought I'd try OnyX to see what it could do. Which might not be much, but I had it repair the disks again and also had it run the daily, weekly, and monthly maintenance scripts.
I checked into the black screen & hyperactive fans booting problem elsewhere in the forums, and saw that it was recommended to run the Apple hardware test and also found the correct procedure for doing so, which was to insert the PowerMac G5 install disc (not the Mac OS X upgrade DVD) and press Option when booting. I loaded the disc, restarted, and held down the Option key, but before I could get anything to actually load, I had several more sessions with the black screen of fans.
Regarding that boot problem, I've sometimes seen the red light inside the case turn on almost immediately after I turn on the computer. Other times, it will not light up by itself. But, when I hold the power button in to shut it down, the red light briefly turns on before the unit shuts down. I've also noticed that the light on the Caps Lock button is coming on and staying on when I'm trying to start the computer.
So, after several tries, I checked my G5 User's Guide and it said to disconnect any external devices before trying the hardware test. I had a USB thumb drive plugged in and a FireWire drive hooked up for Time Machine backups, so I took both of them out. Once again, I tried starting up with Option held down and this time, it worked. The fans started running at full blast after I selected the hardware test, which I hoped was normal. So, I asked it to run the extended test and it found no problems. I restarted my computer without reconnecting anything and, at least for now, it's working normally.
Any new thoughts?

Problems with second 7970 Lightning Card?

Similar Messages

Maybe you are looking for