jtech007

If I put it in the test server and it comes up with the same error as my new disk3, can I fix that drive as well with the check disk and put it back in the array? I think this would cause an issue with the parity, but just covering all my bases.

Attached tower-diagnostics-20160226-2036.zip

unRaid is back up now, all disks are recgonized. I think I might have an issue with my backplane, so for now the drives are connected to the SATA ports on the MB. Now disk 3 (the one with the issue on the old drive and the new one) is reporting Device is disabled, contents emulated. This was the same error that I had with the first drive that I replaced. Also wanted to note the history of this problem in case there was a step that I missed or was not noted previously: Original 4TB drive showed as Disabled/Emulated. Thought the drive was going bad so I bought a new 4TB drive, pre-cleared it, removed the old drive and put the new one in it's place. Started up unRaid. It gave me the option to rebuild the disk, I did NOT format the drive, the drive was rebuilt and reported the rebuild went fine with no errors. I then ran a parity check again to make sure nothing was going to show up missing. New drive has been in the server about a week and then I noticed the Photos share did not have any files at all, completely empty. That's when I started this thread, now after a temp fix for connectivity I am back where I started with the new disk saying Disabled/Emulated. I have attached the smart report for the drive with the issue. What would be the best course of action at this point? Smart_Report.txt

So I have a new problem. Went to pull a smart report for the new drive. Did that but the report was empty and it said the drive did not exist/not found. Upon reboot (to see that would get the drive to show up) three of the five disks in the array are not being found by the motherboard on bootup of unraid. Only the parity drive and one of my 4TB drives is being recognized. This leads me to believe that I have an issue with the M1015 or the Backplane on my Supermicro chassis. I also now wonder if that was the cause of the original drive showing up as bad as it was not being recognized or had a bad connection which caused the errors that the new disk is experiencing. I have another M1015 and also have a lot of SATA ports on the MB so I can remove the card if need be to see if that fixes the problem. So new questions: 1: Once I figure out the connectivity issues, should I attempt to put the old drive back in the array and see if it will work? I imaagine this might cause an issue with the parity, but wanted to see if it was a possibility. 2: Should I try to put the old drive in my test server and see if it will come up as good and working? My goal at this point is to see if the old drive was indeed good after all and the issue was cause by other hardware and not a failed drive.

Good to know, I will get the report later today and hope for the best. Thanks again for everyone's help!

Is that something that would have carried over from the old drive? Or maybe I have a bad cable or controller card that is causing the issue? I can post a report when I get home tonight.

You should never have only one copy of irreplaceable files. Make a backup plan. I was actually working on making that happen when the drive issue came up. I have some of the photos on other drives on a local machine, but not all of them.

Have you checked that the disk is on the included / excluded list in Global Share Settings and / or Specific Share Settings? Global Share Settings: Included disks=All / Excluded Disks = None Specific Share settings: Included disks=All / Excluded Disks = None

Thank you for your help, hopefully the diagnostics file will reveal what is happening. tower-diagnostics-20160225-0803.zip

Had a bad 4TB drive that I replaced with the same model 4TB. Pulled the old drive, set it aside, pre-cleared the new drive, installed it and started up unRaid. It detected the new drive as the one to replace the old one and gave the option to start the array and re-build the drive. Did that, all seemed to go well but I have a whole share that has no files in it. Of course it's all of my photos that I cannot replace. The total TB used and unused is exactly the same as it was before I replace the drive. Is there anything I can do with the old drive to get the data off of it or what did I do wrong with the new drive during the re-build to cause it to not re-build the drive fully?

They have two of them listed at the $289 price currently: http://www.ebay.com/itm/Supermicro-24-Bay-Chassis-SAS846TQ-Server-AMD-QC-2-2GHz-16GB-H8DME-2-BL002-/172098368315?hash=item2811dcb33b:g:L8cAAOSw-zxWpr8k Bad part is they do not come with rails. If they are like the older ones they sold years ago those rails are only available in Europe. I bought two sets from a German supplier but had to use a proxy buyer as they would not ship to the states. Probably best to check with Tams before ordering to see which rails this chassis takes if you require the server to be in a server rack.

Thank you for the quick reply Jon. I will order an AMD card and see how it goes!

If I am reading this correctly you say that AMD standalone cards do not have this issue but NVIDIA ones do? If so, I am glad I looked at this thread as I have a new NVIDIA card in my cart on Newegg to use as my new pass through card for my unraid box. My mobo does not have onboard graphics, should I be shopping for an AMD card then?

I also had Kernel issues when added a second box as a test and redundant server. My were of the "Panic" variety which appears to be different than yours. I ended up having Limetech switch the license over to another thumb drive as the one I was using on 5.0 would work great, but the new 6.x variants would cause the Kernel panic. Curious to see if you can reproduce this same error if you put the new install (thumb drive) in your existing/working setup and see if it reacts the same way. Edit: I also had an issue of a similar variety that was resolved by booting off of a different USB port. If you have 3.0 and 2.0 try the "other" one.

Looks like you installed some of PhAzE's plugins on your Cache drive.

Can you find the server via it's IP address? If not, can you connect to the server via SSH? You can also try to ping an external website from the console to see if the server is setup correctly. Type root at the login prompt and then type ping google.com and see if you get packets.

Could be a bios limitation as it sounds like and older mobo. Squid might be on to something with changing the boot drive type to see if it will recognize the 8gb sticks differently than the 2gb ones.

http://lime-technology.com/forum/index.php?topic=9025.msg86083#msg86083

Two things that worked for me in the past: 1: Get rid of any USB headers or extension cables and plug directly in to the MB. 2: Use a USB 2.0 ports instead of a 3.0 port or vise versa if your MB has both. Both solved my problem when the drive would not boot on my main server.

Upgraded from 6.1.1 to 6.1.3 via the WebGUI with no issues. All VM's and Dockers running fine.

I've just gone back into it and I can't change it either. I definitely typed it in manually yesterday, so maybe start again and see if it will let you do it initially. Other than that can't think of anything else.. For some reason on my first try the network type was set to Bridge. I upgraded my cache drive tonight and re-installed the container and the default is Host and I was able to enter the correct Ip for the server. I have the backend setup now (I think) and just need to setup the frontend plugin on Kodi tomorrow. Thanks again for all your help, hopefully I will be watching TV tomorrow!

Anyone have an idea on this one? All I can pull up are the 172 and 127 ip's. My server starts with 192 I just type the IP address in... For some reason I cannot type anything in to that field. The other ones will let me change them, but that one only allows the two that already exist.

Anyone have an idea on this one? All I can pull up are the 172 and 127 ip's. My server starts with 192

Ok, container is running, RDP in to the desktop and now have an issue where I cannot set my Unraid ip and the IPv4 Local Backend address. I didn't run into this when I ran myth in a unbuntu VM, it found the IP right away.

By default it was set to 80 when I installed it. It looks like it opens up 10 total ports and 80 is one of them. I will change it and see what happens, thanks! Edit: I changed it to 81 and now it is running, thank you again!