HELP: System won't boot--HDD faint clicking

Hello again,

My Sony Vaio laptop won't boot :cry:cry. I believe the hard drive has gone bad; I can hear faint clicking sounds from the HDD location.

What are the tricks to kickstart the drive or to get it functioning to a level where I can attempt to salvage files that are stored on the drive?

Yup, I haven't backed up :cry:cry recently so there is a bunch of stuff to grab. Early on, I partitioned the drive with most of my data in a D-Drive. That is the stuff I really want to get at; the OS and other software I can re-establish.

What do you think...it is the boot sector that is corrupt or problematic and I should be able to copy files. Is there a checklist to approaching this problem that someone can give me or point to?

Thanks in advance.

 

Only two options:

Option #1: Remove said Harddrive and buy the external kit so you can hook it to another OC easily. BUT be very careful because those littler hard drives are delicate.

Option#2: ... "He Dead..."

Give up and just replace the drive... I had a WD Raptor drive die on me and that was like a shot in the chest . It began clicking and then it died altogether.

 

Thanks Frankzro,

I was thinking of trying the take it out approach. I have an external enclosure for laptop drives somewhere in this room...

Hopefully with an added prayer or two, it will start spinning so I can grab data.

 

Try putting it in the freezer and quickly copying the data. This is a last resort but has worked at times.

 

To add to this suggestion, if you do put it in the freezer, be sure to seal it inside a Zip-Loc bag (you do NOT want moisture to get to it), and only leave it in there for an hour or so.

 

I had read somewhere that freezing, it could help. I haven't put them in the freezer yet.

I have removed the drive from laptop and been very careful to place it in an external enclosure. The platters are spinning...I can feel and hear them; the two partitions show up in MY COMPUTER. Unfortunately, when I click on "Properties", they show zero bytes for used and free space. :cry

I think the heads aren't reading or haven't moved. The clicking sound was probably the mechanism attempting to move across the platter surfaces.

Freezer is next inside two zip lock bags.

Wish me luck!

 

Wishing you luck man!

 

Oh darn!

Well, the freezer route didn't make any difference. Both partitions are listed in MY COMPUTER but no files listed...zero bytes registering. I may give the freezer another shot.

So, if that fails and I want those files, is the only remaining retrieval option thru costly, expensive data recovery? Any other ideas?

:banghead :cry :cry

 

Now to reload and rebuild

Well, thanks for help...but had to kiss the old laptop drive good-bye. It wasn't going to reveal anything for me...

Should I consider data retrieval? Anyone know a REASONABLE company?

Moving on: I have replaced bad unit with a new, larger drive and installed another OS. Since this Sony VAIO came with all software (also with a bunch of crapware) on the HD, I don't have access to the old VISTA Business. But, this misfortune does present a good time to upgrade to Windows 7.

Here's the question: How do I rebuild the functionality of my laptop under Windows 7? Will I be able to regain all the capabilities or only limited items? For example, the use of built-in hardware devices, such as touch pad, fingerprint reader, function keys, etc.? I've downloaded a few device drivers from the Sony site which are specific for this model, but they don't seem to work properly.

Case in point is the ALPS touch pad. It worked before but after loading a few drivers for other installed hardware, I noticed the touch pad has stopped working. I can't tell or say which one is the culprit nor when it started. Also, my unfamiliarity with Win7 is hindering my search via control panel etc. :cry

I'm thinking of just wiping the drive clean and starting over again.

Also, don't forget to let me know if you have recommendations or resources for retrieving data from my dead hard drive.

Thanks.

 

On the data retrieval: When you select Properties of the laptop drive when connected to your computer does it show the filesystem as NTFS or FAT32 or does it say RAW?

If it says RAW then Partition Wizard or PowerDataRecovery may be able to retrieve some files. Both are free for home users. If you use powerdatarecovery you have to select the box that says you are a home user when first starting the program or it will ask you to upgrade and pay for retrieval which is not necessary.

If you try partition Wizard you would start the program and then select either partition on the laptop drive and right-click to Explore. See if it sees any files. If it sees files you can then use the partition recovery function to make a fresh copy of the partition table which Windows may be able to read. (Click on the HD in the graph. Select Partition Recovery from the left pane. Use Full Disk and Basic scan options. It will present a list of available partitions--double click the partitions and verify that it sees your files. If it sees the files then check all the boxes for the partitions and click Finish. Then click Apply in the main window. then see if you can access your files from Windows.) If it doesn't list any files then you might try PowerDataRecovery also from MiniTools.

****
One last thought is to do a HD manufacturer's extended test on the HD to see if it can fix any errors. Laptop HDs usually don't have very good utilities but depending on the brand you might get lucky. Which brand is the HD?

 

Hi Sach2,

Unfortunately, the drive is already out of the computer so I can't really do anything like mess with the settings, etc...or do you know how I can do that without causing further damage to the platters/data.

I have spoken with a few reps from data recovery places, and they suggest not trying make the drive spin more that anything. Also, when I first removed it and put it in an external drive enclosure, there was nothing listed...altho the two partitions were visible in MY COMPUTER.

I know, I'm not giving you much more positive info...

The manufacturer is Seagate...a Momentus 160GB.

Thanks for responding to my plea!

 

Hi,

Realistically, data recovery is prohibitively expensive for a home user. Well past $500. So I would think allowing it to spin up a few times won't really do much damage. Just my opinion.

You can use either of those programs with the HD attached by USB. Since the partitions are being seen, some information is being recognized from the drive. What you are looking for is whether or not the problem is a corrupted partition table which might be repairable. If it is repairable then you may be able to retrieve a large portion of your data. I would try running PowerDataRecovery from your new HD with the old one attached by USB. See if it can find any files and copy them to the new HD. Many people have good luck with the program. I really doubt you would be doing more damage and you could rule out a home user solution to the problem. Guide: http://www.powerdatarecovery.com/damaged-partition-recovery.html

Because you hear the ticking sound Seagate's SeaTools utility may not be able to correct the errors but it might be worth a try after attempting to get a copy of your data.

 

You said: "let me know if you have recommendations or resources for retrieving data from my dead hard drive"

If you suspect that a hard drive may be physically failing, I suggest that the first thing you should do is to clone the ailing HDD to another known good HDD, so that you can attempt to retrieve your data from the cloned copy rather than from the ailing HDD.

For the best chance of successful recovery:

• The ailing HDD needs to be connected directly to the motherboard of a desktop PC using either a SATA or IDE cable (not using a USB connection).
• The destination HDD also needs to be connected directly to the motherboard of a desktop PC using either a SATA or IDE cable (not using a USB connection).
• Use a Linux operating system run from a bootable CD or USB flashdrive to perform the cloning (with GNUddrescue).

Reference: DjLizard's data recovery guide

Do you have a spare (empty) HDD of equal or greater capacity than the ailing one that can be connected directly to the computer along with the ailing one?

Do you have a suitable desktop PC available to use for the recovery?

How you choose to go about the data recovery is ultimately up to you and the resources that you have available. It is possible that the data could be retrieved without first making a cloned copy, but there is always the risk that the HDD will fail completely while the data retrieval is in progress and you will lose any opportunity to recover the data.

 

Sach2 and AustrAlien,

Thanks for your recommendations. I was dealing with a malware problem on my desktop so couldn't dedicate the time to resolving the laptop ailments. I appreciate your insightful thoughts and leads.

Another reason for not responding to your recommendations was, on a whim and moment of utter delusion, I had packed and sent away the HDD to AI networks/Data Recovery. They are in CA and may have offered some good news since they offered a free assessment. Well, they just responded with an estimate ranging from $500-1800.. rolleyes. I just asked the guy, named Louis, to return the drive as that kind of money was way out of my league and range. :major

So back to square one to address my predicament.

Here is the situation: I have several computers, mainly desktops, which can be used and left running for data retrieval activities. I have downloaded the recommended software and will study the documentation you've provided.

AustrAlien:
1. You recommend direct connection to the MB which I can do by mounting the laptop drive into the desktop. Does doing this provide better connectivity and increase success?
2. You also recommend using Linux software, I am not very learned in that OS. Does Linux offer a definite advantage and higher potential for success?

Sach2: You mention I can use an external enclosure via a USB. Is your experience that use of a USB hinder or lessen success?

I don't know if I mentioned this before, but I set up my hard drives into two partitions/drives. The first one contains the OS and other apps, while the second partition/drive is where I stored most of the "data" I generated. I am anxious to retrieve as much data as I can...a lot of it being digital pictures.

I realize all of this data recovery/retrieval is way iffy stuff and I appreciate all the help and assistance offered thus far. Thank you, thank you, thank you.

This incident has convinced me to implement back up strategies and setups for all of the computers in my home. Currently, due to power use considerations, I do not run a server but have the capability to do so since my home is hard wire networked. I plan to definitely look into it and recently purchased two 1 TB drives. I have also considered online backup offered by several sites. Any experience or thoughts on those?

Enough...thanks again.

 

OUCH!:eek

Well, that's a good strategy. Power has nothing to do with this, turn it on when you need it. Compared to what it would cost you to retrieve data... I hope you didn't lose anything that's priceless like baby pictures.

 

You said: "I have several computers, mainly desktops, which can be used and left running for data retrieval activities."
Very good!

You said: "You recommend direct connection to the MB which I can do by mounting the laptop drive into the desktop. Does doing this provide better connectivity and increase success?"
Most definitely, it does. A USB connection is not at all suitable for data recovery: It is prone to data corruption and reduces the "readability" of data under problematic conditions. For data recovery, it is always best to have a direct connection to the motherboard and not to attempt to use a USB connection.

You said: "Does Linux offer a definite advantage and higher potential for success?"
Yes it most certainly does. Don't be concerned about the lack of familiarity with Linux: I will provide you with detailed instructions for the task(s) which you will be able to follow easily.

A couple of questions ...
1. Does the ailing hard drive have an IDE/ATA or SATA connection?
2. Will the destination hard drive (for the cloned copy) have an IDE/ATA or SATA connection?
The nature of the HDD connections may influence the way you should go about setting up the hardware, and determine whether you should use a bootable CD or a flashdrive to run Linux.

 

Thanks AustrAlien,

I appreciate your willingness to assist.

In response to your questions:

1. The malfunctioning laptop drive has a SATA connection. I will need some kind of a SATA connector/adapter in order to install this laptop drive into a desktop system. The USB external enclosure setup has the correct connector for the malfunctioning drive but nothing that can be used in a desktop system. I need to do some research.

2. The destination drive can be either SATA or IDE. I have two desktops available...an IDE system and a SATA system. Which ever is more optimal, I will just have to find ways (adapters) to connect the drives directly to the motherboard.

As I understand it, both drives should have the same type of connection correct?

I will do my research and get back to you. Thanks,

bkt

 

SATA connections & hard drives would be most convenient. SATA hard drives, whether 2.5" or 3.5", both have the same connections.

No adapters needed for the SATA hard drives ... just use the normal SATA connecting cables that are already being used in the computer (disconnect the existing hard drive(s)/optical drive and use those cables).

 

OK, then I will be using my primary desktop which has all SATA drives. I will likely have to dismantle most of it, particularly the hds for this purposes.

Now with that settled, it appears I will need to keep a ROM drive in order to boot from CD. Will this process simply make an image of the file contents or do file-by-file downloads? The destination drive I will be installing is brand new. Is there any preparation I need to do such as formatting and/or partitioning it before hand?

I appreciate your being able to walk me thru this process. Thank you.

 

You said: "I will be using my primary desktop"
The recovery may take only a few hours: On the other hand, it may take longer, depending on what is found. Can you afford to be without the use of this machine for 24 hours, a couple of days, .... a week in an extreme case??? If we use a USB flashdrive instead of a CD to run the Linux operating system, a log file of the recovery will be conveniently saved on the flashdrive: You will then be able to stop the cloning process and switch off the computer at any time that you wish, and have the log file saved. You will be able to continue the cloning process at any later time from where you last left off, by using the log file.

You said: "I will likely have to dismantle most of it, particularly the hds"
No need to dismantle anything: Simply un-plug the power and SATA data cables (best to disconnect all other devices to reduce possible confusion later) and plug them into the two HDDs that you will be connecting. The two HDDs can be simply placed beside the machine (out of the box), although you may need to stand them on some books or something similar, so the cables will reach them. This kind of arrangement needs extra precaution ... in that it should be safe from being accidentally upset.

You said: "I will need to keep a ROM drive in order to boot from CD"
No, not necessarily: It would be preferable if you could use a USB flashdrive to run the Linux operating system.

You said: "Will this process simply make an image of the file contents or do file-by-file downloads?"
The initial cloning process will make an exact copy (clone) of the ailing hard drive's data (everything readable), block-by-block, to the destination HDD. From the cloned copy, you can then retrieve your files safely (hopefully).

You said: "The destination drive I will be installing is brand new. Is there any preparation I need to do such as formatting and/or partitioning it before hand?"
Brand new and blank is just fine as it is! Cloning will replicate the partitioning and formatting on the ailing HDD.

 

Well, this desktop is the only one I have which uses SATA connections. If need be, I have the laptop from which the failed drive was removed. So, I probably could get by for a few days. To set things up, I will pull the power and connectors from all drives and ROMs and hookup/install only the problem drive and destination (which will be blank).

OK, no problem with using a USB flashdrive.

I still haven't received the drive from AI Networks yet. Hopefully, it should be here by week's end.

How do we start preparing the flashdrive with Linux? I have never used a flashdrive as a boot source so will need guidance. Also, I ask that you give me a list of specific files and/or direct me to online locations where I download them. As I've said before, this is uncharted territory for me but I look forward to the challenge.

 

You said: "I will pull the power and connectors from all drives and ROMs and hookup/install only the problem drive and destination (which will be blank)."
That's good: To make things easier and minimise the chance of a mistake, I would like you to connect the source HDD (the ailing laptop HDD) to the lower numbered SATA port (you will see the SATA port numbers written on the motherboard), and the destination HDD to a higher numbered SATA port (eg. source > SATA 1, destination > SATA 2).

You said: "How do we start ......... I look forward to the challenge."
I don't think it will be much of a challenge: I have tried to make it as easy as possible for you. Nevertheless, I think you will enjoy the new experience. When you get Linux on the flashdrive, go ahead and test it out, and play around with it.

OK, now let's get started ...

If you intend to use a flashdrive:

• Your computer BIOS must be capable of booting a flashdrive, which will be referred to in the BIOS Setup Menu or Boot Menu, as one of the following:
  • USB KEY
  • USB HDD
    or perhaps some other similar term.
• You will need a flashdrive of 256 MB capacity or greater.

Step 1: Create a bootable RIPLinux flashdrive:

1. Download Bootable ISO (RIPLinuX-13.5.iso)
   • 
     Download file size: 157 MB
     RIP Linux home site!
2. Download Universal-USB-Installer-1.8.6.2.exe
   
3. Follow the directions at the Universal USB Installer (Home Site) to create a bootable RIPLinux flashdrive.

Step 2: Boot to the RIPLinux flashdrive:

• 
  (You may have to configure the Boot Menu or BIOS Setup Menu to boot first from the USB flashdrive.)
• If the system successfully boots to the flashdrive, you will very quickly be presented with a blue box, listing a number of boot options.
• Use the <down-arrow> key to highlight the 4th option down the list:
  • 
    - Boot Linux system to X! (skip keyboard prompt)
• Press the <ENTER> key.
  Please be patient: The system will take a little time to load into memory.
  You will be presented with the RIPLinux Desktop (a blank, blue screen).
  • An introductory window will inform you that right-clicking anywhere on the Desktop will bring up the Menu, and that moving the mouse pointer to the bottom edge of the screen will bring up the Taskbar.

To shut down the computer:

• Right-click anywhere on the Desktop.
• Logout > Halt/Poweroff system

 

Ok...thanks. While I wait for the return package with my drive, I will download the software, look into and setup the bios, load the flashdrive, and familiarize myself with the process and software.

I just checked and the drive was shipped yesterday; it is scheduled for delivery late tomorrow.

I will check back with you if I run into problems along the way.

 

When you are ready ...

Step 1: Setup your hardware for cloning.

Warning: Ensure that all power is switched OFF, and that you ground yourself to the metal box before touching components.

1. Disconnect all HDDs and optical drives attached to your computer motherboard, and disconnect any other unnecessary external devices from the computer.
2. Attach the ailing HDD to SATA port 0.
3. Attach the destination HDD to SATA port 1.
4. Ensure that you have also connected power cables to both HDDs.

Note: Which ports you use doesn't matter, but I would like you to connect the ailing HDD to the lower numbered port: For example if you wished to use ports 2 & 3, then connect the ailing HDD to port 2, and the destination HDD to port 3.


Step 2: Boot to the RIPLinux flashdrive:

• 
  (You may have to configure the Boot Menu or BIOS Setup Menu to boot first from the USB flashdrive.)
• If the system successfully boots to the RIPLinux device, you will very quickly be presented with a blue box, listing a number of boot options:
• Use the <down-arrow> key to highlight the 4th option down the list:
  Boot Linux system to X! (skip keyboard prompt)
  and press the <ENTER> key.
  Please be patient: The system will take a little time to load into memory.
• At the RIPLinuX Desktop (plain blue screen), close the information window by clicking on the small X.
• Right-click anywhere on the Desktop and choose XTerm.
• At the # prompt, type fdisk -lu (that is a lower case L after the dash/minus sign, not a ONE) and press <ENTER>.
  You will see listed there, information about the devices connected to the system, and I expect that you will see three sections there, representing the 3 devices:
  • sda ... the source (ailing) hard drive
  • sdb ... the destination hard drive
  • sdc ... your flashdrive
• Look at the top line of each section, which will read something like:
  • Disk /dev/sdb: <number=size of hard drive> MB, <number> bytes
• Please confirm that the reported size in MB corresponds to the expected capacity of each of the devices, and post the details for me to see, please
  (like this Disk /dev/sdb: <number=size of hard drive> MB .... this is the <?destination> hard drive).

Close the XTerm window and shut down the computer if you wish.

 

Hello AustrAlien,

Sorry for the delay in getting back to you. I had a few other pressing items to address.

I've downloaded the RIPLinuX-13.5.iso and Universal-USB-Installer. After a few hiccups, I figured out I had to select the RIPLinuX from the drop down installer menu in order to see and select the RIPLinuX-13.5.iso. Once I succeeded in getting the flashdrive loaded, I configured BIOS to boot from the flashdrive. I was able to boot from the flashdrive and exit LinuX.

Next, I reconfigured the hard drives per your instructions, booted the system, and initiated the fdisk -lu command in XTerm.

Here's what I see:

Disk /dev/sdb: 1000.2GB, 10002040886016 bytes
Disk /dev/sdc: 4127 MB, 4127195136 bytes

Sadly, not seeing an entry for sda...doesn't look too good....right? :cry

I await your response.

 

I am very pleased to know that you have not abandoned me/the project.

sda .... just has to be there! It will be at the top of the screen. You may have to scroll up/down the XTerm window to see all the information displayed?

• 
  Click the mouse's right-button and left-button in the scroll-bar on the left side of the XTerm window to scroll up/down respectively, if necessary.

Do you see it now?

 

Nope...sda is not there. I knew from the information you provided that the disk identifier "sda" would denote the problem drive.

I don't know for sure if the drive was spinning or not as I thought to check after I had turned off the system. I did detect some heat---a little warmth but not hot...after touching the underside of drive. I will attempt to run the setup again a few more times and once after placing it in the freezer for an hour or so.

If I do get lucky and see a correct entry for sda, what steps will I then do? Will I need any other files, or software, similar to mini data recovery that Sach2 had suggested or will I be using LinuX commands to copy files to the destination drive?

At this point, does anyone foresee problems with repeated efforts, such as these, being detrimental? Also, does anyone see any indications that the high cost of data retrieval ($500-1800) coming down in the foreseeable future? I've even wondered what potential existed for using services overseas, such as in UK?

Again, thanks in advance.

 

I don't want to interfere with Australien's instructions but you may want to check in BIOS to see if the problem HD is being seen there. If it isn't being seen in BIOS then you have a mechanical problem with the drive.

The key to hit for entering BIOS/Setup is usually shown on the splash screen when first booting the computer. You would be doing this on your desktop with the HD attached. Once in BIOS you would be looking for Storage or something of that sort for a list of drives connected. If you give the BIOS vendor and version number we can help with the screens. You can move fairly freely through BIOS as you will always be given an option to Quit WITHOUT saving any changes (recommended in this case since you are only looking for information).

 

Thanks Sach2, good tip...for this motherboard, the DEL key initiates entry into BIOS. The system does show hard drives on the screen during boot up but it flashes too fast for me to be positive what is really there.

So, if the BIOS doesn't see the drive, or the drive can't be coaxed to spin, then only option left is a clean room repair of the mechanics and download of data?

I am somewhat familiar with navigating thru the BIOS screens so no help needed in that area...thanks!

AustrAlien and Sach2:

I did get a hint while LinuX was loading/booting that something may be amiss...there were a few lines/entries referencing slow access to a drive. After a several attempts, it abandoned trying and went on with the rest of the boot up. When I entered the fdisk -lu command in XTerm, it confirmed the difficulties and inability to connect with the malfunctioning drive...absence of an sda entry.

General comment: Way back when, many years ago, I toyed with the idea of dabbling in LinuX. I have a dual pentium...can't recall the socket type but it has the large plastic enclosure...which I built and it is just sitting around taking up space. I kept it to eventually using as a LinuX server. This experience and exposure to LinuX has gotten me interested again...but just a bit. LOL Too many things to do; so little time.

Thanks guys...awaiting further thoughts.

 

If BIOS doesn't see the drive then no software will see the drive. Any OS/Rescue disc is going to be getting its information about the PC hardware from BIOS. So if the drive isn't powering up enough or its circuit board is bad and BIOS can't recognize it then disassembly and data recovery are the only options I can see.

Check BIOS and see if it can see the HD and lists its model number and size. Then you know it is possible to continue various software retrieval methods. I still think PowerDataRecovery is a software option. Burn the CD and see if it recognizes the drive you'll know that much in 1 minute whether you use it for retrieval or not.

 

Thanks sach2: We should have established this information first.

Let's see what is revealed when you check in the BIOS Setup Menu for information about the ailing HDD. If it is detected normally in BIOS, then we have a chance: If not .... then your luck has run out.

If you have no luck first time round, then I suggest trying a different connecting cable, and SATA port ..... preferably the lowest port number available ... SATA 0 ?

 

Thanks for your assistance this far, Sach2 and AustrAlien.

OK, here is the latest update...

I finally got a chance to work on this problem again. I tried the freezer again...no joy I had booted using LINUX and it didn't recognize the ailing drive. Also, as far as I could tell, the BIOS didn't recognize the presence of the ailing drive.

So, I went back to using the USB external enclosure and installed the drive. When connected via USB, the system identifies the two partitions in MY COMPUTER as two separate local drives. I can feel the platter spinning. When I double click on them, I get the dialog box asking if I want to format them...to which I indicate NO. Earlier, I was able to right click and get the PROPERTIES box to display which says:

File system: RAW

0 bytes for used and free space as well as capacity.

What does this say or mean? Any other suggestions?

 

I was wondering where you had got to: Welcome back!

You said: "as far as I could tell, the BIOS didn't recognize the presence of the ailing drive."
That statement does not give me a lot of confidence in knowing one way or the other ... so I am still in doubt about whether or not the ailing HDD is recognised in BIOS or not. Granted, in some BIOS Setup Menus it is difficult if not impossible to determine whether or not a SATA device is detected/present. The fact that you report seeing two partitions displayed in My Computer when connected via USB enclosure indicates to me that the hard drive is being recognised in BIOS.

You reported earlier: "The system does show hard drives on the screen during boot up but it flashes too fast for me to be positive what is really there."
I would like you to try again .... with the ailing hard drive attached to the motherboard of a desktop PC. One of the first screens displayed when booting the computer will list IDE devices: Depending on your particular BIOS, you may also see SATA devices listed beneath the IDE devices ... or .... the SATA devices may be listed separately at a slightly later time in the booting process. It is likely that the screens will change too rapidly for you to thoroughly read and understand what is displayed: If that is the case then you can use the <Pause> key to stop the screen so that you can read it properly, and when ready, press the <ENTER> key to resume booting. It may be that you see options to configure RAID: If so, you may well also see the SATA hard drive listed there.

You said: "When connected via USB, the system identifies the two partitions in MY COMPUTER as two separate local drives."
That is a very interesting observation (and not what I would expect), given what you have reported when the ailing hard drive is connected to the mobo directly and you are booted to RIPLinux.

I don't know whether you might have tried this set up or not. Instead of connecting the ailing HDD via USB to a working Windows system, connect the ailing HDD directly to the motherboard (as a secondary hard drive), and then boot into the usual Windows system normally. Can you boot successfully? Can you see the hard drive/the two partitions in My Computer as you do when connected via USB?

What happens when you boot with the RIPLinux CD with the ailing hard drive connected via USB? Do you see the hard drive and its two partitions also? (use fdisk -lu command)

You asked: "What does this say or mean?"
I admit to being baffled as to the exact meaning of what you are reporting.

You asked: "Any other suggestions?"
I have two: Firstly, we could try cloning the ailing HDD to a new HDD (as we were planning to do) ... even though sda is not being reported in RIPLinux using fdisk. We know it is being seen as sda (just not reported on-screen) .... so we could go ahead with the attempt to clone it. We have nothing to lose by trying this. I simply have not come across this situation before, where the hard drive is not being reported using fdisk.

Secondly, it may be worth trying TestDisk from RIPLinux (while the ailing HDD is connected via USB? .. or otherwise). If the two partitions can be seen in My Computer/Windows, then they should also be found using TestDisk, I would expect, and if so, perhaps we might be able to recover the contents of your D: drive using that.