bowbe

Member
  • Content count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bowbe

  1. Have you tried uninstalling the cable within Device Manager, rebooting, then re-installing? If there was any damage during your attempt, then it most likely would have just shorted out your board (spindles and head should still be okay). Try connecting the drive back up to your PSU, then power on the PC. If it is still good, you should be able to hear the drive 'boot up' and start clicking like the PC is starting up. Of course, you won't see it in your BIOS, but just the fact that the board is still able to spin up the drive should (hopefully) be proof enough that your drive and the PCB is still intact. Keep trying and see if you can get the cable working again.
  2. Try the loopback test to see if your adapter is still working correctly. I can't think of anything in particular that you can do to test whether the drive is still good...
  3. What kind of adapter are you using to talk to the drive? EDIT: Sorry, read your last post... The DKU-5 (other readers correct me if I'm wrong) should be powered 3.3V+ from USB, so you don't need the molex to power the adapter. The SATA power connector just needs to give the drive power, while the TX, RX, and GND from the DKU-5 communicate with the drive's PCB.
  4. You have to remove the pcb to put the cardstock down anyway, so you might as well try it. EDIT: http://www.msfn.org/board/index.php?showto...st&p=850705 It mentions post #701. SPIN ERROR was from no contact on the PCB. When I had the same problem, I unscrewed the screws a tiny bit, then tightened it back down. Spin Error went away after that, and I was able to continue to the next step.
  5. Find out if the adapter is powered from the USB side. If that's the case, you don't need to route power from the PSU. Instead, you'll have to connect as follows since the drive uses GND to communicate with the adapter: Adap.VCC(5V+) <---> Not connected to anything Adap.TX <---> Barracuda.RX Adap.RX <---> Barracuda.TX Adap.GND <---> Barracuda.GND Connect the drive to the PSU like normal.
  6. The drive is back up and running now. But... Have any of you had problems installing the firmware afterwards? I have done everything I can think of to get the Dell DE13 upgrade (R213714) going, but it doesn't do anything. It boots up to three lines of console, then boots directly into Vista. I've tried running directly from command (says conflict with 32bit/64bit), the boot CD, and the boot USB options... Anyone with some tips?
  7. The USB to UART adapter from Alldav seems to work alright. Just remember to buy header pins and have a mini-B USB cable handy. The drivers can be found at the FTDI page (I'll add a link later). If my fix goes as planned, I'll post here. Also, can anyone tell me what happens within the drive AFTER the BSY sig is cleared? Will upgrading the firmware prevent any future mishaps or should I always be weary of this thing? Sorry if this has been answered already but I'm not going to wade through 80 pages of posts. Best of luck to all of you. EDIT: Adapter - http://alldav.com/index.php?main_page=prod...;products_id=21 FTDI - http://www.ftdichip.com/Drivers/VCP.htm Use the link for 2.04.16.