Motherboard/BIOS could previously detect hard drive, but returns "Reboot and select..." error message after adjustments

vgk · Dec 26, 2017

Hard drive: Toshiba - P300 2TB 3.5" 7200RPM Internal Hard Drive
Motherboard: MSI - B350M PRO-VD PLUS Micro ATX AM4 Motherboard
PSU: Corsair - TXM Gold 550W 80+ Gold Certified Semi-Modular ATX Power Supply

Earlier today, I was putting the finishing touches on my new computer. I tried booting it up and it was a success. I then proceeded to screw the sides of the case back on, only to encounter a problem: I'd inserted the hard drive in the wrong way and one panel clearly wouldn't fit on without damaging something. (I didn't actually push it that far; just enough to realize this would happen if I continued pushing.) So I flipped the hard drive around and fixed that problem only to run into another: the "Reboot and Select proper Boot device" error message. When I go into the BIOS, it knows which port I plugged the hard drive into, but for whatever reason, the computer as a whole still doesn't detect it. This makes me think it's a power issue, so I played around with the ports on the PSU, ports on the motherboard, any different cables at my disposal - all to no avail. The hard drive could be making a sound, but even after putting my ear next to the hard drive, it's hard to tell what parts are making what noises.

Update:
I've done further testing on the problem. The hard drive will spin up normally, and after it reaches a certain point it makes a sound like a blade of grass getting stuck in a small fan/belt. (I should emphasize that this noise isn't particularly loud. The drive is relatively quiet throughout.) Following that, I think it makes a few reading noises before settling into silence. I can hear the drive wind down when I turn the system off, so it might be operating normally? I've Googled around on the subject, but all the troubleshooting advice assumes obvious and/or loud noises that my hard drive doesn't neatly map to.

Also can somebody move this to components or storage or another board more appropriate than the one I picked by mistake?

GhislainG · Dec 27, 2017

It doesn't take much to damage a drive; slightly too much stress on a connector can crack the board.

vgk · Dec 27, 2017

GhislainG :

Are there tell-tale signs I should look out for? The board itself looks perfectly fine and again, the sounds it makes don't obviously signal "something has gone wrong"; at least not based on what I've read.

GhislainG · Dec 27, 2017

If you see nothing obvious and it doesn't work, then RMA it.

vgk · Dec 27, 2017

GhislainG :

I haven't been able to check until now, but after checking (what I think is) the serial number, I'm still not sure if the hard drive's in warranty. I'll call later to see if RMA'ing is an option or if I'll have to buy a new hard drive.

vgk · Dec 31, 2017

I'm updating this thread because of the strong chance that my latest problem is a continuation of this one.

I couldn't get an RMA (and it might not matter if I could; I'll explain shortly), so I ordered a new hard drive instead. Everything went in smoothly as possible, but when I started my build again, it took much longer to boot into the UEFI than usual. Rather than go straight into the UEFI or to the previous error screen or anything, it spends some time on the boot-up screen, then some more time on a completely black screen, save a text cursor oddly hanging in the middle of the screen (some resolution mismatch?). All the while, the hard drive is making this noise that's hard to describe without musical notation: a "bup bup bup-bup (rest) bup-bup (whir)" sound. Eventually it makes its way to the UEFI, and the whir sound disappears as it settles into some kind of normal. It's also worth mentioning that where my motherboard could detect my old hard drive just fine, it doesn't recognize this new one at all; I get to choose between booting straight from the UEFI and that's it. Browsing around Storage Configuration confirms it. Everything's connected firmly where it should be, and I've tried switching to a different SATA port in case that was causing it. As far as I can tell, it wasn't.

I changed out the SATA cable and now the noise is closer to "bup (rest) bup (rest) (whir)", for what it's worth.

GhislainG · Dec 31, 2017

It's weird, but it would then be a motherboard issue. Same issue with a SSD?

vgk · Dec 31, 2017

GhislainG :

I don't (think I) own any SSDs, and given how much money I've dropped into this computer for problems like these, I'm really reluctant to spend more money when other options are available.

GhislainG · Dec 31, 2017

Did you test the hard disks on another system?

vgk · Dec 31, 2017

GhislainG :

The only other system I have is an aging laptop.

GhislainG · Dec 31, 2017

What's your plan of action? RMA the moterboard? Is the BIOS the latest version?

vgk · Dec 31, 2017

GhislainG :

RMA'ing isn't really an option for me, and the BIOS version is AB350M Pro4 P3.00, but every piece of writing I can find (including the motherboard's official site) is heavily cautioning me against updating my BIOS.

GhislainG · Dec 31, 2017

You can't RMA and you don't want to upgrade the BIOS to see if it would help. What will you do to resolve the issue?

vgk · Dec 31, 2017

GhislainG :

It's not that I don't want to upgrade the BIOS; it's just that I'm reluctant about doing so because several sources (including the one I link) caution that I could irreversibly damage my motherboard if I do it incorrectly. Regardless, I'm going to try updating it anyway, albeit incredibly carefully.

GhislainG · Dec 31, 2017

That warning is normal, but if you contact support, the firat suggestion probably will be to upgrade the BIOS.

vgk · Jan 1, 2018

I tried updating the BIOS, and I'm having all the exact same problems. I'm guessing this means I have to buy a new motherboard.

GhislainG · Jan 1, 2018

It may sound like a stupid question, but why can't you RMA a brand new motherboard? Was it stolen or illegally acquired?

vgk · Mar 10, 2018

I'm returning with an update on the fixes I've tried since I last posted.

Short version: not only has my original problem remained unfixed, but things got inexplicably worse with each new solution.

Long version: My first response was to order a new motherboard. I installed it, and this time, it wouldn't even POST. It cycled a little bit, but always powering itself off and then back on without getting to the BIOS screen. It wouldn't even send a signal to the monitor. On top of that, my hard drives were making the same sounds as ever, leading me to believe the power supply was the problem. I ordered a new one, installed it...and now my system won't power on period. The graphics card is getting power, the case is getting power (the light for the power button (which I don't remember existing before) is on), but when I press the power button, nothing happens. Short of removing the motherboard from the case and the CPU from the motherboard, I've taken out and reconnected everything I possibly can, and to no avail.

GhislainG · Mar 11, 2018

It may be time to bring it to a competent shop that will identify the source of the issue.

vgk · Apr 25, 2018

I had a repairman look at my computer, and without getting into the details, my only option at this point is to buy a new computer. I'm returning here with one (hopefully) final question: does anybody have recommendations for prebuilt gaming computers? I've already found this article on Tom's Guide, but given everything that's gone wrong so far, I am taking absolutely no chances. My only real requirements are that it cost less than $1000 and be able to play Nier: Automata at decent settings.

Motherboard/BIOS could previously detect hard drive, but returns "Reboot and select..." error message after adjustments

Prominent

Titan

Prominent

Titan

Prominent

Prominent

Titan

Prominent

Titan

Prominent

Titan

Prominent

Titan

Prominent

Titan

Prominent

Titan

Prominent

Titan

Prominent

Share this page