March 3, 201115 yr I was replacing my non-failed 1TB drive with a new 2TB, freshly precleared drive. After almost 1 day it says it will take another 2 days to get it done. I assume there is a problem, but I don't know what or how to stop, fix, etc. at this point. Although, I can sometimes get to unmenu, I can not get to the main web interface anymore. I have attached my syslog from earlier. Thanks, syslog-2011-03-03a.zip
March 3, 201115 yr I'm sure someone will come along with something more useful, I seem to remember that when I replaced at 1TB with a 2TB pre-cleared, it took about 12 hours to complete.
March 3, 201115 yr Author I have attached a screen cap of the unmenu screen in case something stands out. Thanks.
March 4, 201115 yr Author I am working on my build config... I can't even get to unmenu now. Its running out of memory and killing most of my processes. Can I just kill the server and put the other drive back in for now? I assume it wouldn't quite be that simple since I wouldn't want it to start rebuilding on that old drive. Edit - or I have another 2TB drive I could try... Edit 2 - Here's my build... Case: Coolermaster Centurion 590 Drive Cages: Supermicro 5 in 3 hot swappable drive bays P.S.: CORSAIR CMPSU-450VX Motherboard: ASUS M4A785-M AM3/AM2+/AM2 AMD 785G HDMI Micro ATX AMD CPU: AMD Athlon X2 BE-2400 2.3 GHz Memory: 2GB: A-DATA 2GB (2 x 1GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model AD2U800B1G5-DRH HDD Controller: Supermicro AOC-SASLP-MV8 (installed, but not poplulated) HDD (all WD,): Parity: 2TB EARS Disk 1: 1TB EARS Disk 2: 1TB EADS Disk 3: 2TB EARS (currently rebuilding, was a 1TB EADS) Disk 4: 1TB EADS (all EARS – 4k aligned) Flash: SanDisk Cruzer 2GB unRAID plus: 4.7b1
March 4, 201115 yr You can stop and put the old drive back in. The old disk will not be recognized and the array will not start automatically. Add the old drive in its slot. Then type initconfig at the command line. Start the array and let parity rebuild. Once the array is working run a parity check. Then update to 4.7 final. Check parity again. At some point, get a SMART report on the new drive.
March 4, 201115 yr I'm sorry to inform you that your motherboard is incompatible with the Supermicro AOC-SASLP-MV8 card. I did extensive testing with the two and was unable to get them to play nice. See this thread for details. I expect that this is the source of your troubles. Since there are no drives on the card yet, I recommend removing the card and trying the rebuild without it.
March 4, 201115 yr Author Thanks for the reply. Would it be better to put a different 2TB in and rebuild it or just put the original drive back in? My syslog was filled with red, anything stand out? How should I go about stoping the rebuilding process since I can't use the web interface? @Rajahal - What would be the proper way to stop and rebuild? I'm still new and don't want to mess up.
March 4, 201115 yr The current drive will probably work; just not on that card. Stop the array. None of the other drives are being written. They are only being read. Shutdown, remove the card, and attach the current 2T drive to a SATA port.
March 4, 201115 yr I don't know how to stop the rebuild without access to the web interface. I think you'll just have to do a hard shutdown. I did see some errors in the syslog, but nothing that I recognize that would allow me to offer educated advice. Here's what I would do: 1) Hard shutdown the server. The old 1 TB drive is still healthy, so you aren't putting your data at risk. In a worst-case scenario, you can put it back in and have your old array back. 2) Remove the SASLP card (following proper ESD precautions) 3) Boot the server as is (with the 2 TB still installed, and the old 1 TB still uninstalled) 4) Start off the data rebuild again (it will start over from the beginning) 5) Monitor the speeds, they should be normal 6) If the speeds aren't normal or if the server freezes up again, then seek further help here. Finally, I would start shopping for a new motherboard. That motherboard caused me days and days of grief, so I recommend replacing it. The Biostar A760G M2+ is a great replacement that will work with all your other components, including the SASLP card. As long as you are content with just the 6 ports on the Asus board, you can continue using it. However, if the board is still new enough that you are able to return it for a full refund, then I highly recommend taking that route. Also, there's no such thing as unRAID 4.7b1 at the current time. I assume you are just running 4.7 (which is fine).
March 4, 201115 yr unRAID 4.7b1 was released on Jan 14. I suggest that you upgrade to 4.7 final once the array is stable.
March 4, 201115 yr Author Thanks all for your help. Sucks about the MB. I just bought it a month or so ago since my GigaByte board has HPA issues. Thanks for the recommended biostar board. I was able to preclear (2) drives at the same time via screen on that card. However, one took a long time. I redid that drive on that card by itself and it did fine, normal time. BTW, there was a 4.7b1, here's the header from the release notes. The only reason I haven't upgraded yet was 4.7 final didn't change from 4.7b1, just name/version change. unRAID Server 4.7-beta1 Release Notes ===================================== Thanks again.
March 4, 201115 yr Author Took out the card, rebooted and it when I pulled up the web interface it had already started the data rebuild. Now it is going even slowe, like 300k. So I think I definetly have a different/another problem. I was thinking about trying another drive. Should I just shut down, switch drives and try again? Or is there a different procedure?
March 4, 201115 yr Try clearing the MBR with dd if=/dev/zero count=100 of=/dev/sdX where X is the drive number. or run preclear_disk.sh -z /dev/sdX which zeros the mbr Then start to rebuild again. If it still goes real slow post a syslog and SMART report.
March 4, 201115 yr Yes. Cancel the rebuild and stop the array. After the MBR is clear and you restart the array the rebuild will start over again.
March 4, 201115 yr I'm sorry to inform you that your motherboard is incompatible with the Supermicro AOC-SASLP-MV8 card. I did extensive testing with the two and was unable to get them to play nice. See this thread for details. I expect that this is the source of your troubles. Since there are no drives on the card yet, I recommend removing the card and trying the rebuild without it. God, I wish I would have ran into your thread last week. I am now outside of my return window for my Asus mobo. Very sadened by this, as my next purchase was the Supermicro board... supersadface.
March 4, 201115 yr Author Thanks! It is now rebuilding at an average of 27-30 MBps, so I assume that is normal. I wish I new what the deal was. Maybe it was the Supermicro card. I would have never thought clearing the mbr would have fixed it though. Thanks again for everyone's input. After this drive finishes rebuilding, I will mark this thread as solved.
March 4, 201115 yr Author I am at work now, but I assume that the rebuild will be done soon. Do I run /root/mdcmd check NOCORRECT when its done?
March 5, 201115 yr Author Well, after about 20 hours, it is only about 63% done. Now keep in mind that I haven't rebuild before so I really don't know what to expect. Right now all the drives are spun down except the parity and the drive being rebuilt. It looks like its going from 4 MBps to less than 20 MBps. Still seems kind of slow to me.
March 5, 201115 yr That doesn't sound right. All drives are involved in a data rebuild, at least for the first part. If your parity drive and the new drive are much larger than the rest (say 2 TB when the rest are all 1 TB) then what you described would be normal, as once the 1 TB drives were read all the way through they would spin down. However, that last part involving only the two larger drives should be faster, not slower. Post a syslog.
March 5, 201115 yr The syslog seems normal to me. You are running add-ons, I saw at least cache dirs, you could try and stop the add-ons and see if that helps. I would stop the rebuild if its running, stop any add-ons, and start the rebuild again. The rebuild started at 27-30MBps and that is still slow but passable. It really should be almost twice that amount.
Archived
This topic is now archived and is closed to further replies.