RexMundi727

I was able to resolve by doing a force update on the Dockers that did not start.

Just to add on. The Dockers that are not set to auto start on boot will start if I start manually but the ones that are set to auto start will not start.

There is no error. It just starts and all appears to be working fine but Dockers just don't start

I am doing some work on my server and when I rebooted none of my dockers will start. I have rebooted several times with no success in getting Dockers to start. What can I do to resolve this issue? templartower-diagnostics-20250129-1152.zip

Not necessarily as I move from SATA port to SATA port. I can't say for certain but doubt that in the year I have had these issues and the 5 to 10 time I have replaced cables that it ended in the same port each time.

It is the same disk for the most part but it is the 3rd one that is in there.

I have been dealing with ongoing issues for over a year now and been throwing lots of parts at but still have issues. I currently have a disk that is in error state. When I do a parity check it starts out fine then I start to hear a disk click and then time for parity check goes from 1 day to over 200. When I reboot the server there is a beeping sound that beeps 5 times. I have posted previously and the response is that it is SATA cables or HDD power cables. I was also advised it may be a power supply issue or a MB issue. Here are system components: MB - Gigabyte Z690 UD AX CPU - i3-12100 PS 750W Bronze 16 GB DDR4 memory Here is what I have done so far: SATA cables have been replaced at least 5 times and I now have a box or about 30 of them. HDD power cables have been replaced 3 times and have about 15 in the box now. Replaced MB. When I replace cables and start up all runs good for a few days to weeks and then the same issues will come back with Parity check saying over 200 days. As mentioned (I think this may be the cause of the issues) when I boot the MB speaker beeps 5 times. I have read that this may a CPU or MB issue. Is there a way for me to diagnose this and is there some BIOS settings that may be off that I can change. I am not against buying and replacing parts but so far aside from cables I have advised it could be a PS, CPU and MB issue. I am not wanting to replace all if I don't have to as that would be pretty much building a new system. I would really appreciate some feedback on the diagnostics and any help with any BIOS changes would be helpful or at least pointing at what is the likely cause of my ongoing problems. Thank you for taking the time to read and all feedback is appreciated. EDIT: I am working on BIOS setting and the 5 beeps does not happen when I have a monitor plugged in. templartower-diagnostics-20250118-0922.zip

I don't but not may get another one. The thing is when I replace cables all work good for about a month and then issues come back. Aside from the PS the last thing left is the CPU. But I get one of those I have enough parts to build another PC.

How do I tell what is bad? I just can't keep replacing motherboards, CPUs and PS units in hopes it will work.

Thanks, but doubt that is the issue as on 5th set of brand new data cables and 3rd set of power cables.

Sorry about that.

I have been having an ongoing issue that seems to always come back and causes disk errors every few months. This had started out when I do a Parity check which starts out fine for a few minutes and then I start to hear a drive click and then time to run Parity check drops from a day to 200+ days. I have posted here a few times in the past and problem always comes back. Here is what I have done to resolve issue previously but all seem to fail after a month or two and the issue comes back: - Replaced 12TB HDD 3 times. - Replaced SATA cables 5 times. - Replaced HDD power cables 3 times. - On second MB was that was replaced when I upgraded to new CPU. So currently I have a 12TB drive with 280 errors but do not want to buy and replace HDD as certain it is not the issue. Can I just clear or format this drive and rebuild from Parity before I start running tests and replacing more parts? I really want to have all drives and Parity up to date before I really start working on resolution. Seeing that I have already replaced drives, SATA data and power cables I am at a loss on where I should be looking next to try to fix this issues so I can really enjoy unRAID as this ongoing issue is starting to get to me. Thanks, templartower-diagnostics-20250103-1411.zip

I got a new drive and put it an external docking station. turned it on and it was seen as an unassigned drive and I started to preclear. The drive accidently got unplugged. When I plugged it back in it no longer shows as an unassigned drive so now I can't preclear. I plugged into PC and I can see the drive but unRAID can't see the drive. Any idea what the issue may be?

Thanks, I will try a 5th set of SATA cables but running low on power cables.

I had a look at it and don't know what I should be looking for. I just got back from a few days away and was about to troubleshoot and now disk one is in error state and is showing as Unmountable: Wrong or no files system. To me it is telling me it should not be a cable issue and may just be another bad drive.

Thanks, I will check that our when I get back from work and server is not being used.

I have but will try another set. The SATA cables are brand new as I just purchased a fresh set but the power is the ones I have lying around. Excuse my ignorance but where in the diagnostics do I identify it is disk one? If I know where I am looking then I can do some troubleshooting to see if problem follows a cable, disk or STA port.

I have had this ongoing issue for some time now and have been told it was a cable issue but I am on my 3rd set of SATA cables to no avail. The issue is that when I start a Parity check it quickly goes to 150 days complete time and speed are 1.1 MBps. If the issue is not SATA cables (using brand new ones) what else could I be looking at to resolve the issue. Thanks in advance to the wonderful group. templartower-diagnostics-20240805-1540.zip

My apologies as I stopped the check. Attached is the updated diagnostics. templartower-diagnostics-20240515-1903.zip

Attached is the diagnostics templartower-diagnostics-20240514-1609.zip

I have been dealing with this issue on and off for over a year now and thought I had it all working good for the past few months and a few days ago it popped up for me again. I had an issue with real slow cache writes to the array and the content would not move off from cache. I rebooted as then when system came up it started to do a Parity check and the Parity check said it would be 200 plus days to complete. I was advised that this may be a sata cable issue so I bought new sata cables and replaced all 6. This worked for about 10 hours and Parity check was going fine until it stopped and then moved back to 150 plus days. Below is the log when the red error showed up and I have attached is the complete log after a reboot. As mentioned I have been dealing with this on and off for over a year now and whatever I do does not end up in a long term solution. Any help would be appreciated in resolving this issue. May 13 16:21:02 TemplarTower kernel: ata7.00: exception Emask 0x10 SAct 0x800000 SErr 0x4090000 action 0xe frozen May 13 16:21:02 TemplarTower kernel: ata7.00: irq_stat 0x00400040, connection status changed May 13 16:21:02 TemplarTower kernel: ata7: SError: { PHYRdyChg 10B8B DevExch } May 13 16:21:02 TemplarTower kernel: ata7.00: failed command: READ FPDMA QUEUED May 13 16:21:02 TemplarTower kernel: ata7.00: cmd 60/08:b8:d0:4e:b0/00:00:10:04:00/40 tag 23 ncq dma 4096 in May 13 16:21:02 TemplarTower kernel: res 40/00:00:d0:4e:b0/00:00:10:04:00/40 Emask 0x10 (ATA bus error) May 13 16:21:02 TemplarTower kernel: ata7.00: status: { DRDY } May 13 16:21:02 TemplarTower kernel: ata7: hard resetting link May 13 16:21:08 TemplarTower kernel: ata7: link is slow to respond, please be patient (ready=0) May 13 16:21:12 TemplarTower kernel: ata7: COMRESET failed (errno=-16) May 13 16:21:12 TemplarTower kernel: ata7: hard resetting link May 13 16:21:13 TemplarTower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 13 16:21:13 TemplarTower kernel: ata7.00: supports DRM functions and may not be fully accessible May 13 16:21:14 TemplarTower kernel: ata7.00: supports DRM functions and may not be fully accessible May 13 16:21:14 TemplarTower kernel: ata7.00: configured for UDMA/133 May 13 16:21:14 TemplarTower kernel: ata7: EH complete unRAID Log.txt

Attached are the diagnostics. templartower-diagnostics-20230930-1617.zip

I have been dealing with this issue for 6 months now but here is my most recent issue. I woke up this morning with an 8 TB drive with 2 errors and note that contents are being emulated. I took drive out formatted it and put it back in and when started up the disk was being recreated as expected. The issue is the recreation time change from 30 days to 180 days and is running at 1 Mbps. As mentioned I have been dealing with this issue for 6 months now since I update my system with a new MB and CPU. I operated without Parity for about 4 months as the PArtity build was going to take over a year to build. About a month ago I installed my 3rd MB to see if I could get it working better I was able to do a Parity build in 36 hours or so so I thought all was good. All seemed to be good until this morning when I had a measly 2 errors and now I am back to 6 months to rebuild a drive that had 2 TB of data on it. So I have a couple of questions here. First is what could be the cause that would result in a Parity build taking 2 years or rebuilding 2 TB of lost data on a drive taking 6 months? I am now on my 3rd MB and now have one with 6 Sata ports so all 6 drives on connected to the MB. I have replaced every Sata cable numerous times and have probably have gone through 20 or 30. Again, all was good about a month ago when I crated Parity but now it is a no go. Since I have been trying for 6 months to resolve the above and have no idea on how to resolve the issue is there a way that I can just not do a rebuild from Parity and just be able to add the lost data as that would take a few hours and not 6 months? Thanks in advance for any insight.

I have a 4 port SATA expansion card but for some reason when I try to build Parity or RedCheck it says it will take 200 to 300 days to complete. Obvious problem. It was suggested that I purchase a IBM M5110 LSI 9207-8i IT which I did. I installed and it was working good for about 5 minutes. I then powered off put cover or and restarted at which point the drives that were plugged into the M5110 did not show up. Tried several times with no success. Looked at Bios and it says it is IT which I believe is correct. I do have it in a PCI 16 slot but says it should be PCI 8 which the MB does not have. Any suggestions on how to get this card working?