Question Problem windows 10 booting with LSI card and SAS drives

Toggle sidebar Toggle sidebar
N

Nidhal13

Feb 5, 2025
14
0
10
Hello,

This is my second post here and I am thank you all to your help your are providing to people ! I have an Avago SAS3 3008 Fury LSI card which is in IT mode. I have SAS drive alongside with it. My motherboard is a MSI MAG B560 TORPEDO with 16gb ram, an INTEL CPU and all running under Windows 10.

I have a small problems regarding the recognition of my SAS drives. When I open my computer with only the LSI card connected to the motherboard, everything is running smoothly. I see the LSI card bios, and then it boots on windows 10. The problem is that when I connect my SAS drive to the card, the LSI bios shows up again and it lists the SAS drive, then it boots on windows 10 BUT the booting process runs undefinitely with the black screen and the blue windows logo with the small wheel.

I tried to connect the SAS drive after Windows 10 is in the Desktop, it appears but only the symbol and the corresponding letter appears in the folder management tab. When clicking on it, it freezes the whole computer.

Thus, I would like to know which solutions could be applied to access easily these SAS drives and what are the changes I should apply to make it work !

Thank you to all in advance !

Nidhal.
 
Nidhal13 said:
Hello,

This is my second post here and I am thank you all to your help your are providing to people ! I have an Avago SAS3 3008 Fury LSI card which is in IT mode. I have SAS drive alongside with it. My motherboard is a MSI MAG B560 TORPEDO with 16gb ram, an INTEL CPU and all running under Windows 10.

I have a small problems regarding the recognition of my SAS drives. When I open my computer with only the LSI card connected to the motherboard, everything is running smoothly. I see the LSI card bios, and then it boots on windows 10. The problem is that when I connect my SAS drive to the card, the LSI bios shows up again and it lists the SAS drive, then it boots on windows 10 BUT the booting process runs undefinitely with the black screen and the blue windows logo with the small wheel.

I tried to connect the SAS drive after Windows 10 is in the Desktop, it appears but only the symbol and the corresponding letter appears in the folder management tab. When clicking on it, it freezes the whole computer.

Thus, I would like to know which solutions could be applied to access easily these SAS drives and what are the changes I should apply to make it work !

Thank you to all in advance !

Nidhal.
Click to expand...
Have you verified the boot order in the BIOS?
 
evermorex76 said:
How are you powering the drives externally? Are you certain these drives are actually good?
Click to expand...
Yes, I am sure they are rotating and working, I hear it. I power them via Sata connectors that I cut. Since it appears on the disk manager as Raw but when I try to format it, the computer starts to freeze.
 
So it looks like you chose the HGST SAS drives? What is the exact model number/part number on them all? It happens even when you have only one drive connected?
 
Your previous image seemed to indicate that the ST4000 was the first boot device, and the Boot Priority second in the second image matches that. I think the BBS Properties might only apply when you manually interrupt the boot process, showing you which devices you can choose from. It's just because BIOS/UEFI tends to enumerate SATA drives before NVMe. (Windows Disk Management would show the ST4000 as Disk 1, and the MX500 as Disk 0, probably.) It is odd that the MX500 isn't listed separately in the Boot Priority, though. Does either of them actually have a bootable OS on it?

Anyway, just because the drive spins up doesn't mean it's "good". And I think you replied to me mistakenly since I didn't ask about boot order. :)
 
evermorex76 said:
Your previous image seemed to indicate that the ST4000 was the first boot device, and the Boot Priority second in the second image matches that. I think the BBS Properties might only apply when you manually interrupt the boot process, showing you which devices you can choose from. It's just because BIOS/UEFI tends to enumerate SATA drives before NVMe. (Windows Disk Management would show the ST4000 as Disk 1, and the MX500 as Disk 0, probably.) It is odd that the MX500 isn't listed separately in the Boot Priority, though. Does either of them actually have a bootable OS on it?

Anyway, just because the drive spins up doesn't mean it's "good". And I think you replied to me mistakenly since I didn't ask about boot order. :)
Click to expand...
I ordered as sort of "external SAS dock" and the SAS drives were recognised and worked good in my computer. The thing is that after few minutes, the disk disconnected himself for some strange reasons. So I sent back this external solution to Amazon. The MX500 has a bootable OS on it of Windows 10.
I just checked again my Boot priority and the first one is the nvme disk.
 
Okay, weird that boot order is changing by itself, but even if ST4000 was first it wouldn't matter without an OS on it. But if the SAS dock "disconnected himself for some strange reasons" and now the individual drives are causing Windows to freeze, why are you not considering the possibility that the drives are in fact bad? How are you certain that the dock was the problem?
 
evermorex76 said:
Okay, weird that boot order is changing by itself, but even if ST4000 was first it wouldn't matter without an OS on it. But if the SAS dock "disconnected himself for some strange reasons" and now the individual drives are causing Windows to freeze, why are you not considering the possibility that the drives are in fact bad? How are you certain that the dock was the problem?
Click to expand...
Because multiple reviews on this product indicated that people had the same issue as mine.
 
Ah, useful information. I got nothing then, other than a power issue with the cables you've cobbled together, but since it reaches the point of being seen in Windows when you plug it in that's low probability. But I've only seen this sort of behavior with either bad drives or bad enclosures.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom