T500 Updating SATA Driver Fails

Thanks, I would like to try different intel drivers in an effort to maximize SSD performance. There is at least 2 options under storage
in the T500 driver matrix.
On my W520, I get an option in device manager on what driver to install.
W520 4270-CTO | 2720QM | 16 GB RAM | Quadro 1000M | BIOS 1.34 | PwrMgr 3.66 | 256 SSD

Similar Messages

Update graphic driver fails

Hello,
Three days ago i've updated my system via "Pacman -Syu". By then there weren't any problems, but now there is maybe a too big problem. I really don't know what it is and how i can describe it, so I've uploaded a screen:
If I restart the system, there isn't the error any more but if I watch a video it reappears. There is always a video in the "background". It seems like it's burned-in or foggy.
Do you have any ideas how i could solve this problem?

Maybe it's related to https://bbs.archlinux.org/viewtopic.php?id=113368&p=2
What graphics card do you have?
Last edited by karol (2011-03-03 21:49:08)

Cannot update Graphics Driver

I have an HP Envy 4 1030-us. Intel Graphics HD 4000. I have even gone to Intel's forums for help.
1) If I try to install the updated graphics driver - fails
2) Uninstall old graphics driver, per Intel forum advice, restart computer, on restart old driver installs automatically.
3) Uninstall old graphics driver, try to install updated driver, fails, restart, on restart old driver installs uatomatically.
Please don't suggest I have the wrong driver. Any other suggestions warmly welcomed.

Hi @DavidENJ ,
Thank you for your inquiry, I will do my best to assist you.
I understand that you are unable to install the updated driver for the Intel Graphics HD 4000. Intel advised you to uninstall the driver and then restart before installing the new driver but you were unsuccessful.
I would try deleting the driver not uninstalling. Once deleted it cannot reinstall it as it is no longer there.
The latest supported driver for Windows 7 and your notebook is sp58046.exe version 8.15.10.2712.
If you are trying to install a driver from the Intel website, it may or may not work correctly. Downloading or Updating Software and Drivers for HP Computers.
If you are still having an issue with installing the driver, try installing it in safe mode with networking. Entering Safe Mode (Windows 7)
I hope this helps.
Sparkles1
I work on behalf of HP
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 right to say “Thanks” for helping!

Update BIOS SATA drive

I have recently purchased new PC (Hopefully main spec in sig).
The BIOS recognises 4GB of RAM whilst Vista Ultimate only recognises 2GB.
I am trying to update the DIOS using a USB floppy drive and have copied the files across to c:\Temp as suggested in the accompanying instructions.
However, on booting into DOS using the boot disk I am unable to access the c: drive.
I don't want to copy the BIOS update onto the floppy and update from there due to the stark WARNING!!!! in the readme but I want to update the BIOS...
Any suggestions as to a reliable way to get the SATA drive recognised and update the BIOS safely?
Thanks
CBF... noob!

Quote
On boot the motherboard is making a series of 3 slow(ish) beeps.
How many beeps do you get, when you unplug all USB-devices?
Could be USB Status beeps as well.
Quote
Using Vista 32 bit, I am aware that I will not get the full allocation of RAM but have read reports that I should be getting 3-3.5GB available within Vista.
What I fail to see is, how your problem is a BIOS issue. You said, that BIOS shows 4 Gb, right?
In any case, if you really think that you need a BIOS Update use the Forum Flashing tool (use link above).
Latest BIOS can be found here:
http://global.msi.com.tw/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1168

How do I re-download podcasts? My external hard drive failed and I can't figure out how to download them again in the updated iTunes.

How do I re-download podcasts? My external hard drive failed and I can't figure out how to download them again in the updated iTunes.

The Time Capsule drive is a network drive. You have to mount it on the desktop before you will be able to drag/drop files onto the disk. More tips are in this thread:
https://discussions.apple.com/message/17312017#17312017
.....and then delete them from the Mac to free up space?
The Time Capsule was designed for your backups.
If you move a file to the Time Capsule drive and delete the file from your Mac.....you have no backup.
Your only copy of the file will be on the Time Capsule drive. I would only do this with files that I could afford to lose.
All drives fail. When.....not if....the Time Capsule drive has a problem, you will lose your data.

Replacing a failed disk (SATA drive) on UCCX (MSC-7825)

Hi,
I discovered a failed disk drive on the UCCX server (non-HA mode). Now, my task is to get this disk replaced. What are the typical steps to follow and what precautions should I take care besides backing up the config data)? Since thsi would be my first time doing this, I was hoping for some detailed steps to follow while doing this replacement.
The Model we have is the MCS-7825 -H4 CCX - premium. I have received the HD form HP.
I have found only data sheets on the cisco portal & hence was wondering if there is any other guide that can walk me through the steps.
Thanks,

This is pretty standard hardware "stuff".
I suppose the SATA drives are configured in a RAID1+0 array through HP's Smart Array controller. You can open the HP Smart Array tool in Windows and ask it to show you the status. If it indicates the drive has failed, it will help you replace it and mirror up while the box is running.
This is a little scary if you have never done it, so I appreciate your caution.
The best thing to do is to try this on your lab machine. There is NO substitute for experience at this level.
Regards,
Geoff

Oracleasm update-driver failed in OEL 6

Hi ,
I have a problem with oracleasm update-driver command.
I have OEL 6 installed in my machine.
When I entered command : rpm -qa| grep oracleasm it is showing me the below output :
oracleasm-support-2.1.5-1.el6.i686
But after that, when I issued command oracleasm update-driver , it shows me below error :
Kernel:          2.6.32-71.el6.i686 i686
Driver name:     oracleasm-2.6.32-71.el6.i686
Driver for kernel 2.6.32-71.el6.i686 does not exist
As a result of this my ASMLib driver is not Initializing properly. Below is the details of that :
[root@abhishek]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface [oracle]:
Default group to own the driver interface [oinstall]:
Start Oracle ASM library driver on boot (y/n) [y]:
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
*Initializing the Oracle ASMLib driver:                     [FAILED]*
Can anyone please help me to resolve this ?
Thanks
Abhishek

Hi Dude,
Thanks very much for your detailed explanation.
I have successfully updated UEK kernel by following your mentioned steps.
But now I am facing another problem.
I have done upto steps below :
yum install kernel-uek kernel-uek-devel kernel-uek-headers kernel-uek-firmware+
*# reboot*
But when I am trying to enter into that kernel , it is showing dark screen with a arrow pointer .. I think the video driver is not updated for that kernel.
Let me elaborate the scenario :
When I boot my machine , it shows 2 options during boot :
*1. Windows XP*
*2. Other*
When I pressed enter into the Other it is showing 3 more options :
*1. Oracle Linux Kernel - 2.6.32-100.34.1.el6uek.i686*
*2. Oracle Linux Kernel - 2.6.32-131.0.15.el6.i686*
*3. Oracle Linux Kernel - 2.6.32-71.el6.i686*
When I choose 2nd and 3rd option it is showing Gnome GUI properly , but when choosing 1st option it is not showing any Gnome GUI , Just a dark screen and an arrow pointer on that. I can move that pointer here and there over the blank screen. So it is understood that machine is not getting hanged , only display is not coming ( please verify whether my understanding is correct or not ).
Untill the GUI comes, I am not able to test the rest of the commands you gave. So will you please update the solution with detailed steps.
One more information i am pasting here. The output of lsmod command ( running from the kernel : 2.6.32-131.0.15.el6.i686 )
[root@abhishek ]# lsmod
Module                  Size Used by
fuse 56128 2
autofs4 21604 3
sunrpc 197485 1
p4_clockmod 3135 1
ipt_REJECT 1905 2
nf_conntrack_ipv4 7700 2
nf_defrag_ipv4 1013 1 nf_conntrack_ipv4
iptable_filter 2147 1
ip_tables 9541 1 iptable_filter
ip6t_REJECT 3961 2
nf_conntrack_ipv6 7117 2
nf_defrag_ipv6 9847 1 nf_conntrack_ipv6
xt_state 1006 4
nf_conntrack 66010 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
ip6table_filter 2219 1
ip6_tables 10809 1 ip6table_filter
ipv6 266112 29 ip6t_REJECT,nf_conntrack_ipv6,nf_defrag_ipv6
dm_mirror 11652 0
dm_region_hash 10063 1 dm_mirror
dm_log 8520 2 dm_mirror,dm_region_hash
uinput 6218 0
ppdev 7335 0
parport_pc 19348 0
parport 31019 2 ppdev,parport_pc
ir_lirc_codec 3920 0
e100 28774 0
lirc_dev 14570 1 ir_lirc_codec
mii 4289 1 e100
ir_sony_decoder 1817 0
ir_jvc_decoder 1974 0
ir_rc6_decoder 2262 0
saa7134 143379 0
ir_rc5_decoder 1878 0
ir_nec_decoder 2294 0
v4l2_common 8534 1 saa7134
videodev 65768 2 saa7134,v4l2_common
rc_core 16553 7 ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,saa7134,ir_rc5_decoder,ir_nec_decoder
videobuf_dma_sg 8614 1 saa7134
videobuf_core 16927 2 saa7134,videobuf_dma_sg
tveeprom 11298 1 saa7134
sg 24778 0
microcode 12419 0
i2c_i801 9473 0
iTCO_wdt 9644 0
iTCO_vendor_support 2382 1 iTCO_wdt
snd_hda_codec_realtek 244000 1
snd_hda_intel 21424 2
snd_hda_codec 73949 2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 5320 1 snd_hda_codec
snd_seq 46091 0
snd_seq_device 5354 1 snd_seq
snd_pcm 67225 2 snd_hda_intel,snd_hda_codec
snd_timer 18308 2 snd_seq,snd_pcm
snd 52754 12 snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
soundcore 6460 1 snd
snd_page_alloc 7080 2 snd_hda_intel,snd_pcm
ext4 327734 2
mbcache 5918 1 ext4
jbd2 73784 1 ext4
sr_mod 14219 0
cdrom 34036 1 sr_mod
sd_mod 34239 4
crc_t10dif 1191 1 sd_mod
pata_acpi 2487 0
ata_generic 2555 0
ata_piix 19080 3
i915 381685 2
drm_kms_helper 31540 1 i915
drm 173379 3 i915,drm_kms_helper
i2c_algo_bit 4664 1 i915
i2c_core 25799 9 saa7134,v4l2_common,videodev,tveeprom,i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video 16662 1 i915
output 1779 1 video
dm_mod 63127 2 dm_mirror,dm_log
Thanks in advance.
Abhishek
Edited by: Abhishek on Jun 4, 2011 8:45 PM
Edited by: Abhishek on Jun 4, 2011 8:50 PM
Edited by: Abhishek on Jun 4, 2011 8:52 PM

Orig 250Gb drive failed - Installing Barracuda 7200.12 SATA 1.5 TB drive

My original 250Gb hard drive failed and I am going to install a Barracuda 7200.12 SATA 3Gb/s 1.5 TB Hard Drive (ST31500341AS). The old drive isn't completely dead. When I want to the apple store they were able to boot off of an external drive and my drive (after a while) mounted. I was able to transfer some of my files onto a second (500gb) drive that I have installed. During the transfer of one of the largest folders, the original 250Gb drive disconnected/was no longer mounted.
Can I keep my original 250 Gb dive in my Mac Pro, install OS X 10.6.x on the new 1.5 TB hard drive, and then see if the original drive mounts so that I can try to recover my files? Will I have issues having the OS installed on the 2 drives? Does it matter which bay I install the new drive?

You can install the OS to any of the internal drive bays, makes no difference.
Because a drive that is failing can indeed cause problems for the SATA controller, I wold remove the bad drive when I install the OS. Once I have everything installed and working, I wold then shutdown and put the bad drive back into an empty bay, restart, and see if I cold access the bad drive.
Tom
Message was edited by: Tom Nelson1

I updated iPhoto and now can not burn a cd on iPhoto. I am getting error message: The burn to the SuperDrive drive failed. The disc drive didn't respond properly and can't recover or retry.

I updated iphoto 9.4.3 and now it will not allow me to burn pictures on disc. I am recieving the follwing message:
The burn to the SuperDrive drive failed. The disc drive didn’t respond properly and can’t recover or retry.
I have tried to do a SMC Reset and PRAM reset and it still will not work. Before the update I was burning pics onto the same dics with no problem.
Any suggestions on what to do?
Thanks!

Hey MGRUBE,
Thanks for the question. I understand you are experiencing issues with burning a disc. The following resource may help to resolve your issue:
Disc Burning Quick Assist
http://support.apple.com/kb/ht1152
Thanks,
Matt M.

Nx 6310 250 GB sata replacement hard drive failed three times.

Replaced 60 GB OG. hard drive with a 250 GB. sata drive. Drive worked fine for 6 months and died. Replaced under a warranty at no charge new one lasted about 8 months and died last one lasted 3 months and is now dead. I read in the hp nx6310 info that 120 GB is the largest sata drive. Is that because that was the largest drive of the day or is it possable i'm over heating the larger drives ? nx6310 win xp pro 250 GB. 5400 rpm sata HDD. 1gig mem.
This question was solved.
View Solution.

Take a look at the drive that they give you and see if they say recertified. Are you still under warrantee?
Reminder: Please select the "Accept as Solution" button on the post that best answers your question. Also, you may click on the white star in the "Kudos" button for any helpful post to give that person a quick thanks. These feedback tools help keep our community active, so you receive better answers faster.

T61 DVD/CD-RW drive fails to read and crashes

Hello Everyone, I hope people still visit this area of the forums!
I've highlighted and bolded the symptoms to make them easier to find.
I recently purchased a T61 6457-C15 on eBay, and have been in the proccess of setting up and customizing it to suit my tastes. When I recieved the laptop, it looked as though Windows had been restored to original factory state, plus some free software, so I proceeded under that assumption. First I used Windows Update to download all the updates that it could find including IE8. I wanted to have an anti-virus program running on my computer before I used a browser to access the internet. I ran IE8 and went straight to the Microsoft Security Essentials website and downloaded the Install program. At this point I tried to remove the pre-installed and expired Norton Internet Security using the built-in uninstall, but it failed. A message box popped saying that I needed to put the Norton installation disc in the CD-ROM drive so that the uninstall program could find a Norton support file. My computer did not come with any discs, but my mothe had bought Norton 2008, so I took that disc and put it in the drive. The drive started spinning right away, and the uninstall program found the file it was looking for in a few seconds. The support file directed me to the Norton website to get their removal tool, which removed Norton from my system in short order. Afterwards, I ran the Microsoft Security Essentials install program and got MSE running on my computer before doing anything else.
Then I went to the Lenovo support website and had it auto-detect my system. That took me to the support page for my system, where I went to the "Downloads and Drivers" page. I downloaded Access Connections and ThinkVantage Toolbox for Vista 32-bit (my OS is Vista Business 32-bit). I then used Lenovo System Update to retrieve all the updates it deemed neccessary from Lenovo, including those for itself and system components, both software and firmware. There were 35 or more updates suggested, and I trusted the software, so I started downloading them all. I'm not sure, but I think that a DVD/CD-RW drive update was included in the list, but I can't remember if it was auxiliary software, drivers or firmware. After Lenovo System Update was convinced that it had all the neccessary updates, I downloaded Revo Uninstaller and set about removing uneccassary and unwanted programs from my computer and trimming the startup list. I did not touch any Windows or ThinkVantage components, and I searched each program online, so I'm sure that I did not delete or disable any drivers or system files, or anything from Lenovo. I mainly removed Apple products and non-functional software from my system, including an integrated camera driver (my system does not have an integrated camera) and third-party programs that were already missing files or otherwise inoperable when I got my computer. Up to this point I had been using a gigabit ethernet connection to download software; I had not used the DVD/CD-RW drive except for the one time I specified earlier.
Now that I had my system set up to my liking, including personalization and power settings, I started to install my first program: Command & Conquer the First Decade from a DVD-ROM. When I put the disc in the drive and closed it, it took a few seconds for the drive to spin up, and once it did, it was constantly running at high speed and I could hear the reader constantly moving back and forth quickly. After a few minutes the disc's install menu finally appeared, so I clicked on the install button. I waited several minutes but nothing happened, so I tried to view the contents of the drive by going to My Computer > DVD/CD-RW drive (D, right clicking and selecting explore from the menu options. When I did that, the address bar of the My Computer window started to fill up with a dark gray progress bar and said "loading (D", I think with the drive or disc name after it. After it took several minutes to fill completely, nothing happened. I waited a few more minutes to see if anything would change, (nothing did,) I clicked on the X button in the top right corner of the window to close it. A few minutes and clicks later, the My Computer window was labeled as (not responding), and the window itself became grayed-out. I started Task Manager and tried to close the My Computer window, but the entire Windows Desktop disappeared along with it, saying that it would attempt to restart. Even Task Manager became non-responsive and quit after closing My Computer. After a few minutes of staring at my background (and nothing else), I ejected the disc, and Windows Desktop reappeared immediately and acted as if nothing had ever been wrong.
I checked Device Manager, but neither the DVD/CD-RW drive nor any of the ATA controllers were flagged; in fact they all said they were working properly with up-to-date drivers. I ran the ThinkVantage Toolbox diagnostics on the drive using a data CD, a music CD and a different DVD-ROM, but in each case the drive failed the tests and a message box popped-up saying that the discscould not be read because they were scratched or there was a hardware problem. I checked the discs both before I put them in and after I took them out, and they were not scratched; also, all of the discs are publisher-manufactured from a software or music company. I restarted my computer, booted the Rescue and Recovery option and Ran PC-Doctor from there. I ran the same drive read tests with the same failure results. The entire time the drive was behaving the same way it had when it first failed to read a disc. Next I removed and cleaned the drive both inside and out with a can of compressed air; I also cleaned the ultrabay itself. Finally I tried fixing the problem with Microsoft Fix It, but when it automatically ejected the drive and i put a disc in, the disc became trapped in the drive and Windows froze up like before. I had to restart Windows twice (once with a BSOD) in order to get the disc out. When the disc was removed the computer went back to normal operation once again.
Please help me, my DVD/CD-RW drive is a Matshi ta UJDA775, my operating system is Windows Vista Business and my T61's model number is 6457-C15. I have tried all the troubleshooting fixes and none have worked. I have tried updating drivers and using diagnostic software and they have not worked. I have tried disabling drag-to-disc burning and it has not worked. I have treid removing and cleaning the drive and that has not solved my problem. I did notice that the driver for the "Intel(R) ICH8M-E/M SATA AHCI controller" is the only related driver that can be rolled back, so maybe that might fix it. I'm also wondering if a firmware change caused this, and if so, if there is any way I can undo that. The only other fix I've heard of that I haven't tried is editing the registry, but I'm hesitant to do that. I haven't tried booting from the CD drive because I have no bootable CDs and I'm worried that my computer might get stuck in that mode. I'm hoping that someone can tell me what I can do to try to fix this problem, preferably without wrecking my computer. Thank you for taking the time to read my post.
P.S. Just adding a note; I went through both the Microsoft and Lenovo Update histories and the only related updates I could find were: ThinkPad BIOS update, Easy Eject utility, Intel Matrix Storager Manager driver for Windows (32-bit), and maybe one of the two Intel Chipset Support for Vista updates. I tried rolling back the AHCI driver but it had no effect.
Solved!
Go to Solution.

Well, my problem is fixed, and here's how. I had some trouble figuring out how to contact Lenovo technical support; online options directed me to the IBM support website, which was clearly designed for businesses. Selecting the "Call technical support" option on the Lenovo support website and then choosing my country gave me a 24/7 hotline number. After waiting about five minutes on hold, a nice young fellow by the name of "Tyrese" answered (I maybe misspelling his name), but the connection was so bad that we could barely hear each other. Although he semed eager to help, when I told him my problem the first things he suggested were simple, like cleaning the drive, However, when I told him all of my efforts, described above, to fix the problem myself and read him the log from the Rescue and Recovery diagnostic program, after he checked the error codes against his computer database he promptly replied that the only fix was to send out a new drive. I was happy to have gotten such a successful resolution to a support call in less than fifteen minutes; apparently, all the work I had done trying to solve the problem myself had paid off in a way. Unfortunately, although I had tried to spell out my address for him, some of it got left off of the address label, which caused some trouble in receiving the new drive. Once I got it, I installed it using the uninstall & remove (old drive), shut down, start up, insert & install (new drive) method that I referenced earlier in this topic. I've been using the new drive since then without any trouble, so I guess that the only fix was to replace the drive. Also, I noticed that the new drive was a Hitachi, perhaps a T400/410 or T500/510 Ultrabay Slim drive, which should help me avoid the problems that other users were having with the older Matshi-ta drives. I hope this description helps anyone else having a problem with the optical drives on the T61/61p.

R400/T400/T500/W500: display driver "amdkmdap" crashes

Executive summary: All current Lenovo ThinkPads with switchable graphics (R400, T400, T500, and W500) have usability issues in connection with Vista and the use of external monitors. For more than half a year, users were plagued by frequent Windows crashes. During that time frame, Lenovo did not comment on the various available reports and complaints. By the end of April 2009, Lenovo resolved many issues by releasing a new official driver. Though several problems, including severe ones, remain as of today. Lenovo has said to be actively working on the remaining issues (without outcomes so far).
Important information for affected users: If you're having one of the issues reported here, then Lenovo advises you to call your local Lenovo Support. Demand that a case is submitted to hardware engineering. In particular, you should ask for "a CMVC case to be created and escalated". Using these "code words" ensures that your case is properly addressed.
Old problem description
On Vista 32 and Vista 64, the ATI display driver "amdkmdap" crashes when an external monitor was active before OR an application (game) using DirectX technology is used. The user typically receives a couple of so-called "Timeout Detection and Recovery" (TDR) messages from Vista:
(Click here for an explanation of the message from Microsoft)
Sometimes, amdkmdap crashes several times in a row. Then Windows crashes with a so-called "BSOD", likely resulting in data loss. Typically, Windows detects "atikmpag.sys" as the crashing driver. Sometimes, also an instantaneous reboot happens independent of prior TDR crashes. In such a case, no BSOD is displayed.
The following movie illustrates the phenomenon: http://www.youtube.com/watch?v=LBX9QsCmrpY
This behavior above has been confirmed for the following ThinkPad models: R400, T400, T500, and W500 (see below). Problem reports indicate that the symptoms are often related to playing games and/or the notebook being docked and the external monitor being connected via DVI.
Though, the presence of these two conditions is not necessary to trigger the driver crash:
There are reports where no dock was involved and the external monitor was connected directly to the notebook's VGA port.
Furthermore, there are reports where the notebook was docked and an external monitor was connected to the DVI port.
So far, there has been no report relating to a monitor being connected to the Display Port which is available on some models. (Possibly because this port is not used.)
There are a few reports where neither a dock nor an external monitor was involved.
Playing certain games reliably triggers the crash.
Steps to reproduce
While intially (around September 2008 - October 2008) the crash could be triggered easily, the situation is now (December 2008) more complex. The crashes do still occur, though there is no clear pattern anymore. According to various reports, the display driver crash can be triggered as follows:
Resuming from standby
Watching a DVD.
Playing one of these games: Fallout 3, Bioshock, Team Fortress 2, Knights of the Old Republic.
Arbitrarily during normal work. On a normal working day, the problem occurs at least once.
Further issues
Here are more issues which seem to be related. More information can be found in other posts of this thread:
The notebook display and/or the external monitor runs at a low resolution after resuming from standby.
After the login both monitors flicker while adjusting the resolution of the monitor.
The external monitors cannot be activated using Presentation Director.
The external monitor is blank after docking or undocking.
There are some reports about display driver crashes on machines running Windows XP.
The switchable graphics drivers limit the useable RAM under Vista 32 to 2.5GB (i.e. 500MB-1GB less than usual).
Workarounds
Lenovo has released a new "tip" document which provides a link to a new driver. Get it here but be sure to read the instructions!
(Old tips follow below the line. Consider them as obsolete.)
Here are some tips which might make the problem occur less often. I have not tried all of them. Though, A. and B. have improved the situation for me; your mileage may vary.
A. If you do not have to use an external monitor, then switch to Intel graphics for time being.
Otherwise:
B. Make some changes to your system:
Disable Aero.
Create a new profile in the power manager with the following setting: When running on AC, turn off the monitor after 40 minutes. (Thereby, the notebook goes less often to standby.)
Install the newest graphics drivers.
Install the newest BIOS.
Install the newest Hotkey utility.
Install the newest drivers.
C. Disable the switchable graphics in the BIOS setup and install modded drivers from ATI (see zilla's post in this thread for instructions).
The last workaround (C.) has been confirmed to work reliably by several users. Though, thereby you use drivers which have not been tested by Lenovo. It's possible (but not very likely) that damage results by doing so. Also, it might be difficult to install a future Lenovo driver which resolves the issues reported here. Finally, you cannot use the power-saving Intel graphics. Thus, you should only use this workaround if you know what you are doing.
The programs can be downloaded from the following locations. Notice that System Update does not always offer you immediately the lastest versions.
R400 and T400 users: Go here.
T500 and W500 users: Go here.
User opinions
"Is there any chance this will be fixed, or should I just get used to my "workstation-class" machine crashing regularly?"
"I [am] thinking about to sell my w500 if this problems won't be fixed in the next weeks."
"I've got a T400 w/ Vista 64 and I'll say the Switchable drivers on it S[**]K bad."
"Unfortunately for Lenovo, our IT Manager is at the point of a awarding a new and rather substantial Enterprise Agreement for our whole organization's PC's, which included a rollout of many new PC's for 2009. The contract was going to go to Lenovo. He mumbled something about HP when I asked him about the state of affairs with my PC... [O]ur firm's IT Manager decided to return all the faulty Lenovo's for a refund and would replace them with HP's."
"Is someone from Lenovo paying attention[?]"
"i'm getting angry with ati and lenovo."
"there are no new drivers and no ETA for a fix."
"ThinkPads are supposed to be good, so you'd think there wouldn't be a problem like this."
"honestly it is completely unacceptable for lenovo to have done nothing this long. I paid extra to get the ATI card, and now I can't hook up my laptop to an external monitor without it crashing. I will probably end up selling the laptop soon since using an external monitor is extremely important to me and lenovo doesn't seem to care about fixing the situation."
Update:
- Lenovo support has informed me today (2008-10-24) that they are working on the problem.- changed subject (was: Major troubles with DVI-port and a T400) to reflect new information.- changed message body to reflect new information
- See MIGR-70490 (dated 2008-09-21) for an official statement from Lenovo.
- 2008-11-15: The problems are still present and there is still no ETA for a fix.
- As expected, also R400 models are affected. See below for reports.
- 2008-11-26: Still no word from Lenovo when the problem will be fixed. Added information on (partial) workarounds.
- 2008-12-03: Lenovo updated MIGR-70490. Though, problems persist.
- 2008-12-13: Updated problem description on the basis of new reports.
- 2008-12-16: Updated problem description on the basis of new reports.
- 2009-01-07: Updated problem description on the basis of new reports. Still no word from Lenovo. I called Lenovo's customer service in the Netherlands and was promised to receive a callback. Though, so far they didn't (want to) get back to me.
- 2009-01-08: Updated workaround description on the basis of new reports.
- 2009-01-10: Updated executive summary on the basis of new reports.
- 2009-01-14: Updated problem description on the basis of new reports (movie).
- 2009-01-19: Updated workaround section.
- 2009-01-21: Happy birthday MIGR-70490! It's now 4 months. Updated workaround section. I called Lenovo's customer service in the Netherlands again.
- 2009-01-22: Added section "User opinions"
- 2009-01-23: Updated problem description on the basis of new reports.
- 2009-01-24: Small updates.
- 2009-02-02: Small updates.
- 2009-02-03: Changes to section "Executive summary". Added section "Important information for affected users".
- 2009-02-04: Update to section "Credits".
- 2009-02-19: Update to section "Credits".
- 2009-02-27: Quick update to "Executive summary" and "Workarounds".
- 2009-03-10: Quick updates to section "Executive summary" and "Important information for affected users".
- 2009-03-21: Quick update to "Executive summary"
Credits
Workaround "Aero off": Bubbi, TonyK
Workaround "Modded ATI drivers": jtull89, zilla
Thanks to Mark_Lenovo and Confederate for their work behind the scenes
Thanks to feedback from: ajgiordano, Andy_7575, ben2e, brettgri, bri0831, Brimstar, Bubbi, CodeNameSly, cpueschner, dandill, diablo2man, ewilansky, gaccounts, gan, gandalf7, golffreaksi, Homer, hubertlam, Jiraiya, johnsonjf, jordan_moss, jmark, jtull89, kbarina, lenardg, lukest, misitmichaelf, mlb, MMetts, ojisan, pendaluent, Qot, rmccallen, sarnil, shaofengsd, Snakecharmed, StephanK, tarzan23, Texas1040, TheNewNumber2, TonyK, trickyDick, vedman, Vitalus, Waschbecken, xpnet, xrafx, zilla, ZPrime
(Please don't expect that this list is complete. I am not paid to keep it accurate and complete and, actually, I have a life besides writing about Lenovo's problems. )
Original post
Hi there!
I have major troubles using a Dell 2709W monitor with my T400.
The notebook is attached to a Advanced Mini Dock to which the monitor is connected via DVI.
The problems are as follows.
A. Activating the external monitor often fails
Steps to reproduce:
1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T40
2. Start Windows and make sure that the T400 is running on the ATI card.
=> Dell monitor enters power saving mode because no signal is coming.
3. In Windows use either the Presentation Director, Windows, or the ATI tools to activate the Dell monitor.
Expected result: The Dell monitor is activated and the Windows desktop is shown on it.
Actual result: It takes 1-3 seconds for the Dell monitor to display something. The monitor shows the Windows desktop for a short period. Then it's black again and the monitor returns to the power saving mode .
Analysis: It seems that the Presentation Director, Windows, or the ATI tools (or more aptly, I guess, the ATI driver) expect a quick response from the DVI-port that a monitor is present. If they do not receive the response, the DVI-port is deactivated again. Since the monitor is too slow to respond and enters the power saving mode too quickly, the monitor can hardly ever be activated.
Suggested change: Change these tools (or the ATI driver) so that they wait longer for a response on the DVI-port.
B. Resuming from monitor sleep causes Windows to fall back to a low resolution if the Dell monitor was activated before
Steps to reproduce:
1. Attach a Dell 2709W via DVI to an Advanced Mini Dock which is connected to a T400
2. Start Windows and make sure that the T400 is running on the ATI card.
3. Select the Energy Star profile
4. Activate the Dell monitor
5. Don't use Windows until the notebook display and the Dell monitor are set to sleep by Windows.
6. Wake up the displays (e.g. by pressing some keys)
Expected result: Both displays are run in the display mode as before.
Actual result: The Dell monitor still sleeps. The notebook displays is run at a lower resolution (I guess 800x600). The Windows login prompt is not visible and it has to be guessed that it is shown. Though the typical Windows login background is visible. If the password is entered, then Windows can be used again. Though, the resolution is still low and the Dell monitor still sleeps.
Analysis: It seems that by sending the Dell monitor to sleep, the monitor deactivates the DVI-interface or enters a low-power interface mode. This seems to disturb some component in Windows (the Presentation Director, Windows, the ATI tools, the ATI driver) in a way that Windows only activates the notebook display when it resumes from "monitor sleep".
Suggested change: Change these tools (or the ATI driver) so that they can cope with the situation that the DVI-interface is deactivated and wait longer for the interface to be in a useable state. Reactivate an external monitor even if it "sleeps very deeply".
Relevant system information
- T400 2767-CTO (T9400, 2x2GB RAM, ATI, WXGA+ LED)
- Advanced Mini Dock
- Vista 32 Business (German) - fully updated
- All Lenovo updates via System Update are installed- Dell 2709W
- The system runs the ATI graphic card in the described scenarios
Message Edited by Izmi on 05-21-2009 10:34 AM
Message Edited by Izmi on 06-29-2009 03:13 PM
Solved!
Go to Solution.

Lenovo support made me reinstall presentation director to rule out this component as a factor. After the reinstallation, the amdkmdap-problem is still present. Letting Windows go to standby and waking the system up afterwards, is a reliable method in my case to reproduce the problem on condition that an external monitor was active. The problem does not occur if no external monitor is present.
A web search for "amdkmdap", "atikmpag","BSOD" with one of the ThinkPad-series names (like "T400") shows that other persons also have this problem with R400s, T400s, T500s, and W500s:
- t400: Display driver crashes
- W500 Display Driver
- My W500
- T400 Display driver stopped working...
- T500 Video/Video Driver Issues (2056-4SU)
- NUS T400 issues
- T400 Display Driver Issue
- Vista64 + 4GB RAM + External Display = BSOD
- R400 problem report (in Chinese)
- T500 problem report (in Chinese)
- Bioshock keeps crashing (seems related)
- Vista x64, ATI graphics, dock + external LCD = bluescreens? (a report by a W500 user)
- many problems with lenovo w500
- another R400 problem report (in Chinese)
- Vista BSOD on Lenovo T500 with new Switchable Graphics
- switchable graphics and external monitor through port replic
- Problem with Lenovo T500 notebook & external LCD
- Lenovo ThinkPad T400 - some impressions.
- T400 freezes with graphics Intense programes
- Standard Laptop mit ein paar Macken (in German)
Some possibly related Non-Lenovo cases:
- Why Vista crashes so often when dual display is enabled?
- Vista and 7.3 Display driver atikmdag stopped responding error
- 4870 vista x64 multi-mon = atikdmag BOOM
In the cases in which people observe the "amdkmdap"-problem and describe the circumstances, the use of an external monitor is always a factor. These other reports also indicate that it is likely not an issue with the hardware of my notebook (or then a general problem for many batches of these machine types). For it happens a) on many systems and b) on different kinds of systems.
If others want to contribute to the problem solution, then we should provide Lenovo and ATI a good problem description. So, please add your description.
Message Edited by Izmi on 02-03-2009 11:53 AM

[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.

My system won't boot past POST after I plugged in my new SATA drive. (SATA noob

I have a MSI K8n Neo 2 Platinum mobo with a Athlon64 +3500 and 1gig dual channel DDR 400. I currently have 2 drives set up a IDE primary (MAxtor 6Y120) and a IDE slave (Maxtor 6L080).
I recently purchased a Maxtor DiamondMax 10 6L300S0 300GB Serial ATA 7200RPM Hard Drive w/16MB Buffer.
It is my first SATA drive ever so non the less I am a newb. I want to use it as a non Raid media storage device while my primary IDE remains my boot OS drive.
I plugged the SATA in to the sata one port and powered it. I enabled the SATA in the bios with RAID disabled. When the system boots up it does the memory chech and lists all the IDE devices. Then it says "Detecting IDE drives..." and just hangs there. The new drive spins so it definatly has power but occasionaly it make occasional clicking sounds.
Once it actually booted up and windows detected it. I decided to reboot it just to play it safe but it never would get past post screen again. I can boot up the system normally when I unplug the SATA cable.
Please help I need to know if I am doing something wrong or I should RMA the drive. THANK YOU!

Got the same problem:
pata Maxtor Diamond Max =9 200 (40/160) Boot drive
AMD 64 x2 3800
Bios 1.2 090905 using MSi online auto update utility
2x 512 DDR double sided
X850 pro 128mb
PSU Sweetex 650w
Switched power supply
110/220 V switchable (220 V: 5 Amp/ 110V:10 Amp)
+ 3.3 V 28 Amp
+ 5 V 45 Amp
+ 12 V 25 Amp
-5 V 0.5 Amp
-12 V 0.8 Amp
- 5 Vsb 2 Amp PEAK 2.5
Max. 650 Watt
CE, FC
Boots perfectly with 1 pata, adda sata to sata 1 or 2 or 3 or 4
Boot stalls in bios at Raid setup. Tried enable raid with no drives enable , system booted twice, turned off overnight, then failed to start the next day. Will only restart with a cold reboot. Hot reboot produces a long BEEEEEP & power is on but nothing happens no post nothing.
SATA drive was taked from a working system (ECS 755a - AMD 64 3000 - PATA 200 / SATA 200), configured 40/160 40=OS Winxp 64 / 160 = data. System will not boot if this is the sole drive connected.

Urgent - No 64bit Promise SATA driver (not RAID)

I'd already installed XP64 on an old PATA drive without problems, so today I decided to use the new VIA SATA drive to dual-boot it off my SATA drive, along with my main XP32 installation. Unfortunately, although it found the VIA driver at F6 and got to the GUI install it locked solid at Devices. Worse than that it's totally screwed all the boot files so I now can't get to anything on either the SATA or PATA drives, and blue screen on any attempt to boot either drive. That's 4 OS installs gone.
I moved the SATA over to the Promise controller thinking I'd seen 64bit Promise drivers for weeks, but it seems these are only RAID drivers and are called "Promise FastTrak 378 (tm) Controller". Needless to say they don't find a single SATA drive. What I need would be the driver called "Promise SATA378 (tm) Controller" but I can't find it. Have Promise really released a RAID driver but no single SATA driver for the same controller???
If I don't find it I guess I'm looking at 4 days spent formatting and reinstalling.

Hi Jocko
OK, I'll try explain (and remember!)
First I installed XP32 on the lone SATA drive. No problem as it was the only drive.
Then I added an old PATA drive, which BIOS and Windows Setup always sees as Disk 0 and the SATA as Disk 1.
I then installed XP32 onto the PATA drive. No problem, I think it was because Windows saw it as Disk 0 as it put the MBR in the right place.
I then put Server64 and XP64 on the PATA drive to test them (leaving by day-to-day install safe on the SATA drive. Again, no problems, it updated the MBR correctly to let me multiboot between the 3 OSes on the PATA drive.
I then tried to add an install of XP64 to the SATA drive, but because I left the PATA drive connected, Windows setup updated the MBR of the PATA drive instead. On subsequent reboot it failed because it was pointing to the wrong drive (I think). So I had half an install on the SATA drive, and a boot.ini on the PATA which pointed to a non-existent half installation. Even with BIOS listing the SATA drive as the boot device, each time the PC restarted it tried to carry on the installation and of course failed.
That's when I had to refer to my book on Recovery Console...
So it seems that if multiple drives are installed, it will update the MBR on the lowest ID drive, which is not necessarily the drive the installation is actually going on to! I think!

T500 Updating SATA Driver Fails

Similar Messages

Maybe you are looking for