IBM X3650 M3 Windows 2003 Enterprise 설치 시
Server Guide 이용 설치 시 Windows 설치 파일 복사 후 재부팅이 되고
재부팅 후 Windows 설치 과정 중 아래와 같은 메세지가 발생 한다.
The file megasas2.sys is corrupted.
Press any key to continue. |
IBM에서는 설치 OS 가 SP2 이상만 지원이 된다고 한다.
megasas2.sys 라는 SAS 컨트롤러 파일을 인식을 못해 윈도우 설치가 되지 않는다.
따라서 SP2가 적용된 Windows 2003 서버 이미지를 이용해 설치한다. (R2버전 포함)
참조 사이트
http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=migr-5089866
|
|
|
|
ServeRAID megasas2.sys win2k3 driver floppy load failure - IBM BladeCenter and System x
Source
RETAIN tip: H205420
Symptom
IBM ServeRAID M Series and MR10 Serial Attached SCSI (SAS) Controller Driver for Microsoft Windows 2003 Server operating system may fail to load during installation of Microsoft Windows 2003 Server R2 (SP1) 32-bit and 64-bit.
During Microsoft Windows 2003 Server R2 (SP1) x64 setup, the user will see the following error right after the "LSI MegaRAID SAS RAID Controller Driver" has been loaded from the floppy diskette:
| |
The file megasas2.sys is corrupted.
Press any key to continue. |
During Microsoft Windows 2003 Server R2 (SP1) x32 setup, the user may see the following Blue screen stop error(s):
| |
*** STOP: 0xD1
*** msas2k3.sys - Address F76BAxxx base at xxxxxxx,
DateSTamp xxxxxxx |
Affected configurations
The system may be any of the following IBM servers:
- BladeCenter HS12, type 1916, any model
- BladeCenter HS12, type 8014, any model
- BladeCenter HS12, type 8028, any model
- BladeCenter HS22, type 1936, any model
- BladeCenter HS22, type 7870, any model
- BladeCenter HS22V, type 1949, any model
- BladeCenter HS22V, type 7871, any model
- BladeCenter HS23, type 7875, any model
- BladeCenter HS23E, type 8038, any model
- BladeCenter HS23E, type 8039, any model
- BladeCenter HX5, type 1909, any model
- BladeCenter HX5, type 7872, any model
- BladeCenter HX5, type 7873, any model
- System x3200 M2, type 4368, any model
- System x3200 M3, type 7327, any model
- System x3200 M3, type 7328, any model
- System x3250 M2, type 4190, any model
- System x3250 M2, type 4191, any model
- System x3250 M2, type 4194, any model
- System x3250 M3, type 4251, any model
- System x3250 M3, type 4252, any model
- System x3250 M3, type 4261, any model
- System x3350, type 4192, any model
- System x3350, type 4193, any model
- System x3400 M2, type 7836, any model
- System x3400 M2, type 7837, any model
- System x3400 M3, type 7378, any model
- System x3400 M3, type 7379, any model
- System x3400, type 7973, any model
- System x3400, type 7974, any model
- System x3400, type 7975, any model
- System x3400, type 7976, any model
- System x3455, type 7940, any model
- System x3455, type 7941, any model
- System x3500 M2, type 7839, any model
- System x3500 M3, type 7380, any model
- System x3500, type 7977, any model
- System x3550 M2, type 4198, any model
- System x3550 M2, type 7946, any model
- System x3550 M3, type 4254, any model
- System x3550 M3, type 7944, any model
- System x3550, type 1013, any model
- System x3550, type 1913, any model
- System x3550, type 7978, any model
- System x3610, type 7942, any model
- System x3620 M3, type 7376, any model
- System x3630 M3, type 7377, any model
- System x3650 M2, type 4199, any model
- System x3650 M2, type 7947, any model
- System x3650 M3, type 4255, any model
- System x3650 M3, type 7945, any model
- System x3655, type 7943, any model
- System x3655, type 7985, any model
- System x3690 X5, type 7147, any model
- System x3690 X5, type 7148, any model
- System x3690 X5, type 7149, any model
- System x3690 X5, type 7192, any model
- System x3800, type 8866, any model
- System x3850 M2, type 7141, any model
- System x3850 M2, type 7144, any model
- System x3850 M2, type 7233, any model
- System x3850 M2, type 7234, any model
- System x3850 X5, type 7143, any model
- System x3850 X5, type 7145, any model
- System x3850 X5, type 7146, any model
- System x3850 X5, type 7191, any model
- System x3850, type 8864, any model
- System x3950 M2, type 7141, any model
- System x3950 M2, type 7144, any model
- System x3950 M2, type 7233, any model
- System x3950 M2, type 7234, any model
- System x3950 X5, type 7143, any model
- System x3950 X5, type 7145, any model
- iDataPlex dx340 server, type 6389, any model
- iDataPlex dx340 server, type 7832, any model
- iDataPlex dx360 M2 server, type 7321, any model
- iDataPlex dx360 M2 server, type 7323, any model
- iDataPlex dx360 M3 server, type 6391, any model
The system is configured with one or more of the following IBM Options:
- ServeRAID M1015 SAS/SATA Controller, Option part number 46M0831, replacement part numbers (CRUs), any replacement part number (CRU), 46M0861
- ServeRAID M5014 SAS/SATA Controller, Option part number 46M0916, replacement part numbers (CRUs), any replacement part number (CRU), 46M0918
- ServeRAID M5015 SAS/SATA Controller, Option part number 46M0829, replacement part numbers (CRUs), any replacement part number (CRU), 46M0851
- ServeRAID M5025 SAS/SATA Controller, Option part number 46M0830, replacement part numbers (CRUs), any replacement part number (CRU), 46M0854
- ServeRAID-MR10M SAS/SATA Controller, Option part number 43W4339, replacement part numbers (CRUs), any replacement part number (CRU), 43W4341 - Adapter, 43W4342 - Battery, 43W4343 - Carrier
- ServeRAID-MR10i SAS/SATA Controller, Option part number 43W4296, replacement part numbers (CRUs), any replacement part number (CRU), 43W4297 - Adapter, 43W4304 - Daughter Card
- ServeRAID-MR10ie (CIOv) Controller for IBM BladeCenter, Option part number 46C7167, replacement part numbers (CRUs), any replacement part number (CRU), 46C7171
- ServeRAID-MR10is Vault SAS/SATA Controller, Option part number 44E8695, replacement part numbers (CRUs), any replacement part number (CRU), 44E8696 - Adapter
- ServeRAID-MR10k SAS/SATA Controller, Option part number 43W4280, replacement part numbers (CRUs), any replacement part number (CRU), 43W4282 - Adapter, 43W4283 - Battery
The megasas2.sys device driver for the ServeRAID M Series and MR10 SAS Controller Driver for Windows is affected.
The system is configured with at least one of the following:
- Microsoft Windows 2003 Server, Service Pack 1
- Microsoft Windows 2003 Server R2 for 32-bit Servers, Service Pack 1
- Microsoft Windows 2003 Server R2 for 64-bit Servers, Service Pack 1
Note: This does not imply that the network operating system will work under all combinations of hardware and software.
Please see the compatibility page for more information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
Workaround
Choose from one of the following two (2) workarounds:
Workaround 1
Use Microsoft Windows 2003 Server R2 (SP2) instead.
Workaround 2
Use device driver version 4.36 for the IBM ServeRAID M
Series and MR10 SAS Controllers.
This driver package can be downloaded at: http://www.ibm.com/support/fixcentral
To find the 4.36 driver, select the appropriate Product Group, System, Product name, Product machine type, and operating system (which version of Microsoft Windows 2003 or 2003 R2 you are running). Click continue.
On the next page, click include superseded fixes. Go to the SAS section, and find the entry called:
| |
IBM ServeRAID M Series and MR10 SAS Controller Driver for Windows ibm_dd_sraidmr_5.2.103_windows_32-64 |
Click Show superseded fixes. You will see an additional list of drivers, including 4.36 at the top of the list of older drivers. Select this and continue as usual to download that driver package.
Once the operating system is installed, the device driver can be upgraded to the latest version by following the steps listed in the Readme file.txt document provided with the driver.
Note: System reboot will be required in order to use the newly installed driver. Use the Windows Device Manager to be sure that the newly installed driver is actually used by the hardware.
Additional information
Device driver version 4.36 for the IBM ServeRAID M Series and MR10 SAS Controllers use the scsiport driver, which is a legacy way of performing I/O operations and has design limitations for new hardware.
Subsequently, the whole industry has moved on to use the storport driver instead, which has better performance and is designed for newer ecosystems.
This explains why driver version 4.36 does not fail the install operation and why version 5.2.xxx fails the install operation when using Microsoft Windows 2003 SP1 operating system. | | | | |
