I just notice that 2 drive suddenly was unassigned error array and one of the 8TB drive was disable and I don't understand what's the problem and by looking at the dashboard I'm also confuse one of the unassigned drive are still active and the other one are Disable.

What should i don now.

ts-p500-diagnostics-20250728-1804.zip

Disk dropped offline and reconnected again; this is typically a power/connection issue:

Jul 27 13:32:13 TS-P500 kernel: ata8: limiting SATA link speed to <unknown>

Jul 27 13:32:19 TS-P500 kernel: ata8: SATA link down (SStatus 0 SControl 3F0)

Jul 27 13:32:19 TS-P500 kernel: ata8.00: disable device

Jul 27 13:32:19 TS-P500 kernel: ata8.00: detaching (SCSI 8:0:0:0)

18 minutes ago, JorgeB said:

Disk dropped offline and reconnected again; this is typically a power/connection issue:

Jul 27 13:32:13 TS-P500 kernel: ata8: limiting SATA link speed to <unknown>

Jul 27 13:32:19 TS-P500 kernel: ata8: SATA link down (SStatus 0 SControl 3F0)

Jul 27 13:32:19 TS-P500 kernel: ata8.00: disable device

Jul 27 13:32:19 TS-P500 kernel: ata8.00: detaching (SCSI 8:0:0:0)

It it save I can just power down the Server and reconnect the Drive and power. because i notice both drive 3 and Drive 7 are on different enclosure.

Once power on how should i do to reenable the drives?

Because i only had 1 parity.

Reboot and post new diags after the array starts. Since you have single parity, only one disk can get disabled.

1 hour ago, JorgeB said:

Reboot and post new diags after the array starts. Since you have single parity, only one disk can get disabled.

ts-p500-diagnostics-20250728-2054.zip

Hi @JorgeB

Here's the latest diagnostic log after reboot.

1 hour ago, JorgeB said:

Reboot and post new diags after the array starts. Since you have single parity, only one disk can get disabled.

Check filesystem for the emulated disk3

Just now, feins said:

ts-p500-diagnostics-20250728-2054.zip

Hi @JorgeB

Here's the latest diagnostic log after reboot.

15 minutes ago, JorgeB said:

Check filesystem for the emulated disk3

Below is the detail from the check filesystem status.

What's the next action plan?

Phase 1 - find and verify superblock...
bad primary superblock - bad CRC in superblock !!!

attempting to find secondary superblock...
....found candidate secondary superblock...
verified secondary superblock...
writing modified primary superblock
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If the filesystem is a snapshot of a mounted
filesystem, you may need to give mount the nouuid option. If you are unable
to mount the filesystem, then use the -L option to destroy the log and
attempt a repair.  Note that destroying the log may cause corruption --
please attempt a mount of the filesystem before doing this.

Zero the log

5 minutes ago, JorgeB said:

Zero de log

I got alot of files in lost & found folder. what should i do. seems there are alot of corrupted files before this and whats my next step?

If the emulated disk doesn't look great, you can mount the actual disk with the UD plugin and see if it looks better. You need to unassign it first, and if it looks better you can do a new config instead.

11 hours ago, JorgeB said:

If the emulated disk doesn't look great, you can mount the actual disk with the UD plugin and see if it looks better. You need to unassign it first, and if it looks better you can do a new config instead.

Hi @JorgeB Thanks for the suggestion.

I've try to replace the 8TB with another spare unit and now its rebuilding as i scare of loosing any data and felt more save to rebuild from the parity.

Just a question is there a way to make it faster on the rebuild as i notice the rebuild only around 160MB/s

Is there anything that i can tweak on the Disk Setting to improve the throughput?

2 hours ago, feins said:

I've try to replace the 8TB with another spare unit and now its rebuilding as i scare of loosing any data and felt more save to rebuild from the parity.

It will rebuild the same thing you saw on the emulated disk, but you can still do the new config later, if the old disk contents look better, or just copy the data.

On 7/29/2025 at 3:35 PM, JorgeB said:

It will rebuild the same thing you saw on the emulated disk, but you can still do the new config later, if the old disk contents look better, or just copy the data.

All those files inside Lost & Found doesn't make sense cant determine any of those files belong to where.

Lucky Disk 3 are mostly my Media collection and now I've check with Radarr and those listed Missing and I've need to source those missing media again.

If you still have the old disk intact, you can mount it with UD and copy the data over, or do a new config with it installed in the array.

On 7/30/2025 at 10:30 PM, JorgeB said:

If you still have the old disk intact, you can mount it with UD and copy the data over, or do a new config with it installed in the array.

Hi @JorgeB

Sorry for the late update because im having issue with the Server and seems the server keep stop responding.

Lastly ive manage to force reboot and just completed finish the Parity check with 0 Error, and i've complete Preclear the 8TB Drive without any issue.

But when i try to shutdown the server manually and it dont wana shutdown.

Ive manage to download the log file but when i try to generate a Diagnostic file it just down wana complete the diagnostic.

So i only attach the system log file and hope you could find something that keep the server not shutting down.

ts-p500-syslog-20250801-0645.zip

There are multip+lçe crashes logged, difficult to say if they are hardware or software related. Try rebooting in safe mode and leave the docker and VM services disabled for now. If it still crashes, it's likely hardware related.

2 hours ago, JorgeB said:

There are multip+lçe crashes logged, difficult to say if they are hardware or software related. Try rebooting in safe mode and leave the docker and VM services disabled for now. If it still crashes, it's likely hardware related.

Hi @JorgeB

Ive force shutdown and now boot into save mode with HDD auto start Disable, Docker auto Start Disable, I dont use VM so its Disable.

What should i do next?

ts-p500-diagnostics-20250801-1814.zip

Edited August 1, 2025Aug 1 by feins

Start the array, leave the Docker service disabled for now, and see if it's stable. If yes, enable the Docker service and retest.

1 hour ago, JorgeB said:

Start the array, leave the Docker service disabled for now, and see if it's stable. If yes, enable the Docker service and retest.

Ok Array started.

Lets monitor for sometime.

If the Array stable later on I'll enable Docker and keep monitor if it Crash again.

@JorgeB I've notice some of this error and any of them are critical?

So far the Array and Docker are enable as request, the server are still very responsive and seems no issue for nearly a day.

Aug  1 19:05:17 TS-P500 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Aug  1 19:05:17 TS-P500 kernel: ACPI: Early table checksum verification disabled
Aug  1 19:05:17 TS-P500 kernel: floppy0: no floppy controllers found
Aug  1 19:05:17 TS-P500 kernel: i915 0000:00:02.0: [drm] [ENCODER:240:DDI A/PHY A] failed to retrieve link info, disabling eDP
Aug  1 19:05:34 TS-P500 mcelog: failed to prefill DIMM database from DMI data
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 8: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 8: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 8: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 8: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd/udp: socket 1: sendto() error: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]
Aug  1 19:05:17 TS-P500 rsyslogd: omfwd: socket 1: error 101 sending via udp: Network is unreachable [v8.2102.0 try https://www.rsyslog.com/e/2354 ]

Edited August 2, 2025Aug 2 by feins

@JorgeB

The server are running on Save Mode and Docker only for 4 days and everything stable.

But i notice that's and Error on the log.

Aug  4 20:04:16 TS-P500 kernel: ata1.00: exception Emask 0x10 SAct 0x8 SErr 0x400100 action 0x6 frozen
Aug  4 20:04:16 TS-P500 kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Aug  4 20:04:16 TS-P500 kernel: ata1: SError: { UnrecovData Handshk }
Aug  4 20:04:16 TS-P500 kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Aug  4 20:04:16 TS-P500 kernel: ata1.00: cmd 61/10:18:c0:b1:68/03:00:2d:01:00/40 tag 3 ncq dma 401408 out
Aug  4 20:04:16 TS-P500 kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
Aug  4 20:04:16 TS-P500 kernel: ata1.00: status: { DRDY }
Aug  4 20:04:16 TS-P500 kernel: ata1: hard resetting link
Aug  4 20:04:17 TS-P500 kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Aug  4 20:04:17 TS-P500 kernel: ata1.00: configured for UDMA/100
Aug  4 20:04:17 TS-P500 kernel: ata1: EH complete
Aug  4 20:05:28 TS-P500 monitor_nchan: Stop running nchan processes

Edited August 5, 2025Aug 5 by feins

That looks like a power/connection issue, and just one error is not really a problem, but if it keeps happening check/replace cables for that device.

1 hour ago, JorgeB said:

That looks like a power/connection issue, and just one error is not really a problem, but if it keeps happening check/replace cables for that device.

Hi @JorgeB

Thanks for your info.

So by now how should i proceed?

The server already on safe mode and docker only for over 4days without any issue and assume its stable till now.

Should i reboot it back to normal mode and enable all plugin?

1 hour ago, JorgeB said:

That looks like a power/connection issue, and just one error is not really a problem, but if it keeps happening check/replace cables for that device.

41 minutes ago, feins said:

Should i reboot it back to normal mode and enable all plugin?

Start enabling one thing at the time, you can start with the plugins or docker service for example, still in safe mode.

23 hours ago, JorgeB said:

Start enabling one thing at the time, you can start with the plugins or docker service for example, still in safe mode.

Seems Plugins wont be available in safe mode.

11 minutes ago, feins said:

Seems Plugins wont be available in safe mode.

No, for that you need to boot in normal mode; if you do that first, leave the Docker service disabled for now.