BRiT

For reference, I have 2 28TB Seagate Ironwolf NAS drives. Pairty Check finishes a little under 35 hours [1 day 10 Hours 58 Minutes and 14 Seconds]. I use the Parity Tuner plugin with settings to split it across 4 intervals so it only runs overnight when no one is using the array.

Narrator: Little did they know that hiding the post would kick off a series of events causing the heat death of the universe...

What is causing all these concerns around durability and different grades of flash? Is is some large quanitity of writes thats folks are doing to the flash to be concerned with? Is there some sort of read-only pattern that doesn't mix with certain flash types? Are folks rebooting constantly to have concerns about reads?

Unfortunately, there is something with your system that isn't right. Maybe you got a really bad drive or something else. For comparison point, here is my experience with Seagate 28TB drives of type says they are perfectly fine and speedy for Parity and Data. Using 2 28TB drives, 1 parity, and 1 data. I recently went through a full parity build and have had several months of normal use. Both drives models "ST28000NT000" which are identified Seagate IronWolf Pro 28TB (model ST28000NT000) built using HAMR (Heat-Assisted Magnetic Recording) technology. The initial parity build was very fast. The monthly parity checks are fast too. Here's the summary view from the Parity Operations window: Scheduled Non-Correcting Parity-Check 2026-05-04, 05:26:05 (Monday) 28 TB 1 day, 10 hr, 55 min, 49 sec 222.7 MB/s I

The current syslog started on April 17 12:09:05 and ends on April 24 00:48:15. The previous syslog started on April 10 04:40:59 and ends on April 16 08:28:01. The only "read error" or "write error" related to any drives started (and ended) at April 24 00:24:14.

From your syslog, your disk 11 is having READ and WRITE errors. Maybe it's your MPT3 SAS controller or cables? Not sure what more to look at/for, been ages since I looked at this sort of stuff, so out of practice. Hoping someone else can pickup the ball and continue the task. The SMART report seems to be when you were in process of performing an Extended Offline SMART test? SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Self-test routine in progress 90% 11299 - Drive Identification: Apr 17 12:10:25 Unraid emhttpd: online: ST16000NM000J-2TW103_ZR553342 (sdn) 512 31251759104 Syslog error segment: Apr 24 00:24:14 Unraid kernel: mpt3sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1543 CDB: opcode=0x88 88 00 00 00 00 07 0d 30 99 f0 00 00 00 20 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 30286060016 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059952 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059960 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059968 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=30286059976 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1544 CDB: opcode=0x88 88 00 00 00 00 01 07 65 79 68 00 00 00 80 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058024 op 0x0:(READ) flags 0x0 phys_seg 16 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057960 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057968 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057976 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057984 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419057992 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058000 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058008 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058016 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058024 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058032 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058040 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058048 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058056 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058064 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058072 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419058080 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1559 CDB: opcode=0x8a 8a 00 00 00 00 01 07 65 79 68 00 00 00 28 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058024 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057960 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057968 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057976 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057984 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419057992 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1560 CDB: opcode=0x8a 8a 00 00 00 00 07 0d 30 99 f0 00 00 00 20 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 30286060016 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059952 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059960 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059968 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=30286059976 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1562 CDB: opcode=0x8a 8a 00 00 00 00 01 07 65 79 90 00 00 00 58 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419058064 op 0x1:(WRITE) flags 0x0 phys_seg 11 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058000 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058008 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058016 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058024 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058032 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058040 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058048 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058056 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058064 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058072 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419058080 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1563 CDB: opcode=0x88 88 00 00 00 00 01 07 6b 74 48 00 00 00 28 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419449928 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449864 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449872 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449880 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449888 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=4419449896 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1567 CDB: opcode=0x88 88 00 00 00 00 01 92 80 99 c8 00 00 00 20 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 6752868808 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868744 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868752 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868760 Apr 24 00:24:14 Unraid kernel: md: disk11 read error, sector=6752868768 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1584 CDB: opcode=0x8a 8a 00 00 00 00 01 07 6b 74 48 00 00 00 28 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 4419449928 op 0x1:(WRITE) flags 0x0 phys_seg 5 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449864 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449872 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449880 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449888 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=4419449896 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 Sense Key : 0x2 [current] Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 ASC=0x4 ASCQ=0x0 Apr 24 00:24:14 Unraid kernel: sd 11:0:4:0: [sdn] tag#1592 CDB: opcode=0x8a 8a 00 00 00 00 01 92 80 99 c8 00 00 00 20 00 00 Apr 24 00:24:14 Unraid kernel: I/O error, dev sdn, sector 6752868808 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 0 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868744 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868752 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868760 Apr 24 00:24:14 Unraid kernel: md: disk11 write error, sector=6752868768

It would be nice if the NAS product actually provided actual basic NAS features such as Multiple Arrays. Hate to say it, but anyone wanting those 4 top features first are missing the forest from the trees.

Out of Curiosity, how many uninstalls?

Soon™

Not that there's anything wrong with nascompares (or other YTers or influencers), but I'd like to see normal users reviewing the product for multiple reasons.

Wow, was hoping it would be more widely available and not the preorder one or two months in advance of shipping. I guess if anyone finds additional new reviews or posts about the unit to let us know.

It looks interesting, but as far as I know, has no release date specified. If anyone does see it available, please let all of us know.

Would love to see actual Storage related features added, namely support for Multiple Arrays with the unraid type. Many have been asking for this feature for years if not well over half a decade now.

This past update really made the forums a less useful resource for everyone.

Where did the functionality go that enables one to mark all forums as read go? I only see where one can mark an individual forum as read. One should not be expected to have to do that one by one.