hi,

since couple of weeks (coincidentally after i installed a new rig?) i noticed issues with my UD giving regularly a "critical medium error"
sometimes this requires me to do a ntsfix or a chkdsk or in worst case reboot my server.

the drive i am using during this test got a perfect surface write/verify scan.

while i cannot completely run smart 100% on this one,

i had same errors when i tested this a while ago with one of my spare array drives (100% smart ok) .
i have also tested this drive being on a sata port instead of the hba hence not a cable or controller issue.

any suggestions (besides my 'todo' below)  ?

todo?: i could still check with an older unraid version (as i did not have these issues "in the past")
todo?: perhaps also get an older version of the UD plugin up and running
todo?: temporarily assign this drive to my array -as in bypassing the ud plugin- and repeat the test

2 examples below;
a>
i definitely can say i did not "change any partition info" if that is the problem here.
 in this case i loaded that disk is an "support vm" and chkdsk gave no errors.
3/11 would indicate a "Unrecovered error was detected duringData Read"
 

May 13 13:29:26 Tower unassigned.devices: Successfully unmounted '/dev/sdb1'
May 13 13:29:26 Tower unassigned.devices: Removing SMB share '_tor_'.
May 13 13:29:33 Tower kernel: sd 6:0:0:0: [sdb] tag#8128 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=6s
May 13 13:29:33 Tower kernel: sd 6:0:0:0: [sdb] tag#8128 Sense Key : 0x3 [current]
May 13 13:29:33 Tower kernel: sd 6:0:0:0: [sdb] tag#8128 ASC=0x11 ASCQ=0x0
May 13 13:29:33 Tower kernel: sd 6:0:0:0: [sdb] tag#8128 CDB: opcode=0x88 88 00 00 00 00 00 00 00 08 40 00 00 00 08 00 00
May 13 13:29:33 Tower kernel: critical medium error, dev sdb, sector 2112 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
May 13 13:29:33 Tower unassigned.devices: Reload: A udev 'change partition' initiated a reload of udev info.

 

 

b> same error during startup
("sector0"...sector changes every time this nr is likely not that relevent but as this is during bootup therefore thé first one being accessed)
 

May 13 14:32:29 Tower avahi-daemon[29539]: Server startup complete. Host name is Tower.local. Local service cookie is 289622479.
May 13 14:32:30 Tower avahi-daemon[29539]: Service "Tower" (/services/ssh.service) successfully established.
May 13 14:32:30 Tower avahi-daemon[29539]: Service "Tower" (/services/smb.service) successfully established.
May 13 14:32:30 Tower avahi-daemon[29539]: Service "Tower" (/services/sftp-ssh.service) successfully established.
May 13 14:32:35 Tower kernel: sd 6:0:0:0: [sdb] tag#8178 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=6s
May 13 14:32:35 Tower kernel: sd 6:0:0:0: [sdb] tag#8178 Sense Key : 0x3 [current]
May 13 14:32:35 Tower kernel: sd 6:0:0:0: [sdb] tag#8178 ASC=0x11 ASCQ=0x0
May 13 14:32:35 Tower kernel: sd 6:0:0:0: [sdb] tag#8178 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00
May 13 14:32:35 Tower kernel: critical medium error, dev sdb, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2
May 13 14:32:39 Tower SysDrivers: SysDrivers Build Complete

 

syslog.txt WDC_WD60EFRX-68MYMN1_WD-WX41D3405899-2024-02-15 (sdb).txt

They are also logged in the SMART report as a disk problem, run an extended SMART test on the disk