The link you posted is not for the specific drive.
Then that's a problem with the WDC website, because it was the only search that returned a hit for that part number.
I don't doubt that you are seeing the sticker on the HDD as "WD2500BS". Such code indeed matches one possible naming method of older WDC products. But since it is not listed in WDC and there is no "specifications" page for such product, the only way to have such HDD is as part of another product of WDC (or buying it second hand).
It wasn't part of another WDC product or purchased second-hand. As I pointed out in my first post, it's the hard drive from my TiVo Series 3 HD DVR.
Anyway, my intention was to avoid a long series of questions. For example:
1_ Is the HDD SATA_I or SATA_II (there is conflicting info, depending on the source)?
2_ Are you using a (red) SATA_I or a SATA_II cable? Or perhaps you are still using the original bundled WDC cable?
3_ Is the controller SATA_I or SATA_II?
4_ Is this HDD connected internally and directly to the mainboard?
5_ Which HDD jumpers are you using, if any?
6_ Which BIOS settings are you using (AHCI? RAID?, legacy? …)?
Bear with me here, because I obviously don't know what I'm talking about when it comes to SATA HDDs. Here are my attempts to answer your questions, as numbered:
1. That's a tough call. I honestly don't know. (see answer 2)
2. For testing I'm using a red SATA cable in a Dell Dimension 8400. The original bundled cable in the TiVo is also red, same pinout, but is combined with the power cable. In the Dimension, I used separate red SATA data and power cables.
3. I don't know what the controller in the TiVo is. In the Dell Dimension 8400, I'm using a SATA/150 PCI expansion card to interface to the WD2500BS. I'm not using the SATA controllers on the motherboard. You've raised a good point here. I'll figure out which of the MB controller SATA drives is the system drive, and replace the other with the WD2500BS. Maybe the change in controllers will make a difference.
4. See above. It's connected to the SATA/150 PCI expansion card.
5. There aren't any jumpers installed on this drive. Unfortunately, the label doesn't have any info about jumper settings. I checked the circuit card too because sometimes jumper labels appear there, but there weren't any. What I can tell you is that the drive as configured acted as a slave in the Dimension 8400 and didn't interfere with the operation of the other drives.
6. Argh! This one will take time to answer. I'm rendering another Blu-Ray recording on the Dimension 8400 and don't want to interrupt it to run the BIOS setup. I'll post the answer to this one sometime tomorrow.
If you are using this HDD with some other connection (USB-SATA, or eSATA for example), then perhaps DataLifeGuard Diagnostics for DOS might not provide correct results. The fact that the software (in this particular version of the tool) identifies the HDD doesn't mean it supports it for correct scanning. It may, or maybe not.
See my responses above for details on the interface I'm using. I thought I should use internal interfaces exclusively for testing purposes, since the interface in the TiVo was also internal.
You could try using an older version of DLG Diagnostics, if the drive controller and the cable are the correct ones.
I have an EXE for the DLG diagnostics that may be an older version. I just haven't figured out how to get it onto a bootable DOS cd yet.
Generally speaking, if the drive is working (no "clicking" sounds, no bad connections,...) and if Windows can detect the drive, there are many freeware tools that list the S.M.A.R.T. values of each HDD in your system, in which case you could confirm the values you already received.
I noticed during runs of the DLG quick test (whether it was run standalone or as the first part of the extended test) that a lot of clicking was going on in the drive. However I didn't know if this was a normal reaction to the tests, or an indication of a dead drive.
When I booted in Windows to see what would happen, the OS detected the drive in the Windows Disk Manager. However it told me that I would have to initialize the drive in order to use it. That meant formatting it which I did not want to do.
What the hey, if I can't figure out what's going on with the disk in the TiVo, I may be able to use it as a spare in Windows. I really do want to try to recover the recordings on the disk though.
In general, when threshold values are met, it might indicate that the HDD is much closer to its EndOfLife. Just as a HDD with "nice" SMART values can crash without previous signs, having "ugly" values does not necessarily mean that the HDD is already "in bad shape with 100% of certainty". But, it would be wise to have backups of the important info in such drive.
Keeping backups of a TiVo drive is problematic. They don't make it easy to access the data on the drive, at least not in the context of the TiVo DVR. The closest TiVo comes to providing backups is to include a sort of "Recycle bin" of previously deleted recordings. Where those are actually stored is ambiguous. They might be on the internal drive, on the external eSATA expasion drive, or both. In that sense they're not much good as backups.
In some cases, bad SMART values might be originated by bad cables or something else in the system, so eventually changing the HDD might not solve the source of the problem.
I'll have to do some additional work on the SMART values and what they mean. There are other tests on this boot CD which are not specific to drive brand and appear to report the SMART status. But again, I have to wait for that Blu-Ray to finish rendering.
Hey, thanks for your patience in answering my posts. Keep in mind that I'm essentially ignorant, just barely able to get a driving license these days.