Prev: Installing Hyper-V RTM - "The update does not apply to your sy
Next: unable to backup system state
From: Bruce Sanderson on 19 Jul 2008 16:47
This post is related to the one on 5 Jun 2008, but I think I asked the wrong
question in that one!

The operating system is Windows Server 2008 RTM with the RTM version of the
Hyper-V role installed (Windows6.0-KB950050-x64.msu).

The computer is a custom built with an ASUS P5N-D motherboard, which has the
NVIDIA nForce 750i SLI chipset.

This computer has three SATA drives - two ST3320620AS and one ST3500320AS.
The ST3500320AS has two partitions, one of which is the Windows "System" and
"Boot" partition (hosts the operating system).

If command queuing is enabled on the ST3500320AS, I get frequent System
Event Log entries with Event ID 129 from nvstor64 saying "Reset to device,
\Device\RaidPort0, was issued".

When these Event Log entries are recorded, the system temporarily freezes -
no response to mouse or keyboard, no video updates - everything stops for a
few seconds then carries on as if nothing happened.

Enabling command queuing on either or both of the ST3320620AS drives does
NOT cause this problem.

The ASUS web site says that problems with NCQ has been reported with the
NVIDIA nForce 750i SLI chipset and the solution is to update the firmware in
the drive.

Does anyone know where can I get updated firmware for the ST3500320AS or
have any other clue to resolving this problem?

I've disabled commmand queuing on the ST3500320AS, the system works and I
don't get the Event log entries (Event ID 129 from nvsotr64) or system
freezes, but I suspect this is resulting in degraded disk (and thus system)
performance.

--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



From: Meinolf Weber on 19 Jul 2008 17:10
Hello Bruce,

Well, this question better post better to seagate. If you know it's a firmware
problem, that's there task not MS.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> This post is related to the one on 5 Jun 2008, but I think I asked the
> wrong question in that one!
>
> The operating system is Windows Server 2008 RTM with the RTM version
> of the Hyper-V role installed (Windows6.0-KB950050-x64.msu).
>
> The computer is a custom built with an ASUS P5N-D motherboard, which
> has the NVIDIA nForce 750i SLI chipset.
>
> This computer has three SATA drives - two ST3320620AS and one
> ST3500320AS. The ST3500320AS has two partitions, one of which is the
> Windows "System" and "Boot" partition (hosts the operating system).
>
> If command queuing is enabled on the ST3500320AS, I get frequent
> System Event Log entries with Event ID 129 from nvstor64 saying "Reset
> to device, \Device\RaidPort0, was issued".
>
> When these Event Log entries are recorded, the system temporarily
> freezes - no response to mouse or keyboard, no video updates -
> everything stops for a few seconds then carries on as if nothing
> happened.
>
> Enabling command queuing on either or both of the ST3320620AS drives
> does NOT cause this problem.
>
> The ASUS web site says that problems with NCQ has been reported with
> the NVIDIA nForce 750i SLI chipset and the solution is to update the
> firmware in the drive.
>
> Does anyone know where can I get updated firmware for the ST3500320AS
> or have any other clue to resolving this problem?
>
> I've disabled commmand queuing on the ST3500320AS, the system works
> and I don't get the Event log entries (Event ID 129 from nvsotr64) or
> system freezes, but I suspect this is resulting in degraded disk (and
> thus system) performance.
>
> It is perfectly useless to know the right answer to the wrong
> question.
>


From: Charlie Russel - MVP on 19 Jul 2008 17:11
GIYF.

http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw

First hit on: ST3320320AS firmware site:seagate.com

In general, firmware updates are only available directly from the OEM
involved. So, for the Seagate drives, you go to the Seagate site.

As for actual performance of the drive with and without NCQ - most of the
reviews I've seen so far haven't shown a significant benefit to NCQ
enablement in benchmark tests. Real world, of course, is not a benchmark, so
YMMV.

--
Charlie.

"Bruce Sanderson" <bsanders(a)newsgroups.nospam> wrote in message
news:OQ6IjCe6IHA.2336(a)TK2MSFTNGP03.phx.gbl...
> This post is related to the one on 5 Jun 2008, but I think I asked the
> wrong question in that one!
>
> The operating system is Windows Server 2008 RTM with the RTM version of
> the Hyper-V role installed (Windows6.0-KB950050-x64.msu).
>
> The computer is a custom built with an ASUS P5N-D motherboard, which has
> the NVIDIA nForce 750i SLI chipset.
>
> This computer has three SATA drives - two ST3320620AS and one ST3500320AS.
> The ST3500320AS has two partitions, one of which is the Windows "System"
> and "Boot" partition (hosts the operating system).
>
> If command queuing is enabled on the ST3500320AS, I get frequent System
> Event Log entries with Event ID 129 from nvstor64 saying "Reset to device,
> \Device\RaidPort0, was issued".
>
> When these Event Log entries are recorded, the system temporarily
> freezes - no response to mouse or keyboard, no video updates - everything
> stops for a few seconds then carries on as if nothing happened.
>
> Enabling command queuing on either or both of the ST3320620AS drives does
> NOT cause this problem.
>
> The ASUS web site says that problems with NCQ has been reported with the
> NVIDIA nForce 750i SLI chipset and the solution is to update the firmware
> in the drive.
>
> Does anyone know where can I get updated firmware for the ST3500320AS or
> have any other clue to resolving this problem?
>
> I've disabled commmand queuing on the ST3500320AS, the system works and I
> don't get the Event log entries (Event ID 129 from nvsotr64) or system
> freezes, but I suspect this is resulting in degraded disk (and thus
> system) performance.
>
> --
> Bruce Sanderson
> http://members.shaw.ca/bsanders
>
> It is perfectly useless to know the right answer to the wrong question.
>
>
>

From: Bruce Sanderson on 19 Jul 2008 19:06
Hello Charlie - good to hear from you! Thanks for your post.

I have reported the problem to Seagate - no reply yet.

Thanks for the hyperlink. Your searching skills must be far superior to
mine becuase my searching on the Seagate site did not find it!

The page you reference specifically says that for the model ST3500320AS,
which is triggering my problem, "no action is required".

I did find several posts on the Seagate site from people that had "updated"
the firware from SD15 to AD14 and now the drive doesn't work. I pulled my
drive and found that it does indeed have firmware version SD15, so I don't
think I'll be updating the firmware!

The ST3320620AS drives that do NOT cause the problem are Barracuda 7200.10

The ST3500320AS that DOES cause the problem is Barracuda 7200.11.

As to whether and how much performance degredation turning off command
queuing introduces I really don't know. I do notice that Resource Monitor
tells me the drive is "100%" busy when the Virtual Machines are busy
sometimes, but what difference the command queuing would make is hard to
say.

I also found a thread on the Seagate "message board" that someone is having
what appears to be a related problem with Vista 64 bit and a Seagate 7200.11
drive
(http://forums.seagate.com/stx/board/message?board.id=ata_drives&message.id=1916&jump=true#M1916).
I suggested they try disabling command queuing.

--
Bruce Sanderson
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"Charlie Russel - MVP" <charlie(a)mvKILLALLSPAMMERSps.org> wrote in message
news:%23yk7%23Pe6IHA.3684(a)TK2MSFTNGP05.phx.gbl...
> GIYF.
>
> http://www.seagate.com/www/en-us/support/downloads/other_downloads/cuda-fw
>
> First hit on: ST3320320AS firmware site:seagate.com
>
> In general, firmware updates are only available directly from the OEM
> involved. So, for the Seagate drives, you go to the Seagate site.
>
> As for actual performance of the drive with and without NCQ - most of the
> reviews I've seen so far haven't shown a significant benefit to NCQ
> enablement in benchmark tests. Real world, of course, is not a benchmark,
> so YMMV.
>
> --
> Charlie.
>
> "Bruce Sanderson" <bsanders(a)newsgroups.nospam> wrote in message
> news:OQ6IjCe6IHA.2336(a)TK2MSFTNGP03.phx.gbl...
>> This post is related to the one on 5 Jun 2008, but I think I asked the
>> wrong question in that one!
>>
>> The operating system is Windows Server 2008 RTM with the RTM version of
>> the Hyper-V role installed (Windows6.0-KB950050-x64.msu).
>>
>> The computer is a custom built with an ASUS P5N-D motherboard, which has
>> the NVIDIA nForce 750i SLI chipset.
>>
>> This computer has three SATA drives - two ST3320620AS and one
>> ST3500320AS. The ST3500320AS has two partitions, one of which is the
>> Windows "System" and "Boot" partition (hosts the operating system).
>>
>> If command queuing is enabled on the ST3500320AS, I get frequent System
>> Event Log entries with Event ID 129 from nvstor64 saying "Reset to
>> device, \Device\RaidPort0, was issued".
>>
>> When these Event Log entries are recorded, the system temporarily
>> freezes - no response to mouse or keyboard, no video updates - everything
>> stops for a few seconds then carries on as if nothing happened.
>>
>> Enabling command queuing on either or both of the ST3320620AS drives does
>> NOT cause this problem.
>>
>> The ASUS web site says that problems with NCQ has been reported with the
>> NVIDIA nForce 750i SLI chipset and the solution is to update the firmware
>> in the drive.
>>
>> Does anyone know where can I get updated firmware for the ST3500320AS or
>> have any other clue to resolving this problem?
>>
>> I've disabled commmand queuing on the ST3500320AS, the system works and I
>> don't get the Event log entries (Event ID 129 from nvsotr64) or system
>> freezes, but I suspect this is resulting in degraded disk (and thus
>> system) performance.
>>
>> --
>> Bruce Sanderson
>> http://members.shaw.ca/bsanders
>>
>> It is perfectly useless to know the right answer to the wrong question.
>>
>>
>>
>

From: Edwin vMierlo [MVP] on 20 Jul 2008 04:28

"Bruce Sanderson" <bsanders(a)newsgroups.nospam> wrote in message
news:OQ6IjCe6IHA.2336(a)TK2MSFTNGP03.phx.gbl...
> This post is related to the one on 5 Jun 2008, but I think I asked the
wrong
> question in that one!
>
> The operating system is Windows Server 2008 RTM with the RTM version of
the
> Hyper-V role installed (Windows6.0-KB950050-x64.msu).
>
> The computer is a custom built with an ASUS P5N-D motherboard, which has
the
> NVIDIA nForce 750i SLI chipset.
>
> This computer has three SATA drives - two ST3320620AS and one ST3500320AS.
> The ST3500320AS has two partitions, one of which is the Windows "System"
and
> "Boot" partition (hosts the operating system).
>
> If command queuing is enabled on the ST3500320AS, I get frequent System
> Event Log entries with Event ID 129 from nvstor64 saying "Reset to device,
> \Device\RaidPort0, was issued".

Can you post the full 129 event ?
(use copy symbol, including the Hex data at the end)

Thanks,
Edwin


 |  Next  |  Last
Pages: 1 2
Prev: Installing Hyper-V RTM - "The update does not apply to your sy
Next: unable to backup system state