|
Problem description: Picked up a gov surplus computer, probably 3 years old. Put in a new 860 EVO SSD. Installed all my poo poo and I noticed occasionally I get a non-system disk error and it won't boot. I just restart and for a while it would just boot into windows normally. It eventually stopped booting into windows. Attempted fixes: I used diskpart and a host of CMD from a repair CD and I noticed I had no boot partition. No fat32 EFI partition and rebuildbcd would error out. I used gparted to carve out some space at the back and I remade a EFI partition and told windows to boot from it. Upon restart windows actually booted. However when I restarted again I got a non-system disk error. Restart and it booted back into windows. Is this a bad HDD? Recent changes: Plugging in a second HDD. Maybe a cable or mobo connection problem? -- Operating system: Windows 10 System specs: HP Compaq Elite 8300 Location: United States I have Googled and read the FAQ: Yes/No/Maybe
|
#
?
Mar 14, 2018 16:16
|
|
|
|
| # ? Apr 29, 2024 15:11 |
|
|
Goodpancakes posted:Is this a bad HDD? Maybe a cable or mobo connection problem? Yes, it could any of those three. I'd try another SATA cable and different motherboard port and see if it makes any difference. It's a broad error: https://www.partitionwizard.com/partitionmanager/non-system-disk-or-disk-error.html
|
|
#
?
Mar 14, 2018 22:45
|
|
