I just installed the GAZ7711H.86A.0049 bios (was previously at level 39). on DZ77GA-70K MB which appears to have broken something with e-sata handling on boot. I have a WD 2tb MyBook drive connected to the rear e-Sata port. My boot drive is internal on Sata 0 and is set to 1st boot device.
Since the bios update the system will not boot and lock up if the WD e-sata drive is attached. If I unplug the drive the system boots normally. Previously had no problem leaving the drive connected. I have checked all the bios settings, tried resetting to defaults and various combinations with out success.
To be clear, if I connect the drive after boot, the drive is working fine.
Intel needs to be made aware of this problem.
I understand that after you updated the BIOS to version 0049 your WD* 2TB MyBook* drive caused your system to freeze during POST when the drive is connected.
I recommend you to contact the manufacturer to check if the have released a firmware update for your drive. On mi side I will report this issue to the department in charge of the BIOS updates to check if the problem can also be fixed from our side.
I have similar problem, attached e-sata drive and the system didn't boot.
Looked in the bios and the boot drive order was screwed up after attaching the e-sata drive. I didn't change anything in bios but on next boot pressed F10 and changed the boot drive to correct one. The system booted normally and I was able to use the e-sata drive.
But after I disconnected it (system was powered off) I got BSOD on next boot. Disabled the Marvell controller in the bios and working normally now.
I will not use e-sata anymore or activate the Marvell controller before the problem is fixed.
I have a similar issue with 0049. If anything is connected to either internal Marvell port while they are enabled in BIOS, the system fails to boot, with the message "Reboot and select proper boot device or insert boot media in selected boot device and press a key".
I've tried a disk drive, a DVD drive and an Iomega REV drive. All work in the remaining SATA port.
BIOS boot order also has a mind of its own.
This is definitely a BIOS issue, not the device manufacturers' problem.
While looking online for another SATA RAID card to replace my older Promise SATA 300 TX4, I found a review of a totally different adapter card where the reviewer mentioned his card would not work if the on-board RAID controller was enabled.
I removed the SATA 300, and presto, the Marvell ports are working as they should.
Surely, the BIOS should resolve this conflict before loading the OS?
Intel, Victor_Intel, we need a fix ASAP!! PLEASE!!
Message was edited by: Stephen Spratley
The marvell does support raid, but is not activated in bios like the intel.
When you connect two or more drives to the marvell, then at ctrl - m you will see more options are available when you enter the controllers config utility.
It works very differently from the intel contoller.
Jaan: My setup is 2xSamsung 128GB SSD as RAID 0, 3xSeagate 160GB as RAID 5, and a DVD drive on the Intel controller set as RAID. Marvell controller has an Iomega REV70 plus a Seagate 80GB drive.
If I add the Promise SATA 300 TX4 PCI card to the system then, with the Marvell controller enabled the system fails to load Windows.
My issue is an apparent clash between the add-on PCI card and the Marvell controller, which the BIOS should resolve before loading the OS, but doesn't.
Since the eSATA port is also on the Marvell controller, do you have any add-on cards that could be causing the same problem with your system?
It doesn't give the ctrl-m prompt and in documentation it says the raid is supported via the PCH. It doesn't mention raid support with Marvell. Does it still take ctrl-m?
That was my original plan to set up raid on Marvell but then I didn't have the ctrl-m prompt and checking the documentation it looks like raid not supported.