Hi,

 

just a moment ago I got 29 read errors on my drive:

 

I immediately checked the smart data and it looks like this:

The Raw read error rate is going crazy and keeps going higher.

The same is going up for the "Parity 2".

All other drives have Raw Value of Zero.

Both Parity2 and the Disk3 are the 2 newest drives (exos) and are different to the rest.

 

I also dowloaded the full diagnostics. If needed I will upload them but for now the syslog entry of that event:

 

[...]

Apr 26 06:54:40 Tower  move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/StorJ_3/Data/storage/pieceinfo.db-shm
Apr 26 07:00:28 Tower  move: error: move, 392: No such file or directory (2): lstat: /mnt/cache/StorJ_4/Data/storage/blobs/ukfu6bhbboxilvt7jrwlqk7y2tapb5d2r2tsmj2sjxvw5qaaaaaa/zo/m7zkbhmdwijuxw3qqhtdilyvn44xb6mcgl344kzdpnimlheyka.sj1
Apr 26 07:01:17 Tower kernel: mpt3sas_cm1: log_info(0x31080000): originator(PL), code(0x08), sub_code(0x0000)
### [PREVIOUS LINE REPEATED 20 TIMES] ###
Apr 26 07:01:17 Tower kernel: sd 36:0:2:0: [sdk] tag#4429 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=2s
Apr 26 07:01:17 Tower kernel: sd 36:0:2:0: [sdk] tag#4429 Sense Key : 0x3 [current]
Apr 26 07:01:17 Tower kernel: sd 36:0:2:0: [sdk] tag#4429 ASC=0x11 ASCQ=0x0
Apr 26 07:01:17 Tower kernel: sd 36:0:2:0: [sdk] tag#4429 CDB: opcode=0x88 88 00 00 00 00 00 81 13 0a b8 00 00 04 00 00 00
Apr 26 07:01:17 Tower kernel: critical medium error, dev sdk, sector 2165509584 op 0x0:(READ) flags 0x4000 phys_seg 29 prio class 0
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509520
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509528
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509536
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509544
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509552
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509560
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509568
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509576
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509584
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509592
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509600
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509608
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509616
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509624
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509632
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509640
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509648
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509656
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509664
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509672
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509680
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509688
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509696
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509704
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509712
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509720
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509728
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509736
Apr 26 07:01:17 Tower kernel: md: disk3 read error, sector=2165509744
Apr 26 07:02:02 Tower  sSMTP[18019]: Creating SSL connection to host
Apr 26 07:02:02 Tower  sSMTP[18019]: SSL connection using TLS_AES_256_GCM_SHA384
Apr 26 07:02:03 Tower  sSMTP[18019]: Sent mail for [email protected] (221 2.0.0 closing connection) uid=0 username=xxx outbytes=767

[...]

 

 

Can anyone advise me what the problem might be?

Its a fairly new drive but I had a full preclear running without problems.

It does not seem like the sectors themselves are defect (see Smart Values).,

Cables I used are new in a Bundle (SAS - 4xSATA) and the others seem to keep working fine.

10 minutes ago, Anon said:

The Raw read error rate is going crazy and keeps going higher.

That's different for Seagate drives, you can ignore the total raw value, post the diagnostics.

 

 

@JorgeBHi I sent you the diagnostics via PM. Hope thats alright.
I am a bit wary of posting it for all to see publically.

 

I am okay with posting parts that are related to the error here afterwards so people in the future can find this thread and figure it out for themselves.

3 minutes ago, Anon said:

via PM. Hope thats alright.

See last paragraph of the "Need Help" sticky

@trurloh I just meant the diagnostic file as a way of transmitting it. I do not plan on conversing via PMs. I want everyone to profit from the solutation but not always (in my opinion) is every bit of information in the diagnostics really needed for the whole wide world to see

 

Nobody else can help you without diagnostics.

Is there anything in diagnostics you think need to be anonymized further?

Seems diagnostics are already prettya anonymized when looking through them (even emails etc.) so good job. I assumed it just had absolutely everything listed there but when going through it its not that critical.
Maybe Syslog but to be fair you need that to troubleshoot.

tower-diagnostics-20230426-1513.zip

It's logged as a disk problem both on the syslog and on SMART, run an extended SMART test.

Thanks. Its currently running. I'll report back when its done.

 

Did a short self teast before that and it completed without error.

And I also had to set the spin down delay from "2 hours" to "never".

 

 

Alright it ran through without Errors:

 

 

Smart Report: ST18000NM003D-3DL103_ZVT4RXT3-20230428-0826.txt

 

Does this mean I can just ignore this and assume this could have been a one time thing? From what I understand the extended Test goes through  the whole disk so all sectors should work?

 

Disk is OK, at least fore now, keep monitoring.