June 13, 20188 yr The last time I ran a parity check is like ~35 days ago, shall I execute a manual parity check w/o corrections before adding the new HDD, or add the HDD 1st, and then run the parity check? Thnx
June 13, 20188 yr Hello - I would run the parity check now. It's a good idea to know the array is healthy before making changes.
June 13, 20188 yr If you are putting the new hard drive in a currently unoccupied logical slot, then the risk is pretty low, especially if you have drive cages where you don't have to get inside and rewire things. If you are going to be mucking about with motherboard or HBA and power connections to make the addition, then things can get out of control quickly if you fire it up with drives not solidly connected. Either way, a clean parity check and good smart status on all your current drives is a good way to start any config changes.
June 13, 20188 yr Author @tdallen @jonathanm Thnx to both of you for the help... Yes I still have enough slots to add more HDDs to my unRaid system, and I don't need to open the chassis or touch any cables...But what both of you said does make more sense, so I started a non-correcting parity check and if everything was alright I will be adding the hard drive... However, I have a question. Once someone here said although my system supports hot-swap (My method is to stop the array, add the HDD, assign the HDD, then start the array) basically he said he would prefer to power down the system entirely, and then add the HDD...What do you guys think of this? Thnx
June 13, 20188 yr 54 minutes ago, Mat1926 said: However, I have a question. Once someone here said although my system supports hot-swap (My method is to stop the array, add the HDD, assign the HDD, then start the array) basically he said he would prefer to power down the system entirely, and then add the HDD...What do you guys think of this? Hot swap "should just work". However... my personal preference is to power down. Why? Partly because I know it will work, and if something is wonky on the restart, it's one less part of the equation to troubleshoot. If something goes sideways during a hot swap, was it the hot swap part, or did something else cause it? The array has to be stopped anyway, it's only a couple more minutes to power down all the way and restart. It's not like you are in a high availability environment where the services are expected not to be down. Because of the way unraid loads and runs, it's a fresh install on every reboot anyway, so why not replicate the next full power cycle? Hypothetical scenerio... Hot swap (insert) the new drive, everything is peachy, array and all services come back up no issues, but the next time the array is shut down and powered off, it won't boot. What happened? Did the BIOS pick up the new drive and decide to mangle the boot order? Is the PSU just on the edge of being powerful enough to cold fire all the drives? Now you have a troubleshooting session with no clear way forward, and unraid is expecting the drive to be there for parity to be valid, so you shouldn't just pull the drive and retry the boot. Same scenario with a no boot after a powered down cold addition, clear troubleshooting step is to unplug the new drive and see what happens.
June 13, 20188 yr Author @jonathanm Got it all. I will power down the system, and then add the HDD.... Thnx
Archived
This topic is now archived and is closed to further replies.