I'm in the process of adding a new drive to my pool.

 

I initially had:

* 4tb parity drive

* 4tb data drive

* 2 tb data drive

 

The objective is to introduce a new 14tb parity drive at start, move the 4tb parity to the 2tb data drive slot. This would be pretty easy to do using Parity Swap, but I only found out about it later on.

 

I recall doing these steps:

* Preclear the 14tb drive

* Start the array with the 14tb on parity, 4tb parity drive unassigned

* I then realized I'd rather have the 14tb to replace the 2tb drive, so I started the array with the 4tb parity drive in the old place, only to realize I need the largest drive as parity

* I then added both 14tb drive and 4tb drive as parity drives.

 

The idea was to have both parity drives available, remove the 4tb later, and place it on the 2tb. But I now have this problem in the title and the 4tb drive was disabled.

 

Part of the log:

 

Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037168, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037104
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037176, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037112
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037184, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037120
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037192, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037128
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037200, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037136
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037208, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037144
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037216, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037152
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037224, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037160
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037232, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037168
Jun 12 18:27:25 Tower kernel: unraidd0: attempt to access beyond end of device
Jun 12 18:27:25 Tower kernel: sde: rw=1, sector=7814037240, nr_sectors = 8 limit=7814037168
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037176
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037184
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037192
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037200
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037208
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037216
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037224
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037232
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037240
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037248
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037256
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037264
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037272
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037280
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037288
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037296
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037304
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037312
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037320
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037328
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037336
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037344
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037352
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037360
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037368
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037376
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037384
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037392
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037400
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037408
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037416
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037424
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037432
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037440
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037448
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037456
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037464
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037472
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037480
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037488
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037496
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037504
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037512
Jun 12 18:27:25 Tower kernel: md: disk29 write error, sector=7814037520

 

Is this a bug? I'm waiting the 14tb drive parity-sync to finish, then I'll move the 4tb drive to the 2tb drive slot. I intend to add a new 14tb on this originally 2tb drive slot soon, but I just want to understand if this is a problem with the 4tb drive or if it's just a bug. The drive that showed this errors did originally have a faulty SATA cable that I've replaced and haven't had an issue until this one.

 

I'm desperately in need of free space. I want to replace the 2tb drive first because of that, unless there is something very wrong with the 4tb drive.

tower-diagnostics-20240612-1957.zip

Not really following all the steps you did, but recommend doing a new config and re-sync parity, that should get rid of the issue.