public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Leo Davis <leo1783@yahoo.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: bad primary superblock - bad magic number !!!
Date: Wed, 12 May 2010 05:45:03 -0700 (PDT)	[thread overview]
Message-ID: <14845.20130.qm@web112901.mail.gq1.yahoo.com> (raw)
In-Reply-To: <20100512142902.47d1022a@harpe.intellique.com>


[-- Attachment #1.1: Type: text/plain, Size: 1912 bytes --]

> So is I do a - dd if=/dev/random of=dev/cciss/c0d2 , that should fail
> and therby confirm that the drive or array has issues...do i make any
> sense here?

>Uh, you should try the other way around to avoid breaking the
>filesystem :

>dd if=/dev/cciss/c0d2 of=/dev/null bs=131072

>If no error occurs it should be OK.

# dd if=/dev/cciss/c0d2 of=/dev/null bs=131072
796+1 records in
796+1 records out
#

doesn't show any errors here ......

> havent had much success with testing the hard drives, tried mhdd &
> seatools with no luck yet.

>What do you mean? Does the tools report any problem with the drives?

mhdd doesnt detect the drives, probably an issue with chipset...still looking for tools

thanks






________________________________
From: Emmanuel Florac <eflorac@intellique.com>
To: Leo Davis <leo1783@yahoo.com>
Cc: xfs@oss.sgi.com
Sent: Wed, May 12, 2010 1:29:02 PM
Subject: Re: bad primary superblock - bad magic number !!!

Le Wed, 12 May 2010 02:19:16 -0700 (PDT)
Leo Davis <leo1783@yahoo.com> écrivait:

> havent had much success with testing the hard drives, tried mhdd &
> seatools with no luck yet.

What do you mean? Does the tools report any problem with the drives?

> So is I do a - dd if=/dev/random of=dev/cciss/c0d2 , that should fail
> and therby confirm that the drive or array has issues...do i make any
> sense here?

Uh, you should try the other way around to avoid breaking the
filesystem :

dd if=/dev/cciss/c0d2 of=/dev/null bs=131072

If no error occurs it should be OK.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |    <eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------



      

[-- Attachment #1.2: Type: text/html, Size: 3079 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-05-12 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 14:54 bad primary superblock - bad magic number !!! stress_buster
2010-05-10 15:42 ` Eric Sandeen
2010-05-10 18:11   ` Leo Davis
2010-05-10 20:22     ` Emmanuel Florac
2010-05-12  9:19       ` Leo Davis
2010-05-12 12:29         ` Emmanuel Florac
2010-05-12 12:45           ` Leo Davis [this message]
2010-05-13  8:38           ` Leo Davis
2010-05-13  9:41             ` Emmanuel Florac
2010-05-13 11:00               ` Leo Davis
2010-05-13 14:03                 ` Emmanuel Florac
2010-05-13 17:23                 ` Stan Hoeppner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14845.20130.qm@web112901.mail.gq1.yahoo.com \
    --to=leo1783@yahoo.com \
    --cc=eflorac@intellique.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox