Sign in to follow this  
Lurker

Need some expert SCSI help...Atlas 10K III problems.

Recommended Posts

I just bought three Atlas 10K III 36GB drives. Two from one source and one from another.

I cannot get any of them to work completely as I expected. I doubt all three drives would have problems so I'm probably doing something wrong. If anyone can advise, I'd be grateful.

Motherboard - Asus P2B-S (onboard Adaptec U2W, UW, W)

RAM - 3x128MB

CPU - Celeron 566@850 (100MHz FSB)

This system has run flawlessly with around 10 SCSI drives over the years (Seagate Barracuda, Seagate Cheetah, IBM 36LZX, etc.) Currently it is running just a single 36GB IBM 36LZX.

The first drive I attached at SCSI ID=6 and tried to low level format it with the SCSI Disk Utility (Ctrl-A during bootup). As mentioned in another post, I received this error:

Unexpected SCSI Command Failure

Target SCSI ID: 6

SCSI CDB Sent: 03 00 00 00 0E 00

SCSI Controller Status: 00h - No SCSI controller error

Target Status: 02h - Check condition

Sense Key: 05h - Illegal request

+Sense Code: 26h

+Sense Code Qualifier: 02h

I went on to fully Verify it in the SCSI Disk Utility! It also handled an FDISK partitioning, Win98SE Format, and Win98SE Thorough ScanDisk without any problems. Still, the low level format error made me think I had a bad drive.

When I got the next Atlas 10K III in, I put it in the same setup at ID=6 and happily found it would low level format without error. I then unhappily found it would not verify in FDISK, kept halting with a runtime divide by zero error.

So I put the third Atlas 10K III in the comp and unhappily found it would not low level format, giving me the same error listed above that the first drive did. This one, like the first one, would fully Verify in the SCSI Disk Utility (Ctrl-A) as well as work in FDISK. However, it has an NFTS partition, that I cannot remove in FDISK.

All of these operations were performed with the drives mounted in the built-in vertical drive bracket on an Addtronics case. I then tried troubleshooting by using them horizontally, using a different LVD cable, and finally trying them as the only drive on the chain and in the ID=0 position. Same results every time.

What am I doing wrong?

Share this post


Link to post
Share on other sites

well, i would deffinately suggest that you try without overclocking your CPU...

additionally, to delete an NTFS partition in FDISK, just select to delete a "NON DOS" partition and you should have no problems getting rid of it.

sorry, but i really don't have much experience w/ SCSI and not quite sure why you're getting the errors... I know IBM offers a free low level format utility that I have used on other brands with no problems... IBM says it works on both IDE and SCSI drives

wipe.exe:

http://service.boulder.ibm.com/storage/hdd...ddtech/wipe.exe

General Downloads:

http://www.storage.ibm.com/hdd/support/download.htm#

Share this post


Link to post
Share on other sites

I wouldn't worry about the low level formatting. As long as it partitions in FDISK and formats OK. What are you using for termination?

Share this post


Link to post
Share on other sites

Thanks for the replies.

well, i would deffinately suggest that you try without overclocking your CPU...
Yeah, I should have done that...I guess I was just too lazy to look up the jumper placements. I'll go do it now.
additionally, to delete an NTFS partition in FDISK, just select to delete a "NON DOS" partition and you should have no problems getting rid of it.
I don't remember seeing that option, I'll look for it.
I know IBM offers a free low level format utility that I have used on other brands with no problems... IBM says it works on both IDE and SCSI drives - wipe.exe
Thanks for the links, but it looks like wipe.exe is just a simple data overwriter. It says it writes zeroes to every sector on the disk, but only up to 8GB.
Also, try a different cable...  flakey cables do wierd things...   All it takes is connecting-disconnecting-bumping a cable wrong to cause problems..
I did try a different cable. Same exact problems. :(
I wouldn't worry about the low level formatting. As long as it partitions in FDISK and formats OK. What are you using for termination?
I've never had a drive that wouldn't low level format though...why wouldn't a drive do that? It seems indicative of a problem to me, but I'm just guessing.

I'm using the terminator block on the end of the LVD cables.

Share this post


Link to post
Share on other sites

Update

The drive that would low level format but kept giving me a divide by zero error in FDISK now has started working in FDISK. ??? It seems to function perfectly now and I am doing nothing different and cannot replicate the error that I replicated 100% many times in the past two days. System has not changed.

The two drives that would FDISK fine, but would not low level format are still acting in the same manner. Of interesting note however, they are both the same Firmware revision (020K) which is different than the drive that works (020W). Think that might have something to do with it?

Can you upgrade the firmware on a SCSI HDD? I can't find any info on it at maxtor.com.

Share this post


Link to post
Share on other sites

Oh, forgot to mention, the two drives that don't low level format and are the same Firmware revision are built with different chips and came from different sources. One uses agere, the other Lucent for the larger chips showing on the underside. Just thought I'd mention that. The one that is working fine uses agere.

I took a Fujitsu MAJ 36GB out of the closet and it worked flawlessly in this system. It low level formatted and FDISKed without any problems.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this