britechguy
Well-Known Member
- Reaction score
- 4,809
- Location
- Staunton, VA
Hello All,
This is a first for me, so I thought I'd ask here before I started tearing the machine down again and returning things. On my primary laptop I just installed a new keyboard, fan, and Mushkin 1TB SSD a couple of days ago. I cloned the existing drive to it, and everything was hunky-dory up through last night.
I went to bed with my first backup from the SSD to my usual USB backup drive and when I came back downstairs this morning I had a black screen with a "no boot device found" message. Attempts to fire up after a power-button-hold shut down are now just giving black screen. I don't even get the HP splash at the start of boot.
Anyone care to venture a guess as to the root cause? If push comes to shove it's a new computer, but I really hope it doesn't come to that, as I do like the one I've got. I also still have the 2TB HDD that was its system drive that I can plop back in for testing purposes.
I've never had an SSD fail this way this quickly, and I suspect that's what's happened, though.
This is a first for me, so I thought I'd ask here before I started tearing the machine down again and returning things. On my primary laptop I just installed a new keyboard, fan, and Mushkin 1TB SSD a couple of days ago. I cloned the existing drive to it, and everything was hunky-dory up through last night.
I went to bed with my first backup from the SSD to my usual USB backup drive and when I came back downstairs this morning I had a black screen with a "no boot device found" message. Attempts to fire up after a power-button-hold shut down are now just giving black screen. I don't even get the HP splash at the start of boot.
Anyone care to venture a guess as to the root cause? If push comes to shove it's a new computer, but I really hope it doesn't come to that, as I do like the one I've got. I also still have the 2TB HDD that was its system drive that I can plop back in for testing purposes.
I've never had an SSD fail this way this quickly, and I suspect that's what's happened, though.