[SOLVED] Issue with new Hard drive to array

[Enjawd]

Hi Guys,

 

Im trying to put a 6TB hard drive to my existing array, which consist of 1*6Tb for parity an 1*6Tb for disk1. I notice that once i assign the new disk to disk2, i dont see it being reflected in the GUI, and in dashboard it's status is unassigned. There is no option for me to do any format.

 

Please help

 

*Update: Found out i've a bad drive. 

 

 

Edited May 25, 2021 by Enjawd

[John_M]

It looks as though it has dropped off-line. Post your diagnostics: Tools -> Diagnostics and attach the zip file to your next post.

 

 

[Enjawd]

On 5/21/2021 at 10:20 AM, John_M said:

It looks as though it has dropped off-line. Post your diagnostics: Tools -> Diagnostics and attach the zip file to your next post.

 

 

You might be right, i noticed the clearing was pause halfway probably around 70ish% and i had to manually resume it. I did a search and tried the preclear plugin method seems fine but once i assigned it to disk2 it doesn't seems to work.

 

 

Edited May 25, 2021 by Enjawd

[itimpi]

Disk2 has definitely dropped offline according to the diagnostics, and this results in an error in the syslog occurring any time you attempt to do anything with it.

 

since the disk is offline there is no SMART information in the diagnostics to give an indication of its health.

 

I would suggest you power off the server, carefully check the power and SATA cabling for disk2 and then power on the server again and as long as the system sees disk2 take new diagnostics and post them so we can see if disk2 looks like it is healthy or not.

[Enjawd]

6 hours ago, itimpi said:

Disk2 has definitely dropped offline according to the diagnostics, and this results in an error in the syslog occurring any time you attempt to do anything with it.

 

since the disk is offline there is no SMART information in the diagnostics to give an indication of its health.

 

I would suggest you power off the server, carefully check the power and SATA cabling for disk2 and then power on the server again and as long as the system sees disk2 take new diagnostics and post them so we can see if disk2 looks like it is healthy or not.

Thanks @itimpi, ill give it a try swapping the Sata cable and power connector later today.

 

Just to add on, from the “unassigned devices” plugin, its seems to be able detect the drive.

 

 

*Update: swap the cables and power connector, currently on doing its clearing thing. Probably need another 7-8 hours before the next update. @itimpi should i get the diagnostic now or after clearing process?

Edited May 21, 2021 by Enjawd

[itimpi]

Unassigned drives can handle drives dropping offline and re-appearing while the main array cannot.

[Enjawd]

On 5/21/2021 at 8:13 PM, itimpi said:

Unassigned drives can handle drives dropping offline and re-appearing while the main array cannot.

Gday @itimpi, seems like its the same issue(clearing would stuck in around 80+% and i need to manually resume). Could it be a faulty hard drive? I notice theres quite a few error in the smart log for this drive.

 

*attached new diagnostics 

 

 

Edited May 25, 2021 by Enjawd

[John_M]

It's a connection problem:

 

May 22 03:02:18 Tower kernel: ata2: COMRESET failed (errno=-16)
May 22 03:02:18 Tower kernel: ata2: hard resetting link

 

The SATA link is reset repeatedly, reduced in speed and eventually dropped. Did you replace the cable? Since Disk 2 is offline there's no SMART report for it in your diagnostics.

 

Unrelated, there's a huge amount of this in your log:

 

May 22 03:02:34 Tower vsftpd[30644]: connect from 58.222.191.157 (58.222.191.157)
May 22 03:02:36 Tower vsftpd[30652]: connect from 58.222.191.157 (58.222.191.157)

 

Unless you recognise the IP address as friendly, someone in China is trying to hack you.

 

[Enjawd]

2 hours ago, John_M said:

It's a connection problem:

 

May 22 03:02:18 Tower kernel: ata2: COMRESET failed (errno=-16)
May 22 03:02:18 Tower kernel: ata2: hard resetting link

 

The SATA link is reset repeatedly, reduced in speed and eventually dropped. Did you replace the cable? Since Disk 2 is offline there's no SMART report for it in your diagnostics.

 

Unrelated, there's a huge amount of this in your log:

 

May 22 03:02:34 Tower vsftpd[30644]: connect from 58.222.191.157 (58.222.191.157)
May 22 03:02:36 Tower vsftpd[30652]: connect from 58.222.191.157 (58.222.191.157)

 

Unless you recognise the IP address as friendly, someone in China is trying to hack you.

 

Hi,

 

hmm I replace using another cable but might be a old one I found somewhere … let me get a new one and try again.

 

hmm I don’t recognise that ip. Any idea what they are trying to do from logs or just trying to access my unraid. Notice its at 3am as well 😳  … i’ve check my router connection and my tower is not open up. UPDATE: i think it might be FTP…i have closed it. Probably trying to access from there.

Edited May 22, 2021 by Enjawd

[John_M]

8 hours ago, Enjawd said:

it might be FTP

 

It definitely is ftp. There's a clue in the log entry. If you don't need ftp you should disable it and definitely don't forward a port on your router. For more information see here.

[Enjawd]

So I’ve change to a brand new sata cable. Did the clear and i notice the issue might still be there, stuck at 80+% and had to resume manually 

 

I suspect my hard drive could be faulty, as previously the sata cable and port was use for my ssd which act as parity drive. Which later i remove it and replace it the 6tb hard drive

 

attached diagnostic, noticed this time there are a lot of disk0 read error in logs

 

 

Edited May 25, 2021 by Enjawd

[Enjawd]

52 minutes ago, John_M said:

 

It definitely is ftp. There's a clue in the log entry. If you don't need ftp you should disable it and definitely don't forward a port on your router. For more information see here.

Yeah thanks @John_M for the advise. Disabled the FTP option.

[John_M]

2 hours ago, Enjawd said:

I suspect my hard drive could be faulty

 

There is still no SMART report - the disk dropped offline before you captured the diagnostics. So I can't tell. Have you checked the power to the disk?

 

2 hours ago, Enjawd said:

Disabled the FTP option.

 

Are you sure? Incoming connections are still being made:

 

May 22 12:54:19 Tower vsftpd[21347]: connect from 167.248.133.53 (167.248.133.53)
...
May 22 16:02:41 Tower vsftpd[1916]: connect from 104.206.128.22 (104.206.128.22)

 

[Enjawd]

40 minutes ago, John_M said:

 

There is still no SMART report - the disk dropped offline before you captured the diagnostics. So I can't tell. Have you checked the power to the disk?

 

 

Are you sure? Incoming connections are still being made:

 

May 22 12:54:19 Tower vsftpd[21347]: connect from 167.248.133.53 (167.248.133.53)
...
May 22 16:02:41 Tower vsftpd[1916]: connect from 104.206.128.22 (104.206.128.22)

 

Hmm, from the logs i still see the comreset error on ata2 several times. I’ve try using another sata power connector as well. I’ll try to plug in another spare 1tb hard drive to isolate the issue, maybe its just a bad 6tb drive.

 

As for the ftp,  not sure why did the service changes back to enable. I’ve just disable them again. 

[JonathanM]

Remove the port forwarding rule on your router.

[Enjawd]

Alright, weirdest thing just happen. My (Disk2)ata2 came online and parity drive just died. 

tower-diagnostics-20210523-0806.zip

Edited May 23, 2021 by Enjawd

[John_M]

That was the first opportunity to see Disk 2's SMART data. It's not a happy disk. It has a lot of reallocated sectors and a lot of pending sectors. You need to replace it. From your original post you said you were trying to add it to your existing array so it's unlikely to contain any useful data. That's just as well because your Parity disk is not in a good state either. I'd replace that, too. Fortunately, your Disk 1 looks healthy.

[Enjawd]

Ahhh, so its seems like either way both my disk2 and parity drive are in bad shape? I did noticed my parity drive having error on smart awhile ago though….

 

And yes, I’m adding disk2 as a new drive to the array. Originally it was only on 1 parity and 1 hard drive.