mindbrain wrote:
> Hi, we have a Dell 64 bit workstation with two drives. When we boot,
> the bios or os tells us a hard drive failed a test and won't boot in
> windows but we can boot it in suse 10.1 linux.
>
> We'd like to run diagnostics on the hard drives. Any clue about the
> necessary command sequence would be greatly appreciated.
>
> Many thanks in advance....
>
> JK
>

So how many linux users use grc's spinrite?

Beege

Hi, we have a Dell 64 bit workstation with two drives. When we boot,
the bios or os tells us a hard drive failed a test and won't boot in
windows but we can boot it in suse 10.1 linux.

We'd like to run diagnostics on the hard drives. Any clue about the
necessary command sequence would be greatly appreciated.

Many thanks in advance....

JK

mindbrain wrote:
> Hi, we have a Dell 64 bit workstation with two drives. When we boot,
> the bios or os tells us a hard drive failed a test and won't boot in
> windows but we can boot it in suse 10.1 linux.
>
> We'd like to run diagnostics on the hard drives. Any clue about the
> necessary command sequence would be greatly appreciated.
>
> Many thanks in advance....
>
> JK
>

Use fsck from a terminal window-

fsck [ -F fstype] [-V] [-yY] [-o options] special

-F fstype type of file system to be repaired ( ufs , vxfs etc)

-V verify the command line syntax but do not run the command

-y or -Y Run the command in non interactive mode - repair all errors
encountered without waiting for user response.

-o options Three options can be specified with -o flag

b=n where n is the number of next super block if primary super block
is corrupted in a file system .

p option used to make safe repair options during the booting process.

f force the file system check regardless of its clean flag.



--
Claude Hopper ? 3 :) 7/8

On Thu, 17 Jul 2008 15:19:06 -0700, mindbrain wrote:

> Hi, we have a Dell 64 bit workstation with two drives. When we boot, the
> bios or os tells us a hard drive failed a test and won't boot in windows
> but we can boot it in suse 10.1 linux.
>
> We'd like to run diagnostics on the hard drives. Any clue about the
> necessary command sequence would be greatly appreciated.
>
> Many thanks in advance....
>
> JK

personally, I'd start with 'badblocks' run from a Live CD.

I normally just reboot the system using a bootable floppy or CD that
contains a set of HD diagnostics tools. Now, after you correct the
error you need to find what cause your HD error.

It sound like your having the same problem I did with YAST causing
an error in the MBR.

In my case, using SuSE 10.0 and 11.0 it seams that YAST (non-updated)
has an error in the program. Because every time I scan my HD after I
have executed YAST under KDE 3.x, I find that the HD scaner will reports
some repairable errors. Sometime in just the MBR and others in both the
MBR and the "/" Linux partition formatted with ReiserFS.

Note: Some of these errors will cause the BIOS to report HD error while
others will just cause the hard drive data tranfers to slow down.

Now, I only use KDE for system maintenance, since SuSE prefers KDE.
Normally use "Windowmaker" and there has been no errors, until I use
KDE with YAST again.



In <6a803688-0234-4683-93de-a773d891dbd6@8g2000hse.googlegroups.com>, mindbrain <mindbrain315@gmail.com> writes:
>Hi, we have a Dell 64 bit workstation with two drives. When we boot,
>the bios or os tells us a hard drive failed a test and won't boot in
>windows but we can boot it in suse 10.1 linux.
>
>We'd like to run diagnostics on the hard drives. Any clue about the
>necessary command sequence would be greatly appreciated.
>
>Many thanks in advance....
>
>JK
>