July 1, 200719 yr Sorry for posting more troubles here... Here is my set up: Asus P5B-E + Celeron D 2.66GHz + 2x1GB DDR533 3 x 500GB Samsung SATA 3Gb 550W Rowswill PS 1Gb Netgear switch unRAID 4.0 final (Basic) on lexar USB 1GB flash Last night I started to test the unRAID. I copied several 20GB to 30GB folders/files to tower/disk1 and it went through smoothly. I got around 12-15MB/sec write speed, and 24MB/sec read. Then I made a backup job by Viceversa software to copy 140GB data from my USB hard drive to Tower/disk1 and let it go overnigh. This morning I found the backup stopped at 47GB due to "network drive not found" or sth like that. The Tower mainpage were no longer accessible. In a hurry, I rebooted the server. It started parity check at 70MB/sec but soon crawled to 11-12MB/sec and has been staying at this speed. I noticed there are 350 errors listed for parity disk so far, and 5 sync errors were found. As a reference, when I first started array it went through parity sync at 55MB/sec without glitch. There were no erros listed for two data disks. Now I wonder whether the parity disk is defective. I did accidentally dropped it from chair to concrete floor. It's in its plactic case so it's protected a little bit, but I wonder that drop effective ended its useful life. If this is the case then I'll have to get a new drive. I don't know how to read and properly capture the syslog. I did a quick capture with Hyperterminal and here is the end of syslog (the server date is one day off): ============================================================= Jun 30 10:55:36 Tower kernel: [ 985.157895] sector=118506048 i=0 00000000 0000004 i=0 00000000 0000087368e drivers/md/unraid.c0:07:00:00/40 Emask 0 Jun 30 10:5 000 00000000 512: [ 000 0000000 Jun 30 10:55:36 Tower kernel: [ 985.157897] Jun 30 10:55:36 Tower kernel: [ 985.157905] md: bug in file drivers/md/unraid.cnt: 1922] Jun 30 10:55:22 Tower kernel: 000 00000000 512n 30 10:55:30 To , line 30055:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157909] md: bug in file drivers/md/unraid.c61] handle_stripe read error: 118487392r 0:07:00:00/40 tag , line 300ata 233472 , line 29155:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157911] sector=118506064 i=0 00000000 00000s 51/40:10:2d:13:10/85:0 965.730700] ata1: EH completen 30 , line 291n 30 Jun 000 00000000 512Tower kernel: [ 000 00000000 512Tower kernel: [ Jun 30 10:55:36 Tower kernel: [ 985.157931] md: bug in file drivers/md/unraid.c55:23 Tower kernel: [ 972.216866] ata1.00: exc 000 00000000 512on 0x0 967.01187 , line 30055:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157934] md: bug in file drivers/md/unraid.c10:40:28 Ju Jun 30 10:55:23 Tower kernel: [ 972.216871] , line 3000:55:31 To , line 29155:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157937] sector=118506088 i=0 00000000 00000ower kernel: [ 972.216878] ata1.00: cmd 0:07:00:00/40 tag , line 291ata 118784 000 00000000 512Tower kernel: [ Jun 30 10:55:36 Tower kernel: [ 985.157939] md: bug in file drivers/md/unraid.c9:0d:10/85:000: configured for UDM Jun 30 10:55 000 00000000 512 [ 972.216880] , line 30055:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157942] md: bug in file drivers/md/unraid.c1 Tower kernel: [ 980.375932] ata1.00: configured for UDMA , line 30055:18 Towe , line 29155:36 Towe Jun 30 10:55:36 Tower kernel: [ 985.157954] sector=118506104 i=0 00000000 0000040 i=0 00000000 0000080.376198] SCSI device sda: write cache: enabl 10:40:28 Tow 000 00000000 51210:5 000 0000000 Jun 30 10:55:36 Tower kernel: [ 985.157956] md: bug in file drivers/md/unraid.ce drivers/md/unraid.c000000 00000Wri Jun 30 10:55:04 Tow Jun 30 10:55:33 Tower k , line 30082.030093] Jun 30 10:55:36 Tower kernel: [ 985.167372] Jun 30 10:55:36 Tower kernel: [ 985.167411] md: bug in file drivers/md/unraid.cunraid.c 954.107135] ata1.00: exception Emask 0x0 SAct 000 00000000 51207:00:00 , line 1350 30 10:55:3 Jun 30 10:55:36 Tower kernel: [ 985.167429] md: bug in file drivers/md/unraid.c [ 982.030106] res 51/40:08:f9:0d:10/85:000 000 0000000 , line 300ad e , line 13500 10:55:36 Jun 30 10:55:36 Tower kernel: [ 985.167447] md: bug in file drivers/md/unraid.c0000.107147] ata1.00: Jun 30 10:55:33 Tower kernel: [ 982.041 , line 2910: con , line 135010:55:36 To Jun 30 10:55:36 Tower kernel: [ 985.167466] md: bug in file drivers/md/unraid.c 10:55:33 Tower kernel: [ 982.041866] ata1: EH completeel: [ 000 00000000 512 , line 1350:5 Jun 30 1 Jun 30 10:55:36 Tower kernel: [ 985.1674 000 , line 13502l: [ 982. Jun 30 10:55:36 Tower kernel: [ 985.167538] md: bug in file drivers/md/unraid.craid.cnt: 1nel: [ 914. Jun Jun 30 10:55:33 Tower kernel: [ 982.042118] SCSI d , line 1350e 300cache: Jun 30 10:55:36 Tower kernel: [ 985.167558] md: bug in file drivers/md/unraid.cid.c/ ed, read cache: enabled, doesn't support DPO or FUA30 10: , line 291 kerne , line 135029155:24 To Jun 30 10:55:36 Tower kernel: [ 985.167576] md: bug in file drivers/md/unraid.c00t 0/unraid.c Jun 30 10:55:05 Tower kernel: [ 954.119185] 000 00000000 512wr , line 1350000 512ctio Jun 30 10:55:36 Tower kernel: [ 985.1675 Jun 30 10 J Jun 30 10:55:36 Tower kernel: [ 985.177844] md: bug in file drivers/md/unraid.ce drivers/md/unraid.ctors (500108 MB)n 30 10:54:47 Tower kerne J Jun 30 10:55:34 , line 300el: [ 983 Jun 30 10:55:36 Tower kernel: [ 985.187358] md: bug in file drivers/md/unraid.c40 i=0 00000000 00000 Jun 30 10:55:06 Tower ed, read cache: enabled, doesn't sup , line 1350FUArror! 0 Jun 30 10:55:36 Tower kernel: [ 985.187379] md: bug in file drivers/md/unraid.cbug in file drivers/md/unraid.ck 0x0 SAct 0da: write cache: enabl or FUA , , line 1350ie00] Jun Jun 30 10:55:36 Tower kernel: [ 985.197827] md: bug in file drivers/md/unraid.cg in file drivers/md/unraid.c ata1.00: (irq_stat 0x40000008) Jun 30 10:5 , l , line 291el: [ Jun Jun 30 10:55:36 Tower kernel: [ 985.197832] sect 000 00000000 512 Des 000 0000000 Jun 30 10:55:36 Tower kernel: [ 985.197855] md: bug in file drivers/md/unraid.c , line 291 Jun 30 10:55:36 Tower kernel: [ 985.197858] sector=118507032 i=0 00000000 00000 000 00000000 512 Jun 30 10:55:36 Tower kernel: [ 985.197860] md: bug in file drivers/md/unraid.c , line 300 Jun 30 10:55:36 Tower kernel: [ 985.207344] md: bug in file drivers/md/unraid.c , line 1350 Jun 30 10:55:36 Tower kernel: [ 985.207365] md: bug in file drivers/md/unraid.c , line 1350 Jun 30 10:55:36 Tower kernel: [ 985.207383] md: bug in file drivers/md/unraid.c , line 1350 Jun 30 10:55:36 Tower kernel: [ 985.207400] md: bug in file drivers/md/unraid.c , line 1350 Jun 30 11:53:47 Tower in.telnetd[1526]: connect from 192.168.10.172 (192.168.10. 172) Jun 30 11:53:50 Tower login[1527]: ROOT LOGIN on `pts/0' from `192.168.10.172' Jun 30 11:57:26 Tower in.telnetd[1540]: connect from 192.168.10.172 (192.168.10. 172) Jun 30 11:57:30 Tower login[1541]: ROOT LOGIN on `pts/0' from `192.168.10.172' Jun 30 11:59:39 Tower in.telnetd[1554]: connect from 192.168.10.172 (192.168.10. 172) Jun 30 11:59:41 Tower login[1555]: ROOT LOGIN on `pts/0' from `192.168.10.172' ========================================================================
July 1, 200719 yr Author well, I guess I do have a bad disk here. The parity check now dropped to 5kB/sec, and errors increased to 442 for parity drive. Still zero errors for data drive. Part of the newest syslog: ======================================== Jul 1 14:05:36 Tower kernel: [12392.896604] ata1.00: (irq_stat 0x40000008)el: [12372.441331] ata1.00: cmd 60/28:00:9f:7b:fa/00:0ured for UD Jul 1 14 Jul 1 14:05:36 Tower kernel: [12392.896610] ata1.00: cmd 60/08:00:f7:89:fa/00:0db 0x0 data 20480 inl: [12339.209090] ata1: EH complete8 MB)a Jul 1 14:05:15 To 0:16:00:00/40 tag 0 cdb 0x0 data 4096 in1/40:00:ae:7b:fa/85:0el: [12353.933758] Jul 1 14:05:36 Tower kernel: [12392.896612] res 51/40:00:f7:89:fa/85:0 0x9 (media error)286.21 Jul 1 14:04:57 Tower kernel: Jul 1 14:05:15 Tower ke 0:16:00:00/40 Emask 0x9 (media Jul 1 14:05:37 Tower kernel: [12394.214427] ata1.00: exception Emask 0x0 SAct 03. Jul 1 14:04:43 Tower kernel: [12340.515167] res 51/40 Jul 1 14:04: x1 SErr 0x0 action 0x0.94577 Jul 1 14:05:15 Jul 1 14:05:37 Tower kernel: [12394.214432] ata1.00: (irq_stat 0x40000008)ata1.00: configured for UD ed, re Jul 1 14:05:15 Tower kernel: [12372.4531 Jul 1 14:05:37 Tower kernel: [12394.214439] ata1.00: cmd 60/08:00:f7:89:fa/00:0el: [12355.251579] ata1.00: exception , line 1350ct 0ower ke Jul 1 14:05:15 To 0:16:00:00/40 tag 0 cdb 0x0 data 4096 inr! SCSI devic x1 SErr 0x0 action 0x0te [ Jul 1 14:05:37 Tower kernel: [12394.214441] res 51/40:00:f7:89:fa/85:0e read error: 385514344923] sda: Current [descriptor]: sense keor UDMA/133nel: [ 0:16:00:00/40 Emask 0x9 (media error) [12355.25 Jul 1 14:05:15 Tower kern Jul 1 14:05:37 Tower kernel: [12394.226020] ata1.00: configured for UDMA/133] sda: Mode Sens 0 Jul 1 14:05:15 Tower kernel: [12372.453166] ha Jul 1 14:05:15 Tower kernel: [12372.453779] SCS Jul 1 14:05:38 Tower kernel: [12395.532269] ata1.00: cmd 60/08:00:f7:89:fa/00:0:59 Tower kernel: [12356.569402 ed, read cache: enabled, doesn't support DPO or 0:16:00:00/40 tag 0 cdb 0x0 data 4096 inl 1 14:04:27 Jul 1 14:05:15 Tower kern Jul 1 14:05:38 Tower kernel: [12395.532270] res 51/40:00:f7:89:fa/85:01.00: (irq_stat 0x40000008) 00 00e 29 0:16:00:00/40 E , line 291edia error Jul 0:16:00:00/40 Emask 0x9 (media error)] sector=385512104 i=0 00000000 00000 Jul 1 14:05:38 Tower kernel: [12395.543864] ata1.00: configured for UDMA/13304 000 00000000 512 [12340.527 0:16 Jul 1 14:05:15 Tower kernel: [12372.7603 Jul 1 14:05:38 Tower kernel: [12395.543872] ata1: EH completeel: [12356.569415] res 51/40:00:27:72:fa/85:0we , lin Jul 1 14:05:40 Tower kernel: [12396.850088] ata1.00: cmd 60/08:00:f7:89:fa/00:0 error, dev Jul 1 14:05:16 Tower kernel: [12373.792312] res 51/40:00: 0:16:00:00/40 tag 0 cdb 0x0 data 4096 inwer ker Jul 1 14:04:59 Tower kernel: [1 Jul 1 14:05:40 Tower kernel: [12396.850090] res 51/40:00:f7:89:fa/85:0Tower Jul 1 14:05:16 Tower kernel: [12373.804057] ata1.00: configured for UDMA 0:16:00:00/40 Emask 0x9 (media error)- /0, count: 0: bug in fil /0, count: Jul 1 14:05:40 Tower kernel: [12396.861682] ata1.00: configured for UDMA/133or FUA/40 ta , line 2 Jul 1 14:03 Jul 1 14:04:27 To Jul 1 14:05:16 Tower k Jul 1 14:05:40 Tower kernel: [12396.861691] ata1: EH complete1/40:10:9c:cd:0f/85:0 Jul 1 14:03:34 Tow Jul 1 14:04 /0, co Jul 1 14:05:40 Tower kernel: [12396.861787] SCSI device s Jul 1 14:05:41 Tower kernel: [12398.179514] ata1.00: configured for UDMA/133 Jul 1 14:04:59 Tower kernel: [12356.629 Jul 1 14:05:18 Tower kernel: [12 Jul 1 14:05:41 Tower kernel: [12398.179523] ata1: EH complete00 3a 00 Jul 1 14:04: 000 00000000 512[123 Jul 1 14:0 Jul Jul 1 14:05:41 Tower kernel: [12398.179618] SCSI device sda: 976773168 512-bytel: [12375.122045] sda: Write Protect is offd_request: I/O erro 000 0000000 , lin hdwr sectors (500108 MB)04:59 T Jul 1 14:05:42 Tower kernel: [12399.497331] ata1.00: configured for UDMA/133 1 14:05:19 Tower kernel: [12376.439721] ata1: EH completeread cache: enable Jul 1 14:05:42 Tower kernel: [12399.497342] sd 1:0:0:0: SCSI error: return code.439820] SCSI device sda: 976773168 512-byte a Jul 1 14:04:45 Tower kernel: [12 = 0x08000002SI device sda Jul 1 14:05:42 Tower kernel: [12399.497345] sda: Current [descriptor]: sense ke:19 Tower kernel: [12376.439880] sda: Write Protect is off763] ata1.00 Jul 1 14 y=0x3 Towe Jul 1 14:05:42 Tower kernel: [12399.497348] ASC=0x11 ASCQ=0x4 [12376.439884] sda: Mode Sense: 00 3a 00 00327.30377 Jul 1 14:05:42 Tower kernel: [12399.497353] 72 03 11 04 00 00 00 0c 00 Tower kernel: [12377.745769] ata1.00: exception Emask 0x0 SAct 0port DPO or FU 0a 80 00 00 00 00 00ured for UDMA/133 in Jul 1 14:05:42 Tower kernel: [12399.497360] 16 fa 89 f7 exce Jul 1 14:05:20 Tower kernel: [12377.745774] ata1.00: (irq Jul 1 14:05:42 Tower kernel: [12399.497364] end_request: I/O error, dev sda, se04:30 T Jul Jul 1 14:05:20 Tower kernel: [12377.745781] ata1.00: cmd 60/18:00:5 Jul 1 14:05:42 Tower kernel: [12399.497648] SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB) Jul 1 14:05:42 Tower kernel: [12399.497710] sda: Write Protect is off Jul 1 14:05:42 Tower kernel: [12399.497714] sda: Mode Sense: 00 3a 00 00 Jul 1 14:05:42 Tower kernel: [12399.497831] SCSI device sda: write cache: enabl ed, read cache: enabled, doesn't support DPO or FUA Jul 1 14:05:43 Tower kernel: [12400.182548] md: bug in file drivers/md/unraid.c , line 291 Jul 1 14:05:43 Tower kernel: [12400.182554] sector=385515320 i=1 00000000 00000 000 00000000 512 Jul 1 14:05:43 Tower kernel: [12400.182556] md: bug in file drivers/md/unraid.c , line 300 Jul 1 14:05:43 Tower kernel: [12400.192533] md: bug in file drivers/md/unraid.c , line 1350 Jul 1 14:05:43 Tower kernel: [12400.502352] md: bug in file drivers/md/unraid.c , line 291 Jul 1 14:05:43 Tower kernel: [12400.502357] sector=385515568 i=0 00000000 00000 000 00000000 512 Jul 1 14:05:43 Tower kernel: [12400.502359] md: bug in file drivers/md/unraid.c , line 300 Jul 1 14:32:34 Tower in.telnetd[1681]: connect from 192.168.10.172 (192.168.10. 172) Jul 1 14:33:21 Tower login[1682]: ROOT LOGIN on `pts/0' from `192.168.10.172' =======================================================
Archived
This topic is now archived and is closed to further replies.