D&C Lug - Home Page
Devon & Cornwall Linux Users' Group

[ Date Index ][ Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] Can't boot SuSE 8 form the HD

On Sunday 16 June 2002 18:41, lee quick wrote:

On Sunday 16 June 2002 12:49, Keith Abraham wrote:

That's what I thought had happened, Lee. But "fixing" the MBR
really screwed things up. I couldn't boot into the installed system
with the CDROM anymore. SuSE reported that none of the
partitions were Linux partitions. It looked to me as if the HD had
gone down.


My friend had a Fujitsu Drive became intermittant ,it could be early
warning of failure?
Very similar circumstances too tho, he was running win2000 and the drive
lost the mbr and partitions (no big deal i hear you say serves him right
for using M$ ). He reinstalled and all seemed ok for about a day of so then
happened again and again.
As for superblocks er dunno, seen something bout that after i stuffed me
own system and had to re-install :) File systems eh!


I've attached a note I've found about Fujitsu mpg3204ate HDs.
This might have been your friends problem.

How does this relate to Linux?

Keith
Title: Files May Be Damaged During Windows 2000 Setup on Fujitsu Disks
Microsoft Home
   All Products   |   Support   |   Search   |   Microsoft.com Guide  
Microsoft.com Home Page
  Home     Search     FAQs     Downloads     Newsgroups     Customer Service     Contact Us  
  Send   
  Print   
  Help   


Files May Be Damaged During Windows 2000 Setup on Fujitsu MPG3102AT or Fujitsu MPG3204AT Hard Disks (Q311902)

The information in this article applies to:

  • Microsoft Windows versions 2000 , 2000 SP1 , 2000 SP2 , Professional
  • Microsoft Windows versions 2000 , 2000 SP1 , 2000 SP2 , Server
  • Microsoft Windows versions 2000 , 2000 SP1 , 2000 SP2 , Advanced Server


SYMPTOMS

When you try to install Windows 2000 on either a Fujitsu MPG3102AT or Fujitsu MPG3204AT hard disk on a computer that has the Intel 815 chipset, the installation procedure does not report damaged files after Setup copies the initial files and restarts the computer.


CAUSE

This problem occurs because the _STM method of the basic input/output system (BIOS) that sets the Ultra DMA (UDMA) speed for both the controller and the hard disk does not change speeds after being set. When this occurs, the controller and the hard disk run at different speeds, which clips the data flow and causes incorrect data to be written on large files. This problem typically occurs if you extend the BIOS to include ATA 100 features on a computer that has an earlier chipset.


WORKAROUND

To temporarily work around this problem, you can change the cable that connects the hard disk to the controller to the 40-channel cable that is used with ATA 33 drives. When you do this, the drive can run at ATA 33 speeds.

A longer-term solution for manufacturers is to flash the BIOS so that the BIOS initially sets the UDMA cycle time to 0x14 (20) when the computer starts for the first time. This causes the Atapi.sys file to leave the drive running at UDMA 100 timings so that the hard disk and the controller run at the same speed.

Windows 2000 accepts values less than 0x14 and remains at UDMA 100 speeds, but the drive and BIOS need this value to continue to work reliably.

The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.


STATUS

Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.

Published Jan 2 2002 8:39AM Issue Type kbprb
Last Modifed Jan 2 2002 8:39AM Additional Query Words
Keywords kbhw kbsetup kbWin2000PreSP3Fix

COMMENTS?

If you would like to briefly comment on this article, you can enter your remarks in the space below (up to 255 characters).


Submit Comments
Send  | Print  | Help 
 © 2002 Microsoft Corporation. All rights reserved.  Terms of use  Privacy statement  Accessibility 
Lynx friendly