Hi,
I am not quite sure exactly how to describe this one, but I have just completed a new build based around an Asus P8P67-M Pro motherboard, with an OCZ SSD for Windows, plus other essential files, and a Seagate 'traditional' drive for data etc. These are currently connected to the Blue SATA 3.0 connectors, but I have only just realised (while typing this!) that they should really be on the Grey (SATA 6.0) ones... shouldn't they?
Anyway, when the PC is turned on I see the usual ASUS logo screen, then a 'No drives found' message or something similar, and it then caries on to show the same logo screen again before completing the boot up sequence with both drives being recognised correctly.
I believe the message occurs because it is looking for drives connected to another controller (the Marvell one?) or possibly a RAID setup which I obviously don't have (and don't want) and I am sure I read somewhere that it is possible to stop it searching for these drives. Possibly by disabling the Marvell controller?
Just to confirm that I do realise that this not a 'fault' as such; there is nothing actually 'wrong' with my build, and that it is possible to stop the initial screens actually being displayed at all, but it will still go through the same process, which also of course extends the boot time.
I feel sure that there must be a way to overcome this 'feature'... possibly the one I mentioned above (?) and that someone on here will have the answer for me... I hope!
Sorry for the slightly long post, but I hope it all makes sense!
I am not quite sure exactly how to describe this one, but I have just completed a new build based around an Asus P8P67-M Pro motherboard, with an OCZ SSD for Windows, plus other essential files, and a Seagate 'traditional' drive for data etc. These are currently connected to the Blue SATA 3.0 connectors, but I have only just realised (while typing this!) that they should really be on the Grey (SATA 6.0) ones... shouldn't they?
Anyway, when the PC is turned on I see the usual ASUS logo screen, then a 'No drives found' message or something similar, and it then caries on to show the same logo screen again before completing the boot up sequence with both drives being recognised correctly.
I believe the message occurs because it is looking for drives connected to another controller (the Marvell one?) or possibly a RAID setup which I obviously don't have (and don't want) and I am sure I read somewhere that it is possible to stop it searching for these drives. Possibly by disabling the Marvell controller?
Just to confirm that I do realise that this not a 'fault' as such; there is nothing actually 'wrong' with my build, and that it is possible to stop the initial screens actually being displayed at all, but it will still go through the same process, which also of course extends the boot time.
I feel sure that there must be a way to overcome this 'feature'... possibly the one I mentioned above (?) and that someone on here will have the answer for me... I hope!
Sorry for the slightly long post, but I hope it all makes sense!
