• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About SimonAG

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well that saves loads of time. Will rebuilding the parity write anything to the array? I didn't think it would.
  2. I have read the guide on this and I have replaced data disks several times without issue. My situation is, I have 8 drive ports only (with all used) and want to replace the parity disk. In brief steps below? 1. stop array 2. unassign parity disk 3. shutdown 4. remove old parity disk 5. put in new disk 6. start up 7. preclear new disk 8. assign to array as parity disk 9. rebuild parity from scratch? Question, if I have a data disk fail during the parity rebuild, would it be possible to put the old parity disk back in and rebuild t
  3. I did post about my build buying decisions back in 2018. I have since bought a rack, so I thought I would share a photo and current specs. Unraid Logic Case SC-43400-8HS Gigabyte GA-Z87X-UD4H Intel 4670k 3.8ghz 8GB corsair unbuffered 8 Port SilverStone ECS04 7x 6TB Seagate ST6000VN0033 1x 4TB WD 550W Seasonic Focus Gold PSU 2x 80mm back Noctua Fans for Case 2x 120mm front fan 1x 140mm front fan Pfsense in-Win IW-RF100 Supermicro A2SDi-4C-HLN4F 4gb 2133mhz Unbuffered 60gb SSD TP-LINK CAP1750 WAP 8
  4. I read the article on the wiki about cache disk and I am not sure if i can benefit? At the moment I have 8x6tb connected over gigabit with a high spec HBA card and I think it is 8gigabit HBA and I get 112mbyte second read and write with file transfers. I think 112mbyte a second might be the gigabit network limit. If i buy a 500mbyte read and write SSD. Will I benefit? I don't run any dockers, just use it as a NAS through my Windows desktop PC and media center.
  5. I replaced the drive and rebuilt from parity without issue, thanks for your help. Now just have to solve the temperature issue so i can schedule the parity check!
  6. Thank you for your help Frank! I will report how i get on.
  7. I know I should have done more but I have some heat issues in my current case and it is worse when I run a parity check. I have been waiting until the temperature cools down a bit to run it again. I have been meaning to address the heat issue as well by buying a small rack and fixing ventilation. Problem is I think the case design is prone to high temps no matter what I do. Which was clear early on. I don't think the heat caused the smart errors though as disk 7 was always at normal temp, it is just disk 2 and 3 that get hot. How crucial is it to run a parity check before swapping
  8. I am about 16 months in to my unraid setup. I bought 4x6tb Seagate NAS drives 16 months ago when I bought my unraid hardware and I also had 4x4tb Seagate non-nas drives. All four of the 4tb drives are 4 years old with one approaching 5 years old. The 5 year old one has just come up with Reported Uncorrect Smart error at 50. Ideally I would replace all four but if i can get away with replacing one at a time that would be ideal cost wise. Parity is currently 90 days old. Should I run a parity check again before replacing the drive with a new 6tb drive? (parity is 6tb) o
  9. This was not a build thread more a question, I might as well give a conclusion in the case that it might help someone at the same predicament. I ended up using my desktop motherboard (4670k ddr3) as my unraid with a 8x hotswap 4u rack case and buying a new ddr4 microatx motherboard for my desktop PC. This worked out well. I used the existing 4x4gb drives that I had in my desktop PC and moved those to the NAS after the new 4x6gb had been setup with 1 parity. Allowing me to transfer across existing data to the NAS. Adding each disk was no problem, I added the last two disks at the s
  10. I have one parity drive. I have been reading the wiki more and it seems I have two options. One I can remove the disk from the array and rebuild parity, at a risk, if a second disk fails during parity rebuild i could lose data. Second option is the shut down the array and remove the faulty disk and only turn it back on once i receive the new disk back from RMA. Downside I will have no access to my data until the new drive is installed. I am thinking option two might be the best option because I can survive without the data for a week.
  11. While copying data off it has increased to 128, so glad I am RMA the drive now. I ended up using screen and MC to do the copy as unbalance did not have the correct permissions and wouldn't accept a different account. Any ideas on best method for removing the disk? Considering the replacement is not going to be available for a week?
  12. Thanks! the unbalance plugin solves the copying files issue nicely. I read the wiki on removing drives.. I have to post the faulty drive off and then they will confirm the issue and then they will send a new drive. That could take a week. Should i shut it down and remove the disk and wait until the new disk arrives before starting it up again? Should I remove the disk from the array completely. Considering it had no data on any longer, what is best option for this scenario?
  13. What is the easiest way to move all the data off that drive? Some of the folders contain data that is from shares that are spread across multiple drives, so it could be time consuming to copy at the share level. Can I create a share at the disk level? Or maybe there is a quick way to move all the data to other drives in the array? I would rather format the drive before sending it off.