Hello all! 

I am a new user running a licenced version of Unraid 6.5.3. I am trying to do this build on a budget and I am having issues. I started with  4TB external hd for my parity drive [for now, to be replaced with internal soon] several older smaller  SATA drives kicking around from old working builds. I bought a 240 SSI drive and added it as my cache drive. So far so good.

 

I like a greenhorn beginner just fired it all together and "let 'er rip"! The damn thing worked! Right out of the gate. But, I was still learning so played around adding dockers and plugins etc. Then I had a hard drive disappear. [Red x error] Reboot, [not reading the manual yet of course] and it re- appeared ok. So I read up and suspected SATA cables. Mine were out of old builds and not connecting as tight as I would have liked. Replaced SATA Cables. Ok? nope. 

 

I got a stable parity for a short time and then disk errors. I replaced all my disks with KNOWN GOOD units. I still got disk fails. I am thinking I have a hardware issue but I don't know how to tell or diagnose. I also can't sit in front of the machine for days as I drive truck and would like to get the damn thing stable and working and not touch it for a while!! ?

 

 

I have attached the log file for your inspection. I am a rank amature so education along with the public flogging is appreciated! 

 

Thanks in advance,

Zippy

NOTE: I drive truck so I will be AFK for a few hours but back this afternoon. 

 

 

 

tower-diagnostics-20180821-0534.zip

14 minutes ago, 99Zippy said:

I started with  4TB external hd for my parity drive

 

Do you mean your parity drive is connected by USB? Array disks connected by USB are often so problematic that I don't know of anyone who is actually trying to make that work. Typically people will "shuck" an external drive to use the SATA drive inside it in their array.

 

Disk 4 is disabled and will have to be rebuilt. Unfortunately, it isn't even reporting SMART so it has probably dropped offline.

 

Disk3 also has a lot of CRC errors.

 

Shut down. Check all connections, power and SATA, both ends. Reboot and post another diagnostic.

Not directly related to your problem, but you will get far better performance from your drives by switching the BIOS mode for the SATA controller from IDE/Legacy to instead be AHCI

00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390]

 

Thanks Trul;

 

 

 

I did not know that! [USB drive in array] I have made a few other errors along the way. I have pulled all data off this box and want to have a do-over. Is that possible? If it is, Here is how I propose to begin this time.

 

No USB drives.

3TB Drive as parity.

3TB Disk1

2TB Disk2

240GB SSI cache

 

Build and run adding dockers and plugins and let it run for a month or so. I cannot afford any more drives right but I think that would remove 2 drives and allow me to focus on what I know is working. 

 

As you have noticed, Disk2 is unmountable right now and only became so after I had issues with disk5 [Old Maxtor 250GB drive failing] putting out errors [Replaced with brand new Barracuda 2TB] . I have nothing to save and would benefit from re-doing this box again if it is possible. 

 

Thank you for your reply Trul, I am pulling my box apart now to re-check cables etc and will see if I can get a clean build one more time.

 

Lesson: Slow down, start small, read, read, read!

 

57 minutes ago, Squid said:

Not directly related to your problem, but you will get far better performance from your drives by switching the BIOS mode for the SATA controller from IDE/Legacy to instead be AHCI

00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390]

 

Thanks! Will make it so.

 

Ok. I have opened up my box re-seated each cable end and power supply. I also cleaned up my cabling so as to avoid crosstalk. 

 

I didn't change from IDE legacy yet but will do next time I reboot.

 

I got a clean reboot and my array came up clean but Disk5 is not there. I am ok with not using Disk5 if it means a clean array. I have attached my diag. file and I am not going to touch anything. I am not afraid of data loss anymore and if I need to rebuild fresh, I have no problem with that too. I will hold fire until I hear some other thoughts.

 

Thanks for taking a bit of time and helping me out guys! I appreciate it.

 

Zippy

tower-diagnostics-20180822-1508.zip

UPDATE: Sorry I meant Disk4 . I can see Disk4 now and the array is rebuilding now. Last time it looked like a flawless re-build until the very end so I will let it run overnight now and update tomorrow or when I am next back home. I will post diag. again if I can get a clean rebuild. I am going to be very ashamed if it was only a badly seated connector. We will see! ?

 

10 minutes ago, 99Zippy said:

array came up clean but Disk5 is not there. I am ok with not using Disk5 if it means a clean array.

By Disk5, you probably mean Disk4 (Parity isn't referred to as a disk per se).  It's being emulated right now, and isn't recognized.  My guess is either the drive is completely shot, or you forgot to plug a cable in.  No obvious errors in the syslog related.

Well howdy Folks!

 

The latest update on my problem:

 

This morning I returned to find that my array had turned good with NO ERRORS!! Yay. I was and am happy about that. I planned on letting it run for a bit without doing anything to see if it produced errors.

 

I checked in a little later and I see this !! [Screenshot attached] What the holy hell? I have not done a thing. I have not stopped the array, rebooted nothing. I just snapped the screenshot and pulled a diag. The disk that is showing these reads is a brand new Barracuda drive 2TB that went from wrapper to box. [No, I did not pre-clear it.]

I have not rebooted since my last update either.

 

Sorry to be a pest but I am truly stumped

 

Cheers,

Zippy

 

 

tower-diagnostics-20180823-1143.zip

In order to rebuild disk4 of course it had to rewrite the entire disk.

 

You are getting some of these on that port though:

 

Aug 23 08:09:22 Tower kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x40c0000 action 0xe frozen
Aug 23 08:09:22 Tower kernel: ata4: irq_stat 0x00000040, connection status changed
Aug 23 08:09:22 Tower kernel: ata4: SError: { CommWake 10B8B DevExch }
Aug 23 08:09:22 Tower kernel: ata4: limiting SATA link speed to 1.5 Gbps
Aug 23 08:09:22 Tower kernel: ata4: hard resetting link
Aug 23 08:09:24 Tower kernel: ata4: SATA link down (SStatus 0 SControl 310)
Aug 23 08:09:24 Tower kernel: ata4: EH complete

 

On 8/23/2018 at 7:01 PM, trurl said:

In order to rebuild disk4 of course it had to rewrite the entire disk.

 

You are getting some of these on that port though:

 

Aug 23 08:09:22 Tower kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x40c0000 action 0xe frozen
Aug 23 08:09:22 Tower kernel: ata4: irq_stat 0x00000040, connection status changed
Aug 23 08:09:22 Tower kernel: ata4: SError: { CommWake 10B8B DevExch }
Aug 23 08:09:22 Tower kernel: ata4: limiting SATA link speed to 1.5 Gbps
Aug 23 08:09:22 Tower kernel: ata4: hard resetting link
Aug 23 08:09:24 Tower kernel: ata4: SATA link down (SStatus 0 SControl 310)
Aug 23 08:09:24 Tower kernel: ata4: EH complete

 

 

Good evening Trurl,

 

I did a preclear of disk4 then a format. Almost right away the drive disappeared. I looked into the log and got this error happening over and over again. I don't understand what causes this. I have attached my diag. log again.

 

I have had issues with this disk4 since I began. I have switched the socket that this SATA cable plugs into on the motherboard to an unused socket. [I am talking about the location that the SATA cables go into. There are 2 banks of 3 for a total of 6]

 

I would like to just remove disk4 from my array if that would allow me to have a stable system to work with. Any help or suggestions would be appreciated.

 

Cheers,
Zippy

tower-diagnostics-20180824-2222.zip

Did you ever take care of this?

On 8/22/2018 at 5:05 PM, Squid said:

Not directly related to your problem, but you will get far better performance from your drives by switching the BIOS mode for the SATA controller from IDE/Legacy to instead be AHCI

00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode] [1002:4390]

 

 

 

37 minutes ago, 99Zippy said:

I would like to just remove disk4 from my array if that would allow me to have a stable system to work with. Any help or suggestions would be appreciated.

 

Tools - New Config - Retain All, then unassign disk4. Start the array but do not check the parity valid box because parity will have to be rebuilt since you are removing a disk.

1 minute ago, trurl said:

Did you ever take care of this?

 

 

 

Tools - New Config - Retain All, then unassign disk4. Start the array but do not check the parity valid box because parity will have to be rebuilt since you are removing a disk.

I Did make the change in BIOS.

 

Thanks for the help, I will do it tomorrow when I am not so tired! ? I am also going to update my BIOS as it is running 2 versions older than current. I will report my efforts, success or failure!

 

Cheers,

Zippy

Thanks Guys!!

 

I updated Bios to no avail. Still popping errors on disk4. I removed disk4 using the info Trurl supplied and after a long wait for parity to re-build, SUCCESS! I have a quiet humming UNRAID box with no errors. [Knock on wood] I still am not sure why my system dislikes that disk spot but I will work around it for now. 

 

I pulled a diag. from last night after it had been running and the log seems uneventful so I am going to hopefully call this resolved for now.

 

Thanks again for all your help.

Zippy

tower-diagnostics-20180826-2028.zip