Mitchell Laks wrote:
On Sunday 13 March 2005 10:49 am, David Greave wrote: Many Helpful remarks:
David I am grateful that you were there for me.
No probs - we've all been there!
My assessment (correct me if I am wrong) is that I have to rethink my
architecture. As I continue to work with sof
On Sunday 13 March 2005 10:49 am, David Greave wrote: Many Helpful remarks:
>
David I am grateful that you were there for me.
I went to the site. I connected a monitor to the headless machine. I saw the
screen flooded with write errors to the spare drive in the original raid1.
The terminals were
Mitchell Laks wrote:
Hi,
I have a remote system with a raid1 of a data disk. I got a call from the
person using the system that the application that writes to the data disk was
not working.
system drive is /dev/hda with separte partitions / , /var, /home, /tmp.
data drive is linux software raid
Mitchell Laks wrote:
On Sunday 13 March 2005 04:49 am, you wrote:
kernel version, mdadm version?
debian sarge:
[EMAIL PROTECTED]:~$ uname -a
Linux A1 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux
[EMAIL PROTECTED]:~$ export COLUMNS=200;dpkg -l|grep mdadm
ii mdadm
On Sunday 13 March 2005 04:49 am, you wrote:
> kernel version, mdadm version?
debian sarge:
[EMAIL PROTECTED]:~$ uname -a
Linux A1 2.6.8-1-386 #1 Thu Nov 25 04:24:08 UTC 2004 i686 GNU/Linux
[EMAIL PROTECTED]:~$ export COLUMNS=200;dpkg -l|grep mdadm
ii mdadm
kernel version, mdadm version?
David
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
One more bit of information:
this was a bit of info from
tail /var/log/kern.log
Mar 11 04:42:11 A1 kernel:
Mar 11 04:42:11 A1 kernel: hdg: drive not ready for command
Mar 11 04:42:11 A1 kernel: raid1: hdg1: rescheduling sector 215908496
Mar 11 04:42:11 A1 kernel: raid1: hdg1: redirecting sector
I had some more bright ideas and here is what happened:
I am unable to even do ls on the directory mounted on this raid device.
So, I said, maybe the problem is that I need to run fsck.ext3 on the drive
first. So I tried to umount it and i got the error message:
A1:~# umount /home/big0
umount:
Hi: some additional information
1) I tried to add the new spare device to /dev/md0 on friday afternoon. It
still has not rebuilt. I am also unable to do "ls" of the directory of the
drive.
2) I had another idea. Why not umount the drive and then run fsck.ext3 on the
drive. Maybe it needs fsck?
Hi,
I have a remote system with a raid1 of a data disk. I got a call from the
person using the system that the application that writes to the data disk was
not working.
system drive is /dev/hda with separte partitions / , /var, /home, /tmp.
data drive is linux software raid1 /dev/md0 with /dev/
10 matches
Mail list logo
