Intel Communities: Message List

Re: Server lost power and now RAID is initializing parity

webadmin@intel.com — Thu, 18 Feb 2010 18:24:42 GMT

It depends on the size of your RAID volume, but parity initialization can take a long time. It's going through and recalculating and writing parity for every single strip. You can still access the data during the process, so yes, you should still be able to see everything you would normally see on the volume. I hope your system is back to normal again by now.

Re: Intel WifiLink 4965 AGN Driver's DPC Latencies causing audio glitches in Windows 7 X64 (RTM)

webadmin@intel.com — Thu, 18 Feb 2010 18:16:24 GMT

Hey, folks. I'm going to see if I can move this question over to the wireless support forum, if that's ok, in the hopes that you will get more insight into the issue you noted. The wireless forum is at http://communities.intel.com/community/tech/wireless .

Re: Chipset Identification Utility does not work

webadmin@intel.com — Wed, 03 Feb 2010 20:30:46 GMT

I noticed you're both running 64-bit versions of the OS, and the tool only supports 32-bit versions. That might be it ..

By the way, the utility doesn't list driver versions. If you're looking for specific driver versions, depending on what drivers they are, you might be able to try the Intel(R) Driver Update Utility @ http://www.intel.com/support/detect.htm or the beta for the Intel(R) System Identification Utility @ http://www.intel.com/support/siu_la.htm

Re: Does Rapid Recovery volume do fault tolerance in Continuous Update Mode?

webadmin@intel.com — Wed, 03 Feb 2010 20:16:59 GMT

Hi.

1. Really, it would provide fault tolerance whether you were in continuous update or manual update mode. It just refers to the fact that you have some protection in the event of a single drive failure. In continuous update mode, it behaves a lot like RAID 1, so there should be no need to switch in the recovery drive.

2. Sure, as long as the components support eSATA/hot swap, you could hot swap a member drive from a recovery volume. Personally, I wouldn't hot swap the primary drive, but that's just me ..(That being said, if you were in manual update mode, I don't think you could hot swap the primary drive anyway as it would be the only drive in use. As soon as you pulled it out, there would be no system.)

Re: Matrix Storage Console

webadmin@intel.com — Fri, 22 Jan 2010 21:03:44 GMT

Sorry .. this might be of no use now .. but if you open the console app, (View -> Advanced mode if needed), then right-click on the volume in the device tree, there should be an option to cancel the migration. I think you can also do this by right-clicking on the icon in the system tray.

Re: Intel_Chipset_V9111020_XPVistaWin7 Installer Doesn't Complete

webadmin@intel.com — Fri, 22 Jan 2010 20:54:40 GMT

Hi, Paul.

That's because there's nothing for it to do (though it's actually a really fast install regardless).

This article explains what it does: http://www.intel.com/support/chipsets/inf/sb/CS-030865.htm

From it:

Do I need to install the Intel Chipset Software Installation Utility then?
The best rule of thumb is that, unless you are installing an operating system, you don't need to install the Intel Chipset Software Installation Utility. If you do install the Intel Chipset Software Installation Utility after installing the operating system, and the installation program recognizes that some or all of the product names in Device Manager match the product names in the included INF files, it just won't install those INF files.

In the case of Windows 7, the product names in Device Manager all match the product names in the included INF files, so it doesn't need to do anything.

Sorry .. but if you're running into audio/visual sync issues, the chipset INF is not going to help .. (maybe if you start a thread listing your specific issues, someone can suggest something that might help?)

Re: procedure wise and user interface wise differences

webadmin@intel.com — Fri, 22 Jan 2010 20:41:20 GMT

Ok .. I think there's some confusion .. let me see if I can help ..

1). Yes, it said in the following links briefly that you don't have to use F6 installation for IRST any more. But, does it hold true for XP, Vista, and Win 7 all alike?

http://www.intel.com/support/chipsets/imsm/sb/CS-029980.htm

http://www.intel.com/support/chipsets/imsm/sb/cs-009330.htm

comparing with IMSM procedure:

http://www.intel.com/support/chipsets/imsm/sb/CS-021701.htm

But, is this F6 driver installation method all the procedure-wise difference between IRST and IMSM?

Those 3 links all apply whether you're using Intel(R) Matrix Storage Manager or Intel(R) Rapid Storage Technology. The only thing that changed on those pages was the name of the product. The content is the same.

This is the note you are referring to:

Note: The F6 installation method is not required for Microsoft Windows Vista* or Microsoft Windows 7*.

The text did not change. It refers to the need for the F6 procedure on Windows Vista* or Windows 7*. You do not need to use the F6 installation method to install the RAID driver on those OSes because there is a RAID driver included in the final version of the OS. This was the case when the product was called Intel Matrix Storage Manager. It is the case now that the product is called Intel Rapid Storage Technology.

In other words, the procedure applies to the operating system - it does not matter what version of the product you are using.

Can IMSM or IRST users all bypass Option ROM (i.e., Ctrl + I in BIOS) and just use IMSM/IRST console to create/delete RRT/RAID for the system drive unless they choose Linux RAID? Intel China support has confirmed that. IF THE ANSWER IS TRUE, THEN THE ONLY OBVIOUS PROCEDURE DIFFERENCE IS THE DRIVER INSTALLATION METHOD.

Yes - the option ROM is an entirely different component from the driver/software. You can always bypass it. And again, the procedure is not related to a particular version of the product (for example, version 8.x which is named Intel Matrix Storage Manager of version 9.x which is named Intel Rapid Storage Technology), it is related to the operating system that you are installing.

2) Any feature differences between IMSM and IRST?

There is a new user interface.

Re: Latest P55 Chipset Drivers?

webadmin@intel.com — Fri, 22 Jan 2010 17:26:46 GMT

I'd say yes, install away. Basic reason being, since the INF is not installing a driver, it is the same driver managing those devices before/after INF install.

The only driver I know of that manages those devices is the one included in Windows*. The INF tells the operating system what the device is; that way, if it doesn't recognize it, it then does - and knows what driver to use to manage it. It already knows what those devices are (if it didn't, they'd be listed as unknown), so all is well.

CAT files are different from driver files. They are the files that say whether the files have received a WHQL* logo (a testing/certification process for Windows*).

Very good question on "why is it marked as a driver"! It's one of those "that's how it's always been done" and I guess no one ever thought about whether that was confusing things. I'll look at it and see if there is another option/type that would make it much clearer. Thank you!

Re: Raid 5: Initialize : what is it doing exactly?

webadmin@intel.com — Fri, 22 Jan 2010 00:14:54 GMT

for RAID 5, it's initializing parity for every strip on the RAID 5 volume

Re: IMSC initializes array each boot.

webadmin@intel.com — Fri, 22 Jan 2010 00:10:24 GMT

It's verifying at every startup? Oh, gah, that would drive me batty too.. Verify and repair does run automatically in the latest drivers, but it should only run after a dirty shutdown or if it's initiated by the user. Are these clean shutdowns/reboots? (for example Start -> Reboot -- basically shutdowns/reboots that allow all system activities to complete before the system powers off)