Showing posts with label Hardware. Show all posts
Showing posts with label Hardware. Show all posts

Friday, January 9, 2009

Seagate/Maxtor SeaTools Drive Diagnostic - Problems/Solutions

I had a hard time testing some new Seagate ST31000340NS drives recently, and here is what I learned.

  • Always test new drives ASAP so you can return defective drives within warantee period, and avoid lots of wasted work/installs/reinstalls.
  • Download the Seagate SeaTools (also works for Maxtor) DOS ISO for drive testing, and burn the CD (I downloaded v2.13B on Jan-7-2009).
  • The SeaTools Windows version doesn't generally work in Vista x64 (Known problem). Though a certain hack/fix (from this discussion) might work for you in Vista 64 bit. It worked better for me, but I think my hardware hindered the drive detection.
  • Connecting the SATA drive externally via eSATA works great for drive testing (I used a Rosewill eSATA enclosure).
  • My A7N8X Deluxe based computer would not boot with the drive attached. After drive detection, the machine hung.
  • My P5B Deluxe/WiFi-AP based machine booted from the SeaTools CD no problem.
  • The SeaTools software must have a floppy disk in the A drive (possibly writeable) or the long test will not complete. After the test, the floppy disk was completely empty. I put the CD and floppy in, then booted.
  • I ran the Short Test, the Long Test and the Acoustic Test, taking a digital photo of the results of each.
  • I also photographed the drive. The photos are for my inventory and testing results.
If you were wondering my new drives tested as flawless.

-AAron

Tuesday, November 18, 2008

Computer Backups @ Home

After trying lots of different backup strategies for my home computers, I’ve finally settled on a backup system that is fault, fire and theft tolerant. With a convenient combination of live recovery and offsite backup, I can easily recover from single hard drive failures, and even a complete system loss.

The trick is that I’m using a RAID 1 mirror approach with an extra drive. In this scenario, I’ve got two drives working as one that tolerates the complete loss of one of the drives, and the system continues to operate without interruption. Each week, I power down the systems and remove one of the drives (which is a perfect copy of the other). I then install a drive that I had kept offsite in a safe deposit box at my bank. During the boot process I tell the machine to rebuild the RAID 1 array and overwrite the newly inserted drive. The RAID rebuild doesn’t take much processing power, and a few hours later the machine is back to full redundancy.

At any one time, I have 2 drives in a machine acting as fault tolerance, and a third drive at the bank acting as standby for a complete and total loss disaster. I’ve experimented with my motherboard built in ICH8R hardware assisted RAID controller, and I know that I can easily rebuild from only the offsite drive.

To make the process better, I put mobile drive racks into my 5.25 bays. The rack accepts direct insertion of SATA drives (no sleds needed). I don’t even have to disassemble anything to make the drive swap. These days 500GB drives are cheap, which makes this scheme very affordable.

KINGWIN KF-1000-BK 3.5" Internal hot swap rack ($25)
http://www.newegg.com/Product/Product.aspx?Item=N82E16817990001


OEM 500GB drives ($60-$70)

http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=2010150014%20103530113&bop=And&Order=PRICE


This is arguably not a backup strategy. Considering that I have fault tolerance AND an offsite copy, this simple system satisfies all my needs. The offsite “backup” is about a week old at any one point, but I would suggest that it’s more current, more reliable, more viable and more convenient than most people’s backup strategies. Considering that most people backup by taking hours copying files to an external drive, my backup is basically just pulling the drive out of the machine.

Also consider that my RAID 1 mirror strategy can be used like a Virtual Machine rollback feature. If I wanted to, remove one of the drives, and try arbitrary system changes and software installs. If I didn’t like the result, I could remove the remaining drive, and reinsert the one I had pre-removed. At that point the system would be in pre-experimentation mode. The system would need to rebuild the array, but a small price to pay for having rollback capabilities on a physical machine.

There are some issues/annoyances to this approach. First, when a drive is failing, typical consumer drives make “heroic” attempts to prevent data loss. This means it can take extremely long amounts of time retrying and remapping bad sectors (hard drives are S.M.A.R.T. you know :-) I’ve seen this occur on my systems, and it takes a while to realize why the system is semi-freezing, acting erratic, or possibly not shutting down properly. Once I recognize it, I shut down and run my vendor supplied drive diagnostics to find (and possibly correct) the bad drive. I don’t like any drive problems, but these days the diagnostic software will correct them enough that a warrantee exchange can’t be done. The other annoyance is having to shutdown my systems once a week, and drive to the bank. The systems aren’t down for long and it is a short drive to the bank, but it is slightly annoying. If you wanted to attempt this scheme, you would have to RAID enable your system in some way. Maybe buying a new motherboard, or a PCI card, or external NAS RAID… I can see that being annoying too if you don’t have it already.

With my frequent visits to my safe deposit box in the vault, and bringing my precious data (photo collection, word docs, personal projects, etc…), I feel like it would be cool to have one of those steel secret-agent brief cases handcuffed to my wrist :-)

Note:
I could use an online Internet cloud-based backup solution, but my Honda Civic can transfer 1.5TB of data to/from offsite in about 20 minutes. My cable modem at home can't achieve that type of bandwidth every week :-)

Sunday, August 10, 2008

Service manuals are very useful !

My printer broke and I was confident that I'd be able to fix the simple problem once I downloaded the service manual. I have to say it was very cool to be able to get a hold of that manual ! It has instructions on how to diagnose, disassemble and fix. The printer went through the motions, just didn't lay any ink... must be clogged, should be easy to fix.

The printer actually stopped printing about 2 years ago, and I had since abandoned the overly expensive and questionable ethics of that printer's manufacturer. Since I HAD purchased extra printer ink cartridges with that company's settlement to the class action lawsuit (pertaining to questionable ink practices)... I wanted to use up that ink, and spare some ink on my new Canon PIXMA MP780.

I have to applaud any company (even the maker of this printer and its expensive ink) that has a service manual that I can find online (I got it at this site). Kudos ! I also found community help for exactly the problem I had. Regardless of technical expertise or skills, I think everyone should have the chance to get the full manuals and self-help for all the products they own.

My project started following A FIX for Clogged Printheads which was VERY nice. The disassembly, construction of make-shift tools, and use of anti-freeze... all went great removing tons of gunk from my old printhead. Followed all instructions, didn't help in the end. I was still happy and empowered by the community help.

Then I found and dove into the service manual. I wouldn't gotten nearly as far carefully and gracefully locating and removing the proper screws without it. I usually break things as I'm being careful, which I didn't do as I followed the manual.

As the manual pointed me at screws that could only be reached with long narrow specialized screwdrivers I started to get frustrated, but still thinking there was SOME hope that I'd be able to reseat them all and get this thing back together.

Having to ultimately go for removing the printhead itself (ugh), I abandoned the manual, and honestly all hope of ever getting this darn thing back together. Just think though, without the manual I wouldn't have ended up with this, or potentially in the mood to buy a new printer. Too bad I already decided I didn't like this one's manufacturer, I might have bought another of their printers merely because I was empowered with the service manual to destroy my old one!


Care with the service manual lead to not caring and destruction.

Well, at least the 3 day project is now over, and I've got some additional neat parts for my Junk box.

Saturday, June 28, 2008

Samsung ESTOOL Drive Diagnostic Does Nothing (here's why)

Or does it?

http://www.samsung.com/global/business/hdd/support/utilities/ES_Tool.html

I have been trying to get the ESTOOL hard drive diagnostic program to work for over a day now, and just figured out the problem. The bootable floppy disk seems to work. It lets me auto detect and select my Samsung hard drive. It lets me see information about the drive and its settings. When I choose "Drive Diagnostic," it asks how many loops to run, and when I hit enter (defaulting to 1), I end up back at the main menu.

Ends up that the ESTOOLS boot floppy disk MUST NOT BE WRITE PROTECTED ! It wants to write a status log to the disk, but fails silently if the disk can't be written to. I'd guess that if the floppy disk were full, the same silent error would occur. So, to save yourself the grief I went through, don't lock the disk, and make sure there is at least 10K for log files (they are actually less than 5K each).

Would have been nice if the program told me what the problem was !!!
(I thought it was that my chipset was Nvidia, which was the problem with another vendor's hard drive diagnostic toolset)