F5F Stay Refreshed Software Operating Systems Laptop with SSD and HDD installed; replacing HDD leads to failure to start.

Laptop with SSD and HDD installed; replacing HDD leads to failure to start.

Laptop with SSD and HDD installed; replacing HDD leads to failure to start.

D
Darst04
Member
56
04-16-2022, 04:16 AM
#1
I have an older Dell M6500 laptop equipped with a 256GB M.SAT boot SSD and two 500GB hard drives. It functions well as a portable workstation. I plan to upgrade one of the drives to a larger capacity, moving from a 500GB WD Blue to a 1TB WD Blue. The new drive is completely unallocated and freshly formatted after an SFF installation. Once the system restarts in Windows, I should navigate to Disk Management, format and partition the new drive as usual. I previously backed up all data from the 500GB drive to an external storage device as a precaution, intending to transfer everything over once the new drive is installed. After swapping the 500GB WD Blue for the 1TB WD Blue, the system displays a blinking line that seems to persist indefinitely. This behavior is unusual since the operating system resides on the SSD, which hasn’t been modified during this process. My Windows 10 installation remains fully functional and up-to-date, and I ensured it was shut down properly—even disabling Quick Startup in Power Options. I attempted various troubleshooting steps: checking for a BIOS reset by removing the battery, adjusting boot order to prioritize the SSD, and manually selecting the drive via the startup menu. All attempts yielded no results. I discovered a recovery partition on this drive that I need to replace or upgrade. I’m uncertain why this partition is required for booting, as it appears I only selected the SSD during the initial installation. Should I move this recovery partition to the new drive? Am I missing something obvious? Or do I need to reinstall Windows 10 onto the SSD without any other drives attached? Please let me know—any guidance would help extend the life of this laptop.
D
Darst04
04-16-2022, 04:16 AM #1

I have an older Dell M6500 laptop equipped with a 256GB M.SAT boot SSD and two 500GB hard drives. It functions well as a portable workstation. I plan to upgrade one of the drives to a larger capacity, moving from a 500GB WD Blue to a 1TB WD Blue. The new drive is completely unallocated and freshly formatted after an SFF installation. Once the system restarts in Windows, I should navigate to Disk Management, format and partition the new drive as usual. I previously backed up all data from the 500GB drive to an external storage device as a precaution, intending to transfer everything over once the new drive is installed. After swapping the 500GB WD Blue for the 1TB WD Blue, the system displays a blinking line that seems to persist indefinitely. This behavior is unusual since the operating system resides on the SSD, which hasn’t been modified during this process. My Windows 10 installation remains fully functional and up-to-date, and I ensured it was shut down properly—even disabling Quick Startup in Power Options. I attempted various troubleshooting steps: checking for a BIOS reset by removing the battery, adjusting boot order to prioritize the SSD, and manually selecting the drive via the startup menu. All attempts yielded no results. I discovered a recovery partition on this drive that I need to replace or upgrade. I’m uncertain why this partition is required for booting, as it appears I only selected the SSD during the initial installation. Should I move this recovery partition to the new drive? Am I missing something obvious? Or do I need to reinstall Windows 10 onto the SSD without any other drives attached? Please let me know—any guidance would help extend the life of this laptop.

E
Eppikx
Senior Member
447
04-16-2022, 04:16 AM
#2
x
E
Eppikx
04-16-2022, 04:16 AM #2

x

K
Kavenoke
Member
242
04-16-2022, 04:16 AM
#3
I can use BIOS with the 1TB drive, but it always ends up at the blinking prompt regardless of boot settings or manual selection via F12. I’m not sure the 1TB is failing; I just cleared all previous partitions on another system without issues. I’ll check if the OS can start using only the SSD. I haven’t tried that yet.
K
Kavenoke
04-16-2022, 04:16 AM #3

I can use BIOS with the 1TB drive, but it always ends up at the blinking prompt regardless of boot settings or manual selection via F12. I’m not sure the 1TB is failing; I just cleared all previous partitions on another system without issues. I’ll check if the OS can start using only the SSD. I haven’t tried that yet.

L
legonalas
Junior Member
10
04-16-2022, 04:16 AM
#4
This setup uses the Windows bootloader to start the installation. During installation, the bootloader isn't always placed on the selected drive. Once you connect the SSD, you must generate a new bootloader by booting into the Windows installer and entering the recovery mode, then proceed with the provided guidance.
L
legonalas
04-16-2022, 04:16 AM #4

This setup uses the Windows bootloader to start the installation. During installation, the bootloader isn't always placed on the selected drive. Once you connect the SSD, you must generate a new bootloader by booting into the Windows installer and entering the recovery mode, then proceed with the provided guidance.

G
Grim11
Junior Member
13
04-16-2022, 04:16 AM
#5
that seems just stupid enough that windows would actually do it. i will try this later today.
G
Grim11
04-16-2022, 04:16 AM #5

that seems just stupid enough that windows would actually do it. i will try this later today.

M
monkeykatje
Junior Member
12
04-16-2022, 04:16 AM
#6
I've attempted the recommended actions, but the SSD isn't functioning as a GPT drive.
M
monkeykatje
04-16-2022, 04:16 AM #6

I've attempted the recommended actions, but the SSD isn't functioning as a GPT drive.

T
Thumps209LV
Member
226
04-16-2022, 04:16 AM
#7
Transform your SSD to GPT format and follow the guide at the provided link.
T
Thumps209LV
04-16-2022, 04:16 AM #7

Transform your SSD to GPT format and follow the guide at the provided link.

H
happy_felix
Junior Member
4
04-16-2022, 04:16 AM
#8
will this end up wiping the drive? if thats the case i may as well reinstall with no other drives in place. this is a legacy system, i do not believe it has uefi.
H
happy_felix
04-16-2022, 04:16 AM #8

will this end up wiping the drive? if thats the case i may as well reinstall with no other drives in place. this is a legacy system, i do not believe it has uefi.

D
DDBanister
Member
60
04-16-2022, 04:16 AM
#9
It turns out the M6500 model is really challenging to work with. I attempted a workaround but encountered issues where the disk wouldn’t validate during setup. When trying to boot using only the SSD, it displayed the same error repeatedly. Eventually, I found a solution that functions for me and likely not others—using the 500GB backup drive instead. That drive works perfectly, so I replaced the problematic one with the 1TB model. Now everything is stable. This system seems particularly tricky, probably due to its older hardware paired with first-generation SSDs.
D
DDBanister
04-16-2022, 04:16 AM #9

It turns out the M6500 model is really challenging to work with. I attempted a workaround but encountered issues where the disk wouldn’t validate during setup. When trying to boot using only the SSD, it displayed the same error repeatedly. Eventually, I found a solution that functions for me and likely not others—using the 500GB backup drive instead. That drive works perfectly, so I replaced the problematic one with the 1TB model. Now everything is stable. This system seems particularly tricky, probably due to its older hardware paired with first-generation SSDs.