Hello Unraid Community,

 

I'm encountering some disk issues on my Unraid server and could use some guidance and assistance from the community.

Here's the situation:

 

• I discovered that one of my disks (Disk 4, 3TB) is displaying the "disk in error state" message. When I attempted to stop the array in Unraid, there was no response, and even trying to change parameters didn't work, leading to a manual reboot.
• After the reboot, I observed that another disk (Disk 1, 8TB) is showing the "Unmountable Unsupported or no file system" message.
• When I tried to unassign Disk 4 from the array and reassign it, a blue icon appeared with the message "new disk..."
• Upon mounting the array, the rebuild process started at an extremely slow speed of 237.5 KB/sec.
• Additionally, Disk 1 still displays the "Unmountable Unsupported or no file system" message.

 

I'm not an expert in Unraid, and I want to ensure that I take the right steps to resolve these issues without risking data loss. I've attached a diagnostic file for reference.

Please note that the data on Disk 4 consists of backups, so it's not critical.

 

If anyone in the community has encountered similar issues or has expertise in diagnosing and resolving disk problems in Unraid, I would greatly appreciate your insights and guidance.

 

Thank you for your assistance!

badrserver-diagnostics-20231220-0901.zip

Dec 20 05:55:01 BadrServer kernel: ata2.00: cmd 60/40:f0:d0:3b:00/05:00:00:00:00/40 tag 30 ncq dma 688128 in
Dec 20 05:55:01 BadrServer kernel:         res 40/00:f0:d0:3b:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
Dec 20 05:55:01 BadrServer kernel: ata2.00: status: { DRDY }
Dec 20 05:55:01 BadrServer kernel: ata2: hard resetting link
Dec 20 05:55:01 BadrServer kernel: ata6.00: exception Emask 0x50 SAct 0x80000 SErr 0x4890800 action 0xe frozen
Dec 20 05:55:01 BadrServer kernel: ata6.00: irq_stat 0x08400040, interface fatal error, connection status changed
Dec 20 05:55:01 BadrServer kernel: ata6: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch }
Dec 20 05:55:01 BadrServer kernel: ata6.00: failed command: WRITE FPDMA QUEUED
Dec 20 05:55:01 BadrServer kernel: ata6.00: cmd 61/00:98:10:2b:00/01:00:00:00:00/40 tag 19 ncq dma 131072 out
Dec 20 05:55:01 BadrServer kernel:         res 40/00:98:10:2b:00/00:00:00:00:00/40 Emask 0x50 (ATA bus error)
Dec 20 05:55:01 BadrServer kernel: ata6.00: status: { DRDY }
Dec 20 05:55:01 BadrServer kernel: ata6: hard resetting link
Dec 20 05:55:01 BadrServer kernel: ata1.00: exception Emask 0x10 SAct 0x7c000000 SErr 0x4890000 action 0xe frozen
Dec 20 05:55:01 BadrServer kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed
Dec 20 05:55:01 BadrServer kernel: ata1: SError: { PHYRdyChg 10B8B LinkSeq DevExch }
Dec 20 05:55:01 BadrServer kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 20 05:55:01 BadrServer kernel: ata1.00: cmd 60/40:d0:50:31:00/05:00:00:00:00/40 tag 26 ncq dma 688128 in
Dec 20 05:55:01 BadrServer kernel:         res 40/00:f0:50:46:00/00:00:00:00:00/40 Emask 0x10 (ATA bus error)

 

ATA errors in 3 disks, could be power related if they share a splitter for example, try to fix that and post new diags.

Thanks for your reply.
Yes they are sharing the same splitter, maybe this is the problem.
I'm also concerned about the slow Data-Rebuild process, which appears to be progressing at an extremely slow pace. At this rate, it seems like it could take more than 60 days to complete...

Is there a way to stop or expedite the Data-Rebuild process while addressing the power-related issues?

Edited December 20, 20232 yr by ikossane

15 minutes ago, ikossane said:

'm also concerned about the slow Data-Rebuild process, which appears to be progressing at an extremely slow pace. At this rate, it seems like it could take more than 60 days to complete...

Those continual resets will be what is slowing things down.    You should stop the data rebuild; fix the reset issue; and then restart the rebuild

Thank you all for your valuable input and suggestions. Based on the insights I've received, it seems that the power-related issues may be at the root of the problem, especially given the ATA errors in three of my disks that share a PSU splitter.

As a result, I've decided to proceed with changing the PSU and providing separate power sources for each HDD to address this concern. I believe this step will help resolve the challenges I've been facing.

Once I've completed these modifications, I'll be sure to post a new diagnostic report to update the community on the progress and any changes in the system's status.

8 hours ago, JorgeB said:

 

ATA errors in 3 disks, could be power related if they share a splitter for example, try to fix that and post new diags.

 

Hello once again,

 

I wanted to update you on the latest developments with my server. Following your valuable advice, I made changes to the PSU setup, specifically by connecting two HDDs to one splitter, two HDDs to another splitter, and a single HDD to a separate splitter.

Here's the current situation:

• Disk 4 (3TB) is now detected as a new HDD, and the Data-Rebuild process has commenced. The good news is that this time, the process is running at a significantly higher speed, and it's estimated to finish in approximately 6 hours.
• However, I'm facing the same issue with Disk 1 (8TB), which contains all my media files. It's displaying the message: "Unmountable Unsupported or no file system." This is perplexing, as it was functioning correctly before I shut down the server as mentioned in my first message. In the Array Operation section, it now shows "Unmountable disk present: Disk 1 • ST8000VN004-3CP101_WWZ3D40H (sdc)" and suggests formatting.

I'm quite puzzled by these developments and would appreciate any insights or guidance from the community.

 

To provide you with more information, I've generated a new diagnostic report.

 

Thank you for your support.

 

EDIT : When the rebuild process will finish i will follow this documentation : https://docs.unraid.net/unraid-os/manual/troubleshooting/#unmountable-disks:~:text=checking and repairing

 

 

badrserver-diagnostics-20231220-1845.zip

Edited December 21, 20232 yr by ikossane

10 hours ago, ikossane said:

EDIT : When the rebuild process will finish i will follow this documentation

Yes, do that, and run it without -n

Hello again,

 

I wanted to share some great news with all of you. The Data-Rebuild process for Disk 4 (3TB) has been successfully completed with no issues. The rebuild finished ahead of schedule, and all data has been recovered successfully.

 

Regarding Disk 1 (8TB) and the "Unmountable Unsupported or no file system" message, I followed the troubleshooting steps in the Unraid documentation and used the -L option. I'm pleased to report that this action resolved the problem, and Disk 1 is now functioning correctly.

 

Thank you all for your help!