feins

I never had any problem since day 1 till now.

Oooh. any idea which plugin? because i dont have much plugin install.

The diags are during the problem occur i ssh into the system and run the diagnostics command.

Hi this two day i encounter this issue suddenly i cant login after the server are up for a while and i need to SSH into the server and do a reboot and everything are working again. Attach are the diagnostic file and hope that the issue is been log. ts-p500-diagnostics-20260115-1531.zip

Oooh i dont have VMs just Docker and Plugins. and this attach screen shot is the only Docker that being used. Did it indicate what's been utilized more RAM than normal? Ive reboot the server in normal mode since yesterday and seems stable till now. The logs now looks pretty quiets aswell. On the Disk3 filesystem corruption can it be recover? syslog-10.10.2.10.log

Hi @JorgeB its been a while, yesterday my server crashed and as usual a hard reboot and the server back online. I got some error on the logs. and i attach here together with the diagnostic. My last message received from my Telegram at 4.40am and i found the server crashed and cannot login or SSH at 12:40pm where i initial a hard reboot. Hope the logs find something on your site. ts-p500-diagnostics-20251229-1822.zip syslog-10.10.2.10.log

It's been up for over a day on Plugin only. there no additional errors till now. Seems everything are ok by now. ts-p500-diagnostics-20250808-1803.zip

Seems Plugins wont be available in safe mode.

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?

@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

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 ]

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

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

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.

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?

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?

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.

ts-p500-diagnostics-20250728-2054.zip Hi @JorgeB Here's the latest diagnostic log after reboot.

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.

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

Noted, Will try that out. i had other PSU and may swap out the RAM. But i've run memtest before and come out pass will that's enough on the RAM portion?

But how to troubleshoot as it dont crash at the same situation so i dont know how to simulate and replicate the issue. I dont overclock the hardware aswell. What type of info should i provide.

one of my docker apps Kometa icon went missing after previous update for that particular docker. I notice the log keep prompt the error unable to grab the icon error. Ive tried remove the docker and add it again and the icon still missing. webgui: Kometa: Could not download icon https://raw.githubusercontent.com/Kometa-Team/Kometa/nightly/docs/_static/logomark-color.png ts-p500-diagnostics-20250412-1304.zip

Yes last year it happened quite frequently I remember when I bought 2 12tb Seagate Exon and it had a similar crash while doing preclear. But after completed the two drives preclear the system never had such crash until recently. according to those call tracer anything you might think off? Another update I had a fren which had a similar system, same motherboard, same processor, different memory amount, different drives and nvme. He told me he had similar crash intermittently as well sometime the system crash and reboot itself, sometime everything just not responding can’t remote and force reboot just like my cases. He mention this symptom start from version 6.12 onward like mine.

Hi @JorgeB Thanks for your respond. The thing is it don't have a pattern the last crash if not mistaken are nearly a year back. During the last crash I've done Memtest and Hardware stress test also pass. I don't have VMs just dockers and the server runs as purely NAS and Media application only.