bought a new 14tb drive and added it to my server. Pre-cleared, then stopped the array and added the new drive.

When I tried to write to it, it spit out these errors:

[134070.932535] unraidd7: attempt to access beyond end of device
                sdj: rw=0, sector=23622320272, nr_sectors = 8 limit=0
[134070.932536] md: disk7 read error, sector=23622320208
[134070.932537] unraidd7: attempt to access beyond end of device

and failed the drive.

I did a rebuild and everything completed successfully, once I tried to access the drive, I got the same errrors.

Any clue what's going on?

homer-diagnostics-20250830-2333.zip

Disk dropped offline and reconnected. This is typically a power/connection issue. Also, seeing issues for disk5, check/replace cables for both disks, especially if they share something like a power splitter.

On 9/1/2025 at 3:35 AM, JorgeB said:

Disk dropped offline and reconnected. This is typically a power/connection issue. Also, seeing issues for disk5, check/replace cables for both disks, especially if they share something like a power splitter.

It's weird, I switched the disk to a different port. (this is a supermicro MB with a SAS backplane). I cleared the disk and added it again, unraid did a clear and gave me the option to format the drive. When I tried to format, it took the drive offline again.

I'm currently doing a full preclear with a pre-read right now. What's weird is that I was able to write to it fully, it wasn't until I added it to the array and formatted it that it failed. This is the 2nd time it's happened. I don't believe that there is a connectivity issue with the drive, it feels like the array is reading something incorrectly. This is a Seagate Exos 2x14 Mach 2.

Once the pre-clear has completed, I'll send a new diagnostic file. It would be strange if there were no disconnection issues during a full read/write cycle, but only when the array tries to access the drive.

homer-diagnostics-20250903-2056.zip

5 hours ago, Groo said:

It would be strange if there were no disconnection issues during a full read/write cycle, but only when the array tries to access the drive.

Agreed, could be a different issue.

2 days of heavy I/O on the same drive and no errors or issues. gonna try and upgrade to the latest beta, then next step will be to roll back to 7.0.1.

homer-diagnostics-20250905-2010.zip

Closing this, there's no solution here. The drive is a Seagate Exos 2x14 Mach 2, Dual-actuator drive. It's simply not supported in Unraid. However, it may work if in a ZFS pool.

just an update, I was able to use the drive as parity disk, no issues at all, was able to re-use my old parity in the array.