I have HP N54L with 4 disks (1 parity and 3 data drives). 2 data drives have been there for a long time, they are working fine and I just added 3rd data drive and I did the pre-cleaning on the disk. I did everything I could but the 3rd data drive is not showing up. What did I do wrong? Thank you for the help.

I have HP N54L with 4 disks (1 parity and 3 data drives). 2 data drives have been there for a long time, they are working fine and I just added 3rd data drive and I did the pre-cleaning on the disk. I did everything I could but the 3rd data drive is not showing up. What did I do wrong? Thank you for the help.

You have to add it to the array. Stop the array. Select the drive in the dropdown. Start the array.

I did stop the array but I didn't see any drop down boxes to select the drive. What is that I am missing? I am attaching the screen shots..

 

In the UnraidMain (attached) I don't see any drop down box. I did stop the array and I haven't seen any drop-down boxes. In the defaultview (attached), in the bottom of the list, it shows new drive with + sign but I don't know how to add this to array. Any help is appreciated. Thank you guys.

 

Neither of those screen shots shows the array as stopped.

 

Stop the array, click an empty slot and take a screen shot of that.

Are you using a paid version? Free only supports 3 devices including parity.

Smart.. I am using the free version that might be the reason I don't see another drop down box for new drive. Please check the attached picture of the unraidMain view. Thank you guys. You guys are the best.

 

 

I am using the free version that might be the reason I don't see another drop down box for new drive.

 

That is the reason, time to buy a license.

 

 

Just got the plus version. Thank you and you guys are amazing.

You should upgrade to V6. If you don't care about running apps on your server, V6 has new features that make it a better NAS. If you do care about running apps on your server, V6 does it much better. And it is easier to support for all of us because that is what we have.

Thank you for the suggestion. I just did it. It was an easy upgrade and looks like everything worked fine. Is it normal, after upgrading to v6 does it do a parity validity? It is doing it to me. I want to make sure that it is okay.

 

I also have one question, what is the best practice to setup shares, I had public access (it worked fine) and now I am trying to secure them so anyone hacks to my network will not have access to NAS. I created a specific user with password and etc. From windows when I try to map the NAS it asked me user name and password and I gave user name and password that I created in unraid and it doesn't seem to work. I am sure I am missing something. Any help would be appreciated.

Thank you for the suggestion. I just did it. It was an easy upgrade and looks like everything worked fine. Is it normal, after upgrading to v6 does it do a parity validity? It is doing it to me. I want to make sure that it is okay.

 

I also have one question, what is the best practice to setup shares, I had public access (it worked fine) and now I am trying to secure them so anyone hacks to my network will not have access to NAS. I created a specific user with password and etc. From windows when I try to map the NAS it asked me user name and password and I gave user name and password that I created in unraid and it doesn't seem to work. I am sure I am missing something. Any help would be appreciated.

I would let the parity check finish, but it is not normal. You get an automatic correcting parity check anytime unRAID thinks the array wasn't stopped before shutdown. This is in case there are any incomplete parity updates.

 

Flash has a file config/super.dat that stores your disk assignments. It also records whether the array is started or stopped. If unRAID boots up and that file says the array was started then it will do the automatic parity check. If you did stop the array before shutting down and it did the parity check anyway then you may have had corruption on your flash that prevented that file from recording that fact. unRAID V6 also attempts to fix flash corruption when it boots so it is probably OK now. Another way this can happen (the way I discovered it in fact) is if you make a backup of this file while the array is started by copying it over the network and then restore that backup. The flash is still accessible over the network even after you stop the array so you should stop it first then make the backup then start it again. Be very careful with super.dat backups. More than one user has restored an old backup that told unRAID that one of his data drives, which was a reused parity drive, was still parity and it started overwriting it with parity. When in doubt it is safer to delete the file. unRAID will then make you reassign all your drives.

 

While we're here, the recommended way to get diagnostic information to the forum on V6 is to go to Tools - Diagnostics and post the complete zip file that results. This zip contains the syslog, SMART for all drives, and other things that can be useful for troubleshooting. You can post one now if you want and we can see if there is anything to tell us why the parity check started.

 

For your security/login issue, if you're on Windows (I think Mac calls it a Keyring), go to Control Panel - Credential Manager and delete any stored credentials for your server. This will cause them to be renegotiated. Windows will only allow one login at a time to another computer so if it already had one another one won't work even if it asks you to login. See this old thread for more details about this.

Thank you for all the details. I can see that you are very kind. Here is the diagnostics zip file. If it is too much for you, please give me pointers I can get into the details. I have already asked you too much. Have a great day.

 

tower-diagnostics-20160124-0937.zip

BTW, I cleared the previous credentials from credential manager and it still says access denied.

 

I just made my share private and created a user with password to share the SAN share. Did I do anything wrong? Do I need a SAMBA? May be after my upgrade, do I need to re-install SAMBA plugin? I don't want to go through plugin route because it can bring instability to UNRAID. What is the best way to add extra components? I am thinking Dockers. I would take an expert advise before I do anything. Thank you.

Your syslog makes me think you must have started with a clean install and then assigned your drives. Then if you don't check the trust parity box it will start a parity build, not a parity check. Is this what happened?

 

I don't understand what you mean in your latest post. SMB is already installed and as far as I know it has never been a plugin on any version since it is critical to the NAS functionality. Share security takes place within the context of a specific protocol, such as SMB or NFS. When you said you made the share private, you must have made it private in SMB or NFS or something. Maybe post a screenshot showing the share setting and its private setting you made.

Yes sir, you are correct. I had another flash drive and went ahead with v6 on the new flash drive and replaced the old flash drive when ready, which makes this system upgrade easy task because we can always go back to the old flash drive in case of any issues but I hope that doesn't arise.

 

I didn't check the trust parity box, I guess I might have missed it. I am not able to try anything on shares until the system finishes the parity build. I will share the share details as soon as possible. Thank you for all your help. You guys rock!!

Parity was rebuilt and my shares are private now. Looks everything is good. The only challenge is the parity drive is Toshiba 5TB, it is operating at 39 degrees. Is that normal?

 

Data drives are at 32 and 27 degrees. Thank you.

That's fine, anything between 30 and 40C is normal, more than 45C I don't like, but dangerous is usually >55C.