11-27-2010 06:17 PM - edited 11-29-2010 06:23 AM
I've got a D20 Mod. 4155 and want to use beside it's default SATA hard disk four SATA SSD disks for virtual machines. Windows Server 2008 R2 will be the OS with the use of it's Hyper-V functionality.
I have aproblem with detecting the disks in OS setup. All 5 disks are visible in the BIOS setup of the Marvell Controller. it is possible to configure a RAID over the SSD etc., but I don't "see" any disk in OS setup. I tried to load additional drivers in the GUI part of the setup utility, but this didn't worked. I tried with the Marcell SAS driver and the Intel Matrix driver, both found at http://www-307.ibm.com/pc/support/site.wss/migr-72280.html.
Any suggestions for PC BIOS / Marvell BIOS / OS setup configurations?
Kind Regards, Chrischmi
Solved! Go to Solution.
11-28-2010 05:48 PM
Disconnected all disks but SAS disk. Tried to load i386 x64 SAS driver - no driver found (CDSAS09WS17), no disk found. Tried (just for test purpose) the amd64 directory: driver found, disk found. But setup fails because of wrong processor architecture later (never reproduced this...). Therefore I assume a problem in the driver package?!
External eSATA drive (connected to intel controller) and USB flash disks get detected, but not the default SAS drive. ;-(
Tried to run a clean setup of Windows 7 x64, same problems...
Any help will be much appreciated...
11-28-2010 09:41 PM
welcome to the forum!
do you have the RAID array or SAS drive shown in the boot device list in the BIOS? if not, they need to be added to the list.
11-29-2010 03:05 AM - edited 11-29-2010 06:25 AM
yes, the default drive is part of the boot device list in computer BIOS and as well is shown in the boot process, while the Marvell controller is detecting drives.
Unfiortunately I trusted a wrong product description. The default hard drive is a SATA drive and not SAS. I changed the title of this thread to match that.
11-29-2010 06:02 PM
I found the solution on myself. After detecting, that the default disk is a SATA disk (and not SAS), I had the idea to test it on the Intel SATA controller. It was possible to install the machine wit the disk attached to the Intel controller. After setup I went to Device Manager and installed the Marvell driver from Lenovo, switched the disk back to the Marvell controller and booted. Successful. Yeah!
On my way to the solution i had another problem: In the GUI part of Windows setup, I got a 0x80300001 error with the Intel SATA driver from Lenovo. It was not possible to install windows Server on the SATA disk with reason0x80300001. very helpful message, Microsoft! ,-) I decided to use the default Microsoft driver for the Intel SATA controller after a reboot. Setup run well, but ended with a 0x80070017 error and problems copying some (unknown) files. The solution (found after some hours...) was to burn a new Windows Server setup DVD. I don't want to talk about this anymore...