Trim Support in RAID 0 on a P55-GD65

I have some confusion regarding TRIM support in RAID 0. I have 2x80 GB Intel X-25M G2 SSDs in RAID 0 on a P55-GD65 mobo. I am not using a RAID card, and my OS is Windows 7 Ultimate x64. I just flashed the latest firmware update for the drives. According to the Intel SSD Toolbox, TRIM is not enabled. I have the latest Intel Chipset Drivers from Intel's site rather then the MSI downloads center. After doing some reading it sounds like if I back up my data, set the drives to ACHI rather then RAID, rebuild the array, and restore my back up, the drive will support TRIM. Is that correct?

If I am not mistaken, "TRIM" is generally a no-go in RAID-Mode conigurations.
Quote
After doing some reading it sounds like if I back up my data, set the drives to ACHI rather then RAID, rebuild the array, and restore my back up, the drive will support TRIM. Is that correct?
Try & see.

Similar Messages

Question about AHCI and TRIM support in NF980a-GD65

Is it available through the chipset? I have a 780i motherboard and it's not supported on there. I'm deciding between NF980a-GD65 and 890FXA-GD65 for my Phenom II X6. The only reason I ask is that I'm planning to use a SSD. I would like to have the full ACHI and TRIM support.

TRIM is a feature of the operating system and the drive itself, not the chipset.
See:
http://en.wikipedia.org/wiki/TRIM
http://www.bit-tech.net/hardware/storage/2010/02/04/windows-7-ssd-performance-and-trim/1

MOVED: P55-GD65 2x raid setup advice (R/W activities pauses time to time)

This topic has been moved to Intel Core-iX boards.
https://forum-en.msi.com/index.php?topic=159695.0

Topic title:
"Re: P55-GD65 2x raid setup advice (R/W activities pauses time to time)"
What you say you have:
"MSI P67A-GD65 B3 iP67, SATA600 RAID, USB3.0
Which one is it you actually have?
Edit: Edited topic title

Does MSI P55-GD65 support eSata hot-plug?

I believe the title is self-explanatory, but I'll explain anyway..
I have a MSI P55-GD65 motherboard which has an onboard eSata port. I have a second eSata port in the front plate of my case.. The thing is, that the only way for it to recognize my eSata external hard drive, is if the drive is connected and powered BEFORE I boot my PC. Not very convenient when it comes to portable devices. Is there anything I have to change in the BIOS or any drivers I should install (for Windows 7 Ultimate 64-bit) so that I can power on and off my drive while my PC is working?

Actually, I did some more digging after my post, I figured out how to do it (I tweaked the registry because I had installed Windows 7 with sata mode set to IDE), and now it works fine..
There's only one issue. My external drive does not appear in the devices I can "safely remove". So I don't know how risky it is to just turn of my HDD while the PC is powered on..

P55-GD65 Voltage Discrepancy

Why is the voltage variance of this board so high? With low Vdroop enabled on a voltage of lets say 1.36 in the bios I get a 1.40v reading in CPU Z @ idle. This turns into 1.42 or more under load. Am I missing a setting that will keep it closer to what I set it at? This variance is rather ridiculous if you ask me. I have all the standard power saving features turned off before anyone asks.
Thanks!
My System:
Mobo: MSI P55-GD65
CPU: Intel i5 750
GPU: Ati 4870x2 2 GB
Mem: 2X 2 GB G.Skills Ripjaws DDR3 1600
SSD: OCZ Agility 60 GB
HD: 2x WD Black 500gb ea Raid 0
PSU: PC P&C Silencer 750

Songokussm the same issues I reported to support, they responded to me, that my MB is faulty and I should RMA ( did it twice, 4 month without MB ) I prove them otherwise, I had 3MB P55-GD65 with the same issues. Short speaking every MB with ERP=040 is faulty on engineering level Overvoltage like you described, problems with fans on sysfan1 and sysfan2, restore AC on power loss not working correctly and sometimes USB2 stops responding.
My conversation with MSI support ended when they statement that they can`t check if I`m correct because they don`t have MB with ERP=040, so the problem is .... gone I bet that with bios 1.9 in your case issue still occur but is`t less "visible".

P55-GD65 - SATA port and driver installs for SSD ?

Please can anyone help...
I have a MSI P55-GD65 mb (AMI BIOS v1.2/012.020.000.015) and am about to do a clean install of Win 7 64 bit onto an unused Crucial M4 SSD (firmware rev 010G). After disconnecting my existing HDD from SATA1.....
Q1 Should I update the mb BIOS? I currently have no probs....if it aint broke....
Q2 Which SATA port should I connect the SSD to?
   SATA 1-6 ports are Intel P55, SATA7 is supported by JMicron JMB363
Assuming the next steps are:
   plug CD/DVD drive into SATA 4
   boot into the BIOS, enable AHCI and set the SSD as the primary boot drive after the CD/DVD drive
   boot from the Windows 7 disc and install the OS,
Q3What do I do about installing drivers?
Allow any default drivers to install from Win7, then install drivers from the mb disc (starting with chipset drivers), then update them with the latest from MSI. Or what?
I understand that rebooting after installing each driver (and the updates) is a good idea (NickN from SimForums), but this suggests a lot of reboots !
If some reboots can be left till several drivers are in, at which points should reboots be done if there are 5 or 6 drivers+updates to install? I wouldn't be bothering with any RAID configuration or the floppy drivers.
Finally..
Q4 At what point do I perform the firmware update of the Crucial SSD (to rev 040H) ? I'm assuming a driver install will be required for this.
Thanks

Quote
Q1 Should I update the mb BIOS? I currently have no probs....if it aint broke....
If all is well don't do anything.
Quote
Q2 Which SATA port should I connect the SSD to?
SATA 1-6 ports are Intel P55, SATA7 is supported by JMicron JMB363
All of the ports are SATA II, so any port 1-6 would be fine. I suggest port 1 or the purchase of a sata III card. IE:
http://www.amazon.com/SIIG-SATA-6Gb-2-Port-PCIe/dp/B006Q4MGOM/ref=sr_1_3?s=electronics&ie=UTF8&qid=1368545006&sr=1-3&keywords=sata+iii+card
Although I won't make a huge amount of difference.
Quote
Q3What do I do about installing drivers?
Allow any default drivers to install from Win7, then install drivers from the mb disc (starting with chipset drivers), then update them with the latest from MSI. Or what?
I leave the internet disconnected until I have loaded all of the drivers. I also generally do an F6 installation with the most recent AHCI / Raid drivers available if applicable.
Once all of the drivers are install, I connect the internet and let it update.
Quote
Q4 At what point do I perform the firmware update of the Crucial SSD (to rev 040H) ? I'm assuming a driver install will be required for this.
If there is a firmware update available, the best thing to do would be to install the ssd in another computer, update the firmware, then place it in your computer. (or keep the existing hdd in for a moment to do this)
Data loss is very possible during an ssd firmware update.

My SSD install in Lion shows no TRIM support. How do I fix?

Hi folks. I had my new 2011 mini upgraded with an OCZ Vertex 2 SSD drive. I checked for TRIM support after a clean install of Lion and it says No. How do I fix this? Thanks.

I think some want to believe TRIM is needed; or, it was with older model SSDs.
The TRIM Enabler has a change log, and history of sorts.
SATA-IO has said that 3.1 specification will incorporate TRIM into NCQ (command queueing) going forward now that it is final and adopted which is a much better solution.
The lack of free space or having to reuse storage cells (a month's worth is a good number) and the background garbage collection will take care of your drive.
I would not. OWC does not recommend its use, and they just use Sand Force controller and firmware also.
Also, a lot of PC users set motherboard RAID, TRIM is not supported in RAID configurations, and that seems to be fine.
My Corsair SSDs (5) are 6 months and going strong.

Lion RAID0 SSD TRIM support

Hi all,
From what I've read so far it would appear that if I go to a RAID 0 SSD setup in my Macbook Pro... I'll lose TRIM support, even if both disks support TRIM by themselves?
I've got an Apple Supplied 128GB SSD and a Samsung 470 series 128GB SSD... I was thinking of reinstalling Lion (yes I have the bootable DVD) and configuring them in RAID 0, mainly to get one large 250-256GB volume...
Also, a lot of people are saying that 64Kb stripe size is the way to go....
Finally, someone mentioned about putting the disk utility into developer mode to elinimate the recovery partition off the Apple SSD?
Thanks for all feedback.

Cindy,
Thanks for the quick reply. If I'm understanding correctly, the SCSI unmap command was implemented in last November's Solaris 11.1 release but has since been disabled due to performance problems. I'm running the original November release with no updates so can I assume that SCSI unmap is enabled on my system? If so, do I run any risk of data corruption by staying with my current version? I'm currently running Solaris 11.1 from a SATA SSD.

P55-GD65 BIOS bug

Hi! I`m having compatibility problems with my imon remote/reciever! It is supposed to turn the computer ON but the BIOS won`t let it! There`s no option in the BIOS for turning on the computer by USB device! It works by shorting the power button pins, but if the USB cable is connected it doesn`t work.

Songokussm the same issues I reported to support, they responded to me, that my MB is faulty and I should RMA ( did it twice, 4 month without MB ) I prove them otherwise, I had 3MB P55-GD65 with the same issues. Short speaking every MB with ERP=040 is faulty on engineering level Overvoltage like you described, problems with fans on sysfan1 and sysfan2, restore AC on power loss not working correctly and sometimes USB2 stops responding.
My conversation with MSI support ended when they statement that they can`t check if I`m correct because they don`t have MB with ERP=040, so the problem is .... gone I bet that with bios 1.9 in your case issue still occur but is`t less "visible".

P55-GD65 Wont start Phase 4 LED wont come on

I just got a P55-GD65 and i got every thing on i have to say my PSU isint very good but i want to make sure that its a PSU problem before i go out bouying a 120$ PSU. The components are 2x2GB 2000MHZ OCZ memorys, an HD 4850 as video card and a i5 as the CPU, when i turn on it starts all the Phase LED's go on except for the Phase 4 LED, at first i tought it was a memory problem, i solved it puting both memorys in the black slot and it stoped beeping 3 times. but now it just turns on, all the leds go on except for the 4 phase led and after 4 seconds it goes off agian and goes back on and keeps doing the same thing over and over agian( going on and off on and off).... can someone help me ???!? its not the video card i tested it in a friends pc, might be memory havent tested it cuz i dont have another DDR3 supporting mobo.. PLZ HELP! im going crazy!! plz someone tell me its PSU!!!!
PS i tryd it with a 450 wats Seventeam PSU

Quote from: emer50n link=topic=132988.msg1000594#msg1000594 date=12595034a
i did this procedure (clearing cmos and puting only 1 memo on 1 DIMM slot) now what happens is that every thing goes on i get no noises but nothing happens i get just a black screen and the video wont boot up(the pc wont turn off nowbut wont boot)... eny more ideas ?
You have inserted ur RAM on the very first slot (The blue one) right?? ...... Insert that in the first black slot on left side, thats the 1DIMM slot..... If you wanna use ur 2nd ram as well, then insert that in the 2nd black slot.... I don't think its ur PSU.

P55-GD65 BSODs

The last two weeks I've experiencing fairly frequent (1 or 2 a day) BSODs. They are 4 or 5 different ones that happen.
I'm running the following equipment:
MSI P55-GD65
Win 7 64 bit
i7-860
Two sets of G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL7D-4GBRM
SAPPHIRE Vapor-X 100281VX-2SR Radeon HD 5870 1GB 256-bit GDDR5
APC BR1500LCD 1500VA 865 Watts 8 Outlets BACK-UPS RS
SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" (raid 5)
CORSAIR HX Series CMPSU-850HX 850W
LG Black 8X BD-ROM 16X DVD-ROM 40X CD-ROM SATA
Thermaltake Armor water cooled box.
This system has been running this configuration for about 3 months. Temps are around 19 at idle and high 40s under 100% load. When the BSODs started I first ran memtest86 and found no problems. I have a second rig and swapped out the following
Replaced CPU with second i7-860.
Replaced memory with two sets of CORSAIR XMS3 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666)
Replaced Video card with SAPPHIRE 100215L Radeon HD 3870 512MB 256-bit GDDR4
Made sure that all the drivers were up to date and tried various versions of bios.
I'm still getting BSODs. Only thing the same are Motherboard, disks, OS and PSU. Since most BSODs are related to drivers or Memory problems I believe that it may be the mother board which is bad. Time to RMA the board?
Dan

Here are all the errors. The system was totally clean before 22 May.
22 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80003305410). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-25334-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d6bd0, 0xfffffa80069d6c30, 0x0000000004060017). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052210-24460-01.
27 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa80069d59e0, 0xfffffa80069d5ab0, 0x00000000040d0007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-29078-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x000000000000077a, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-30841-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x0000000000000020, 0x0000000000000009, 0x0000000000000000, 0xfffff88004e0b7d7). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052710-26582-01.
28 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000d9f10, 0xf5500001bdf32886, 0xfffff8a0108b57b9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052810-26379-01.
29 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000010000006f, 0x0000000000000002, 0x0000000000000000, 0xfffff88001a368f9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-32479-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800374d5c8, 0xfffff8800374ce30, 0xfffff8000322f9e9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 052910-36270-01.
30 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000000bf20e, 0x0000000000000003, 0x0000000000209de5). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053010-26083-01.
31 May
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff8800b67a8d8, 0xfffff8800b67a140, 0xfffff880016c172f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-28158-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000019 (0x0000000000000020, 0xfffffa800ca6c270, 0xfffffa800ca6c740, 0x00000000044d0005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-27924-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000403, 0xfffff68000103670, 0xa12000022385c867, 0xfffff6800002b840). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 053110-29920-01.
1 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041201, 0xfffff680000243d8, 0x97b0000066e89867, 0xfffffa800c772810). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060110-29811-01.
2 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x000000000020ad1d, 0x0000000000000003, 0x0000000000016a25). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-22682-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000031, 0xfffffa800d81fa50, 0xfffff8800820c000, 0xfffff8a00e4be67d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-23899-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff800035b8f1a, 0xfffff8800c0dde00, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-33805-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000001f6fe9, 0x0000000000000003, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-24835-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000352f90d, 0xfffff8800ad85080, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-30279-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000096, 0xfffff800032da873, 0xfffff8800be47600, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060210-31574-01.
3 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffffbbc0209541b, 0x0000000000000000, 0xfffff800032d543b, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-23337-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff680000203d8, 0xb310000169bc8886, 0xfffff6800004fca1). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-22838-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000124b4a, 0x0000000000000002, 0x0000000000123bb4). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-25272-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x0000000000172aeb, 0x0000000000000002, 0x00000000001721ea). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060310-31995-01.
4 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xfffff88004bfb000, 0x0000000000000000, 0xfffff88004eb56a0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060410-33665-01.
5 June
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff88001274efa, 0xfffff88003b398b8, 0xfffff88003b39120). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25989-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffffc0000005, 0xfffff80003309371, 0xfffff8800375b0e8, 0xfffff8800375a950). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-25677-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000034 (0x0000000000000c72, 0xffffffffc0000420, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-27315-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c6d3b30, 0xfffffa800c6d3e10, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-26176-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000000411, 0xfffff6800001a270, 0xa2f0000223f1c886, 0xfffff8a00aec7c29). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-29343-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000004e (0x0000000000000099, 0x00000000005422f1, 0x0000000000000003, 0xccccccccccc35f20). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-33228-01.
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800c0f9940, 0xfffffa800c0f9c20, 0xfffff8000358c540). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 060510-34055-01.

P55-GD65 won't boot with OC Genie activated

I have an P55-GD65 mobo that runs just fine with no problems except when I tried to activate the OC Genie. When I pressed the button and then tried to boot the machine -- it would begin the boot process then reboot over and over again without actually completing the boot process. When I pressed the OC Genie button again to deactivate it -- the machine booted just fine.
I've got Windows 7 Professional 64 bit installed.
What is my problem and how do I fix it so the OC Genie works?
Thanks,
Crockett

What is your current BIOS Version?
Quote
I have an P55-GD65 mobo that runs just fine with no problems except when I tried to activate the OC Genie. When I pressed the button and then tried to boot the machine -- it would begin the boot process then reboot over and over again without actually completing the boot process. When I pressed the OC Genie button again to deactivate it -- the machine booted just fine.
What memory frequency, timings and Comman Rate does the BIOS set when everything is set to default (check with CPU-Z)?
The BIOS has a tendency to automatically set the Command Rate to 1T instead of 2T which causes stability problems in many cases.
Quote
If the RAM is running at 1600MHz the OC Genie won't work properly.
There is a flip site to this kind of observation: The CPU does not natively support DDR3-1600 and most modules sold as DDR3-1600 are actually just factory overclocked DDR3-1333 modules that require higher than standard voltages settings to have a chance to run stable. This in itself already is an inherently tricky situation that does not get better when you enable the OC Genie.

P55-GD65 Won't soft boot.

Updated my P55-GD65 to bios 1.6 and ever since my computer won't soft reboot via Windows. If I try to reboot in any normal matter from Windows the computer fully restarts up to just before an actual post and sits there until I either turn it off and back on or use the hard reset button. If I change settings in the bios and it soft reboots the machine it still posts, only happens from Windows.
System Specs:
Windows 7 Ultimate x64
1x Seagate Sata II 500GB (Boot Drive)
2x Seagate Sata II 1TB (Raid 0)
4x Patriot 1600EL 2GB RAM sticks (Using EMP timings)
2x Sapphire Radeon 4870 (Crossfire)
I have disabled OC Genie and hard set the CPU multiplier to 21x.

Newer hardware having compatibility issues with Win 7 doesn't really points to BIOS update, more to driver issues most of the time. Anyway, in the future, only update the BIOS if you have BIOS related issues like unable to boot from USB, controllers not working for examples. Now, you have to try to roll back to the last working version and see if you can get the system to normal.

MSI P55-GD65 onboard eSata doesn't show Hard Drive..

Here's the deal..
I've got an MSI P55-GD65 board. This board has an onboard eSata port. The thing is, that when I plug my external drive in the onboard eSata board, windows don't recognize the drive. I've even tried powering it on before I turn on the PC, when it boots I get the following message,
http://imageshack.us/photo/my-images/231/p7230163.jpg/
, showing that the hard drive IS recognized by the controller, but I windows 7 64-bit cannot see it..
Now, I've gone through the manual a bit, it seems that this board has 2 sata controllers, Intel P55 and JMicron JMB363. And if I get it right, 6 onboard sata ports are controlled by the Intel P55 controller, while 1 onboard sata and 1 onboard eSata are controlled by the JMicron controller.
As for BIOS settings,
I've set AHCI on RAID Mode in the "Integrated Peripherals" tab
http://imageshack.us/photo/my-images/851/p7230158.jpg/
and also AHCI on RAID Mode in the On-Chip ATA Devices sub-menu:
http://imageshack.us/photo/my-images/851/p7230158.jpg/
I suppose "on-chip controller" refers to the Intel P55 and "extra controller" refers to the JMicron controller, right?
I've put AHCI cause I want to user eSata hotswap for my external hard drive..
There's nothing wrong with my drive, if I use the case's USB port instead, the drive is recognized immediately. I also tried the front panel eSata port with the same drive and it works too.. So I guess it has something to do with the JMicron controller..
Have I done anything wrong with my configuration? I must say that I don't use any of my hard drives in RAID pair or something..
You can check some of my other settings in the screenshots..
Thank you

Quote
I suppose "on-chip controller" refers to the Intel P55 and "extra controller" refers to the JMicron controller, right?
Yes.
In Windows, look under Computer Management/Drive Management to see if the drive appears there. You may have to set it active in Windows and assign a drive letter in order to be able to use it.

MSI p55-gd65 1.8 bios update issue

Here we go:
So I prompted myself to update my p55-gd65 bios from...either 1.6 or 1.7? to 1.8 I used the LiveUpdate Online feature on MSI's website. Seemed to be fine after until my computer sometimes froze while watching streaming flash videos.
I thought it was caused by an outdate video driver so I updated it, either before or after the video update (can't remember) I shut down and reset the CMOS settings (took out the battery for +30sec), still froze.
Decided to Update the Intel 3/4/5 Chipset v9.1.1 provided by MSI, completely wiped the video driver, reinstalled it, still froze. Wiped adobe flash player and cache from firefox, reinstalled flash...still froze.
I noticed too late that the LiveUpdate requires 32bit Win7. and that the manual DL for the bios update I tried installing popped up with an OS incompatibility error. Does v1.8 not support 64bit? or would it have been better for me to flash the bios update?
Thanks for any help!

Quote from: Henry on 24-June-10, 06:30:57
Can you post a screenshot of CPU-Z 'Memory' & 'SPD' tabs? I don't know on the P55 MB's but on both of mine that RAM runs perfect out of the box on Auto setting in BIOS at 1333, 9, 9, 9, 24, 1T @ 1.47V. Of course CPU-Z will show 1.5V for it.
here's the screens:

Trim Support in RAID 0 on a P55-GD65

Similar Messages

Maybe you are looking for