May 2, 201115 yr Level One Cert for: SUPERMICRO MBD-X9SCL-F-O (Sandy Bridge LGA 1155). My current setup: OS at time of building: 4.7 Pro CPU: Intel i3-2100 Motherboard: SUPERMICRO MBD-X9SCL-F-O RAM: 4GB (2 x 2GB) of Kingston DDR3 1333 ECC Case: NORCO RPC-4224 Drive Cage(s): Included in case Power Supply: Corsair CMPSU-650TX 650W SATA Expansion Card(s): Two SUPERMICRO AOC-SASLP-MV8 SAS Cables: 4 x NORCO C-SFF8087-D SFF-8087 to SFF-8087 Internal Multilane SAS Cable and 2 x NORCO C-SFF8087-4S Discrete to SFF-8087 (Reverse breakout) Cable Fans: 6 x ENERMAX UC-8EB 80mm Case Fan Updated to include new syslog. syslog-2011-05-05.zip
May 3, 201115 yr Post it and we'll take a look. A perfectly clean syslog is preferable of course, but for the short term yours might be OK. Once you run another parity check in a month or so you can update the syslog with a clean one.
May 4, 201115 yr The syslog looks good. BAMF indeed This part shows disk 5 being rebuilt: May 2 19:26:13 BAMF emhttp: writing mbr on disk 5 (/dev/sde) with partition 1 offset 63 May 2 19:26:13 BAMF emhttp: re-reading /dev/sde partition table May 2 19:26:13 BAMF ata_id[3604]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' May 2 19:26:13 BAMF kernel: sde: sde1 May 2 19:26:14 BAMF ata_id[3630]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' May 2 19:26:14 BAMF kernel: mdcmd (30): start RECON_DISK May 2 19:26:14 BAMF kernel: unraid: allocating 69560K for 1280 stripes (13 disks) May 2 19:26:14 BAMF kernel: md1: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md2: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md3: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md4: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md5: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md6: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md7: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md8: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md9: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md10: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md11: running, size: 1953514552 blocks May 2 19:26:14 BAMF kernel: md12: running, size: 1953514552 blocks May 2 19:26:15 BAMF emhttp: shcmd (27): udevadm settle May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk3 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk1 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk7 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk5 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk2 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk6 May 2 19:26:15 BAMF emhttp: shcmd (28): mkdir /mnt/disk4 May 2 19:26:15 BAMF kernel: mdcmd (31): check May 2 19:26:15 BAMF kernel: md: recovery thread woken up ... May 2 19:26:15 BAMF kernel: md: recovery thread rebuilding disk5 ... And then here's the disk 5 rebuild completing: May 3 04:51:25 BAMF kernel: md: sync done. time=33910sec rate=57608K/sec May 3 04:51:25 BAMF kernel: md: recovery thread sync completion status: 0 I also don't see the parity check. Did you run it after rebuilding disk 5? Would you mind running another one and posting that syslog just to be sure?
May 4, 201115 yr Not to hijack the thread, but I just completed a parity check on pretty much the same build (850W Seasonic, with replacement of 120 mm and 80 mm fans). I noticed some of the same errors as onthecake, but don't know if I should pay any heed. Hope this is helpful... syslog-2011-05-04.txt
May 5, 201115 yr Author Updated first post with new syslog. It looks like it has the parity check in it. May 5 03:30:10 BAMF kernel: md: sync done. time=39130sec rate=49923K/sec May 5 03:30:10 BAMF kernel: md: recovery thread sync completion status: 0
Archived
This topic is now archived and is closed to further replies.