From: "Jean-Rene Cormier" <jean-rene.cormier@cipanb.ca>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Software RAID1 problems
Date: Sat, 1 Mar 2003 13:28:46 -0400 [thread overview]
Message-ID: <004901c2e01e$323fd500$8400a8c0@jrc> (raw)
In-Reply-To: 15961.19952.717406.146896@notabene.cse.unsw.edu.au
----- Original Message -----
From: "Neil Brown" <neilb@cse.unsw.edu.au>
To: "Jean-Rene Cormier" <jean-rene.cormier@cipanb.ca>
Cc: <linux-raid@vger.kernel.org>
Sent: Sunday, February 23, 2003 6:40 PM
Subject: Re: Software RAID1 problems
> On Thursday February 20, jean-rene.cormier@cipanb.ca wrote:
> > >
> > > I cannot explain the mounting problem. Maybe if you give more
> > > specifics....
> >
> > Well what I did was:
> >
> > mdadm -Cv -l2 -n2 /dev/hde1 /dev/hdg1 /dev/md0
> > mke2fs -j /dev/md0
> > mount /dev/md0 /home
> >
> > then I unmounted it and when I tried to mount it again right after
> > unmounting it I got the Wrong FS type error and I get a bunch of error
> > message on the console.
>
> If that is really what you did, no wonder it didn't work. The md
> device must be listed first, not last.
>
> However if it is a typo, and you really listed /dev/md0 first, it is
> strange. Maybe if you could include the 'bunch of error messages' -
> dmesg > /tmp/afile
> should get them for you.
Yes that was a typo sorry. I did reformat /dev/md0 and a when it started
formating it gave me those errors again. I did a little searching and the
problem is not in the raid array, but I'm still not sure what is causing the
problem. The error was:
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hde: drive not ready for command
hde: status timeout: status=0xf0 { Busy }
hde: drive not ready for command
ide2: reset: success
I get a bunch of those. I removed the drive and I reformated the array and
it works fine but I guess that if I put that drive back in it'll start doing
it again. Could it be a bad drive or something? If it is what's the use of
having a RAID-1 array if it corrupts your file system when a drive is bad?
Jean-Rene Cormier
next prev parent reply other threads:[~2003-03-01 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 13:20 Software RAID1 problems Jean-Rene Cormier
2003-02-21 0:11 ` Neil Brown
2003-02-21 3:12 ` Jean-Rene Cormier
2003-02-23 22:40 ` Neil Brown
2003-03-01 17:28 ` Jean-Rene Cormier [this message]
2003-03-02 1:08 ` Alvin Oga
2003-03-02 14:41 ` Jean-Rene Cormier
-- strict thread matches above, loose matches on Subject: below --
2005-09-12 7:42 ANNOUNCE: mdadm 2.1 - A tool for managing Soft RAID under Linux Neil Brown
2005-09-12 14:30 ` Software RAID1 problems Andy Dawson
2005-09-12 22:23 ` Neil Brown
2005-09-23 15:45 ` Andy Dawson
2005-09-23 15:52 ` Neil Brown
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='004901c2e01e$323fd500$8400a8c0@jrc' \
--to=jean-rene.cormier@cipanb.ca \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).