On Mon, Mar 30, 2009 at 11:12 AM, D. Hugh Redelmeier wrote:
> | From: L
>
> | <5>Linux version 2.6.17.14 (cla...@mccoy.oxsemi.com.asic.oxsemi.com)
> | (gcc version 4.1.1) #1 PREEMPT Fri Jan 18 10:40:25 GMT 2008
> | <4>CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
> | <4>Machine: Oxsemi N
| From: L
| <5>Linux version 2.6.17.14 (cla...@mccoy.oxsemi.com.asic.oxsemi.com)
| (gcc version 4.1.1) #1 PREEMPT Fri Jan 18 10:40:25 GMT 2008
| <4>CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
| <4>Machine: Oxsemi NAS
Neat! Fedora(?) on an ARM!
http://fedoraproject.org/wiki/Architect
On Mon, Mar 30, 2009 at 10:24:24 +1100,
L wrote:
>
> Bruno,
> below is the output from dmesg. as you see, when generation /dev/md4,
> partition /dev/sdb4 as undetected at all. I did curious tests (--fail
> --remove; reboot; then --add; reboot) on
>
> /dev/sdb3 on /dev/md3
> /dev/sdb2 on /dev/
On Mon, Mar 30, 2009 at 3:52 AM, Bruno Wolff III wrote:
> On Sun, Mar 29, 2009 at 20:15:53 +1100,
> L wrote:
>>
>> this partition is about 455GB, there is no IO error from log.
>
> I would suggest looking through /var/log/messages to see if you see any
> references to the array or partition and
On Sun, Mar 29, 2009 at 20:15:53 +1100,
L wrote:
>
> this partition is about 455GB, there is no IO error from log.
I would suggest looking through /var/log/messages to see if you see any
references to the array or partition and check if any of them shed some
light on what is going on.
It's po
On Sun, Mar 29, 2009 at 20:31:53 +1100,
L wrote:
>
> any suggestion??
Look through your log files to see why its being dropped from the array.
There may be bad blocks or something.
Run a smartctl long test on the disk to see if that picks up any bad blocks.
If you find one, you can boot up i
On Sun, Mar 29, 2009 at 5:18 PM, Bruno Wolff III wrote:
> On Sun, Mar 29, 2009 at 10:00:07 +1100,
> L wrote:
>> Hi
>>
>> I have RAID1 system, the partition /dev/md4 is in raid1 with
>> /dev/sda4 /dev/sdb4. In order to check /dev/sdb4 I remove it from
>> /dev/md4
>
> There are ways of checking d
On Sun, Mar 29, 2009 at 10:00:07 +1100,
L wrote:
> Hi
>
> I have RAID1 system, the partition /dev/md4 is in raid1 with
> /dev/sda4 /dev/sdb4. In order to check /dev/sdb4 I remove it from
> /dev/md4
There are ways of checking disks without pulling them out of service.
smartctl can do surface s
Hi
I have RAID1 system, the partition /dev/md4 is in raid1 with
/dev/sda4 /dev/sdb4. In order to check /dev/sdb4 I remove it from
/dev/md4
mdadm /dev/dm4 --fial /dev/sdb4 --remove /dev/sdb4
after checked it, I added it again
mdadm /dev/md4 --add /dev/sdb4
The system did sync md4, this lasted ~
