Problems with second hand Zen visio

Hi I recently sold a zen vision m 30gb, it was working fine when i sold it however i could not find the software that came with the player..... I checked the support page and everything seemed to be there that the buyer would need to get the player up and running...........however the buyer states the player is not charging and he cant get the software from the support page installed as there is no player already installed on his PC.
How can we get the player to work on his PC without have the orginal software I've had a check and can't seem to find any answers using the search function.....please help this is driving me nuts

What accessories went with it's If a wall charger was one of them good tell them to charge that way if not tell them that the charger for the playstation portable will work with it for charging. They should be using a REAR usb port to charge the player. Try a different usb cord. Buy a new dongle/power cord http://cgi.ebay.com/-ITEMS-ACCESSORY...dZp73.m53.l262 They do not really need the Creative software to use the player it will work with Windows Media Player
Before they can do this function they MUST have 50% power of the battery:.......First have them boot player into recovery mode & do a Cleanup> Format>Reboot on the player & tell them I can't stress this point enough DO NOT CHOOSE RELOAD FIRMWARE!!!!!!! That function erases the firmware & will render the player useless.
http://forums.creative.com/creativel...ap&thread.id=3 Check you private messages.

Similar Messages

  • Problem with a new Zen Visio

    Hello :0I just got today my Zen Vision:M and I have a problem After using the player for few minutes the Touch Pad freeze... all the other keys are working, just the Touch Pad freezes.. I tried to reset and no change, I tried to Clean up and again not helping, I tried format.. firmware uninstall/upgrade.. no change.. Is there a solution for this problem or I will have to replace it's?Thanks,Matan

    jessevsm wrote:
    I got my Zen yesterday, and the player itself works great! And I've installed the software for it, and this is where my problem is. None of the software for it seems to be seeing that the player is connected to my computer. My computer recognizes it's there, and the player says it's docked. But yet when I access the Media Explorer or the other media programs that it came with, none of them recognized that it was there. And another problem that I've been having is it takes 'forever' to get into the Media explorer. I click on it from My Computer, and it takes a couple minutes just to get through. But then it still says that the player isn't connected. I've sent an e-mail to Creative talking about this problem. And I haven't gotten a response. I called earlier today and the person who I talked to said she was sending me a few things through email to fix the problem. But I never got that email for some reason, so now I'm coming here in hopes that someone may know how to fix this problem I'm having. I haven't been able to put any music or anything on my Zen because of the fact I can't get the software to work correctly.
    try to uninstall the softwares and install them again with full packages.

  • Problem with my hand cursor: it shows three little hands

    Hi there,
    I work for many years with CS4 and now suddenly, my hand cursor shows up as three little hands in a row. I don't know what went wrong or how to correct this. Please help
    Bert

    Hi there,
    That works! And my mouse is scrolling a lot smoother too! Thanks a lot! I am very grateful.
    Best Regards
    Bert
    Boteijken 323
    3454 PD De Meern
    Tel:   030-8201164
    Mob: 0655-720309
    Email:  <mailto:[email protected]> [email protected]
    Van: R_Kelly [email protected]
    Verzonden: zaterdag 31 augustus 2013 17:32
    Aan: Roozworks
    Onderwerp: Problem with my hand cursor: it shows three little hands
    Re: Problem with my hand cursor: it shows three little hands
    created by R_Kelly <http://forums.adobe.com/people/R_Kelly>  in Photoshop for Beginners - View the full discussion <http://forums.adobe.com/message/5642784#5642784

  • Problems with my new zen mi

    I just bought a new zen micro this week and have been having a few problems with it. I bought it specifically to use with rhapsody to go and it is replacing an ipod mini so that I can use it with subscription services
    I have upgraded the firmware to 2..02 which gives it the plays for sure ability. The problem is that the delay when skipping songs is ridiculous. It takes about 5-7 seconds to skip between songs and is quite annoying. It has also frozen 4-5 times in the past 3 days since I bought it. I haven't tried to reload the firmware as I don't want to go through the hassle of transferrring all my music again 9though I'd be willing to do it if it ixed the problem). Anyone got any ideas or fixes on this or has anyone had similar problems
    P.S. I'm also very used to how well my ipod worked, it never delayed or froze or anything in the six months since I bought it, so maybe I'm jsut expecting too much

    I have done some more trouble shooting and have some more info on my problem. I did the disk cleanup and reloaded the firmware. Nothing changed, still had the same problems.
    So I changed the firmware to the updated non-playsforsure firmware (ver. ..0). It formatted the unit and put the firmware on. I then added some normal mp3's and they worked fine. no delay when skipping songs or anything.
    So i then re-updated the firmware to 2..02 (the plays for sure firmware upgrade) and added some of my own normal mp3's. they work fine. i then added some of the wma files i have from rhapsody to go. the problems then started up again. So it seems that one of two things is going on. Either the files that rhapsody is sending are messed up somehow or the way my zen micro handles the wma files isn't right.
    Does anyone have the rhapsody to go service? HAs anyone seen similar problems? Any help would be appreciated.

  • 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 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 (admin) user profile

    Hi all,
    I'm having trouble with a certain user profile. I got a new MacMini with Lion (10.7), to which I imported two user profiles from a Time Machine backup of a Snow Leopard system. The first profile, which used to be the admin profile on the old Mac, works just fine. But the second profile, which used to be a "normal" user profile encounters massive problems. First thing I did was to make the second user admin as well, but that did not fix anything. I assume there is a problem with the permissions and "repair permissions" didn't do anything either.
    Here are some examples of the issues:
    First example: I cannot delete or rename folders in Mail, unless I delete or rename them in the respective ~/Library folder. This concerns folders which I imported from the Time Machine backup. There are no issues with new folders.
    Second example: I cannot start SPSS, which runs just fine on the other profile. It starts and then just closes right away without any error message or anything. I found a workaround which is to start the program with a rooted terminal command ("sudo /Applications/..."). There is no problem with Java (which would be common) and there are no license issues. I found an article in some other forum which stated that SPSS reads and writes in its preference folder at startup and closes right away if permissions are denied for that folder.
    Third and most annoying example: I cannot permanently delete or create icons in the dock. I can remove or create icons temporarily, but after restarting the Mac, the new icons are gone and the deleted items are right back where they were.
    Does anybody have any idea on how to fix this?
    In the short run, It'd be very helpful if anyone could tell me how to create dock icons with a Terminal command.
    I thank you in advanced for helping me out. Every little hint is appreciated.
    Sebastian
    PS: I have not tried to setup a new user profile instead of the second profile, yet. With all the programs and preferences that would take at least two days and I need to keep the Mac running. I would only do it as a very last resort.

    Well i went ahead and made that new admin like you said and I set it up and transfered only the files that I thought were important to me, Then i went ahead and fixed or repaired the permissions On the new admin user name and deleted my other admin profile with the key board issue.I fixed the permmissions  with an OSX Lion boot disk instead of lion because I don't have the Mountain lion DVD anymore. Every thing seems ok but was that a smart move or will that come back to haunt me?
    Now what Im worried about now is I didnt keep any of the certificates or anything in that nature, So My final question is What should i do now to hands down lagitimanetly make This the offical ADmin with all keys and things of that nature that make it the main one?
    Thank you so much and I'll watch my jokes from now on... I don't want to hurt anyone's feelings,

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

  • 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 my new Zen Sl

    I have a zen sleek and am using Rhapsody to Go. I managed to load all of my music, including ripped cds, purchased tracks, and Rhapsody to Go subscription tracks without any problems. I've since?downloaded some more subscription tracks and attempted to do a synchronization. At that point, I got told that my device would run faster if I was using usb 2.0 (I thought I was using it, since I had not gotten a warning the first time). I tried to do the synchronization anyway (later I purchased a brand new usb 2.0 card, which didn't help). It took over a day, and every single track gave me an error message (unable to obtain certificate). I tried with both the zen sleek software, with Rhapsody 3., and with the Creative Mediasource software. Nothing worked (at least the rhapsody program gave me a meaningful error). I looked up the error on the rhapsody help site, and it said I should check the time and date on my player (which I corrected). I tried again, this time with a new usb 2.0 card. I didn't get the same warning, but it still took just as long to tell me that all of the transfers failed. The errors were either "Unable to obtain certificate for device", or "incompatible media type" (they were 60 mbps wma files).
    Next thing I tried was to simply drag some files to the device. This time, the first two files I dragged transferred without any error, but after that, every subsequent file gave me errors. This leads me to believe that I there is something else going on. Note that I had zero errors using the old usb . card, so this leads me to believe that the slow speed is due to errors. Does anyone have any suggestions of what I should do or what may be going on? Do I need to reformat the device and start from scratch?

    Haldur,
    Try updating some WMP0 hotfixs from Microsoft website that's meant for PlayForSure stuff. More information in this Knowledgebase article SID793.
    Jason

  • Problem with Starting Up Zen To

    I have been having problems starting up my Zen Touch (ZT) when I press the START button on the side. I often have to press it multiple times, and sometimes it refuses to start up at all! This occurs even when the battery level is >30%.
    There doesn't seem to be a problem when I start the ZT by connecting it to a PC via the USB cable. There also is no problem with shutting down (by pressing the START button).
    Has anybody else had this problem?
    Thanks

    I have found that sometime my "hold" button is not completely "off", and I have to make sure the button is completely in the "unhold" position.

  • PLEASE HELP - Serious problem with my Creative Zen Touch firmware

    Ok, so I finally decided that I would upgrade to the latest firmware version for my Creative Zen Touch. I knew that doing so would erase everything on it, so I backed up everything onto my computer's hard dri've. So from that standpoint, I'm in the clear.
    HOWEVER, during the upgrade process, my computer froze, leaving my precious MP3 player without ANY firmware. This then drove it into "recovery" mode, where I can either clean up, format, or reload firmware. I've gone through each of these options, but when I go to "reload firmware" my computer will no longer detect my Zen! I've tried reinstalling different driver versions, different firmware versions, etc. The bottom line now is that my mp3 player has no firmware, and my computer won't detect it.
    I feel like I probably need to go back to the basics. Unfortuantely, I don't have my installation CD with me. Can anyone post the initial installation file please? Thanks in advance!
    I really hope I can work this out, I don't know if I've gone a day without my Zen in the past two years!

    Simon, this is actually a common problem with the touch. Mine did it about a year after purchase, so I was safe to open it up and fix it. It is actually a really simple fix and is due to a loose connector. I know alot of other people on nomadness.net were having this problem, so I posted a solution here. Hope this helps!
    http://www.nomadness.net/modules.php?name=Forums&file=viewtopic&p=42838

  • Serious Problem With my Cretive Zen Microph

    Hi!?I've a little problem with my mp3 player.when i turn on it,the player stops on the screen "creative". I try to start the recovery mode,but hopless. The player dosen't work.How Can I solve the problem?Thank U and sorry for my english!

    I try to remove and reinstert the battery,i lunch the recovery mode,i click on "format All" but the player seems to block.At the same way if i click on clean-up,reboot,reloaded firmware. There isn't a button to reset completely the player how in the creative zen v plus?

  • Help please!!! problem with setting up Zen NX (software/driver e

    <SPAN class=postbody>Hello, i am new to this forum and have limited knowledge about the Zen NX and would really appreciate any help or advice that you could offer. O.K. i got a Zen NX in Jan 2004, ran the software disc supllied, no problem. I then turned on the player but it was not recognised by the computer ("Device not connected") so i went to the support site and found out that this was a known problem and needed to download a piece of software which i think was named (Drv_JB3.EXE)?. Once this was done i had no problem at all and the player turned out to be a great piece of kit. About two months ago i had to re-set my computer to the factory settings because of a virus, anyway yesterday i decided i would put the software back in for the Zen NX and add some new music. I did everything as before, and luckily i had saved the extra piece of software that was required in order to get the computer to recognise the player. Unfortunately, everytime i tried to download the software it just kept saying that there was a problem with the driver and that i should reconnect the player in order for the software to work, which of course never happened and it just kept on repeating this message everytime i reconnected the player. Anyway i spent the rest of the day uninstalling the main software and reinstalling and then trying the latest drivers downloaded from the creative website and also the latest version of Media Source etc, all to no avail (getting well pi**ed off at this point) i even did a "restore" in XP to see if this would help but no joy. Just to let you know i think that the origional driver version was (.23.00) and the Creative Media Source version was (.0.84). I do not think that there is a problem with the USB port or cable as the computer recognises that a new piece of hardware as been added when i plug in the player.
    <SPAN class=postbody>I have posted this message on nomadness.net but as yet i have had no reply<SPAN class=postbody>
    Any help or advice would be gratefully appreciated, before i launch the Zen out of the window!!!
    <SPAN class=postbody>
    cheers, Burni.

    Get the following:
    . Creative Zen and Jukebox Driver Upgrade version .30.03
    2. Creative MediaSource Player/Organizer 3.30.2
    3. Creative Zen and NOMAD Jukebox plugin 2.00.9 for Creative MediaSource
    Install . then connect the player to the PC. Then install 2. and 3. (the player must be connected for 2. to verify you have a Creative product).

Maybe you are looking for