Blinking cursor error and error not being able to create an array in the raid menu when bo

[Itmust]

I can't boot anything on the server, cursor blinking, but when I plug in another windows hdd, it works, but I can't use it because it has an archive disk, it can't be usb boot, I can't do it on the raid disk, I want to open artay because it says un assigned, the room gives this error, no drive selected or reached max number of drivers allowrd, please help with the solution

[Azr_geek]

Hello @Itmust,

A blinking cursor usually means the server cannot see any bootable drive. Your RAID controller also shows the disks as unassigned, which means no RAID array exists, so the server has nothing to boot from. When you plug in a Windows hard drive from another system, it boots because that drive already has an OS, but you cannot use it for RAID because it is not part of your array.

To fix the problem, go into the RAID controller menu, delete any old or partial configurations, then select the disks you want and create a new RAID array. If it still says “no drive selected or max number reached,” it often means the disks are in the wrong mode (e.g., configured as JBOD, foreign, or locked). Clear any foreign configuration, set all disks to “unconfigured good”, then try building the RAID again. After the array is created and initialized, the server will allow you to boot from USB or install an OS normally. If the error continues, one or more drives may be faulty or not supported by the RAID controller.

Regards,
Azr_geek

[Itmust]

My friend, I forgot to press space, that's why the driver wasn't showing up. I fixed that, but even though I opened the array, it still isn't working. I partitioned the hard drive as a bootable section and installed it that way with AHCI.

[Azr_geek]

It sounds like the server still can’t boot, even though you recreated the array and installed the system using AHCI. This usually happens when something in the boot setup doesn’t match how the operating system was installed. Make sure the server is using the same boot mode you used during installation (UEFI or Legacy), and check that the correct drive is first in the boot order. Also, confirm that the controller mode hasn’t changed; if the OS was installed in AHCI but the server later switched to RAID mode, it won’t boot. Sometimes the problem is with the partitions as well: UEFI needs an EFI boot partition, and Legacy needs an active MBR partition. If the drive is in a hot-swap bay, the server may need a specific controller mode to boot correctly. Firmware that is out of date on the BIOS, storage controller, or iLO can also cause the drive to disappear during boot. If you share the server model and OS, I can guide you step-by-step in a simpler way.

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".