On Thursday February 20, jean-rene.cormier@cipanb.ca wrote:
quoted
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.
NeilBrown
----- Original Message -----
From: "Neil Brown" <redacted>
To: "Jean-Rene Cormier" <redacted>
Cc: <redacted>
Sent: Sunday, February 23, 2003 6:40 PM
Subject: Re: Software RAID1 problems
On Thursday February 20, jean-rene.cormier@cipanb.ca wrote:
quoted
quoted
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
On Sat, 1 Mar 2003, Jean-Rene Cormier wrote:
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
make sure you have the same speed disks on the same ide cable
- best to use only one ide drive per cable
- do NOT mix ata-33 w/ ata-66 w/ ata-100 w/ ata-133 on the same
cable
use better and SHORTER ide cables ?? ( should be 80 conductor )
make sure you do NOT have kinks in the ide cable ( keep it straight )
make sure your kernel has the ide chipset support enabled for your
motherboard
-- otherwise... you have a failing or dead disk drive...
-- if its an ibm deskstar... get rid of it...
c ya
alvin
----- Original Message -----
From: "Alvin Oga" <redacted>
To: "Jean-Rene Cormier" <redacted>
Cc: <redacted>
Sent: Saturday, March 01, 2003 9:08 PM
Subject: Re: Software RAID1 problems
On Sat, 1 Mar 2003, Jean-Rene Cormier wrote:
quoted
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
quoted
problem is not in the raid array, but I'm still not sure what is causing
the
quoted
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
make sure you have the same speed disks on the same ide cable
- best to use only one ide drive per cable
- do NOT mix ata-33 w/ ata-66 w/ ata-100 w/ ata-133 on the same
cable
Both drives are new 60Gb Maxtor DiamondMax Plus 9 on separate IDE channels
on a Promise Ultra TX2 IDE card
use better and SHORTER ide cables ?? ( should be 80 conductor )
I did switch the cable on the drives to see if it would make a difference
and it's still the same drive who gave me those errors so I guess it's not
the cables.
make sure you do NOT have kinks in the ide cable ( keep it straight )
make sure your kernel has the ide chipset support enabled for your
motherboard
I noticed yesterday that my kernel didn't have IDE support for the Promise
Ultra compiled in so I recompiled the kernel with it. I'll put the drive
back in the computer and try it again to see if it works better
-- otherwise... you have a failing or dead disk drive...
-- if its an ibm deskstar... get rid of it...
I'll try this drive in another computer to see what it'll say.
Thanks
Jean-Rene Cormier