I was given a server computer, an old dual CPU AMD computer with a SATA Raid controller (not on board SATA ports). Three(3) Sata drives, one primary and two Raided. When originally starting up the computer it went to a Windows Server 2003 startup screen saying the license has expired and would not let me proceed any further. Turned the computer off and took out one of the SATA drives. They slide and latch into the computer. When I connected the WD 250gb 2400xxxxx drive to a SATA ready PC, BIOS read the drive and its type and its size. When I used XP's computer management, it would not read the drive, even when I connected it to a SATA to IDE or SATA to USB 2.0 it would not see the drive. Some partition tools would recognize the drive and see it as a 250GB drive and its WD ID but any attempt to format, partition, wipe, or change the drive results in an I/O read error. Puppy Linux was able to also see the drive when I tried to partition it and it also had I/O errors.
I then tried the same operations and attempts on the two remaining identical SATA WD drives and they all result in the same end, I/O errors. When I placed the SATA drives, in order, back into the 'server' pc, it will not even load into the Windows 2007 server screen.
Aditional information:
WD2500JS 250 GB SATA 3 Gb/s 7200 8.9 ms 8 MB
I placed the SATA HD off the RAID card, on to that server pc SATA0 directly and took it into the "BIOS" raid diag setup and removed the raid partition and did a complete low level format on the drive.
The drive is readable and writable on that old server computer
The drive is accessable and it was formatted (low level)
On any other computer either through a SATA0 port, or a device like this: USB to SATA/IDE Universal Kit with One Touch Backup, the drive type and size can be seen, but it has nothing but I/O errors.
That server PC says there is no longer any RAID setup at all on the drive.
I have downloaded a WD program or two to see if this can help but haven't tried them yet.
Another question is, do I need a seperate SATA driver on more modern Motherboards to access a SATA drive with no partition on initial reboot? I remember like 8 years ago, you need additional SATA drivers on a floppy disk to even see an unpartitioned SATA drive and I have no idea if that is still true today.
Again, XP and VISTA, Puppy Linux and a few other partition programs see the drive but can do nothing with it.
Sometimes, when all you want is to gain your freedom, you must be willing to risk it all.
I hope this is not the case, but it is possible that a piece of equipment has made the HDDs go bad, maybe the SATA to USB cable or something in the desktop/server. It may even be the software you used to read the drives (the software thing happened to me on 2 drives).
I also use a SATA to USB cable, and in my experience if the system can't read the drive that way, it is shot.
An unfounded opinion of another is a reflection upon oneself. -Me (awesomeness)
I still, in my experience, never had a hard drive accessable to the level of a full low level format with no errors, detectable in Bios and HD is Identified, but any access outside that server pc just yields I/O errors.
Also, this is happening to all three HDs.
One was the main and the other to, Im presuming, were the RAID back ups.
If I had any additional HD issues, or even one that wasn't affected in the same way, Id go for a general HD failure, but this just seems that Im missing some setup or configuration.
I'm still holding out hope.
Sometimes, when all you want is to gain your freedom, you must be willing to risk it all.
Does the "new computer" have that port assigned to a Raid array? If so, you'll have to go into the RAID setup and set the status of the drive accordingly. The BIOS only checks for the hardware available on the ports, but it is the drive controller which decides if, and how, the drive is presented to the operating system.
Wide awake in a world that sleeps, enduring thoughts, enduring scenes. The knowledge of what is yet to come.
From a time when all seems lost, from a dead man to a world, without restraint, unafraid and free.
Mostly retired Discovery member. May still visit from time to time.
' Wrote:Does the "new computer" have that port assigned to a Raid array? If so, you'll have to go into the RAID setup and set the status of the drive accordingly. The BIOS only checks for the hardware available on the ports, but it is the drive controller which decides if, and how, the drive is presented to the operating system.
The hard drives are:
WD2500JS 250 GB SATA 3 Gb/s 7200 8.9 ms 8 MB
I looked to see if this was a specific RAID drive, and either due to my massive lack of understanding or the specs, it just lists it as a generic SATA drive. I presume the drive controler is what the mother board uses or the HD controler?
I used a bios setup like this to strip the RAID setting on the hard drives and format the things.
The RAID setup was through a RAID card on that server pc and I was able to format the things when I bypassed the RAID controler and put it right to the mother board on that computer. The "New computers" I have a dual core lapotop and two P4 gigabyte motherboards with 4 SATA ports and they all respond to the SATA drives the same way. It sees the drive, gets the ID, I/O errors.
Sometimes, when all you want is to gain your freedom, you must be willing to risk it all.
The firmware of the harddrive controler was locked from direct access. Even a low level format will not change this as the lock is a setting in the hard drive's firmware.
I've never seen that in my life. When I used a WD diag program I got:
drive is locked 0220
So now I all I got to do is try a few programs I've found and see if these Hard drives can be "un locked"
Sometimes, when all you want is to gain your freedom, you must be willing to risk it all.
First please check the drives with that WD-Tools - it's more precaution but i consider it important since these are used HDDs
Then please check the actual jumper setting of every HDD and change them accordingly to your use.
As for this 'locked' message: http://forums.storagereview.com/index.php/...rive-is-locked/
See post #9 - the drives has to been deleted from the array in the old PC before removing them.
This may be the problem but there is this known bug with XP as described below.
Now here the info which may important for you when using XP:
XP will not recognize any SATA disk when there was NO SATA drive connected (or the HDD controller set to SATA mode) actually when installing XP.
Blame M$ you cannot change that nor reinstall any driver.
Anyway, I recommend to check the drives with a LINUX Live-CD.
There is a very good USB bootable Live-CD with a great partitioning tool: http://partedmagic.com/doku.php?id=downloads
The page also contains instruction how to create the Live-USB but i recommend YUMI: http://www.pendrivelinux.com/yumi-multib...b-creator/
This way you can easily check the drives and repartition your current drive
as i think you need to reinstall XP.
' Wrote:First please check the drives with that WD-Tools - it's more precaution but i consider it important since these are used HDDs
Then please check the actual jumper setting of every HDD and change them accordingly to your use.
As for this 'locked' message: http://forums.storagereview.com/index.php/...rive-is-locked/
See post #9 - the drives has to been deleted from the array in the old PC before removing them.
This may be the problem but there is this known bug with XP as described below.
Now here the info which may important for you when using XP:
XP will not recognize any SATA disk when there was NO SATA drive connected (or the HDD controller set to SATA mode) actually when installing XP.
Blame M$ you cannot change that nor reinstall any driver.
Anyway, I recommend to check the drives with a LINUX Live-CD.
There is a very good USB bootable Live-CD with a great partitioning tool: http://partedmagic.com/doku.php?id=downloads
The page also contains instruction how to create the Live-USB but i recommend YUMI: http://www.pendrivelinux.com/yumi-multib...b-creator/
This way you can easily check the drives and repartition your current drive
as i think you need to reinstall XP.
Whats happening on that link "http://forums.storagereview.com/index.php/topic/17412-western-digital-drive-is-locked/" is pretty much spot on to my issue. Trinity repair software and a WD utility is confirming its a 0220 locking error. I tried a partitionmagic program from a few hiren CDs I have to no avail. I'll check out that YUMI.
Sometimes, when all you want is to gain your freedom, you must be willing to risk it all.