bwhittaker

Update: I ran a parity check twice over the past couple days and each time the parity drive showed up as 3TB with no errors. I figured it was safe to replace the smallest 250GB drive with another 3TB since it appeared that the problem had went away. I physically replaced disk 9 with another of the same brand 3TB drives and when it booted up the parity drive was recognized as a 2TB drive that was "wrong". Its the same serial number so I'm still experiencing the problem. I attached a copy of the diagnostic report. - I don't believe its a sata port issue but I'm using 4 ports on a Gigabye GA81945-PL-G with two 4 port PCI cards for a total of 12 drives. I can get the brands of the cards if that might be the problem. - I originally thought it was the old version of unraid but I upgraded that first so I know that's not the issue. Any more thoughts. I'm thinking of trying the second 3TB hard drive I have as the parity. The only problem is that drive is also recognized as 2TB right now so it probably has the same issue. tower-diagnostics-20150820-2059.zip

The drive was originally used in a windows computer so it was previously partitioned. I did not clear it before trying to use it. I attached a copy of the information from the telnet connection. Tower.txt

Here are some of the diagnostic reports. The .zip file was 237KB so I could not post the entire file. Let me know if I need to attach anything else. Thank you. Log.zip

I have had Unraid 4.5.3 running virtually untouched for a few years with 12 hard drives and 12.5 TB of storage. I was running out of space so decided it was time to replace a couple of the smaller hard drives. I was able to get a couple of 3TB Toshiba hard drives from a friend that was upgrading. My current parity drive was a 2TB Hitachi so I knew that I needed to replace that first. When I installed the 3TB in that location and turned on the server it recognized the hard drive as a 2TB. I did some reading and thought it was possible that version 4.5.3 did not support greater than a 2TB hard drive. I then upgraded the server to version 6.0.1. After the successful upgrade I installed the 3TB hard drive and it was recognized correctly as 3TB. Over two days it did a parity check and everything looked correct. Once it complete I thought everything was good but wanted to wait a few days before replacing the other drives. A day later the power happened to go out and when it checked the parity on boot up the verification failed. It was now recognizing the 3TB with the same serial number as 2TB. I had it run the parity again and it completed correctly though only recognizing the same hard drive a 2TB. Once it completed I decided to run the parity check again. It failed as it recognized the drive now as 3TB. It appears that I do not have a protected array as every time the parity is run it will flip between recognizing the same drive as either a 3TB or 2TB. Has this happened to anyone else? Should I just give up with these drives? Any suggestions are greatly appreciated. Thank you.