[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Corrupt data - RAID sata_sil 3114 chip

Bengt Samuelsson skrev:

Justin Piszcz skrev:



On Fri, 2 Jan 2009, Bengt Samuelsson wrote:



Hi,

I need some support for this soft-raid system.
I am running it as RAID5 with 4 samsung spinpoint 500G SATA300 tot 1.3T byte 

And it runs in http://sm7jqb.dnsalias.com
I use mdadm sytem in a Debian Linux
CPU 1.2Mhz 1G memory ( my older 433Mhz / 512M dont work at all )
I have 'some courrupt' data. And I don't understand whay and how to fix it. 
Mybee slow it down more, but how slow it down?

Any with experents from this cheep way of RAID systems.
Ask for more information and I can get it, logs, setup files and what you want 
to know.

--
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

+46(0)703686441

http://sm7jqb.se


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
If this is an mdadm-related raid (not dmraid) please show all relevant md info, mdadm -D /dev/md0, I have cc'd linux-raid on this thread for you. 



~# mdadm -D /dev/md0
------------------------------
/dev/md0:
        Version : 00.90.03
  Creation Time : Fri Sep 12 19:08:22 2008
     Raid Level : raid5
     Array Size : 1465151616 (1397.28 GiB 1500.32 GB)
    Device Size : 488383872 (465.76 GiB 500.11 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Jan  2 16:53:10 2009
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 128K
UUID : 68439662:90431c4a:5e66217b:5a1a585f (local to host sm7jqb.dnsalias.com) 
         Events : 0.13406

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
       2       8       33        2      active sync   /dev/sdc1
       3       8       49        3      active sync   /dev/sdd1
------------------------------


 >
You'll want to read md.txt in /usr/src/linux/Documentation and read on the check and repair commands.
In addition, have you run memtest86 on your system first to make sure its not memory related? 

I am vorking on this.


No memory error

Next?



Justin.







--
Bengt Samuelsson
Nydalavägen 30 A
352 48 Växjö

+46(0)703686441

http://sm7jqb.se
Reply to: