[pparker1500]

jpiszcz, on 29 January 2010 - 05:52 PM, said:

As far as I know the only way to flash these drives is to use the DOS boot disk, also note that about only half of my drives flashed, in addition someone else ran the flash and it hung up. I really think the Velociraptors simply do not work correctly in a parity-raid configuration.

It looks like we are going to dump the drives we have, send the new ones back as switch to a different Mfg'r and different drive, which will probably be a 7200RPM (there are no other 10,000RPM/SATA/2.5" drives out there)

Do you know if a single drive, no RAID will have an issue with Linux?

[jpiszcz]

pparker1500, on 29 January 2010 - 05:58 PM, said:

It looks like we are going to dump the drives we have, send the new ones back as switch to a different Mfg'r and different drive, which will probably be a 7200RPM (there are no other 10,000RPM/SATA/2.5" drives out there)

Do you know if a single drive, no RAID will have an issue with Linux?

Hi,

That is what I am currently running but not on a 24/7 host, it did run ok for a few days, did not have any problems. I am continuing to use it in single-disk configuration, will update this thread if I see any trouble with it.

Justin.

[pparker1500]

jpiszcz, on 29 January 2010 - 05:52 PM, said:

As far as I know the only way to flash these drives is to use the DOS boot disk, also note that about only half of my drives flashed, in addition someone else ran the flash and it hung up. I really think the Velociraptors simply do not work correctly in a parity-raid configuration.

Justin,

Do you know if this same issue shows up in a single drive, non-RAID config running under Linux?

- Pat

[jpiszcz]

pparker1500, on 01 February 2010 - 08:53 PM, said:

Justin,

Do you know if this same issue shows up in a single drive, non-RAID config running under Linux?

- Pat

Assuming second message was a mistake? So far no issues running with just 1 disk.

[jpiszcz]

Well,

I had been using a single Velociraptor hard drive for my Linux system.
It worked well for awhile (never kept it on for more than a few hours).

Recently, I left the computer on for more than 24 hours.

# screen -ls
-bash: /usr/bin/screen: Input/output error
# ls
-bash: ls: command not found
# dmesg
-bash: dmesg: command not found
# ls
-bash: ls: command not found
# /bin/ls
-bash: /bin/ls: Input/output error
# echo "This is what happens when you use a Velociraptor hard drive."
This is what happens when you use a Velociraptor hard drive.
#

In addition, when I reboot, the system can no longer boot, e.g.
UNABLE TO BOOT FROM HARD DISK

Fun stuff, I don't have time now but I will look at this later to try and figure out what happened.

Justin.

[jpiszcz]

I am making another attempt, I am RMA'ing all 12 hard drives to WD, we will see if they have fixed the problems.