- Thread Author
-
- #1
Hello,
I had a working 64gigs SSD + 160gigs (friends) HDD. Today, my new 1TB HDD arrived, so I switches the HDDs, but after I wanted to boot, weird thing happened.
no partition
Grub Rescue >>
and something like that...
Okay I tried some things I found on net, but then I just reinstalled my PC. It booted okay, everything smooth. After I restarted PC and took out the instalation CD, same happened (with new instalation).
After I put back the CD, Windows can normally boot. Weird thing is, that when I tried to load new instalation from CD and tried to repair my Windows, it saw the instalation of my Win 7, but it was situated on D:/ disk. My system disk is actually on C:/.
So, did something wierd happening, and the system thinks that my bootloader is situated on D:/ when its on C:/ instead? Anyone can help me with it?
PS: I had never have a linux distro on this SSD.
Thank You!
edit: switching sata cable do make C:/ master helped
I had a working 64gigs SSD + 160gigs (friends) HDD. Today, my new 1TB HDD arrived, so I switches the HDDs, but after I wanted to boot, weird thing happened.
no partition
Grub Rescue >>
and something like that...
Okay I tried some things I found on net, but then I just reinstalled my PC. It booted okay, everything smooth. After I restarted PC and took out the instalation CD, same happened (with new instalation).
After I put back the CD, Windows can normally boot. Weird thing is, that when I tried to load new instalation from CD and tried to repair my Windows, it saw the instalation of my Win 7, but it was situated on D:/ disk. My system disk is actually on C:/.
So, did something wierd happening, and the system thinks that my bootloader is situated on D:/ when its on C:/ instead? Anyone can help me with it?
PS: I had never have a linux distro on this SSD.
Thank You!
edit: switching sata cable do make C:/ master helped
Last edited:
Solution
- Joined
- Mar 14, 2023
- Messages
- 100,447
It sounds like there was an issue with the bootloader location after installing the new 1TB HDD. Since switching the SATA cable made the C:/ drive the master and resolved the problem, it likely corrected the boot sequence and bootloader detection. Here's a brief explanation of what might have happened and why changing the cable helped:
Bootloader Location and SATA Configuration:
- Bootloader Location: The Windows bootloader manages the startup process. If it was mistakenly associated with the D:/ instead of C:/ during the HDD switch, it could cause boot issues.
- SATA Connection: The SATA cable change can affect the drive order detected by the BIOS. By making C:/ the master drive through the cable switch, the system correctly identified the bootloader location.
Resolution and Future Considerations:
- Boot Configuration Data (BCD): Windows uses the BCD for boot information. It's crucial to check and confirm the correct bootloader path in the BCD for future reference.
- BIOS Boot Order: Adjusting the boot device order in the BIOS can also help ensure the system boots from the correct drive.
Preventive Steps:
- Backup and Recovery Options: Having a backup of critical data is essential to prevent data loss during such transitions.
- System Imaging: Creating system images can help restore the OS to a working state quickly if issues arise during hardware changes.
- Boot Repair Tools: Consider keeping boot repair tools handy, such as Windows Recovery Environment or third-party boot repair utilities. By ensuring the correct drive is recognized as the boot drive and checking the BIOS boot order, you can maintain a stable boot environment and avoid similar issues in the future. If you encounter any other complexities or need further assistance, feel free to seek additional help.