F5F Stay Refreshed Software Operating Systems No dispositivo bootável foi detectado?

No dispositivo bootável foi detectado?

No dispositivo bootável foi detectado?

P
Paddy121999
Junior Member
6
11-07-2016, 08:08 AM
#1
Your hard drive is producing an unusual sound. After turning it off, unplugging it, and restarting, the system reported no bootable device despite NVMe being listed as the first one. The BIOS confirmed NVMe as the bootable option. You recently wiped the drive clean and backed up your data, then it started working again. What should you try next?
P
Paddy121999
11-07-2016, 08:08 AM #1

Your hard drive is producing an unusual sound. After turning it off, unplugging it, and restarting, the system reported no bootable device despite NVMe being listed as the first one. The BIOS confirmed NVMe as the bootable option. You recently wiped the drive clean and backed up your data, then it started working again. What should you try next?

D
DarkBoy__YT
Posting Freak
898
11-08-2016, 09:00 PM
#2
It seems your storage device is failing, possibly with lost boot sectors. You're taking the right steps. Disconnecting the NVMe drive will help. What additional actions are required?
D
DarkBoy__YT
11-08-2016, 09:00 PM #2

It seems your storage device is failing, possibly with lost boot sectors. You're taking the right steps. Disconnecting the NVMe drive will help. What additional actions are required?

N
NoNe_1
Member
188
11-09-2016, 04:42 AM
#3
That's correct. In the BIOS, the first boot option is my NVMe drive. It instructs the system to start from a bootable device once the HDD is disconnected.
N
NoNe_1
11-09-2016, 04:42 AM #3

That's correct. In the BIOS, the first boot option is my NVMe drive. It instructs the system to start from a bootable device once the HDD is disconnected.

D
Diba070
Member
75
11-09-2016, 01:34 PM
#4
Removing the HDD causes the BIOS to completely ignore the NME drive.
D
Diba070
11-09-2016, 01:34 PM #4

Removing the HDD causes the BIOS to completely ignore the NME drive.

V
ViiRaL_Hyper
Member
167
11-16-2016, 05:09 AM
#5
It acknowledges the observation.
V
ViiRaL_Hyper
11-16-2016, 05:09 AM #5

It acknowledges the observation.

X
xRAWRx
Junior Member
3
11-16-2016, 05:56 AM
#6
Un plug the HDD Go in your BIOS and make sure your CSM is disabled. If it fails, give us the rundown on your MOBO make and model, your CPU and your NVME drive.
X
xRAWRx
11-16-2016, 05:56 AM #6

Un plug the HDD Go in your BIOS and make sure your CSM is disabled. If it fails, give us the rundown on your MOBO make and model, your CPU and your NVME drive.

C
CAPNBOSS
Junior Member
17
11-16-2016, 01:32 PM
#7
When you reinstall the HDD, it restarts? You might have connected both drives during Windows setup by accident. The installer spreads the boot data across all storage devices. I've experienced this before—likely a part of the boot process is stored on that specific drive, which is why it won't start without it.
C
CAPNBOSS
11-16-2016, 01:32 PM #7

When you reinstall the HDD, it restarts? You might have connected both drives during Windows setup by accident. The installer spreads the boot data across all storage devices. I've experienced this before—likely a part of the boot process is stored on that specific drive, which is why it won't start without it.

I
ItzHF_
Member
74
11-23-2016, 04:01 PM
#8
However, the device has been erased completely without leaving any residual information.
I
ItzHF_
11-23-2016, 04:01 PM #8

However, the device has been erased completely without leaving any residual information.

S
sacapatates
Posting Freak
843
11-23-2016, 05:00 PM
#9
Yes, when setting up multiple drives during the Windows installation, the system might not place the bootloader on the selected drive. The bootloader is essential for starting your operating system. Windows10 typically installs it on the first drive it detects. To avoid this issue, ensure only one drive is connected during setup. Fix the problem by booting into the Windows installation media, then creating a fresh EFI partition and bootloader specifically on your NVMe drive. For more details, see the guide at the provided link.
S
sacapatates
11-23-2016, 05:00 PM #9

Yes, when setting up multiple drives during the Windows installation, the system might not place the bootloader on the selected drive. The bootloader is essential for starting your operating system. Windows10 typically installs it on the first drive it detects. To avoid this issue, ensure only one drive is connected during setup. Fix the problem by booting into the Windows installation media, then creating a fresh EFI partition and bootloader specifically on your NVMe drive. For more details, see the guide at the provided link.