March 18, 201313 yr Hi I need more storage and i bought a new 3tb Seagate drive (ST3000DM001) to replace the 2tb wd i were using as parity but i cant get it to work as a paritydrive. I removed the 2tb WD green that was paritydrive and run preclear on the new one and then added it as parity and started paritysync. It all locked fine up to 75% then i went to bed and then when in the morning it showed a redball and said 2 errors. I ran preclear again, made a logfile just in case then added the drive and started paritysync. It looked good up to 70-80% but later its the same again. 2 errors and redball =( Any idea? Attaching the log from the second preclear and a screenshot. /Magnus https://dl.dropbox.com/u/5314933/Tower-Main.png smart.txt
March 18, 201313 yr Post the entire syslog and the preclear log files for the new disk, you find them on your usb flash drive in the folder "preclear_reports"
March 18, 201313 yr Author ok here they are syslog was to big to attach but here it is: https://dl.dropbox.com/u/5314933/syslog.txt preclear_finish__Z1F1TQZ5_2013-03-17.txt preclear_rpt__Z1F1TQZ5_2013-03-17.txt preclear_start__Z1F1TQZ5_2013-03-17.txt
March 18, 201313 yr Please provide a detailed hardware config, including MB and SATA cards. Check for BIOS updates for SATA cards and MB. See my sig to disable all add-ons for testing. Zip and attach syslog if failure occurs with no add-ons.
March 18, 201313 yr Author System Overview unRAID Version: unRAID Server Pro, Version 5.0-rc11 Motherboard: Gigabyte - GA-MA78GM-S2H Processor: AMD AthlonTM Dual Core 4850e.K - 2.5 GHz Cache: L1 = 128 KB L2 = 128 KB L3 = 512 KB L4 = 0 KB Memory: 4 GB - DIMM0 = 800 MHz (1.2 ns) DIMM1 = 800 MHz (1.2 ns) DIMM2 = 800 MHz (1.2 ns) DIMM3 = 800 MHz (1.2 ns) Network: 1000Mb/s - Full Duplex Uptime: 2 days, 8 hrs, 6 mins, 5 secs Running bios F4 and vill update the bios as a first step. The new drive is connected to the motherboard on SATA0. When i first got the drive i connected it to the cheap 4p card i got from dx.com and run the first preclear and it went fine but the preclear speed was 80mb/s on that card and like 140mb/s on the motherboard (ofcorse thats megabyte not megabit =). This is the sata card http://dx.com/p/silicon-image-4-port-sata-pci-expansion-card-4660 and i got one more with 2 sata and 1 PATA that came with a drive a couple of years ago) No problems until now with the new drive but i will update the bios and get back after the parity sync.
March 18, 201313 yr Yikes; I'm doing exactly the same thing. Hope I don't run into trouble (of course, I'm at hour 30, and counting...of the 1st pre-clear)
March 19, 201313 yr Author Grrr, this time i got 99 errors =( Everything take so much time =/ Its time to remove the drive and reinstall the 2tb and think about what to do. Ill try to connect the drive to a usbdock connected to my laptop and see if i can run some error checking software from Seagate. EDIT: Just realized that i got 2 movies (50gb) on my cachedrive that cant be moved to the diskpool because thats not enought free space. Can that cause the errors? Well im removing them and trying to make a paritysync again. EDIT2: I ran SMART extended test and it completed without errors.
March 20, 201313 yr Author Before i disable addons i want to post this last part of the log. Got 6 errors this paritysync and i can see 6 "Tower kernel: attempt to access beyond end of device" Should i still disable addons and try again i will do that. Also i attach the smart.txt from the extended text. /usr/bin/tail -n 40 -f /var/log/syslog Mar 20 03:40:01 Tower logger: ./test/ Mar 20 03:40:01 Tower logger: .d..t...... test/ Mar 20 03:40:01 Tower logger: mover finished Mar 20 04:40:44 Tower kernel: mdcmd (49): spindown 3 Mar 20 04:40:45 Tower kernel: mdcmd (50): spindown 4 Mar 20 04:40:45 Tower kernel: mdcmd (51): spindown 5 Mar 20 04:40:46 Tower kernel: mdcmd (52): spindown 6 Mar 20 04:55:14 Tower dhcpcd[1060]: eth0: renewing lease of 192.168.1.73 Mar 20 04:55:14 Tower dhcpcd[1060]: eth0: acknowledged 192.168.1.73 from 192.168.1.254 Mar 20 04:55:14 Tower dhcpcd[1060]: eth0: leased 192.168.1.73 for 86400 seconds Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967296, limit=4294967295 Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967304, limit=4294967295 Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967312, limit=4294967295 Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967320, limit=4294967295 Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967328, limit=4294967295 Mar 20 05:02:51 Tower kernel: attempt to access beyond end of device Mar 20 05:02:51 Tower kernel: sde1: rw=1, want=4294967336, limit=4294967295 Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967288/0, count: 1 Mar 20 05:02:51 Tower kernel: md: md_do_sync: got signal, exit... Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967296/0, count: 1 Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967304/0, count: 1 Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967312/0, count: 1 Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967320/0, count: 1 Mar 20 05:02:51 Tower kernel: md: disk0 write error Mar 20 05:02:51 Tower kernel: handle_stripe write error: 4294967328/0, count: 1 Mar 20 05:02:51 Tower kernel: md: recovery thread sync completion status: -4 Mar 20 05:02:51 Tower kernel: md: recovery thread woken up ... Mar 20 05:02:51 Tower kernel: md: recovery thread has nothing to resync Mar 20 05:40:00 Tower kernel: mdcmd (53): spindown 1 Mar 20 05:40:01 Tower kernel: mdcmd (54): spindown 2 EDIT: Found this http://lime-technology.com/forum/index.php?topic=25075.0 and will try without addons. if everything is ok without addons can a re-enable them after paritysync? Can it be the seagate that it the problem or any 3tb? smart.txt
March 20, 201313 yr I haven't had any trouble so far; but then again...I don't think I had any "add-ons" in 4.7. I ran a pretty vanilla box.
March 20, 201313 yr Author Just finished paritysync without any errors. https://dl.dropbox.com/u/5314933/Tower-Main2.png Running a parity check now. What to do now... skip the use of unMENU och other addon/extras? Any ideas?
Archived
This topic is now archived and is closed to further replies.