Major Problem - VISTA RTM / P5WD2-Premium / ICH7R SATA RAID
- I have tried loading the x32 RTM version of Vista on my P5WD2-Premium with
absolutely no luck. I have tried many different ICH7R SATA RAID drivers
including the one that comes on the OS DVD. The OS installs but, upon first
reboot, the RAID array becomes corrupt and will no longer boot (solid HD
light). I have tried RAID0 and 1. Both have the same results.
Anyone else seen this issue? If so, is there a solution?
Thanks,
Frank
All Replies
No solution, but I am having the same problems and symptoms with x32 RTM on an ASUS P5B Deluxe (ICH8R) system. I can only get it to install when I select an IDE configuration (not RAID or AHCI).
Intel released a new set of RAID drivers for their newer chipsets with RAID support. You can pick the drivers from the intel site.
http://downloadfinder.intel.com/scripts-df-external/Product_Filter.aspx?ProductID=2107&lang=eng
Be sure to download the floppy configuration utility and not the other one, you can create a floppy with the appropiate drivers with the downloaded file.
Good Luck!
- Sorry, I tried them already. It still doesn't work.
Frank - So did I. Didn't help. Very frustrating. RC1 and RC2 worked fine on the same system.
I also have the same issue trying to install either x64 or x86 Vista RTM on a Tyan i5000XT system with the Intel ESB2 ICH supporting Sata RAID 5 array. The member drives in the array get "error occurred" displayed during the 2nd boot sequence of the install. I am able to dual-boot into XP to re-enable the volume. I've also tried the new Intel drivers to no success.
I have been successful in installing on a Non-RAID SATA drive of all versions of Vista.
Hi,
I got the same problem here with ICH8R on Asus P5B deluxe/wifi. IDE installation works without problem, but with RAID enabled, the setup hangs after the first reboot. Without loading the newer Intel Matrix Storage Manager driver, the setup can't even format the disc and - if a raid partition is already available - sometimes crashes with bsod.
I thought, that the driver included in the setup (iastorv.sys) caused the errors, but even when deleting the driver during first part of setup (pressing F10 in the target HD selection screen and then deleting the driver after it's copied to the target disc), the second step of the setup hangs. When trying to boot in safe mode, the safe mode hangs loading crcdisk.sys.
Anyone knows how to fix this? I'd really like to install my Vista RTM version on a RAID system.
Best regards, Björn
- I got the same problem here with ICH8R on Asus P5B deluxe. IDE installation works without problem, but with ICH8R RAID enabled, the setup hangs after the first reboot in Green Loader.i can install Vista RC2 On it ,but There is No way in RTM!,even with An Image That Loaded From Image Drive,Whats wrong here?
Has anyone contacted ASUS tech support for help on this issue? I've tried contacting my vendor who is Tyan and they were not helpful at all. They just said we don't fully support Vista yet until full release. I've gotten the same answer from Intel on their support request. This is very frustrating. I have a ticket open to Microsoft to get "official" support. Since this is a release that is already widely availiable to many different communities I don't understand how support could be so lax. I suspect Microsoft will eventually respond but they will point the finger back to the H/W vendors i.e. ASUS, Intel, Tyan etc. The eventual solution is probably a BIOS update from the MB vendor but there is no definitive root cause as of current.
- I just loaded Vista Enterprise from DVD on a second raid partition on my P5WD2 Premium. I did not load any additional drivers for the Intel Raid controller. I had the partition already formated in XP. The drivers from the Vista DVD are working just fine for me. I now have a dual-boot system with XP-Pro/Vista. Did you try it without loading a driver? The driver loaded from DVD is 6.2.0.1015 dated 10/6/2006.
- I have the same problem with my Dell XPS 410 which uses the Intel P965 ICH8R chipset. Freezes like crazy - "The device, \Device\Ide\iaStor0, did not respond within the timeout period." I'm using Vista 32 Ultimate RTM. I got it to work fine for a couple of days then the symptoms surfaced again. I also use MCE to record and it doesn't even bother to record scheduled programs. Very frustrating!
I tried to debug the problem. Looks like that there is a deadlock in Intel's iaStorV.sys driver. Unfortunately Microsoft doesn't have sources to Intel OEM drivers, so we need to wait until they release a working version.
- MSFT
COSD wrote: I tried to debug the problem. Looks like that there is a deadlock in Intel's iaStorV.sys driver. Unfortunately Microsoft doesn't have sources to Intel OEM drivers, so we need to wait until they release a working version.
- MSFT
If it helps, I did not have a problem with build 5744 (RC2) installs on the same system. Is this an oversight by Microsoft? And will new drivers be integrated into a final Jan GA release build?
i sent a mail to Asus Technical Support 3 times.they replyed me with a new beta bios(V908 for Asus p5b-deluxe) to test with.but i got the same error and nothing changed.im forced to use the RC2 version now
.who knows the source of this *** problem that gets the only final or RTM version to crash?????????????????????????????????.Asuse+ich8r+raid0 only+vista RTM=Installation Impossible!
Hi,
Same here. Vista RTM won't install on my brand new Dell. I tried unRAIDing the disks, but no luck. I will try the Intel download, a dual boot setup. If that doesn't help, I'll reread http://chris123nt.com/guides/5219/index.html and http://forums.us.dell.com/supportforums/board/message?board.id=vista&message.id=2929
Kind regards
Hans
Hi,
Follow-up: Vista eventually installed on the machine. This is how I could solve the problem: unRAID the two disks, and do a clean install of Vista. No extra drivers were necessary.
Kind regards
Hans
- You Look Clever Hans Le Roy !.All Guys here Know that This problem is Related to Raid Drivers not anything more and as many guys mentioned before.but we dont wana waste our time to reinstall bunch of programs(in my case 3 installed windows versions, each one for 1 job,visual studio,sql server,web server,etc..).its even impossible for me,and more important we choose raid array because we really need it!,therefore clearing the main question wont solve the problem!!!
Hi Mike,
I think we have a different idea about what a forum is all about. I came here two days ago because I experienced the problem you are talking about, and I just wanted to tell you what I've done with the information and what the results are. No intention of looking clever.
Kind regards
Hans
Hi Mike,
can you perhaps send me the beta bios for p5b deluxe? I'd like to test it on my board.
Thanks for any info and help on this issue.
Best regards,
Björn
I think the issue here is that Windows Vista RTM has issues with Intel ICH7R / ICH8R SATA RAID.
Though I got it to install on a RAID 0 (Dell XPS 410), I still get intermittent freezing related to the iastor.sys driver. The first time that I installed Vista RTM on my Dell, it froze up for about 30 seconds every 10 mins. I've since reinstalled it and it is down to about 5 times a day. I didn't do anything different, so I assume that it has to do with some sort of dynamic updating that Vista does when you install on a machine that's connected to the internet.
I found the Exact Source of This error(I hope)
Error Source: Intel(R) Matrix Storage Manager Option ROM(Raid Bios setting For ICH7R or ICH8R in Bios)
its integrated and stored in MotherBoard Bios ROM and it can be changed with bios update.you can find it During the POST(or system Bootup screen) and see the exact version of it.or you can simply enter it with special hotkey(Ctrl+I in My M/B:ASUS P5B-DELUXE) and Find its Version on Top of The Screen.
I found that Intel Releases New Option ROM with each version of its Riad Driver,therefore both of them(Raid ROM & Driver) should have same versions in order to working Properly.but my mobo Raid version is 6.1.0.1002 (About 3 month older than Newest Version Of Matrix Riad Manager that u can find in Intel's Site> Support >download,its version is:6.2.0.2002,11/8/2006 ) and also its older than Raid files integrated in VISTA RTM....then you can guess what's happened here!
yes, we Have Incompatible Raid Bios And Raid Drivers!
Solution: Updating Bios To Newer one that Should be Contains the Same (or Newer )Raid Bios Version as Vista RTM Has
its also Describes the ability to Successfull installing Of Vista RC1 or RC2 ,because their integrated Raid drivers were compatible(and newest version) with our Mobos at Time Of release.
plz join us to Ask Motherboard Suppliers for on Demand Availiblity of Updated Raid Bios that work with Vista RTM.
we need it Now ,Before Official Vista Release(jan 30)
I just received a beta bios update (0910) from Asus support for my P5B Deluxe board, but it doesn't fix the raid problem :( - It also doesn't include a newer version of the raid rom.
I wrote an reply to ask them for an update of the raid rom - maybe there will be a fix availabe soon - I hope it at least...
- Same problem here with Asus P5B Deluxe and 4 discs in a RAID.
I tried the drivers that came with VISTA and the new Intel drivers - both with the same problems. Anybody have better luck yet? I am just curious on what brand/model drives everyone is using. All my drivers are Western Digial RE2 models which have TLER. I suspect there there is a timing issue between the drive volume and the Vista install process.
Are people having problems actually installing Vista x86/x64 or just running Vista once its installed? I've had problems installing Vista on a RAID volume but not on a standalone drive.
Thus far, I've heard about this problem mainly on ICH8R southbridges, but my machine uses the ESB2 southbridge with the 5000X chipset on a Xeon platform. Both these chipsets are slightly newer than the ICH7 and support the same Level of Matrix Storage functionality according to Intel.
bstickler wrote: Hi Mike,
can you perhaps send me the beta bios for p5b deluxe? I'd like to test it on my board.
Thanks for any info and help on this issue.
Best regards,
Björn
Rest assured you are not alone. I have the same type of problem. Windows Vista Ultimate (version 6000) installs on my ASUS P5B Deluxe (bios version 0903) after checking compatibility is OK. However, the system then suffers from incessant "Not Responding" errors which can take several minutes to clear before it can be accessed again. In essence, the system is unuseable for normal purposes! With much percevearance I have established that:-
1. The guilty party is the Intel 82801 HR/HH/HO raid controller
2. Windows installs driver iaStorV.sys in the Drivers section of the Windows System 32 directory.
3. The driver is version 6.2.0.1015 and is provided by Intel.
4. The driver is digitally signed by Microsoft.
5. The Event Viewer shows the following:-
Log Name: System
Source: iaStoreV
Event ID: 9
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Study
The device: \Device\Idle\iaStor0, did not respond within timeout period.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/event">
<system>
<provider Name="iaStorV />
<EventID Qualifiers="49156">9<EventID>
<Level>2</Level>
<Task>0</Task><Ketwords>0x8000000000000</Keywords>
TimeCreated SystemTime="207-01-22T17:22:54. 360Z" />
<EventRecordID>1914</EventRecordID>
<Channel>System</Channel>
<EventData>
<Data>\Device\Ide\iaStor0</Data>
<Binary>0F0005000100000000000000090004C000100000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
I have tried numerous suggestions to resolve this matter but nothing has worked. I suspect that Intel/Microsoft need to produce a new driver to overcome this problem before the official retail release date at the end of this month.
I'm using 3 Maxtor 6V250F0 Drives. So I don't think the Harddisk is the source of the problem. I also wrote to Maxtor (Seagate) support and they replied very quickly. They said, that the problem is not caused by the harddisk. I still think that it's a problem with the raid controller / rom / driver.
I've been following the thread for a week or two now - I'm having exactly the same problems with P5B Deluxe/WiFi and a pair of WD2500KS in a RAID0 configuration. BIOS and driver updates once the OS was installed have helped a bit - so long as I don't stress the drives too much. As soon as I try and do something labour intensive (such as installing VS2005) I start getting the error 'The device, \Device\Ide\iaStor0, did not respond within the timeout period.' in the error log. This happens more frequently the longer I use it until Vista becomes locked or I get a BSOD. About half of the time this has happened I have to rebuild the RAID and re-install Vista. On one occasion Vista displayed a notification saying 'RAID0 stripe becoming corrupted - please restart the machine'
I used XP and Vista RC2 on the same harware in the same configuration with absolutely *no* storage related issues - and that's using it 8 hours a day for 5 months. I have repeatedly been trying to contact ASUS about this but am unable to load their support form (too many users....I wonder why?)
My setup is:
Intel(R) 82801HR/HH/HO SATA RAID driver:Version 6.2.1.1002
The firmware version on the RAID controller shows 6.1.0.1002
BIOS: 1004 released on 2007-01-26. (I also tried 0804 and 0910 final version - same problem).
Memory: 2GB Corsair TwinX XMS2 PC6400 (5-5-5-12)
Hard Drives: 3 x 250GB Western digital WD2500KS - two in RAID0 and one standalone (holding a number of Vista install images - thank you Acronis)
Optical Drive: LiteOn SATA DVD connected to the JMicron port (although I have tried disabling this)
All other drivers were supplied on the Vista disc.I hope asus sort their act out and release a BIOS to update the firmware pretty soon - the 'Vista isn't officially released yet' line is growing tiresome!
Just to throw in my 2 cents...
I have the same problem with the P5B Deluxe Wi-Fi / Vista RTM / 2 RAID'd WD 500GB RE2 drives. When the disks were in RAID 1, I got timeout errors from iaStor and system performance was sluggish - drivers 6.2.0.2002. I'm booting off of the JMicron controller in AHCI mode with a 74GB Raptor, and I was using the mirrored drives for all my data / photos / etc. It got to the point where I ended up with a couple of intermittent blue screens. One blue screen actually managed to kill the second drive. Or at least I thought. First boot showed that the second drive was having issues in the Matrix Storage Manager (and at boot time). Second boot, the drive didn't come back to life, and my RAID set was considered fully degraded with only 1 disk. I was prepared to RMA the drive, but ran it through some tests first while hooked up to another machine. The drive is actually fine -- I could read data off of it fine. I ran all sorts of controller and surface scans and everything checked out without a hitch... so I ended up formatting it and it now sits on my desk awaiting fixed drivers from Intel. Performance is much better in the degraded RAID 1 state -- I don't have iaStor problems and my system doesn't pause. I have since upgraded to 6.2.1.1002, but I don't believe that the timeout bug is fixed yet in the iaStor drivers.
Here's where it gets kind of interesting. I'm not so sure that ASUS is to blame here -- I think the problem is Intel and their lame ICH8R drivers and Intel Matrix Storage Manager (which doesn't work too well in Vista). When I was running 6.2.0.2002, I was looking around at other manufacturers sites to see if they had beta drivers from Intel. None did, but it turned out that Gigabyte had 6.2.0.2002, but with a different readme bound up in the release. The Gigabyte version contained a list of known issues that was removed from the readme published on the Intel site (again, even though the versions were identical). Find the Gigabyte version here -- http://www.gigabyte.com.tw/Support/Motherboard/Driver_DownloadFile.aspx?FileType=Driver&FileID=2924
Here's the original known issues list from that alternate release notes file -- pay attention to 1997508
Known Issues in Production Candidate 6.2.0.2002
Reference No
Description
Affected OS's
216105
‘Another instance of setup is already running’ dialog has text corruptions in KOR. Known issue in Install Shield* 10.5 and 11.0 wrap.
All OS’s
2126106
Cancel button is only partly visible on Install Shield* extraction dialog in Greek. Known issue in Install Shield* 10.5 and 11.0 wrap.
All OS’s
2126464
Two types of fonts used in 1 single dialog in JPN. Known issue in Install Shield* 10.5 and 11.0 wrap.
All OS’s
2079371
(Vista*-Microsoft Bug)On ICH7MDH systems, RAID volumes are not visible in ‘Advanced Mode’ on reboot, after creating a RAID volume using the create volume wizard from UI when ATA controllers are enabled on the system.
Windows* Vista/ Windows* Vista* x64
1997508
(Vista* - Microsoft Bug) - iaStor timeout errors in system event viewer
All OS’s
2100122
(Vista* - Microsoft Bug) - VISTA cannnot be installed on Calistoga when LAN is enabled.
Windows* Vista/ Windows* Vista* x64
In the latest 6.2.1.1002, you'll see this list of fixed issues, where actually none of the known issues from above are fixed.
http://downloadmirror.intel.com/df-support/12474/ENG/relnotes.htm
Issues Resolved in Production Version 6.2.1.1002
Reference No:
Description
Components
Affected OS's
2195165
On systems with a RAID volume greater than 1TB, a blue screen may occur if the system enters the S4 power state while a rebuild or parity initialization of a RAID 5 volumeis in progress
Driver
Windows* Vista/ Windows* Vista* x64
2199965
Use of the -s switch does not result in a silent installation when used with other incorrect commands
Installer
Windows* XP/Windows* Vista/ Windows* Vista* x64
2199692
Double-clicking the Intel® Matrix Storage Console while in Administrator mode does not run the Intel® Matrix Storage Manager with full privileges
So I think Intel's to blame... and they need to get their act together. 6.2.0.2002 was released on October 13, 2006, which means they've known about our timeout problem for a long time.
attempting to instal vista x64 rtm on my gigabyte GA-965P-DS4 (965P+ICH8R) would degrade my raid5 array (3 x WD2500YS). disabling the onboard Marvell Yukon 88E8053 GbE solves this.
after install, i tried enabling the lan, but hibernate would screw the raid again. updated the lan drivers to 9.14.4.3, but the raid keeps getting degraded. disabled lan again, dropped in an old realtek 8139 pci 10/100, and all is fine.
so, is this intel's or marvell's fault?
note: xp x86 rtm installed fine, maybe cause it doesn't have in-box drivers for the marvell?
That's very very interesting... I've been trying for some time to get Vista onto a GA-965P-DQ6 box with an ICH8R controller, and had pretty much proved to myself that it was the RAID controller drivers/bios causing a blue screen as it rebooted into the second part of the setup routine. The board is a model up from the DS4, but the controller is the same - did you have any such issues? The only other difference is that I am running RAID0 not RAID5.
As for the issues with your network card - that's down to Marvell, no doubt.
at first I was also thinking it was the raid, as I was getting a restart during installation (was trying raid1 at that point).
but when I also tried to install onto a single drive on the ich8r (still set to raid mode - in this mode, single drives appear as though they are on an ahci controller), the installer was getting stuck at 'completing installation'. I took a wild guess that it was doing some network thingy, so I disabled the marvell, and tried again. bingo.
after this sucess, I then tried raid1 without the marvell, and that worked. now I am using raid5 (I was waiting for my 3rd drive to arrive from the shop during this period, hence the raid1 tests)
try it yourself with your GA-965P-DQ6
No luck here, intall of Vista is without problems. However when using it by installing driver (ati 7.1) or any other HD activity all files get corrupted.
Setup 150G Raptor on Jmicron, Raid10 4x250g Samsung on intel/ezraid.
Intalling Vista on either one works, but with same result, within 3 restarts files corrupted.
Xp on this setup is no problem.
Mainboard is Asus p5w dh deluxe, tried install with Marvell on and off, same result. Using all the latest drivers.
- Just thought I'd chip in here as I've had no issues installing Vista x86 or x64 on an ASUS P5B Deluxe Wi-Fi board using two drives configured as RAID0 and another two drives as a RAID1. This has been using the driver built into Vista and the latest Intel driver updated from a USB key. I'm not using the latest BIOS, worried about the non-roll back statement in case its not reliable, but have used the previous two releases. Seems that it might be a faulty board because I've seen no BSOD's caused by the ICH8R.
Hello all. My recent Vista ultimate install is constantly "not responding." Programs drop out entirely, the control panel won't open, explorer fails. The Raptor crunches for minutes at a time after startup, shut downs can take 3 to 4 minutes with Zero activity. I am at my wits end. Here's my rig:
ASUS P5B Deluxe WiFi Edition (Bios 1004)
Intel E6700
Corsair P4C - 6400 2 Gigs
Nvidia 8800 GTS
Plextor SATA DvD
Western Digital Raptor (150) SATA
I also have a corallery problem that my DVD won't boot the ultimate disc (YES it's the FULL version). I recently tried booting the xp disc to erase Vista from my life and it started fine; I loaded the f6 SATA drivers and it proceeded to tell me that the hard disc is corrupt or the hard disk controller is corrupt. I bought a NEW SATA drive and repeated the install with the xp disk and got the same error. So the hard disk controller is hosed! How can I fix this?
So has anyone solved this!!! What is up with the ICH8R drivers and VISTA!!! Does anyone out there have a working P5B build with Vista? Seriously!! Sorry for the shouts, I am really frustrated. I don't even know what other motherboard I should buy to just ditch ASUS and these problems. Who has a working vista build with modern components? What motherboards work! Thanks.
I have P5B-E Plus.I have installed Vista Ultimate OEM with raid0.No problems what so ever.
Bios 504.Two Seagate 7200.10 E6400 oced to 3.2Ghz. Team Extreem 6400 4-4-4-10 @4-4-4-4.
Marvel lan & onboard audio disabled.Everything seems to work ok.I have cheap additional 10/100 network card.
My vote to Marvel probs.
Tried one last option. Installed Vista, after complete install disabled the ich7r controller. And for sure Vista keeps running without corrupting any files, I will keep you informed. Marvell is enabled btw!
is that vista x86 or vista x64
I tried to install Vista X32 and X64 RTM into an existing ICH8R Matrix-Raid with 4 Raid-5 and one raid-0 partition hosted on 3 Samsung 501LJ harddisks. I have XP installed on two partitions without any trouble, the system runs perfectly stable.
The mainboard is Foxconn P9657AA-8EKRS2H, and the gigabit adapter is a Marvell Yukon
Loading the installer took really long time, after about 15 mins I got the install onto menu. BUT the Raid-5 partitons are missing. The menu shows one big raid-5 and one raid-0. Using the intel iastor.sys 6.2.0.2002 did not change anything.
After installation abort, the raid was currupted, the intel raid bios was able to reactivate two drives, one did still fail. This allowed to start the existing XP installation. Finally I was ably to reactivate the last harddisk in the intel storage manager and after a few hours of rebuilding, the raid was online again.
I did not try the latest intel driver, since it is too risky and time consuming to eventually recover from the failed raid. And I did not try disabling the ethernet, I will not buy another adapter just to install vista.
My conclusion is that the intel (fake)-raid is not vista compatible, until either a bios or driver update that will fix this.
Hmmm,
Hans
Just found this forum:
http://www.wilderssecurity.com/showthread.php?t=142689
I have been using Acronis for a while. So my partitions are created with that program. It will take time to move all files around and recreate the partions, if I find that prevents corruption I will let you know.
- Just one question. are you guys using the jmicron or intels chip?
Used Partition Magic to clear all partitions made with Acronis, made new partitions with PM, then reinstalled.
Vista working like a charm, raid10 on intel and raptor on Jmicron. Marvell ethernet in use.
Hope it is of help for any of you, had similar problems on the ich7r as described in this thread before.
With P5B-E Plus...
RAID 0 with ICH8R
Vista Ultimate X64 OEM
Marvell Gigabit disabled.
Still no probs after 3 days.
I have a problem installinG vISTA
""A problem has been detected and window has been shut down to prevent damage to you computer
this BIOS in this system is npot fully compliant. Please contact your system vendor for updated BIOS.
Technical information;
**STOP 0X000000A5(0X00000011, 0X000000007, 0XFFDOD010, 0X0100000E) ""
I upgraded the BIOS. I am still having the same problem.
I've got the same problem here: iaStor events in the system log and timeouts with the hard drives. Using 4 x 320 GB WD's in a Raid-5 array on a P5B Deluxe/WiFi.
However, I'm running XP Pro SP2 and have never installed Vista on this machine yet. This is my second install of XP Pro and I'm still receiving the same errors. Using the latest Intel ICH8R driver that I could locate - 6.2.1.1002, and most recent BIOS from Asus - 1004. Previously using BIOS 0804 with same problem. So this error would not seem to be limited to Vista installs only. There would seem to be definite issues with the Raid controller / driver. Any info for a fix would greatly appreciated.
- I am having a similar problem with the ICH7R SATA RAID.
I am attempting an upgrade from withing XP MCE to Vista Home Premium.
If I have SATA RAID enabled I boot until a STOP 7B after the first reboot.
When I revert to SATA IDE I STOP 7B during windows setup and safe mode.
Safe mode gets as far as (xx)disk.sys, I have to go back and look at the exact file.
Somethings not all that ready with ICH7R SATA RAID and Vista at this point.
FYI, upgrade advisor gave no warnings to the SATA RAID prior to the upgrade attempt.
I had to kill my RAID and revert to SATA IDE to get Vista installed. If i try to rebuild my RAID array I get the same STOP 7B every time I turn enable SATA RAID in BIOS. - Same problem here, 2 systems one with p5b del. wifi and 4 x WD 250gb Raid5 and the other with same board and 4 x Maxtor 80gb Raid0, both work great under XP Sp2, tryed installing Vista and get timeouts/degraded raid.
I guess I have been lucky so far with Vista x64. I have a P5B-D (bios 1004) and my RAID has yet to be degraded(RAID 0 with 2x500gb Seagate 7200.9). I downloaded this 64bit floppy driver creation application. There is an IMA that contains Intel's RAID drivers version 6.2.1.1002.
About dvd booting: The Vista install dvds do not like booting from SATA DVD drives when the controller is set to RAID. Other cds do not mind booting in such a configuration. My workaround for this is having RAID enabled on the Intel controller while having the other controller (JMicron) be set to IDE mode and have the SATA DVD drive attached to the one set to IDE.Fixed the problem !!
i had the same issue with my p5wd2-premium
Boot Vista in safe mode using F6 and then F8
I have made a boot disk with the RAID/AHCI driver version 6.2.1.1002 from the intel web site...
I have installed the drivers before making the partitions ....
Good luck !!
Sounds good Neijix.
As someone who has been sitting on the fence awaiting a solution to the driver problem, I was wondering exactly what you did that others didn't?
I haven't tried installing Vista yet, let alone with RAID, and would be grateful if you could give an additional couple of clues.
To load the RAID drivers under the Vista install one presses F6 like in XP? Just a side question, really.
You mention that one has to boot Vista in Safe mode....I thought the problem with the RAID drivers was that Vista wouldn't install or would be corrupted during install. Presumably one cannot start Vista in Safe Mode without installing it first? I am sure I am missing something fundamental here, but would appreciate being told what! :-)
How did you install Vista in the first place? Back to the beginning, what did you do that others didn't manage?
- I'm experiencing a similar problem to you guys, but this time on a new system.
I purchased a new Dell machine earlier this week running Vista with two 250gb Samsung drives RAID striped under an "Intel 82801HR/HH/H0 SATA Raid Controller".
I used it for a few hours in Windows and didn't really notice any issues, but running Media Centre live TV and video playback with freeze for 10 seconds maybe once every half hour at which point the disc access light is on constantly. Checking the event viewer, at these times a log entry is written with an Event Id of 9 for iaStor saying "The device, \Device\Ide\iaStor0, did not respond within the timeout period."
I have version 6.2.0.2002 of the Intel Matrix Storage Manager installed like yourselves. I'm hoping the issue will be as simple as a driver upgrade as I really don't wanna have to get involed with Dell's (non)Technical Support.
Just to provide a little more detail... When the computer freezes the mouse and remote control still work, but it appears all PCI devices are locked. All TV recordings I've tried to set up have been split in two with a ten second gap missing! Hello,
I had the same problems with RAID0 and ICH8R under Vista Ultimate 32-bit Beta 2, RC 1 and at least the release version 6000 (mainboard: ASUS P5B Deluxe WiFi).
My solution is very simple:
1 - Update your BIOS to the newest version (P5B Deluxe: 1004)
2 - Install the latest version of Intel Matrix Storage Manager for your chipset (in my case: iata621_cd.exe) - within Vista
3 - Very important: Install the latest version of Intel's INF Update Utility (8.1.1.1010 - infinst_autol.exe) - within Vista
Here an excerpt of Intel's readme.txt for the Matrix Storage Manager:
"* 2. SYSTEM REQUIREMENTS ************************************************************ 1. The system must contain an Intel(R) Pentium(R) Processor or Intel(R) Xeon(TM) Processor and one of the following Intel products: - Intel(R) 82801HR/HH/HO I/O Controller Hub (ICH8R) - Intel(R) 631xESB/632xESB I/O Controller Hub (ESB2) - Intel(R) 82801GHM I/O Controller Hub (ICH7MR) - Intel(R) 82801GBM I/O Controller Hub (ICH7M) - Intel(R) 82801GR I/O Controller Hub (ICH7R) - Intel(R) 82801GH I/O controller Hub (ICH7DH) - Intel(R) 82801FR I/O Controller Hub (ICH6R) - Intel(R) 82801FBM I/O Controller Hub (ICH6M) 2. The system must be running on one of the following operating systems: - Microsoft* Vista* - Microsoft* Vista* x64 Edition (NOTE 1) - Microsoft* Windows* XP Home Edition - Microsoft* Windows* XP Professional - Microsoft* Windows* XP x64 Edition (NOTE 1) - Microsoft* Windows* 2000 Advanced Server - Microsoft* Windows* Server 2003 - Microsoft* Windows* Server 2003, Web x64 Edition (NOTE 1) - Microsoft* Windows* Server 2003, Standard x64 Edition (NOTE 1) - Microsoft* Windows* Server 2003, Enterprise x64 Edition (NOTE 1) - Microsoft* Windows* Media Center Edition NOTE 1: If the system is running Windows* 64-bit version, the Intel Matrix Storage Manager Driver supporting 64-bit should be used. 3. The following operating systems are not supported: Any version of the following Microsoft operating systems: - MS-DOS - Windows 3.1 - Windows NT 3.51 - Windows 95 - Windows 98 - Windows Millennium Edition (Me) - Windows NT 4.0 - Windows 2000 Datacenter Server Any version of the following operating systems: - Linux - UNIX - BeOS - MacOS - OS/2 4. The system should contain at least the minimum system memory required by the operating system. 5. The 'Intel(R) Chipset Software Installation Utility' must be installed prior to installing the Intel(R) Matrix Storage Manager."OK, that was it! My system is running perfectly now - no Raid Controller timeouts.
Perhaps this can solve your problems.
Good luck and regards from Germany
Bernhard L.
Yes, I'm another victim of this problem. Brand new system as follows:
- ASUS A5B-E
- Duo-Core E6600
- Dual Seagate Barracuda 320 GB Drives configured RAID0
- PNY Nvidia 8800 GTS
- 2 x 1024 OCZ Platinum DDR2-800
- No other cards installed
- 680 W Apevia Iceberg PS
Everything was looking good with the MB straight out of the box. I was able to install Vista Home Premium OEM and several applications including MS Office 2003. It looked like it was going to be stable. I had not yet tried any overclocking or fine tuning. In fact, I changed very little in the BIOS other than setting up for RAID0.
The ASUS install disk failed to run. So I downloaded the latest BIOS and as many Vista capable drivers as I could find from the ASUS site. Unfortunately, I didn't realize that flashing the BIOS on a system running RAID might be a dangerous thing to do. Apparently all of the settings get reset to factory default when you load a new BIOS. (As in set back to IDE mode) At least that's what I heard and it might explain what happened next.
Immediately after completing the reflash, the system failed. I think the drives became corrupted. Eventually, I gave up and started over. However, I have not been able to get nearly as far as I did before. It seems that the system is no longer as stable as it was prior to the reflash. Unfortunately, I don't recall what BIOS version it had, but I know the knew one is 1002. I think the prior one was 08xx.
This isn't sufficient evidence to suggest the BIOS is the cause. In fact, I think someone said they had this problem with older BIOS revs as well.
Right now, I can boot from the DVD drive using the Windows install disk. When I enter the repair tool, it doesn't even see a copy of Vista on the RAID array although it did the first time around before I reinstalled Vista. I guess the boot partition is completely hosed and this is my second install.
I don't know what rev. of RAID controller driver I have installed. I did not update the Intel driver because I didn't find one on the ASUS site.
I.m experiencing also the same timeout issues.
I have a HP Pavilion 76xx serie desktop with Windows Vista on it and i have also experiencing freezes for +- 10 seconds
It has a Intel 82801 HR/HH/HO Sata Raid Controller and Intel P965 Chipset.
There is still no BIOS update available @ hp. Is Intel aware of this problemThis is a report from the Intel Matrix Storage Manager
System Information
Kit Installed: 6.2.1.1002
Kit Install History: 6.2.1.1002
Shell Version: 6.2.1.1002
OS Name: Microsoft® Windows Vista™ Ultimate
OS Version: 6.0.6000 Build 6000
System Name: DIMENKIKI-PC
System Manufacturer: ASUSTek Computer INC.
System Model: Basswood
Processor: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
BIOS Version/Date: Phoenix Technologies, LTD 3.08, 09/18/2006
Language: ENU
Intel(R) RAID Technology
Intel RAID Controller: Intel(R) 82801HR/HH/HO SATA RAID Controller
Number of Serial ATA ports: 6
RAID Option ROM Version: 6.0.0.1022
Driver Version: 6.2.1.1002
RAID Plug-In Version: 6.2.1.1002
Language Resource Version of the RAID Plug-In: 6.2.1.1002
Create Volume Wizard Version: 6.2.1.1002
Language Resource Version of the Create Volume Wizard: 6.2.1.1002
Create Volume from Existing Hard Drive Wizard Version: 6.2.1.1002
Language Resource Version of the Create Volume from Existing Hard Drive
Wizard: 6.2.1.1002
Modify Volume Wizard Version: 6.2.1.1002
Language Resource Version of the Modify Volume Wizard: 6.2.1.1002
Delete Volume Wizard Version: 6.2.1.1002
Language Resource Version of the Delete Volume Wizard: 6.2.1.1002
ISDI Library Version: 6.2.1.1002
Event Monitor User Notification Tool Version: 6.2.1.1005
Language Resource Version of the Event Monitor User Notification Tool:
6.2.1.1005
Event Monitor Version: 6.2.1.1005I have had the same problems with my 965WH board and Intel Matrix RAID 6.2.1.1002. The performance in Vista x64 was incredibly sluggish. Navigating through directories would take 10+ seconds to refresh and at times Vista would take 20+ minutes to shutdown. My RAID 1 was degraded three times, system restore would not work and eventually the disk directory structure was corrupted and unusable. I set the disk controller back to legacy IDE mode and reinstalled Vista. Everything now is fast just like a clean XP install. I can't beleive Intel released these drivers, and I can't beleive the drivers made it through WHQL.
Has anyone tried running the RAID drivers and disabling the Matrix RAID manager service? I am thinking the Intel Matrix RAID task bar application may be what is screwing everything up. I'm going to use IDE until they get the drivers fixed, and then figure out a way to get back to a RAID configuration.
I had all these same problems with RAID on a Gigabyte GA-965P-DQ6 with new VISTA install. Gigabyte support apparently gives the nod to the earlier poster who pointed to the Marvell LAN conflicting with RAID somehow, as their solution:
http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372
is to flash the Marvell (yukon).
- Joined to reply to this, its worked for me using this Eprom update http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 I have a Gigabyte DS4 all my Vista raid problems seem to have gone.
System specs.Manufacturer: Gigabyte DS4 Bios revision F8 MotherboardProcessor: Intel(R) Core 2 CPU 6400 @3.6GHzMemory: 4096MB RAM Corsair 6400C4 @900MHz 4-4-4-12-2THard Drive: 2*250Gb SATAII Maxtors @500GB RAID0 +320GbVideo Card: NVIDIA GeForce 7950 GX2Monitor: ViewSonic VA1912w SERIES @1440*900Sound Card: SB X-Fi Extreme Music - This is not just happening to Raid Sata drives. It is also happening other sata drives. I tried installing on a brand new Western Digital Hard Drive sata model wd500ks WD Caviar SE16 500GB Drive or my orginal drive
Western Digital 250-GB 7200-RPM 80GPP SATA Hard Drive
Intel 865G Chipset, consisting of:
- Intel 82865G GMCH
- Intel 82801EB ICH5
- 4-Mb FWH
When Installed on IDE it works great. Sata it is totally nuts.
Anybody know what is going on with this?
I have read so many different ways to fix this and everyone has a different fix. How the heck is this supposed to be improved?
- they want 500$ for that?
Alas, this isn’t just happening on systems with a Marvell LAN adapter. I have the same problem on a new Dell XPS-410 with the Intel ICH8R and two 250 GB SATA drives configured as a RAID0. As with the rest of you, the problem is chronic and severe NTFS corruption accompanied by Event ID 9 Errors in the System log to the effect that “The device, \Device\Ide\iaStor0, did not respond within the timeout period.” Of course the file corruption leads to a wide variety of application and OS errors. Just run chkdsk c: /f to go on system startup, and watch the errors start to come.
Deleting the partition and restarting Vista Setup using F6 and loading the Intel RAID Controller 6.2.0.2002 driver before creating the partition didn’t work for me, despite Neijix’s results. And I’ve tried with Home Premium (the edition supplied by Dell with this computer), Business and even Enterprise. It doesn’t seem to matter if I use 6.2.0.1015 (the default from a Microsoft Vista installation) or 6.2.0.2002 (what Dell’s OEM image comes with). Currently the ROM is Intel Matrix Storage Manager option ROM 6.0.0.1022. Dell Express Premium Support didn’t have much to offer, just telling me to restore my image, then report back (the associate I spoke to intimated that he’d been kept very busy with Vista driver problems since Dell dropped WinXP in favor of Vista on its new systems). I plan to call the repeat callback number, and if they still don’t have a solution to this, I’ll try it with RAID1 instead of RAID0, then will grumble to Dell’s Customer Care (probably demanding to exchange my system at that point). Very annoying, as you can all relate.
- I'd be very interested to hear how you get on Schell, as I have exactly the same problem as you (as posted earlier) on a Dell Dimension 9200 - twin 250gb RAID 0 striped drives, running Vista Home Premium preinstalled. I'm just hoping an Intel Matrix Storage Manager update will solve it...
I will again go back to my post from several weeks ago, because there are people who seem to think that Intel is not to blame (not previous poster, just further up the thread).
This is definitely a bug in the Intel driver. They have acknowledged in their own internal bug tracking system that it is a bug in their driver. They have given it a issue number. They have known about it since version 6.2.0.2002, which was released on October 13, 2006. Yet they don't seem to be actively doing anything about it.
They intentionally removed the known issues list from the public release on their site, but must have mistakenly left it on the Gigabyte release (see my previous post). Here is their tracking number.
1997508
(Vista* - Microsoft Bug) - iaStor timeout errors in system event viewer
All OS’s
We need to collectively badger Intel for a new driver.
I'm a software developer myself, and I know that writing good drivers can be tricky -- especially considering how difficult they can be to debug, etc. However, this issue has been around for a long time, and there's no excuse for a company as big as Intel to have not tracked down a fix yet. The only thing that I can think of is that this issue has been fixed, but the QA process at Intel lags several months behind the fix. (Note the internal dates on the release notes vs. the publish date on Intels site).
-e
- Thanks for clarifying this Iristyle, I'd missed your earlier post. Like you say, hopefully the fix to this has just slipped through the net on the 6.2.1.1002 release and will be resolved in the next release.
Out of interest where did you get the information regarding their internal bug tracking? Do you know someone at Intel? With the number of different posts on the Internet regarding this issue you'd think they'd be aware of the sheer magnitude of the problem. At least you guys are able to install the OS. I'm note even able to install Vista on a RAID partition.
I have a ticket open with MS regarding this issue and the MS Support Rep is constantly checking with Intel to no avail.
- Computer manufacturers who sell Vista-certified computers that use the ICH7R/ICH8R can also be encouraged to "badger" Intel. I'll certainly be suggesting this to Dell in the case of the XPS-410.
- First of all, to all previous posters, THANK YOU!After much research on on many forums for my 965P-DQ6 Vista RAID problems, this forum, IF YOU READ ALL THE PREVIOUS POSTS (and their links!), is one of the most thorough and enlightening.My specifc problem (and research) has led to things that might help some of you. Gigabyte explained my symptoms as "a known software conflict between the ICH8R and the Yukon Marvel LAN". This was brought about because BOTH Intel and Marvel have been providing newer drivers to Microsoft for Vista (&XP), which Microsoft then pushed to both OS's through Windows update. Meanwhile, Gigabyte was trying to "patch" Marvel (and Intel) with Gigabyte BIOS updates. In other words, everybody was trying to slowly fix this problem, and the second fix broke the first fix, the fourth fix broke the third, etc...To sumarize the PROBLEM:a) The problem can apply to ANY device connected to a SATA port back to ICH5R (note the 'R'), even if they are not RAIDED. {Note solutions on many similar forums related to SATA DVD Vista INSTALL http://www.google.com/search?q=problem+SATA+DVD+install+vista&btnG=Search }b) The problem "developed" during Vista developement, but applies to XP, as some driver updates were pushed by Microsoft Update to XP users!c) The problem is *partially linked* to the Gigabit LAN drivers/PROMS, both Marvel and Intel(Intel 82566DC for you Dell 410 users).d) The problem has appeared and disappeared in combinations of OLDER versions of Intel inf drivers, Intel Matrix, chipset BIOS, and LAN drivers/PROMS { On 12/27/2006, Intel released a BIOS update 1612 in which they "Reverted back to RAID option ROM v6.1.0.1002" from 6.2.0.2002. http://downloadmirror.intel.com/df-support/12466/ENG/MQ_1612_ReleaseNotes.pdf}The commonest SYMPTOMS of the problem:A) Small delays in accessing SATA HDD or CD/DVD drive, with or without drive activity light. (This may be the only symptom, and is often not even noticed.)B) Delay during boot (multiple of 20seconds?) with iaStor error in event log. (Again, this may be the only symptom, and is often not even noticed.)C) Inabiltity to install / use SATA devices during OS (XP / VISTA) install (especially install to RAID or ACHI). Can't install VISTA off SATA conncted DVD. (Kinda noticable, therefore often posted to forums.)D) Errors (possibly even BSOD) during XP / VISTA usage, especially during high disk activity (especially for RAID, which can become corrupted).Current SOLUTIONS:1) Make sure you have the most recent intel chipset infAND MatrixStorage (and use it during OS install!)
http://downloadfinder.intel.com/scripts-df-external/Product_Filter.aspx?ProductID=2101&lang=eng
2) Find a flash for you Gigabit LAN, or disable.[For you 965P-DQ6 owners (SteelBytes, this also means YOU!), Gigabyte has recently released a flash for the Marvel EEPROM in DQ6 support area. (some were able to test this solution by simply disabling LAN in Vista or XP, for others the test failed, but the flash still fixed) http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 ]Iristyle, your ASUS P5B Deluxe/WiFi-AP has (two) older Marvel PROMS that ASUS needs to get you flashes for...
3) Make sure your main BIOS is updated. [For you 965P-DQ6 owners, use the newer F9 bios from Gigabyte, http://tw.giga-byte.com/Support/Motherboard/BIOS_List.aspx
Pick the correct rev for your board! The difference between rev 1.0 and 2.0 (rev 3.3 has only been shipping a couple weeks) is enough to cause MORE problems for those flashing wrong one.]4) If you can't get main BIOS (and LAN driver/PROM) newer than December '06, consider trying an OLDER one, as some (Gigabyte for example) tried to "patch" this ongoing "Vista" / ICH8R / Gigabit problem with their BIOS, and ended up breaking some "real" fixes!Iristyle & SteelBytes: Thanks for great research, leads and posts! - Very interesting.. FWIW, my P5B Deluxe/WiFi (not sure if it's ICH7R or ICH8R) works fine with Vista Ultimate RTM. I have two arrays on the same controller:
2x200GB (PATA w/SATA adapters) WD in RAID 0
2x500GB SATA2 WD5000YS in RAID 0
One of them constantly gets a warning because it doesn't respond after hibernation, but that's another matter. HOWEVER, my boot drive is a PATA drive. I haven't experienced any corrpution or freezes.
That said, and the reason I found this forum/topic is because I'm trying to set up a RAID on another system with an XP Pro SP2 install on an Asus P5WDH Deluxe mobo. For some reason, this particular model has only 3 SATA connectors on the ICH7R controller (1, 3, and 4) with an empty spot where the 4th should be. At any rate, here's my config:
1x 500GB WD5000YS - For Windows/Programs
2x 750GB Seagates in RAID0
Now the single drive was already installed and running XP Pro SP2 w/all updates, so I figured I'd just go into the BIOS, enable RAID, and use the "wizard" to create a RAID0 array for the 2 750GB's. Easy enough. The Intel bios reported that the single drive was a non-member, and the other 2 were successfully arrayed. But when I went to reboot, I got a BSOD halfway through the bootup. Tried again, same result. Tried Safe Mode, same result. Next, I went back into the BIOS and set the controller back to standard IDE mode, and it booted fine. I tried manually installing the drivers (Right click on the INF files from the floppy), and re-enabling the RAID mode, but it still crashed on boot. Finally, I decided to backup all my files and do a clean install of XP. I made a slipstream of all the latest updates, provided the drivers via F6, and the install completed successfully. Unfortunately, after the install, it still bluescreened when booting.
After reading your post, it makes sense that it may have something to do with an update MS rolled out, so I'm going to try to install an older version of XP without the latest patches and see how that goes. Not sure which update is the culprit though, so I'll have to be careful about installing updates (if I'm even successful).
I'd really prefer to keep all of my drives away from the Silicon Image or Jmicron controllers, so hopefully I don't have to resort to that. It's pretty discouraging (though not surprising) that this issue has not yet been resolved. I'm running Vista Home Premium on ASUS P5B Deluxe Wifi mobo, and have this problem in spades.
I can install and run Vista just fine when set to IDE mode in BIOS, but simply CANNOT figure out a way to get the system to fire up under AHCI (let alone RAID) mode (I have - well had, under XP) 2 x RAID 1 arrays: one for OS and one for documents. Everything worked 100%!!
Per suggestions earlier in the thread I have
1) installed Vista in IDE mode (all worked OK)
2) updated all Intel inf files (seems to work OK)
3) updated the ICH8R driver files (for the 4-port controller and the 2-port controller) to latest Intel drivers (downloaded from Intel) to AHCI drivers
4) shut down
5) reset BIOS to AHCI (was IDE)
6) system cannot restart (fails with the 'Cylon Eye' continuously crossing the screen).
So, have people found the above suggestions RELIABLE - has the workaround worked for everybody, or have you come to the point where you just CANNOT make Vista work on the ICH8R in AHCI mode, no matter what you try?
Thanks.
- hi!
I have the same problem with my Asus P5B Deluxe. with me was it however also that my SATA DVD with that Vista BOOT DVD did not want boot. there only one firmware update for the dvd drive assembly helped. still Vista in the Raid mode does not want to install itself! didn't vLite functioned unfortunately yet correctly, because it would be nevertheless worth a consideration, as long as one does not have functionality option rom to integrate older raid drivers in Vista dvd, or?
thanks!
sorry for my english (translated from german to english by Google.com)
original text:
"
ich habe das selbe problem mit meinem Asus P5B Deluxe. bei mir war es jedoch auch, dass mein SATA-DVD mit der Vista-BOOT-CD nicht booten wollten. da half nur ein firmware-update für das dvd-laufwerk. nach wie vor will sich Vista im Raid-Modus nicht installieren!
vLite funktioniert leider noch nicht richtig, denn es wäre doch eine überlegung wert, solange man kein vernüftiges option rom hat, ältere raid-treiber in die vista-dvd zu integrieren, oder?
danke!
" - Same problem here... :(
Motherboard: ASUS P5B deluxe WiFi
BIOS: 1004 (the last one)
HDs: 2xMaxtorDM10 6v250f0 with VA111900 firmware rev.
- Under Windows XP my HDs works very well both in AHCI and RAID0 modes.
- No way to make this disks working on Vista in AHCI and RAID0. Only IDE mode work good.
- flashing LAN firmware or disabling them doesn't solve the problem.
I wrote to Maxtor, the answer is: there isn't a know bug for Maxtor with VA111900 rev. and a Intel driver update is probably needed.... Firstly i wish to thank everyone for their research , but this problem is really starting to annoy me.
I have a Asus p5b delux wifi
lastest bios 1004
2x Maxtor sata Hard drives (Running Raid0)
I took the previous advice and downloaded the lastest Intel raid drivers and disabled the onboard lan
Success! Windows Vista (32bit) actually installed, then restarted for first boot up.
Now the screen brings up the "micorsoft corporation" scrolling loading bar. the bar moves but my hard drive light is solid and windows just wont come up!
Am i still doing something wrong or are the lastest intel raid drivers still no good enough?
- Looks like the P5B Deluxe folks are taking over this thread. Clearly the problem is common across boards with the Intel RAID controller chips. There is a fair amount of discussion around the web.
Let's make sure that we all report thr problems to ASUS tech support (direct reports using the web form) and make lots of noise about it on the ASUS forums. I'd suggest that we also make noise on the Intel forums, but they don't seem to exist any more. Hi, I have the same motherboard (GA-965P-ds4) with the same raid vista problems and I have used this rom update http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 from Gigabyte support centre.
But now my Marvel Yukon controller does not work at all. It does not recive the ip address from dhcp server. Never with manual settings of ip it seems working.
Do you now how can I roll-back to original shipped with rom?
Thank you and to all the guys will help me.
Webw0lf359 wrote: Joined to reply to this, its worked for me using this Eprom update http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 I have a Gigabyte DS4 all my Vista raid problems seem to have gone.
System specs.
Manufacturer: Gigabyte DS4 Bios revision F8 MotherboardProcessor: Intel(R) Core 2 CPU 6400 @3.6GHzMemory: 4096MB RAM Corsair 6400C4 @900MHz 4-4-4-12-2THard Drive: 2*250Gb SATAII Maxtors @500GB RAID0 +320GbVideo Card: NVIDIA GeForce 7950 GX2Monitor: ViewSonic VA1912w SERIES @1440*900Sound Card: SB X-Fi Extreme MusicHi, I have the same motherboard (GA-965P-ds4) with the same raid vista problems and I have used this rom update http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 from Gigabyte support centre.
But now my Marvel Yukon controller does not work at all. It does not recive the ip address from dhcp server. Never with manual settings of ip it seems working.
Does anyone know how can I roll-back to original shipped with rom?
Thank you to all the guys will help me.
Jez82c wrote: Firstly i wish to thank everyone for their research , but this problem is really starting to annoy me.
I have a Asus p5b delux wifi
lastest bios 1004
2x Maxtor sata Hard drives (Running Raid0)
I took the previous advice and downloaded the lastest Intel raid drivers and disabled the onboard lan
Success! Windows Vista (32bit) actually installed, then restarted for first boot up.
Now the screen brings up the "micorsoft corporation" scrolling loading bar. the bar moves but my hard drive light is solid and windows just wont come up!
Am i still doing something wrong or are the lastest intel raid drivers still no good enough?
I think the drivers are still not correct.- Are the correct drivers available or is it just hope that new drivers come out shortly?
- I think we are all waiting for updated (working) drivers to be released.
I've tried to install every version (Ultimate, Business, Enterprise, Home Premium but not Basic) of Vista RTM on my Gateway Laptop Model: Gateway M350E (WVN) and continue to get the same error message:
A problem has been detected and window has been shut down to prevent damage to you computer
this BIOS in this system is not fully ACPI compliant. Please contact your system vendor for updated BIOS.
I have the latest BIOS, drivers, everything; but Vista will not install.
I found the same message occurs with XP on some machines. A work around for XP is described at http://support.microsoft.com/kb/314830/ but I have not tried what they have described with Vista and from reading the article, I do not think it applies to Vista because it is my understanding that Vista does not use HAL that is used on XP to work around the ACPI compliance problem.
The hardware manufacturers and Microsoft need to fix these problems. The average Joe will never understand paying $350 for an operating system that will not install. They have (nearly) always installed before, why not now? I can't stand the thought of buying a MAC but I'm starting to think it might be an actual alternative if the manufacturers and software companies continue to write software that is designed to sell new computers, new versions of software instead of always giving us backward compatibility for the use of the computer systems that we already have. These computers that I am having difficulties with are just 2 and 3 years old. My gosh man; they ought to be compliant with anything that Microsoft releases. So do we have to hope that a first Service Pack for Vista will have a resolution to this problem or will it ever be solved? Should we throw away our new computers just so that we can see Aero in Vista? I don't think so. I think that Microsoft can do better than this.
- Motherboard: MSI 975X Power Up Edition
Hard Drive Config: Raid 10 + Raid 5 over 4 drives
Problems:
Vista installs fine. When I put load on the hard drives, the transfers start failing, Intel reports that 2 of my 4 hard drives have failed. When I restart, if I boot into Windows XP, I can restore those drives/my raid 5 partition and, as far as I can tell, most/all of my data is intact.
But this makes vista a non-viable O/S yet.
Any new ideas / drivers? Michele from italia wrote: Hi, I have the same motherboard (GA-965P-ds4) with the same raid vista problems and I have used this rom update http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 from Gigabyte support centre.
But now my Marvel Yukon controller does not work at all. It does not recive the ip address from dhcp server. Never with manual settings of ip it seems working.
Does anyone know how can I roll-back to original shipped with rom?
Thank you to all the guys will help me.
Ciao Michele,
Sorry for italian... ;)
prova a usare il comando:
yukonvpd -M macaddress
è sul floppy che hai usato per flashare la LAN. Il problema è che ti si è azzerato il macaddress e non funziona più il DHCP. Oppure puoi provare ad impostarlo via software da Windows. Comunque fatti fare da qualcuno che ha la tua scheda il backup della rom originale, si usa il comando "yukonvpd -R nomefile", non si sa mai...
Io purtroppo ho una P5B dlx e ho già flashato la ROM... Mi era successa la stessa cosa.
Ciao, ottimo italiano, da dove scrivi?
Problema risolto cambiando il MAC addres con una utility scaricata da internet. Poi ho scoperto che si può cambiare anche da windows. grazie
Io ho messo un MAC casuale, secondo te dovrei rimettere l'originale? e dove si trova?, sulla scheda madre ho trovato una etichetta vicino alla porta della LAN RJ45 con un numero che sembra proprio un MAC address, sarà questo? boh!
Se poi ci rimetto la rom originale di un amico avrò un MAC clonato, non credo che sia normale, potrebbero verificarsi problemi nella routing table di qualche dispositivo su internet, non credi?
ciao.
*****************************************************************************************************************************************************
For non italian people:
Problem fixed with mac addres changing. Please change you mac address after flashing the rom of your Marvel yukon lan adapter, with this command and the utiliy downloaded from gigabyte (http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372):
yukonvpd -M macaddress
For what it's worth, Dell's XPS support escalation folks told me they're well aware of this problem, and it comes up every week in a tech conference call with Intel. They've heard more troubles with striping (e.g., RAID0) than with mirroring (RAID1), though there have been some complaints about the latter too. I'm guessing that the problem simply takes longer to present in the case of RAID1 since most people are not actively doing chkdsk c: /f at bootup or monitoring for Event ID 9 in the System log, and thus don't realize they have a problem until the NTFS corruption starts causing applications or the OS itself to fail.
Of course the question comes to mind: if they know this is a problem, why are they selling computers with a configuration that's known not to work?
I can confirm that the problem occurs with RAID1 as well. I don't think the issue is so much that chkdisk is run less often, it's just that if a RAID0 screws up then that's it for the NTFS data whereas a RAID1 might at least regenerate itself. Generally on my 250GB disks that throws up about 100 or so errors each time!
I'm not convinced that the problem is with RAID per se as much as the Matrix drivers themselves. I've actually deleted the RAID1 configuration on my machine and am still seeing iastor0 errors.
I have a replacement system on the way from Dell. If they are aware of the problem as Intel's then someone needs to let the Dell support department know. I suspect that the left hand isn't talking to the right hand.
That said, if Dell, and other suppliers, are losing money replacing systems then hopefully this will keep the pressure on Intel much more than any number of unhappy end-users can.
Yes, we are all waiting for an Intel driver update.
In the mean time... I was wondering if one of you with a P5B with most recent BIOS could go into Matrix Storage manager and post what Option ROM version you all have. [Matrix Storage Console>View>System Report>Intel Raid Technology>{third line of text}] (FYI, Gigabyte BIOS F9 has 6.0.0.1022)
And speaking of "in the mean time" ... don't try to install Vista off a SATA connected DVD drive
... just don't!Sandokan71 , can you post where you found LAN firmware for your P5B?
To fix these specific problems (and also another class) Marvell released GBT5613n on 1/27/07 for the 88E805x series, which includes 88E8056, one of the two gigabit ports on the P5B Deluxe. Again, you can download this firmware at http://tw.giga-byte.com/Support/Motherboard/FAQ_Model.aspx?FAQID=2372 ( I have not yet found this update on ASUS site). The other gigabit adapter on the P5B WiFi is a Marvell Yukon 88E8001/8003/8010, but I don't know where you can get the firmware for this one! You can probably disable it until Sandokan71 posts a firmware location.
Also, in response to richardnau
>>6) system cannot restart (fails with the 'Cylon Eye' continuously crossing the screen).
I notice you did not yet disable your gigabit adapters (or, better, flash their firmware) and this is EXACTLY the solution recommended no less than 8 seperate times in this thread. Please read the symptoms posted on the Gigabyte link (I KNOW you have an ASUS, but you also have a Marvell Yukon 88E8056, which is the "real" problem [other than Intel RAID drivers!])
- x EnterSpace,
I've used Gigabyte firmware to update P5BDeluxe's 8056 LAN. You can find the firmware on Gigabyte site (support-FAQ). Michele from italia wrote: Se poi ci rimetto la rom originale di un amico avrò un MAC clonato, non credo che sia normale, potrebbero verificarsi problemi nella routing table di qualche dispositivo su internet, non credi?
Hello Michele!
I'm very happy for you.
There isn't problem flashing firmware, normally this don't overwrite MAC. But now you are able to overwrite it if necessary... ;)
Yes, it's possible that the original MAC is printed near LAN adpter.
For P5B deluxe users: the 8056 LAN's firmware can be updated with the Gigabyte's LAN firmware. Pay attention to flash the right LAN (the P5B have 2 LAN adapters). Usually the 8056 LAN is reported as LAN1 into bios (then switch off LAN2).
For your information: I didn't get any usefull benefit by flashing the LAN...Hi all
These are the answers I got from Asus and Intel regarding this issue:
Asus: "At the moment from Asus side this motherboard is not Vista supported yet. The hardware is capable of Vista. But the drivers will not be provided by Asus. Atleast not at the moment."
Intel: "The issue you are experiencing has not been duplicated in our labs. Then again, there must be something about your Windows* installation that may be triggering this issue. Since we have not ran into such problem in any of our tests, we would not be able to provide you with a "workaround". ...this motherboard is not manufactured by Intel. Intel(R) will not support a product from a third party manufacturer. Please contact ASUS* for additional information and troubleshooting assistance."
Looks like we are all pretty much scr..wed
- EnterSpace: I have tried with the LAN ports disabled in BIOS and with them enabled but using latest Yukon drivers - to no avail. Soory I left that out of my list.
I have not tried updating the LAN port firmware on my Asus board using Gigabyte firmware - and I'm not sure that I'm game to do it! Have you tried it? Success? - [quote user = Sandokan71]
For your information: I didn't get any usefull benefit by flashing the LAN...
So you haven't solved the problem? You still can't get Vista going with your motherboard and RAID drives?
Thanks. - Any idea what rev this utility takes the Marvell ROM FROM and TO?
According to information on the ASUS BIOS release notes, the Marvell Yukon ROM should already be at 5.17.1.3. I've tried looking in the Gigabyte-provided files to see what the ROM rev will be after running the utility, but I can't see it.
I've been thinking about this all day, and I've had a look at the files. It looks like the updater is not Gigabyte-specific, so I reckon I will have a go at updating the Marvel ROM to see whether this helps me out at all.
I'll keep posting with news/results.
Richard. richardnau wrote: [quote user = Sandokan71]
For your information: I didn't get any usefull benefit by flashing the LAN...
So you haven't solved the problem? You still can't get Vista going with your motherboard and RAID drives?
Thanks.
I think that, actually, there isn't a way to make Vista working on Maxtor DM10 (6V250F0) in raid configuration on a Asus P5B deluxe...
:(
Sandokan71 wrote: richardnau wrote: [quote user = Sandokan71]
For your information: I didn't get any usefull benefit by flashing the LAN...
So you haven't solved the problem? You still can't get Vista going with your motherboard and RAID drives?
Thanks.
I think that, actually, there isn't a way to make Vista working on Maxtor DM10 (6V250F0) in raid configuration on a Asus P5B deluxe...
:(Hi Sandokan71, a solution maybe exists:
1. Install Vista on a single Serial ATA drive (p.e. on secondary gigabyte controller)
2. install last ICH8R driver (all is working fine and vista can read and write form raid hard disk on intel controller)
3. make an image of the SATA hard disk with norton gost (only partition or full disk depending on the case) and write it on the partition of the raid system.
4. Now you can boot from raid controller!!!
I have personally tried to do this and the only problem I did not fixed was related to the label and letter of the unit. Shortly, the copied partition must have the same letter and label of the original one, if not, you have to leave the original hd plugged in becasue the OS still read some files (imho the swap file) from it.
Sorry for my english!
- Sandokan 71 wrote: I think that, actually, there isn't a way to make Vista working on Maxtor DM10 (6V250F0) in raid configuration on a Asus P5B deluxe...
I fear you may be correct! I am growing more frustrated by the day and I don't see any options before me right now.
I have now updated ROM in the Marvell Yukon chip on my Asus P5B Deluxe/WiFi board using the updater from the Gigabyte site (thanks to previous contributors for finding this and suggesting it). I'm pretty confident that it DID update the ROM, because Windows Vista (which I have installed in IDE mode) detected the change and ran through the 'new hardware' process. No problems with MAC address - that side of things all working fine.
Then I- re-installed the RAID drivers for the ICH8R ports (using 'update driver' in the Device Manager)
- rebooted the PC and changed the BIOS configuration from IDE to RAID
- confirmed that the ICH8R could see all the connected drives (using its BIOS display)
- allowed the computer to proceed to reboot.
This is exactly what happened before I updated the ROM. And it's exactly what happened when I first tried to install Vista on the machine: everything looked OK while the first part of the upgrade process went on (hosted by XP), but as soon as the system rebooted to let Vista take over and move on to the next stage of installtion, I got the 'Cylon Eye' and the activity light stuck on. This behaviour was 100% repeatable irrespective of whether I allowed Vista to use its inbuilt Intel drivers or whether I loaded the latest available drivers from the Intel download centre.
So - what do I know?- system worked 100% fine under XP, so there's no fundamental hardware issue
- Vista can work on this mobo/CPU combo, because it works fine in IDE mode
- under RAID (or AHCI, for that matter) mode, things START OFF OK when the system is starting up (or completing installation) -- if it was just a total failure I wouldn't get the Microsoft copyright notice and the 'Cylon Eye', and in the event of a failed restart I wouldn't get the 'system failed to start' options page (which I do).
FYI, I have raised a support request on ASUS, but so far the interaction hasn't been fruitful. I explained in my support request that "Cannot install or load installed Vista O/S when Hard Drives configured for AHCI or RAID."
The ASUS support rep's suggested solution was: "I'm afraid the problem is caused by the Raid driver. Would you please reinstall Vista on the Raid volumn? Please load the Raid driver when you installing OS." Ho hum....
Has anybody (ANYBODY?) had success in finding a solution? As I said above, I reckon I'm out of options, and (IMHO) everything points to the RAID drivers as the thing that needs to be fixed. But there are no forums (that I can find) over on intel.com, and I can't see any sign that they acknowledge the problem or have any schedule to fix it.
Let's keep the dialogue flowing here - maybe someone will stumble upon the magic bullet.
Richard. - re-installed the RAID drivers for the ICH8R ports (using 'update driver' in the Device Manager)
Michele from italia wrote: Sandokan71 wrote: richardnau wrote: [quote user = Sandokan71]
For your information: I didn't get any usefull benefit by flashing the LAN...
So you haven't solved the problem? You still can't get Vista going with your motherboard and RAID drives?
Thanks.
I think that, actually, there isn't a way to make Vista working on Maxtor DM10 (6V250F0) in raid configuration on a Asus P5B deluxe...
:(Hi Sandokan71, a solution maybe exists:
1. Install Vista on a single Serial ATA drive (p.e. on secondary gigabyte controller)
2. install last ICH8R driver (all is working fine and vista can read and write form raid hard disk on intel controller)
3. make an image of the SATA hard disk with norton gost (only partition or full disk depending on the case) and write it on the partition of the raid system.
4. Now you can boot from raid controller!!!
I have personally tried to do this and the only problem I did not fixed was related to the label and letter of the unit. Shortly, the copied partition must have the same letter and label of the original one, if not, you have to leave the original hd plugged in becasue the OS still read some files (imho the swap file) from it.
Sorry for my english!
Hi Michele, I could confirm that your solution actually work =) Thanks!!!
I finally able to get my vista work on the ICH8R with raid. I guess this is the only possible solution for many of us to get Vista work on the ICH8R now. I have tried many possible way to clean install Vista on the ICH8R with raid/ahci enable, however, neither of them work successfully.
- Francis, Michele,
Thanks for telling us about your experiences.
Isn't what you've done basically the same as installing Vista with the system set to IDE mode (in BIOS), then loading RAID drivers, restarting and setting board to RAID mode?
If I understand your process correctly, you:
1. Install Vista on a SATA drive in IDE mode (on another controller)
2. Load the RAID drivers (but don't restart!)
3. Ghost this config (now with RAID drivers) onto a RAID array
4. Restart from the RAID array.
Did I get that right?
The process I've seen written up on the ASUS website (and which I've tried without success) is as I said in one of my earlier posts:
1. Load Vista on a drive in IDE mode (using a drive on the ICH8R controller)
2. Update the driver to RAID (the new driver won't be loaded until restart)
3. Shut down
4. Upon restart, enter motherboard's 'setup' mode
5. Reconfigure the drive dfor RAID mode (not IDE)
6. It should all now start up OK.
This latter process is discussed in this thread: http://vip.asus.com/forum/view.aspx?SLanguage=en-us&id=20070213235101731&board_id=1&model=P5B%20Deluxe&page=2&count=23.
By the way, I tried this and no luck at all.
I'm going to try starting again with some WD drives. If it works, I'll move the Maxtor's into my home server PC for added backup storage.
Richard. Hi Richard,
What i did is to install vista on IDE mode, install the lastest Intel Matrix Storage, and the chipset inf. The next process is to backup the entire partition with Norton Ghost or True image. After that reconfig with the Raid setup again, and run the Norton Ghost or True Image with a CD, and recover with the backup partition. Make sure you recover on the same drive letter that you backup for. Actually the current Intel raid driver run fine on Vista, I just don't get why I won't able to do a clean install with Raid/Ahci. I hope this might help out =)
Well, just incase I will show you my steps here
1) unplug all the hard disk drives, just leave one and have it run on IDE mode.
2) install Vista
3) after finished install Vista, install the lastest Matrix Storage, and Chipset Inf.
4) backup the entire partition with backup utilities and create a recovery CD ( Norton Ghost or True Image)
5) Plug in all the drives again and re setup with Raid config
6) Run the recovery CD and recover the partition on the Raid array drive.
ps. if you plan you format the Raid array drive before the recovery, make sure you don't create partition or format drive with True image. True image have some problems with formatting and creating partition with Raid array.
Francis
Grande Michele! Funziona!
Great Michele! It works!
I hope that Microsoft and Intel will find a final solution to avoid all these steps...
- EnterSpace: the latest P5B Deluxe Wifi BIOS (1004) has Intel Option ROM 6.1.0.1002.
Richard. - Francis,
Thanks for the detailed instructions. I don't have Ghost, and the trialware version won't install on my Vista PC (it says the trial has already expired) so I can't try your process at this time. A couple of questions:
1) Are you using a Gigabyte or Asus motherboard?
2) When you installed Vista in IDE mode, did you do that on an ICH8R port in IDE mode, or on some other controller?
3) Did you use Ghost or TrueImage? Which version?
4) Is it necessary to format the RAID array before the recovery process? If I use two brand new (unformatted) drives, will the recovery process format them? If it's necessary to format first, then I guess the array will have a different drive letter... Can the drive letter be changed during the recovery process?
Thanks for your help.
FYI, I had read on a number of forums that the problem is related to Maxtor drives. I tried a clean Vista install on WD drives (brand new drives set up as RAID 1 in BIOS) and got EXACTLY the same problem again. After the Windows installer loads files for a few seconds (the white bar crosses the screen), then the green 'Cylon Eye' appears, the hard drive LED comes on solid and nothing further happens. So I guess it's not a Maxtor problem... - UPDATE...
I had a couple of spare hours, so I tried Francis' suggestion:
1) Downloaded the TrueImage trialware and installed (much easier to install than Ghost, which produced several Windows Vista errors). I made a TrueImage Restore CD (CD that can boot the PC without any other OS, and then move things around from drive to drive).
2) Installed a pair of new SATA drives and had Windows format them (so that TrueImage would not need to do that - heeding Francis' warning: "True image have some problems with formatting and creating partition with Raid array.").
3) Set a system restore point so that, in the event of failure, I'd have soething to come back to.
4) Updated the drivers for the ICH8R controllers (using the iastor driver from the latest Intel download).
4) Made a TrueImage image of the Vista C: onto another HDD on the system (I have a lot of drives).
5) Shut down the computer and reset the HDD mode to RAID in BIOS. I made sure that the two empty drives that would be target of my TrueImage Restore were visible through the RAID setup screen and that they were set up in a RAID 1 array -- all OK.
6) Rebooted the computer using the TrueImage restore CD that I made in step 1. It rebooted fine. I selected the image I made in step 4 and asked TrueImage to restore that image onto the RAID 1 array that had been set up. TrueImage found the array fine and clunked away for 12 minutes restoring the image.
7) I shut down the computer and took out the TrueImage Restore CD so that the next boot would be from the RAID array.
8) The system started to boot up... and... the disc clunked away... and... the Microsft copyright notice appeared (so Vista was able to at least start reading from the drive)... and the 'Cylon Eye' appeared... and the HDD activity LED came on and stayed on and nothing more happened.
So that's it folks, I've tried EVERYTHING that I can find. I tried:
a) disabling the LAN chip in BIOS
b) loading new LAN ROM
c) updating drivers and rebooting onto same HDD (after changing ROM setting)
d) re-installing from scratch on a pair of new HDDs
e) updating drivers and booting onto a 'restored' image (on a pair of new HDDs).
I don't think I've missed anything from the recommendations in the forum. And I am no further advanced than I was a week ago.
I guess that some (many) have already come to the conclusion that nothing but new Intel RAID drivers will fix this problem. After much trial and no progress and can only say that I am in full agreement!
Does anybody see any sign of new drivers? Hi!
richardnau,
try these steps:
1) Set JMicron controller in AHCI mode, and Intel controller in RAID mode into BIOS then attach one HD to JMicron and start Windows setup from DVD
2) When driver load button appear load JMicron 1.17.11 drivers (you can find this drivers on Micron site). Don't load other drivers.
3) After Vista setup: install Intel Chipset INF 8.1.1.1010 and then Intel Matrix Storage 6.2.1.1002 (reboot after each step).
4) Make a image clone of the disk with a tool like Acronis True Image 10 and restore the image on the 2 HD connected to Intel RAID controller
This works on my ASUS P5B Deluxe and a couple of Maxtor DM10.
Bye!
- Does anyone have a timeline as to when these drivers will become available from either Intel or ASUS?
Intel does not at all acknowledge the problem and claim that the fault lies with Asus so from them I dont think we can expect anything.
Asus acknowledges that the motherboard does not officially support Vista but also claim that Intels drivers should work and therefore don't prioritize doing any additional work.
So my guess is never...
- If ASUS tells you that the P5B Deluxe (or P5B Deluxe Wifi/AP) does not support or is not supported by Vista, ARGUE. They are both listed on ASUS' Vista compatibility list, here: http://www.asus.com/products1.aspx?l1=3&l2=0&l3=0&modelmenu=0&share=txt/11
Let's keep pressing ASUS for a solution. I am afraid that arguing won't help as I am using the P5WD2-E Premium board that the thread intially started off discussing... Then some thread hijackers came along and clouded the issue a bit :)
- The swine!
It's probably pretty cold comfort that even if your board IS on the 'supported list', the problem can still exist. On your behalf I'm hopeful that IF a solution arrives for the P5B Dlx brigade, it will work for you, too.
I am working through a (painfully slow) dialogue with Asus at present. So far no useful suggestions - just 'have you got another version of Vista you can try?'
R. What we can hope for is that the problem actually lies within the Intel controller and that they due to problems with other (vista supported ASUS-boards) will be forced to release a new set of driver
Talking to Asus is like talking to a brick wall. Especially the nordic support who seems to be very disconnected from the movers and shakers in Taiwan.
- I have been in contact with Dell Technical Support regarding this issue on my Dimension 9200. They were apparently unaware of this issue ocurring and at first got me to run a series of drive tests. When all these passed they got back to me suggesting getting the latest version of the Intel Matrix Storage Manager. I'm not sure if that was through my suggestion, or through their own research. Having informed them that I had already got the latest version they now acknowledge the issue to be "compatibility between Vista and Raid", and are offering me a system swap to a non Raid enabled configuration.
Obviously, it'll be quicker and easier for me to format the drives and re-install Vista in a non-RAID configuration. I just don't know how much longer I'm willing to wait for an updated driver from Intel... - I guess that we can hope that Dell carries some more clout with Intel than we do:)
- I call BS on Dell Technical Support not being aware of the problem. Have you read this, there might be some suggestions there:
http://www.dellcommunity.com/supportforums/board/message?board.id=dim_harddrive&thread.id=124682 You're all heroes.
I just stumbled over this problem at the weekend and it scares me that some of you have been waiting around for months for a solution. Clearly Asus have a lot to answer for in suggesting the P5b deluxe Wifi-AP board is Vista ready but Intel's apparent indifference to the end user is by far more reprehensible.
My experience is that I got 32 bit to work albeit sporadically and 64 bit install basically outstares you no matter how many hours you spend trying. Raid 0 with a Sata DVD as well.
You guys are wasting your time trying to find work arounds for this. I had Vista running for 2 weeks on my ICH8R 965WH board in a RAID 1 configuration. The problems were:
1. Performance was horrible, the system would hang during shutdown for several minutes,it would take 10 seconds+ just to open a folder, system restore inexplicably stopped working
2. After 2 weeks the volume became corrupt (chkdsk errors) and I did loose some data because of it and
3. It was a pain to get it to install and boot in the first place. Not worth sharing my method because of 1 and 2 above.
This wan't a fluke either, because I reinstalled Vista again and had the same issues for another week. Even if you get it to install and boot you are not out of the blue. I thought it was just because of Vista that everything was so slow, then I reinstalled and left the BIOS in legacy IDE mode and everthing was as responsive as XP. If you are installing RAID it is because you want data protection or a performance improvement. The current ICH RAID drivers under Vista will give you neither.
The only thing to do is make a lot of noise about this. The only way for customer support issues at huge tech companies to get escalated is for there to be a very high call volume.
- Hi guys,
I'm following this thread for some while now, because I have the same problem on the Asus P5B-E Plus (iaStor0 did not respond within time limit) on Vista 64bit
I contacted Intel about this problem, but they keep responding with "We cannot replicate the problem". With other words, its my problem, not intels.
Now I have opened a case with Asus... They still need to respond, but I will keep you posted on my progress...
In the meanwhile, lets stick together, and keep this thread rolling. Everytime I contact asus or intel, I'll add a link to this thread, to show that I'm not the only one with this problem.
Regards,
Roy - Have Intel confirmed that they have tried to replicate the problem with the same motherboard you are using? I guess not. When I asked that question the support person got very defensive and said that they dont support 3rd party products (ie the asus motherboard) and that I need to contact Asus for further help. Perhaps Intel should realize that in this case they are in fact the third party and their stuff don't work...
I agree, i'm hoping everyone has at least logged a detailed fault message with Intel. The link is http://supportmail.intel.com/scripts-emf/welcome.aspx?id=40,1090,2101 for "Email Technical Support". Family = "Chipsests", Line = "Chipset Software" and Product = "Intel(R) Matrix Storage Manager".
They ask for every possible detail which makes it impossible for them NOT to replicate the problem. I just wish they'd sent me a response or even just a confirmation that my request was acknowledged.
I have no doubt Intel are aware the problem exists but (at the risk of sounding overly dramatic) they should at least have the courtesy of informing us of the resolution status and far more importantly: any relevant timeline. I love my motherboard but (hate to say it) would have made a different purchase last weekend, had I known.
- I have reported to Asus and Intel.
After three replies from Asus with no significant help, the last reply says that they 'have arranged particular test'. The email is copied to someone in Romania (presumably an outsourced support engineer). Maybe this is a good sign.
I have also reported to Intel. So far all I have is a boilerplate 'we will respond as soon as possible' note.
Nothing is fixed yet, but I agree that the main weapon we have seems to be to make sure the companies are aware of the widespread nature of the problem. I have no doubt it will be a tricky problem to solve - when only a proportion of apparently similar systms are impacted, it CAN be difficult to reliably reproduce the symptoms in a lab. VISTA installed successfully on ICH7R SATA RAID
Finally, I successfully installed Vista on my P5WD2-Premium i955x on a SATA RAID10 partition on ICH7R.
Thats what I did:
- I updated the BIOS with version 0802 beta from:
http://support.asus.com/download/download.aspx?SLanguage=en-us&model=P5WD2%20Premium
(it's not listed on the "map" tab, go to the BIOS tab) - I disabled the Marvell Yukon Network Interface in the BIOS
- I prepared an Intel ICH7R RAID driver disk from:
http://downloadcenter.intel.com/scripts-df-external/Detail_Desc.aspx?agr=N&DwnldId=12150&lang=eng
selecting 955x chipset and Vista OS, then downloading f6flpy32.zip - I ran Vista Setup from Win XP SP2 on the RAID with dynamic update option enabled and chose "New installation"
- During setup, when asked for the installation location, I selected "Load driver" and loaded the RAID driver from the disk
- Then I chose a freshly formatted empty NTFS partition on the RAID drive as the installation location
- Vista installed successfully, with one bluescreen during second phase, but completing after another reboot
On my previous attempts, Vista setup never came up after the first reboot! So this is a great success for me.
There are still some other issues, but thats another story...
- I updated the BIOS with version 0802 beta from:
I would happly lend them my mobo if they just agreed to take the issue seriously:)
- For those who are interested, I've created a small page listing various places on the web where this issue is being discussed:
http://www.flyingnerd.com/intel-raid-problem-under-windows-vista/. Here's another workaround that I found to work on my setup.
Install Vista on a Single SATA drive in RAID-ready configuration. Boot into XP and migrate Raid-Ready config to desired RAID (I upgraded to RAID 0 in my config). This config worked for me but started to hang until I updated the OOB RAID drivers to the latest 6.2.1 drivers dloaded from Intel's site.
Obviously this is limited workaround on specific configs.
After successfully installing Vista on a RAID partition on Asus P5WD2 Premium, and after some Windows updates got installed, my harddrive got completely corrupted.
It may be after the ATK0110 ACPI UTILITY update, but I am not sure. Has anybody seen similar things and is also suspecting that ACPI thing?
- Response from Intel:
There are no driver updates coming up that we know of. However, we tested this RAID controller under Windows Vista* and we have not ran into any issues whatsoever. Then again, we followed the process I detailed previously and the driver does not crash.
At this point we can only recommend that you check again the integration of the systems and contact ASUS*, the motherboards manufacturer, for additional information and troubleshooting assistance.Anybody else get a response?
I have similar responses:
First:
"The issue you are experiencing has not been duplicated in our labs. Then again, there must be something about your Windows* installation that may be triggering this issue. Since we have not ran into such problem in any of our tests, we would not be able to provide you with a "workaround"."
Then after pointing out that others have the same problem (and not only with Asus motherboards):
"You may not be the only one, however, this motherboard is not manufactured by Intel. Intel(R) will not support a product from a third party manufacturer."
And then after sending a link to the various forums describing the problems:
"We at Intel appreciate your feedback in this matter. Thank you for taking the time to communicate this issue to us."
And then finally after sending yet another link and expressing a wish that Intel would help out and perhaps communicate with the motherboard manufacturers to solve the problem:
"" (nothing)
Perhaps it is worthwhile CC'ing ASUS and Microsoft in all emails to Intel, and vice versa for emails to Microsoft and ASUS? They can't all point fingers at each other.
I too am having the same issue with Asus P5B Deluxe. Errors came every 2 minutes, to the second, when I was using the computer, and otherwise every 7 minutes of 15 minutes when the computer was idle. I finally gave in and re-installed the SATA drives in IDE compatibility mode.
I, too, confirm the problem with RAID 1 (mirroring) on my ABIT AW8-MAX with Vista Ultimate x64. Same story as so many others: difficulty installing Vista, other random problems after Vista is installed (such as the inability to install Microsoft Office 2007), and certainly multiple file system corruption events reported by a manually-requsted chkdsk of my RAID volume during the next boot. The file system seems most corruptable under heavy disk activity, such as a RAID rebuild while attempting large file transfers, or hibernating the system to a RAID 1 partition.
I've tried everything listed in this forum that others suggested, and I've come to the conclusion that the Intel RAID drivers are faulty. No other changes I make have any significant impact on preventing the file system corruption.
The only thing I can't rule out is a possible mismatch, or incompatibility, between my motherboard's BIOS (and thus the Intel RAID ROM code), and the current Intel Matrix RAID drivers for Vista x64. However, the same BIOS level was successfully used with Windows XP Professional and Intel's Matrix RAID drivers for XP.
I have a working solution that I'd like to share with my fellow sufferers: I purchase a HighPoint RocketRAID 2300 PCI-e SATA RAID controller, and switched my Western Digital and Seagate harddrives from the Intel ICH7R to the RocketRAID controller. Now I have full performance, and what my tests show to be reliable RAID 1 volumes.
I further recommend you take this oppertunity to stop buying--and if possible, stop using--any Intel storage controllers. Like Intel's abysmally slow graphics controllers, Intel's history of making decent harddisk controller and associated drivers is pretty poor. I've had one bad experience after another with their storage controllers over the years. Remember the Intel DMA-enabling drivers for Windows 98 and Windows 2000? Several versions were busted, and resulted in data loss. And how about the hardware DMA support that had to be disabled in BIOS on some systems because it, too, resulted in data loss unless it was disabled. I also remember a misable experience with the Intel Application Accelerator driver a few years ago: we had just finished getting several workstation ready to go and one of the last steps (after installing the Intel Application Accelerator) was to convert the system disk from a Basic to a Dynamic disk under Windows XP. Each workstation then became unbootable--we had to reinstall Windows XP and all the applications again from scratch. This time, however, we skipped install the Intel Application Accelerator, performed the upgrade to Dynamic disks successfully, and everything was fine.
Hey, why not go further? Stop using any motherboards with Intel support chipsets! That way, you can select a new motherboard that uses another marker's support chipset that includes support for hardware RAID--including working Vista drivers. And why stop there? If you give up using anything from Intel--including processors--you can get compelete motherboard solutions that don't have any busted Intel hardware, nor depend on Intel to develop and deliver a single working driver!
I see DELL now sells AMD-based systems; I wonder if a RAID 1 solution is available from DELL using one of their AMD-based workstations?
Intel's attempt to hide from this problem may not be what we want to hear, but we should listen to what is says. The message is load and clear to me: don't bother us, don't count on us, don't trust us, and certainly don't buy or use any Intel products.
I have been in contact with Intel CS about the RAID issues I am having with my 965WH Intel Desktop board. They have told me to try new harddisks (I am using two Samsung Spinpoint 400GB drives) and if the new hard disks also have the same problem they will RMA my board. The rep said they do not have a list of disks that had been validated against the raid controller, and no known incompatibilities with Samsung drives. 500Gig drives have dropped to a lower price/gig than the 400 Gig drives so I may switch to some WD drives anyway. I am really skeptical that it is a hardware problem, but it's worth a shot. If the board is really defective I want to get it replaced.
I have lost enthusiasm for my plans to set up a RAID 5 on Intel Matrix, because of the problems I have run into, and with the 4 disk max RAID 5 config you lose 25% of your storage capacity. A Linux or Solaris Samba file server with software RAID is sounding a lot more attractive.
- After following a suggestion posted on another forum I seem to have overcome the problem...
As posted earlier I have a Dell Dimension 9200, pre-installed with Vista Home Premium and running RAID striped, along with one DVD-ROM and one DVD-RW drive.
Reading the thread on http://www.dellcommunity.com/supportforums/board/message?board.id=dim_harddrive&thread.id=124682
from other people with the same computer and same problems I have experienced, I moved the two DVD drives from ports 2&3 to 4&5.... two hours video watching later I've not had a freeze or any Event Log errors. I previously have been getting one at least every half hour.
I have no idea how or why, but am interested if this solves the issue for other people, and also if it only occurs with two DVD drives. - I am using The mother board (gigabyte p965-dq6)but cant seem to get it working with all of the previous suggestions. The problem I keep running into is that I am using all six of the sata ports of the ich8r and it seems to always drop the number 2 disk (numbered 0 thru 5). while in vista it will claim this disk is not available and the raid is degraded but if I revert back to xp I can now see the drive but have to rebuild the raid (which takes hours). --- Any Suggestions?
TIA -- Bob For me on P5WD2 Premium (955x), the solution was to install newest intel tekoa driver and keep marvell yukon disabled. Then I never installed the "important" ATK - system - ATK0110 ACPI UTILITY update!
It's running stable on ICH7R RAID10 now for more than 8 hours. Event my Hauppauge PCR350 is working out of the box, except that I cannot choose the composite input where my stream input comes from :-(
@sipuncher: Having one DVD and one DVD-RW on primary ide controller. No troubles about this.
Please inform me, if the ATK0110 ACPI update fix (NOT to update it) has some impact for you!
See ya
here is the thread for the same Intel RAID issues for the XPS 410
- I may be finding my way out of the woods. I'm not certain yet - I need to do more tests - and I won't be able to do the tests until Thursday (Australian time). In the mean time, here's some information that may prove useful...
Quick summary of my situation (on ASUS P5B Deluxe Wifi motherboard):- unable to install Vista onto existing RAID array as upgrade from WinXP (installation fails at first restart with 'Cylon Eye' and HDD activity LED stuck on)
- unable to install Vista onto a brand new (including brand new drives) RAID array 'from scratch' (installaton fails early on with same symptom as above)
- CAN install Vista onto HDDs in IDE mode (set in BIOS), but CANNOT sunsequently transition to RAID mode (same failure mode as above).
http://tinyurl.com/37c46o
In short, the article says that there may be problems installing Vista IF the target system has multiple drives with more than one logical partition. The article suggests that if Vista finds a logical partition on a higher-number HDD, then Vista may start installing its code into that partition, and then finish installing in the place you asked it to go. The end result is that Vista won't run!
I discounted this article as NONE of my physical HDDs or RAID arrays has more than one logical partition. I built my own system, and I've never put anything other than ONE partition on any physical device. I have none of those 'hidden' recovery partitions so beloved of vendors like Dell.
A trip into the Disk Management plug-in (Computer Management/Storage/Disk Management) from the Control Panel opened my eyes. My C: had a small (13MB) partition on it that I never put there. (This is in my Vista system running in IDE mode.)
How did it get there? I have no idea.
I Googled words like 'Vista partition problem' and found my way to the following Microsoft KnowledgeBase article:
http://support.microsoft.com/kb/928230/en-us
The article explains the reasons behind the error message: Error: uncaught exception: (failed UI_ASSERT).
I've never seen that error message.
But I was drawn to the listed causes:This problem occurs if the following conditions are true:- The hard disk on which you want to install Windows Vista has many partition entries in the partition table.
- All the partition entries point to the same byte offset location.
I noodled around with the two articles mentioned above, neither of which seems to completely describe my problem, and decided to try an experiment. Here's what I did:- Disconnected EVERY hard drive in my system - physically pulled out the SATA plugs.
- Connected two new HDDs to the system (SATA 1 and SATA 2 connectors on my board).
- Set the IDE mode in BIOS to RAID.
- Set up a RAID 1 array using the Intel Option ROM utility (Ctrl+I before system loads).
- Commenced installation of Vista from DVD.
- Shook my head in disbelief when it didn't fail within the first 30 seconds (I previously tried all the above steps EXCEPT step 1, and every time Vista would fail to install).
- Installed the latest Intel driver when offered the opportunity.
- Per the KB article, I pressed Shift+F10 at the point when the installer asks for the key code.
- Per the KB article, I ran 'diskpart' and ran the 'clean' utility.
- Per the KB article, I exited diskpart and carried on with the rest of the installation.
It restarted when needed during the installation process, and didn't get stuck at the 'Cylon Eye' stage. I was able to restart after the installation, again with no problems.
So, what was different?- In previous installation attempts, I had not disconnected ALL my other HDDs. (I did disconnect the other drives I use in RAID mode, but I had left my non-RAID drives connected to the ICH8R controller.) Making this change seemed to allow the installer to proceed past its previous early failure point.
- I ran the 'diskpart' utility to ensure that any logical partitions present on the RAID array were removed.
- I was pressed for time last night, and I have not tried to run Vista with my other drives reconnected.
- Likewise, I haven't had the opportunity to run over an extended period to check for any other errors or slowdowns.
As to the cause of the problem: I'm not sure.
It looks like the Vista installer has - for some reason or other - created a small and unwanted partition on the target HDD. It further looks like Vista installs part of itself into this partition or in some other way messes up the place that the computer looks when it comes time to start up.
It looks like this peculiar behaviour is triggered by the presence of other HDDs in the system. Dont know why.
I have no idea why the system reacts differently in RAID mode compared to IDE mode - the unwanted partition is clearly present in IDE mode as well, but its presence doesn't seem to have the same fatal results. Maybe a HDD file system engineer can explain that.
I don't see any reason to believe that this 'workaround' will help out the folks suffering from 'Stop Errors' or slowdowns. I SUSPECT these are caused by a different problem.
And I now don't know who 'owns' this problem - is it something in the Intel RAID driver that causes the Vista installer to have an apoplexy, or is it just a dumb installer?
As ever, your mileage may vary. If your problem is similar to mine (see the top of this post), this approach may be worth a try. I'll report back after more extensive testing on Thursday.
Please post your results if you try any of the above. This is the answer I got from Intel customer service:
The issue you are experiencing has not been duplicated nor has it been reported by other customers. From our side, we can only recommend that you contact the motherboard integrator, in this case ASUS*, for additional information and troubleshooting assistance.
Then I replied with a link to this thread. Thats the next answer I got:
We regret to inform you, the issue you are experiencing seem software related. Please contact your software developer for additional information and troubleshooting assistance.
They didn't even look throu the thread, I am sure. I find this very arrogant of Intel. I might consider bying less Intel connected hardware in the future :)
My installation is still running stable with disabled Marvel LAN, but I have very poor read performance on the Intel LAN interface on my P5WD2 Premium... (only about 2 MB/s)
@richardnau: Vista uses some kind of installation image to speed up the installation process. This might be the reason for the additional partition you found.
I guess it's creating it during the first phase and then tries to boot from it during the second phase. I had about 6 logical drives spread over one RAID 0 volume and one RAID 5 volume during my first tries (without any additional drives except my 4 raid drives connected).
After I rearranged to one RAID10 volume with only 3 logical drives I had a success in the first time. Although I got data corruption afterwards. But disabling the Marvell Yukon seems to work so far. What board are you using?
- Rodge asked: What board are you using?
P5B Deluxe Wifi
Same here!
I have a Dell 9200 Dimension running Vista home prem. It has 2 x 250Gb HDD's setup as RAID0. I was getting all the same errors as above i.e. “The device, \Device\Ide\iaStor0, did not respond within the timeout period.”. The whole system used to completely freeze for around 30 seconds.
This was brand new in the beginning of Feb. The fault was logged on the 1st day of receipt! Still Dell cannot advise on a fix.
I decided to try things myself. I rebuilt the disks using RAID1 & re-installed the OS. Added all the usual updates. Would you beleive it, no more freezes...
There must be a RAID0 issue with Vista...
The most annoying issue I have is that I have supplied this fix to Dell... They are a multi-million company that must be employing useless engineers if they cant find this problem! All along they where pointing the finger at me, saying I had installed software or new hardware!
Watch this space !!
@Richardnau
Many thanks for all your hard work here. I am also indebted to Sandokan71, Michele form Italia & Francis Wong. After following this thread since late last year, I have finally managed to get Vista booting from a RAID 0 volume on the ICHR controller using Intel Matrix Manager.
The steps largely followed the advice from Sandokan71 and Michele in relation to my P5B deluxe board:
1. Set Jmicron controller to AHCI and Intel controller to RAID in BIOS
2. Attach one only SATA HDD to the Jmicron port and start to load Vista from DVD
3. During instal Load JMicron driver ( 1.17.11) and allocate a 15Gb primary partition for the Vista installation
4. After installation, load latest Intel chipset (8.1.1.1010) and reboot
5. Then load latest Intel Matrix Manager (6.2.1.1002) and reboot. Then close down again.
6. Attach a pair of clean SATA HDD disks to ports 1 & 2 on the Intel controller and ensure that the boot sequence in BIOS is still set to the Jmicron attached drive
7 Fire up Vista again on the Jmicron attached HDD and run the Intel Matrix Manager Console to set up a RAID 0 (or 1) volume on the array of two SATA HDDs.
8.Close down and then reboot using an Acronis boot CD to load Home safe True Image. Select Clone disk ( not backup copy) and set the source as the Jmicron attached HDD and the destination as the Intel attached RAID Volume. After approx half an hour, the cloning is completed.
9. Close down, disconnect the Jmicron attached HDD and enter BIOS to ensure the boot sequence is set for the RAID Volume. Reboot and voila Vista successfully loads from RAID for the first time since trying 4 months ago!
So thanks to all for your help. I am now looking into whether I can get a dual boot of XP & Vista to work under this RAID scenario, but my first attempt this morning failed when, having selected Vista, it would not load as it was seeking the file "winload". It would appear that the pointers are not set correctly. More reading to do!
- Fellow sufferers,
How to condense six hours of Vista-wrangling into just a few lines?
Let's see... it's something to do with Maxtor DiamondMax 10 drives!
That's not the answer I expected or hoped for.
The story...
You will have read above that after many unsuccesful attempts at installingVista onto a RAID 1 array while other HDDs were connected to the ICH8R, I finally got it done onto an array of 2 x WD drives (WD3200KS) when no other drives were connected.
Now, I didn't really want to use these WD drives as C: - I wanted to use some of my Maxtors. So, having proven that I COULD install Vista onto a RAID array, I set out to do the same thing onto an array made up of Maxtors (6V200E0) using the technique described in my last post.
Well, it installed, but things didn't go the same way as with the WD drives.
First, there was some sort of funny reboot during the first installation attempt.
Then, I thought it had stalled on the 'Cylon Eye' - but after a couple of minutes things came back to life again.
Then, when it came to 'diskpart', the 'clean' utility couldn't see the array at all. (I have, through this process and my own stupidity, somehow managed to reformat and apparently ruin my USB memory stick that I was using as a source for the RAID drivers -- but that's another story.)
The installation DID complete onto the Maxtor array, but it was S-L-O-W and every time the computer restarted, the 'Cylon Eye' made a lengthy appearance.
When I checked the Windows error logs, I found dozens of iastor errors (iastor not responding). I guess this is what caused the slowness during the installation process and when Vista finally installed on the Maxtor array.
I certainly couldn't live with that, so I went back to the WDs. I reinstalled them in the PC (no other drives connected) and ran the Vista installation process. It went though quickly and painlessly.
I checked the WIndows error logs - no iastor errors. I spent an hour installing stuff and checked the logs again. Still nothing.
OK, so this was looking hopeful. Time to reintroduce the RAID array for my document storage. I hooked a couple of Maxtors up to the ICH8R, configured them into a RAID 1 array in the BOOT ROM utility and started up. What's this? Cylon eye appeared for ages. System ran as slowly as a wet week. Heaps of iastor errors. This is no good at all.
Time for an experiment. Disconnected the Maxtor RAID array and connected up a Samsung drive in non-RAID config (on the ICH8R) - still using the WD array as C:. All systems go. Fast, smooth and no iastor errors.
Next part of the expirement: connected up a Maxtor drive in non-RAID mode (a different drive - not one that had ever een part of a RAID set). S-L-O-W again, and many, many iastor errors.
It was certainly starting to look like the system was interacting in some way with the Maxtor drives.
Time to bite the bullet. Off to the PC store to buy a pair of Samsung 400GB drives (HD401LJ). Connected these to the PC and configured into a RAID 1 array (no Maxtors connected). Bingo! RAID array visible to Vista. Fast startup. Fast operation. No iastor errors - not even one!
At this point, definitive conclusions are difficult -- especially since lots of folk seem to have problems with other brands of drives. For me, it seems that:- if there are Maxtor drives (6V200E0) connected to a RAID-enabled system (other than as C:), then something bad happens, and Vista messes up its installation -- I could NEVER get a working installation on ANY RAID array if there was a Maxtor connected in the box (to the ICH8R)
- if Vista is installed on a Maxtor-based RAID array, the installation will be unreliable and slow
- if
Vista is installed on a non-Maxtor RAID array, and a Maxtor drive is
subsequently connected to the ICH8R, then everything turns to mush
(that's a technical term)
- if I take all the Maxtors out of the system, Vista installs and runs like a dream
- WD and Samsung drives SEEM to be OK; I steered away from Seagate, not knowing how much of the technology is shared with Maxtor (my supplier swears blind that the 6V200E0 Maxtors are nothing more than rebadged Seagates).
So, what's causing the problem? And why didn't it happen under XP? NAd why doesn't it happen in IDE mode under Vista?
I can only conclude that there's some adverse interaction in the way that Vista talks to these drives when the advanced features of AHCI/RAID are enabled. Maybe it's the way the (Intel) drivers work. Maybe it's the way Maxtor implemented NCQ. Maybe lots of things - sorry, but I just don't know!
And just so that I don't sound smug - let me say that I won't condider the problem solved for me until I have several weeks of stable operation under my belt. Stories like DaveT's (last post) scare me. But so far, my Maxtor-free system is looking good. - Hi richarnau!
I'm running Vista on a couple of Maxtor Diamond Max 10 (6V250F0 with VA11190 firmware ) disks in Raid0 without problems. I'm using two Raid0 logical disks. No iastor error appear in event viewer and the performances misured by HDTach 3.0.1.0 are very good (132MB/sec average transfer rate).This appear if Vista is installed with the alternative procedure based on installation cloning (the original one is made on a singular Maxtor disk connected as AHCI on the JM363 controller).
The problems (for my disks) appear using the standard Vista installing procedure.
For some reasons the Vista installer is uncompatible with my Maxtor disks (and with some other else...). Both using enbedded drivers or newer ones. Hi Guys,
I too am using Maxtor SATA HDDs (7V250), which would not allow load of Vista via normal route, only via imaging as posted earlier.
I have managed to image over a dual XP/ Vista set up on to the pair of Maxtors in RAID 0, but then had fun and games trying to get Vista to load from Boot manager. It seems that when I came to clone the donor HDD, there were the two partitions containing the OSs but between them was a very small ( 188kb) unallocated partition - which I had not put there! Needless to say when cloned, only the two partitions came across and the unallocated partition must have been merged with the other unallocated area (approx 200GB). When I ran EasyBCD (1.5.2) , it revealed that the boot manager was pointing to a deleted partition to load the starter file for Vista (winload). Finally, after using EasyBCD to try to rewrite the loader files - which may have worked only in part, I booted from the Vista DVD and - eventually- and after loading the IASTOR file, the installation page appeared following which I selected "repair your computer", which found problems with the MBR and offered to correct them - which it did.
So now I appear to have a fully working dual boot on RAID 0. However, I now need to load up the apps and data on to a proposed second volume in RAID 1 on these Maxtor HDDs. I am apprehensive still, given the flakiness which seems to surround the Maxtor HDDs, although Sandokan71's comments are a little more re-assuring. I need to see how this goes over the next couple of weeks.
Thanks again for sharing your experiences.
- The post about Maxtor being the problem - and Seagate if the drives are the same - sounded promising, since I was using 3x Seagate 7200.10 in a non-boot RAID 5 configuration and they didn't work. However I am talking now to someone with essentially the same build as me, Asus P5B-Deluxe motherboard like me, and a pair of Seagate 7200.10 drives in RAID 0 working perfectly under Vista. Key difference: He is using the earliest BIOS version, that shipped on the motherboard. Otherwise our configs are very very similar. So I don't know what to make of it...
- I also have a p5b-deluxe mother board, having same problems installing vista.. I also this it is maxtor drives as this happens : -
With SATA set to AHCI mode with all my drives connected, i get the eye.
if i set the SATA mode to IDE vista installs fine....
how ever if i disconnect all of my maxtor drives and just leave my WD drive, vista installs in AHCI mode, i only have one none maxtor drive so i can not test raid... but at least i got a ahci install done.
I have the following maxtor drives
Maxtor 6V300F0 x 3
Maxtor 6V200E0 x 1
and a
Western Digital WD5000YS-01MPB0
Hope this helps, and i hope one of the companys ASUS or Intel admit a problem soon Hi, am in a similar situation, al be it, the problems are a bit different.
I have a Seagate 160G Sata II as my boot drive, but have a Maxtor 6B200M0 also on one of the SATA ports, tried SATA port 1 and port 3 (black connector) but seems not to make any difference. When I start Vista the Maxtor shows up and seems fine, but at some point in time I am getting the ioStore timeout errors and the drive is removed from the system by the Intel storage manager (this is indicated in the event log). As far as I can see it happens when OOdefrag tries to run on the MAxtor, so it seems related to hi drive usage as reported before.
Very very annoying. Wondering though if it may be related to the fact that Maxtor is a SATA I drive and running at the same time as a SATA II (my seagate) drive and maybe it is talking to fast to the maxtor for some reason (intel ????)
Maybe someone with a MIX of a SATA II and SATA I drive can confirm this or deny this ....
My Mobo is a ASUS P5B-E plus, E6400 processor and 2 Gigs of corsair XMS2 PC6400 memory. the intel storage drivers are the latest from Intel website. (BIOS : sata is enhanced, AHCI mode)
PS I have a external SATA from maxtor running on the JMICRON and have no probelms with this, also the seagate on SATA port 0 is not showing any problems at all so far (knock on wood)
Something needs to be done, intel, asus, maxtor ??? are you listening
Erick otto
- heavy problem
I tried to install vista final , but not installed!
my driver&bios is up to date!
E6400
GIGABYTE 965P-DQ6
2 GIGA DDR2 800
asus 7600gt
4x Maxtor 6V200E0 (raid 0 with ich8r)
my system working good with windows xp... - NEW TOPIC:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1360061&SiteID=17 Here is my story:
I have (had) a Matrox Diamondmax 10 250GB and a Samsung 400GB. The Matrox was my primary drive, Samsung just for storage. Both connected to ICH8R SATA ports and also a Samsung DVD-RW was connected to the same ports. Jmicron controller is disabled.
I have tried (many many times with different methods) to install Vista with a AHCI enabled P5B Deluxe, no raid in the system, just AHCI. I have Win XP on the first partition and after that a 25GB partition for Vista.
I was not able to install: with Vista's buildin drivers install was very slow, my SATA DVD drive copied the files for hours and after reboot Vista showed blue screen. With Intel "F6" drivers install was fast but reboot always locked in the Cylon eye. With regular IDE mode there were no problems and install was fast.
I also tried to install to the Samsung drive but still the same problems.
And now it gets interesting: I swapped my Matrox to a Samsung 500GB hard drive, cloned/copied all partitions and once again tried to install Vista to the 25GB partition now on the 500GB Samsung hard drive. This time there were no problems, I just selected the partition and installation was quick with the Vista build-in AHCI-driver.
So the Matrox drive caused all these problems and it also causes the SATA DVD drive to slow down. Still I had no problems in XP with the same setup so Vista & Intel drivers are somehow getting confused when there are Matrox drives in the system.
- It might be worth dropping in to this thread on the Asus forums:
http://vip.asus.com/forum/view.aspx?id=20070223061009256&board_id=1&model=P5B+Deluxe%2fWiFi-AP&SLanguage=en-us&page=4
There is corroborating evidence there pointing to a conflict with Maxtor drives.
Also, I tried my Maxtor drives set in SATA150 mode (previously SATA300) - no change: problem persisted. richardnau wrote: I have now received an updated firmware for the Maxtor HDDs
my HDDS firmware is VA111630
what is firmware update for the Maxtor HDDs?richard, glad to read that new firmware seems to have fixed your problem, as it so happens I ran seatools last night on the Maxtor 6B200M0 drive and it ran for 8 hours with about 40 odd errors and still running, I'll be returning the drive for a replacement since I still have warrantee on it, after I get it back i'll see if I am still getting iaStor errors.. seems my newer Maxtor 6V300F0 is not having problems, although I can't be sure of it. I need to keep an eye on the event logs.
From what firmware to what firmware version did the tool upgrade your drives ? and what is the drive type u are using ?
Cheers,
erick
@ Kacang: Regarding SATA-I and SATA-II I have a WD Raptop SATA-I and 3x Seagate 7200.10 SATA-II ... Perhaps SATA-I/SATA-II is the problem.
Otherwise, someone was mentioning that Seagate 7200.10 320Gb drives are similar/identical to Maxtor drives - can anyone confirm this? I am not running a Maxtor, yet I get the same problem, so it can't be Maxtor-related only, unless the Seagates are very similar to the Maxtor drives.
I should also point out another person I know, running Seagate 7200.10 drives in RAID on a P5B-Deluxe, earliest BIOS revision, has no issues whatsoever.
- For those who have asked...
The firmware on my Maxtor drives (which exhibit problems interworking with the ICH8R under Vista) is VA111630.
The replacement firmware supplied by Maxtor is VA111900.
I have not yet tried out the new firmware. It'll be a couple of days before I get to it and, since I now have my system 100% working on non-Maxtor drives, my need is no longer pressing. That said, I now have four spare Maxtor drives and I want to be sure that they are fully working before I on-sell them, so I WILL install the new firmware when I am able. - my 4x Maxtor 6V200E0 firmware updated to VA111900
but no change: problem persisted
problem to be continue...
oh my god Could this forum post have any bearing on the situation?
http://forums.storagereview.net/index.php?showtopic=22435&st=25
People having a problem with 3ware/amcc or any other brand on-board or PCI RAID controllers experiencing infrequent(!) drive timeouts on all drives in combination with Maxline III drives models 7VxxxF0 or DiamondMax 6VxxxF0 should contact Seagate/Maxtor and ask them for a solution in the form of a firmware upgrade VA111680.
Don't even consider upgrading to VA111680 if you are not experiencing any problem. There is no performance gain in doing so.
Just relating to the firmware updates, at least.
- Hmmm... could be a related issue. We're talking about a different (family of) RAID controller(s) and a different OS, but I note that the later firmware upgrade discussed in the thread you linked is the same firmware upgrade I was sent (but haven't yet tried).
I'll be very interested to see how this pans out. - I do not believe this is a Maxtor problem. I have this same problem with a P5B Deluxe WiFi and a single WD Raptor 150GB running in AHCI. Vista installs correctly, but every 2 min it freezes up while the HD is active. I'm shocked that it has been this long with no correction - has anyone convinced ASUS/Intel that this is a real problem?
Again I also have the exact same configuration - P5B Deluxe, WD Raptop 74.4Gb in AHCI (but I also have Seagate drives). So unless the hard drive problems extend beyond Maxtor, I don't think that is a problem either.
Perhaps it is something about the SATA interface? Perhaps all the SATA drives we're having problems with have firmware with AHCI issues? Could it be a problem with NCQ? I am trying to think of a connection between all the drives that we have established to be having problems. The problem sounds like it occurs on both SATA-I and SATA-II, individually or both.
Maybe we should list all affected hardware and try to find a pattern. You know, like detectives trying to find a serial killer. "Find the pattern, and you find your killer"...
- My problems with Vista and RAID involved Maxtor 7V250 drives. However, the firmware is already VA 111900, and so I am not at all confident that the upgrade to be carried out by Richard Nau et al will be successful in eradicating the problem.
Maxtor, aka (Seagate) send me the updated Firmware ( VA111900 ) and it changed sweet nothing!
They now informed me to do the following:
I would like you to try the following and see what happens. Use MaxBlast to 0-fill the drives and then do your install of the OS with setting up the raid and formatting with in the OS. Also what cluster size are you using?
Regards,
Rick B.
Seagate Technical Support: disc.support@seagate.com
I will keep you posted on what happens!
- Update : I haven't received my Maxtor 6B200M0 back so I can't say anything yet, HOWEVER, today trying to overclock just a little on my ASUS P5B-E plus, just from 266 Mhz to 300 Mhz and memory a bit higher with standard set from SPD. Guess what, getting Jmicron errors now as below...
The driver for device \Device\Scsi\JRAID1 detected a port timeout due to prolonged inactivity. All associated busses were reset in an effort to clear the condition.
Wondering if maybe now the PCI bus is going to fast for it to keep up with the MAXTOR 6V300F0 through jmicron.
I am starting to dislike this vista, asus mobo, ICH8, jmicron stuff.
Any suggestions ???
Erick
- Status report:
I used the Seagate/Maxtor process to upload the VA111900 firmware to my 6V200E0 hard drives. There was ABSOLUTELY no change in the way things happen: when I re-introduced the Maxtor drive to the ICH8R controller, Windows Vista was unable to start - frozen on the copyright screen with the 'Cylon Eye' scanning and the HDD activity LED fully on.
I have passed this information to Seagate/Maxtor.
More news as it comes to hand. - By the way - is anyone else being driven to distraction by this forum? To access the last page, I have to go via page 1 then page 5 then page 7 then page 9. Am I doing something wrong? Is there something to click on that will take you straight to the last page?
grumblegrumblegrumble Hi richardnau
Yep, Just add Page 11 to your Favorites and you will go straight to this page! It is a bad Forum design by Microsoft!!
I think we must all put enormous pressure on Intel, Asus and Maxtor/Seagate/WD to fix this major problem ASAP! Vista Final has been out since November 2006!!! We as customers deserve MORE!!!!!
- Thanks, f007. Done that. I thought maybe there was something I was missing. Dumb BBS indeed. Maybe they should run the forum on phpBB!
Lol...Haha.. Mybe!!! I'm shocked that these big companies take so long to fix these problems or deny its existence! I paid allot of Money for Vista and now I can only run it at half speed! Sighhhh...
- Arghh! My RAID array on the 2 Maxtor 7V250 HDDS has just become corrupted. Enough - I am off to get two new WD HDDs. I'll decide what to do with Maxtors when this is eventually(?) sorted out!!
Hi Ray T
Will you be so kind to inform us if the New H-drives make a diff!! ASAP!!!
I think this problem might be caused by a certain Hardware version on Asus Motherboards. That will explain why Asus Support and some other people have no problems and the rest of us (10000000's) want to shoot ourselves and eat our Motherboards!
I think Asus want to prevent a major recall and save Money!! So keep the Pressure ON!!! I e-mail Asus and Maxtor about 3 times a day!
Let’s all hope for a miracle!
Hi
I am experiencing the same RAID-problems with WD320Gb disks. (P5B Deluxe Wifi)
For me the source-problem seems to be related to the intel-drivers, since I had no problems when running Vista RC2.
Some days ago I tried to reinstall RC2 just to check, and it installed successfully when doing a straightforward installation on the RAID1 volume.
But when I tried to install RC2 by loading the 6.2.1.1002 ICH8R intel-drivers during setup, I was unable to install RC2 because of constant HD-activity.....
All, it would probably be good to have a couple of short-cut URL links in this forum which point to intel/asus/jmicron/maxtor/WD/seaget etc where we can file our complaints. Like I said even with a bit of overclocking Jmicron also getting timeouts on my brandnew seagate. I have emails seagate already asking for newer firmware if any is out there.
has anyone ever tried using hi quality sata cables ? I know when I was running ATA133 drives that a coolermaster cable made a big difference in speed at that time compared to the standard asus cables ???
Erick
Contact Details for ICH8 and all Raid Problems:
ASUS:
http://vip.asus.com/eservice/techserv.aspx
or
http://support.asus.com/contact/contact_right.aspx?SLanguage=en-us
Seagate/Maxtor:
WD:
http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/ask.php
Microsoft Prob with WD:
Intel:
http://supportmail.intel.com/scripts-emf/welcome.aspx?id
Or
http://www.intel.com/cd/ids/developer/asmo-na/eng/58987.htm
Microsoft:
http://support.microsoft.com/windowsvista
Best of Luck!!! And Keep Us Posted!!!
A few pages back I posted about the problems I had with my Intel 965WH desktop board (ICH8R) using the Intel Matrix RAID on a pair of Samsung HD400LJ drives. Vista would not install on the RAID 1 array (cylon eye hang), so I installed to a single disk and then used the Intel Matrix Storage Manager to migrate to a RAID 1. Big mistake, as I had numerous hangs when openning folders (20secs), shutting down (5 minutes+), and eventually data corruption which rendered a big chunk of my filesystem unreadable. After emailing Intel customer support they asked me to try setting up the RAID using a differe