PanteraGSTK

Members
  • Posts

    129
  • Joined

  • Last visited

Everything posted by PanteraGSTK

  1. Picked up one from natex. Even got an email asking if it being a dual nic board was OK. Already shipped. Seems legit enough to me. Got the board today. Well packed. No way it could have been damaged in shipping. They used two heavy copper heatsinks to protect the sockets so that's something I won't have to buy if they keep the CPU heat in check. Dual nic board with 6 pcie slots will work great for me since I can merge my two servers into one now. CPUs will be here tomorrow. Can't wait.
  2. Picked up one from natex. Even got an email asking if it being a dual nic board was OK. Already shipped. Seems legit enough to me.
  3. I solved that problem with my purchase in the e5-2670 thread. Picked up two of those and 64gb of ECC registered memory. Just need a board to put them in. I'm excited.
  4. Well, a lot has happened since my last post on this topic. I kept getting parity check errors even after removing the pre-fail disks and starting a new config. Mostly PHP errors that caused the UI to stop working and the parity check to stop. Parity had lots of errors before stopping. I went back to v5 to see if it had the same result. Still got PHP errors, but the check worked (tons of errors) after a new config was done. Read a lot of info on this forum and decided to do a memtest. Didn't take long for tons of errors to pop up. Removed two of my DIMMS and no more errors. Parity check completed on my current v6 config without errors. I'm going to say this issue is resolved. I'm glad I had this issue (sort of) as it was a learning experience and I am now much more comfortable and confident in unRAID. Thanks for all your help everyone.
  5. Will that board work in one of the 24 drive norco cases? Or does it have to go in an Intel chassis?
  6. If I've been reading correctly these boards will not work with these cpus because they're v1. Am I incorrect? The blurb on their site only mentions v2, but v1 and v2 chips share the same socket. Assuming I have the model number correct, Intel lists the e5-2670v1 as compatible with this board http://ark.intel.com/products/56333/#@compatibility EDIT: I tried their shopping cart, and it doesn't look like they ship outside of the US... Not sure if a manual order will be different... Looks like it supports the first get 2670 just fine. The 24 pin and dual 8 pin power connectors are in an odd place, but other than that the $175 price is hard to pass up. Anyone purchased one of these yet?
  7. Had to do it. Just bought 2 E5-2670s and 64gb registered ddr3 1333. Less than $300. Can't beat that. Found a good board, but that can wait a bit. Thanks for the find.
  8. It seems that there are some different views on how to maintain data integrity. Checksum and parity checks go hand in hand, but not all of that seems to be documented as a best practice. Nor is backup verification. What I mean by this is I'm not as seasoned as you guys when it comes to making sure my data stays intact and I think a "data integrity verification" guide of some sort would be a great addition to standard documentation. Plus it would be a good learning experience for me to learn how to maintain my system with as little oversight as possible. If this is documented then please point it out, but it'd be great to find a way to automate this process. Thoughts?
  9. Well, I just tested this and it's not true, a correcting parity check can update parity in case of a read error, and cause corrupted files after rebuilding, this is why I've always did and will continue to do non-correcting checks. By non correcting checks you are referring to a parity check, correct? What is the benefit of this practice?
  10. Great. I'll check the dynamix plugin use that going forward.
  11. I've already made sure my non media file backups are good. The media files on the failing disks are easily recoverable from the original copy so I'm not at a loss there. I don't do checksums, but wish I would have known that was necessary (smart). I will going forward. With the data on those drives that are having issues, it won't be too hard to find out what data is good and what has problems. I'll report my findings once I finish.
  12. One question I didn't think of earlier. If I can't trust parity, how am I going to get back to a "ready" state if I can't trust the data being rebuilt once I replace the drive? Are we talking moving all data off of unRAID and starting over? That won't be fun.
  13. Thank you for looking. Now I know what to look for. I'll get on replacing these drives as I've been slowly doing that, but it seems that I need to do it faster. Thanks again.
  14. Done. Thanks. unraid-diagnostics-20160220-0357.zip
  15. Hi all, I don't post much because unRAID usually just works for me and I don't really run any plugins. For some reason after updating to v6.1.8 I'm having issues. My version 5.0.6 setup ran well with the exception of my cheap SATA controllers giving me fits. I upgraded to a AOC-SAS2LP-MV8 and haven't looked back. While I was upgrading the HBA I beefed up the CPU to an old q6600 I had and put in 8gb of memory. Wasn't needed in 5 so I didn't use it, but i wanted to play around with the new VM and docker capabilities so I figured why not. I'm using an nforce 750 board that never gave me issues when it was my main gaming rig board, but it is still pretty old. I'm not sure if my aging hardware is the issue or if something else is going on, but I can't get a parity check to complete now. It had been a while since I had done one on my v5 setup so I figured it was time. It starts off fast at around 80mbps, but then slowly crawls to a halt with errors in the syslog (attached). I'm not sure what other information you guys need, but I'm worried that v6 may not like my hardware, or there was an issue with the v5 setup I wasn't aware of. unraid-syslog-20160220-0338.zip
  16. After having issues with my P5N-E SLI I swapped it out for my EVGA 750i FTW. Unraid reads the config off the USB without issue, but for some reason the board isn't recognizing all of my SATA controllers at once. All of them work, but with it being a dual slot 16x pcie board only one pcie slot seems to be active at a time. I can move the controllers around in any combination and only 2 are recognized at any given time. All pcie slots on the board work fine, but the two x16 slots won't work at the same time. I think it may be some sort of limitation of he Nvidia chipset. Anyone got any ideas?
  17. Thanks everyone for the help. I've resolved the issue by putting the known working disks in a new config and setting everything up again. It was simple since I don't use any plugins at the moment. No loss of data, parity sync went through without issue. Thanks again.
  18. This is the reason it is recommended to backup your flash drive before any changes are made. If you had/have done that then you could restore the config folder from the backup and put the old drives back into the array and restarted your array and it shouldn't have any problems with size. Agreed. That will be standard practice from now on. Thanks.
  19. Yes, that's what I was trying to do. Just upgrade a drive from 320 gb to a 2 tb drive.
  20. Formatting a drive is not part of the rebuild process. Maybe that is where you are going wrong. When replacing a drive you should not be trying to format the new drive. Yes. Just make sure you assign the drives correctly and most importantly don't put a data drive in the parity slot or unRAID will overwrite the data with parity. Thanks. I'm actually not trying to format, unraid says "unformatted drive" and then has the option to format. No rebuild option is present. I'll grab a screenshot as asked so you can see what I mean.
  21. After reviewing the thread, this question now after all that has already been done to get to this point is very confusing. Any use of New Config even if you include parity will mean you can't rebuild a drive. In fact, it is not clear if you can get to a state where a rebuild would be possible. If you don't mean you still need to rebuild a disk, then I don't know what you mean by this question. The parity drive does not contain any of your data. Thank you for taking the time too look this over. I bought a new drive just in case and have the same issue. I originally started with 5 320 GB drives and 6 2tb drives. I upgraded one of the 320 GB drives with the 2tb drives in question and it just refuses to format and rebuild. Tried everything. Wrote zeros and verified the drives, nothing of note in the smart report. I have not touched anything on the 320 GB drive that was in the working array just in case. I tried to put it back in but it won't let me because it now has a size discrepancy. Can I start a new config with the drives that were working and not use any of my new 2tb drives and rebuild parity? Basically go back to 5 320 GB drives and 6 2 tb drives that I started with to get things back to a working state? I no longer trust my config.
  22. If you are reasonably happy the drive (and its cabling) are OK and simply want to start over then I would: With the array stopped, back up the files on your flash to somewhere outside unRAID (e.g.your PC) so that you can revert to the current configuration if necessary. Make sure you know what the current assignments are (by serial number). A screen shot may be a good idea Use the 'new config' option from the Tools menu to clear the current assignments. Assign your drives as you want them (at this point I would leave off the parity drive). In a New Config state unRAID will add unRAID formatted data drives with existing data unchanged. Start the array and check everything looks as you expect. At this point you can also check that you can format the problem drive Stop the array and assign the parity drive. The reason for not doing it initially was in case you made an error assigning the data drives as assigning one incorrectly as parity would lose its contents. Start the array to rebuild parity. When the parity build has completed then it is worth doing a parity check to validate that parity can be read back correctly. If you really wanted a completely clean start without any plugins then you could have reformatted the USB drive and put a fresh install on it instead of going the New Config route, but that would mean any add-ins or settings relating to shares would need redoing. Still might be worth doing to guarantee a completely clean state. Thanks. I do have a question. Since the problem drive is replacing an existing working drive won't I lose data if I start then new config without parity?
  23. I would agree with you except for the fact that other instances of unraid have no issue with the drive. I've already written zeros to the drive and verified the drive after. No issues. I think there is something wrong with my instance of unraid since a blank config with the exact same hardware has no trouble with the drive. At this point I'm looking for the easiest method to start over and keep my data.
  24. Ok. I put the drive in my windows box and deleted the partition. I then formatted to NTFS just to see. Now I no longer get block read errors, but the drive still won't format. I've attached the latest log and a smart report. smart.zip unraid.zip
  25. All sata and power connections are fine. I even changed to alternate sata ports where other drives are working. Same error. I attempted to run reiserfsck --check and get the following: The problem has occurred looks like a hardware problem. If you have bad blocks, we advise you to get a new hard drive, because once you get one bad block that the disk drive internals cannot hide from your sight,the chances of getting more are generally said to become much higher (precise statistics are unknown to us), and this disk drive is probably not expensive enough for you to you to risk your time and data on it. If you don't want to follow that follow that advice then if you have just a few bad blocks, try writing to the bad blocks and see if the drive remaps the bad blocks (that means it takes a block it has in reserve and allocates it for use for of that block number). If it cannot remap the block, use badblock option (-B) with reiserfs utils to handle this block correctly. This error does not come up if I use a fresh config or move the drive to a different box. I've looked and can't seem to find a straight forward way of just starting my config over as I think something may be corrupt on the flash drive. From what I've found in older how-to guides I just need to put my drives in the same spot and start the array and let parity rebuild. How will that work if I have one drive unformatted? I did a parity check before all this started and had no errors. Please advise.