April 11, 20197 yr Hi All I am moving a lot of data on my Unraid server, and this morning I got this in the log file. (I have an array with 2 x Parity drives, was hoping these would correct errors) The disk have no errors in the SMART logs and the check is fine? Can I ignore this? no errors transferring data so would these be corrupt? Any recommendation to apps/tools for checksum or other solution to mitigate this when it happens? As always thanks for helping out spending your time answerings our many questions kernel: md: disk20 read error, sector=7015350792 kernel: md: disk20 read error, sector=7015350800 kernel: md: disk20 read error, sector=7015350808 kernel: md: disk20 read error, sector=7015350816 kernel: md: disk20 read error, sector=7015350824 kernel: md: disk20 read error, sector=7015350832 kernel: md: disk20 read error, sector=7015350840 kernel: md: disk20 read error, sector=7015350848 kernel: md: disk20 read error, sector=7015350856 kernel: md: disk20 read error, sector=7015350864 kernel: md: disk20 read error, sector=7015350872 kernel: md: disk20 read error, sector=7015350880 kernel: md: disk20 read error, sector=7015350888 kernel: md: disk20 read error, sector=7015350896 kernel: md: disk20 read error, sector=7015350904 kernel: md: disk20 read error, sector=7015350912 kernel: md: disk20 read error, sector=7015350920 kernel: md: disk20 read error, sector=7015350928 kernel: md: disk20 read error, sector=7015350936 kernel: md: disk20 read error, sector=7015350944 kernel: md: disk20 read error, sector=7015350952 kernel: traps: python[14567] general protection ip:1471431a2350 sp:14713ca30da0 error:0 in libpython2.7.so.1.0[147143113000+be000] root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token root: error: /webGui/include/Notify.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token root: error: /webGui/include/DeviceList.php: wrong csrf_token root: error: /webGui/include/Notify.php: wrong csrf_token BTW I also have this error but all mounted drives is working okay? root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token
April 11, 20197 yr Author 18 minutes ago, johnnie.black said: Please post the diagnostics: Tools -> Diagnostics Sure thing diagnostics-20190411-0842.zip
April 11, 20197 yr Community Expert It was a media error, i.e., bad or failing sector, though SMART still looks good, you should run an extended SMART test, but since SMART shows more than one read error on very different sectors I would replace it. Since the disk didn't get disabled Unraid could successfully re-write those sectors, so data is good for now, as long as it can be read back from that disk, or on a disk emulated by parity.
April 11, 20197 yr Author 8 hours ago, johnnie.black said: It was a media error, i.e., bad or failing sector, though SMART still looks good, you should run an extended SMART test, but since SMART shows more than one read error on very different sectors I would replace it. Since the disk didn't get disabled Unraid could successfully re-write those sectors, so data is good for now, as long as it can be read back from that disk, or on a disk emulated by parity. @johnnie.black Thanks! copying all data away from the drive now!
April 11, 20197 yr Community Expert 3 hours ago, casperse said: @johnnie.black Thanks! copying all data away from the drive now! Why not just replace and rebuild to a new disk instead? Or if you intend to remove it instead of replacing it you will have to New Config and rebuild parity.
Archived
This topic is now archived and is closed to further replies.