Comments on: [en] Solution to SIL3124-2 “no valid device” http://acogitosis.krop.pl/2009-05-29-en-solution-to-sil3124-2-no-valid-device/ polscy naukowcy udowodnili: myślenie boli Sat, 11 Feb 2012 09:12:24 +0000 http://wordpress.org/?v=2.3.2 By: Grzegorz http://acogitosis.krop.pl/2009-05-29-en-solution-to-sil3124-2-no-valid-device/#comment-5446 Grzegorz Tue, 08 Sep 2009 07:16:06 +0000 http://acogitosis.krop.pl/2009-05-29-en-solution-to-sil3124-2-no-valid-device/#comment-5446 <p>No worries, that's whole point in teaching Google such things ;)</p> No worries, that’s whole point in teaching Google such things ;)

]]> By: Shaun http://acogitosis.krop.pl/2009-05-29-en-solution-to-sil3124-2-no-valid-device/#comment-5442 Shaun Tue, 08 Sep 2009 00:11:53 +0000 http://acogitosis.krop.pl/2009-05-29-en-solution-to-sil3124-2-no-valid-device/#comment-5442 <p>Dude! YOU ARE THE MAN!! I was having exactly the same issue on a Windows Server 2003 system. The existing SATA card was dying (Sil3512) and we bought a new Sil3124 controller card to replace it. When we replaced the 3512 with the 3124, we got the same error ("no valid device").</p> <p>Following your advice, we flashed the BIOS on the new controller (sil3124) with a newer version and used the BASE bios update file (b6409.bin). We went from SATARaid BIOS 6.3.18 to SATALink BIOS 6.4.09. We also installed the BASE driver on the Windows boot partition and updated to the latest driver version. Once the drive was connected to the new controller and booted, the drive was immediately seen and bootable and Windows Server 2003 came right up. No other issues.</p> <p>Thanks very much for this jewel of information. This issue is nowhere in the tiny documentation sheet. No indication that the BIOS EITHER RAID or Non-RAID and not BOTH. Thank you, thank you, thank you!! Saved much time and aggravation!</p> Dude! YOU ARE THE MAN!! I was having exactly the same issue on a Windows Server 2003 system. The existing SATA card was dying (Sil3512) and we bought a new Sil3124 controller card to replace it. When we replaced the 3512 with the 3124, we got the same error (”no valid device”).

Following your advice, we flashed the BIOS on the new controller (sil3124) with a newer version and used the BASE bios update file (b6409.bin). We went from SATARaid BIOS 6.3.18 to SATALink BIOS 6.4.09. We also installed the BASE driver on the Windows boot partition and updated to the latest driver version. Once the drive was connected to the new controller and booted, the drive was immediately seen and bootable and Windows Server 2003 came right up. No other issues.

Thanks very much for this jewel of information. This issue is nowhere in the tiny documentation sheet. No indication that the BIOS EITHER RAID or Non-RAID and not BOTH. Thank you, thank you, thank you!! Saved much time and aggravation!

]]>