rikdegraaff Posted April 28, 2019 Share Posted April 28, 2019 Hello everyone, I have my unraid server, who crashed a few weeks ago (https://forums.unraid.net/topic/79147-unraid-crashed-now-nothing-assigned/), now let check his parity. The result my parity check gave me was shocking!! The check found 9,415 errors. I did not let the check wrote them to the parity disk. How can it be that the check found so many errors?? Hereby my syslog. Thank you'll in advance. Rik rik-tower-syslog-20190428-2219.zip Quote Link to comment
JorgeB Posted April 29, 2019 Share Posted April 29, 2019 11 hours ago, rikdegraaff said: How can it be that the check found so many errors?? A few thousand errors are normal, even expected, after an unclean shutdown, run a correcting check. Quote Link to comment
rikdegraaff Posted April 29, 2019 Author Share Posted April 29, 2019 3 hours ago, johnnie.black said: A few thousand errors are normal, even expected, after an unclean shutdown, run a correcting check. Thank you, I just started a correcting parity check. Quote Link to comment
rikdegraaff Posted April 30, 2019 Author Share Posted April 30, 2019 (edited) Sorry but the parity check could not finish. I got an error (x) on disk 6, no smart test able. What is going on with that disk? Disk log gives me this: Quote Apr 30 09:44:53 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Apr 30 09:44:53 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#2 CDB: opcode=0x88 88 00 00 00 00 01 5b 0d ed 70 00 00 02 00 00 00 Apr 30 09:44:53 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5822606704 Apr 30 09:44:53 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Apr 30 09:44:53 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#4 CDB: opcode=0x88 88 00 00 00 00 01 5b 0d ef 70 00 00 02 00 00 00 Apr 30 09:44:53 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5822607216 Apr 30 09:55:45 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 30 09:55:45 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#3 Sense Key : 0x3 [current] Apr 30 09:55:45 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#3 ASC=0x11 ASCQ=0x4 Apr 30 09:55:45 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#3 CDB: opcode=0x88 88 00 00 00 00 01 5b 42 55 08 00 00 02 00 00 00 Apr 30 09:55:45 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826041096 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#4 CDB: opcode=0x88 88 00 00 00 00 01 5b 42 61 08 00 00 02 00 00 00 Apr 30 09:57:16 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826044168 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#6 CDB: opcode=0x88 88 00 00 00 00 01 5b 42 63 08 00 00 02 00 00 00 Apr 30 09:57:16 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826044680 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 5b 42 69 08 00 00 02 00 00 00 Apr 30 09:57:16 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826046216 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#1 CDB: opcode=0x88 88 00 00 00 00 01 5b 42 67 08 00 00 02 00 00 00 Apr 30 09:57:16 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826045704 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 01 5b 42 61 08 00 00 04 00 00 00 Apr 30 09:57:16 RIK-TOWER kernel: print_req_error: I/O error, dev sdi, sector 5826044168 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] Sense not available. Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] Sense not available. Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] 0 512-byte logical blocks: (0 B/0 B) Apr 30 09:57:16 RIK-TOWER kernel: sd 7:0:1:0: [sdi] 4096-byte physical blocks Apr 30 09:57:16 RIK-TOWER kernel: sdi: detected capacity change from 3000592982016 to 0 Apr 30 13:08:14 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:14 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:08:14 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:14 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:08:15 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:15 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:08:15 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:15 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:08:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:08:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:08:48 RIK-TOWER emhttpd: shcmd (103534): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:48 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:48 RIK-TOWER emhttpd: shcmd (103535): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:08:48 RIK-TOWER emhttpd: shcmd (103554): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:48 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:48 RIK-TOWER emhttpd: shcmd (103555): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:08:50 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:50 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:08:50 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:50 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:08:50 RIK-TOWER emhttpd: shcmd (103574): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:50 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:50 RIK-TOWER emhttpd: shcmd (103575): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:08:50 RIK-TOWER emhttpd: shcmd (103594): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:50 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:50 RIK-TOWER emhttpd: shcmd (103595): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:08:51 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:51 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:08:51 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:08:51 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:08:51 RIK-TOWER emhttpd: shcmd (103614): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:51 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:51 RIK-TOWER emhttpd: shcmd (103615): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:08:51 RIK-TOWER emhttpd: shcmd (103634): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:08:51 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:08:51 RIK-TOWER emhttpd: shcmd (103635): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:12 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:32 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:11:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 30 13:11:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 30 13:11:48 RIK-TOWER kernel: sd 7:0:1:0: [sdi] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 30 13:11:48 RIK-TOWER emhttpd: shcmd (103660): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:11:48 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:11:48 RIK-TOWER emhttpd: shcmd (103661): echo 128 > /sys/block/sdi/queue/nr_requests Apr 30 13:11:48 RIK-TOWER emhttpd: shcmd (103680): /usr/local/sbin/set_ncq sdi 1 Apr 30 13:11:48 RIK-TOWER root: set_ncq: setting sdi queue_depth to 1 Apr 30 13:11:48 RIK-TOWER emhttpd: shcmd (103681): echo 128 > /sys/block/sdi/queue/nr_requests Edited April 30, 2019 by rikdegraaff Quote Link to comment
JorgeB Posted April 30, 2019 Share Posted April 30, 2019 Post the full diagnostics. Quote Link to comment
rikdegraaff Posted April 30, 2019 Author Share Posted April 30, 2019 Here ya go Thanks in advance! rik-tower-diagnostics-20190430-1748.zip Quote Link to comment
JorgeB Posted April 30, 2019 Share Posted April 30, 2019 Disk dropped offline so there's no SMART, reboot and post new diags, but it looks like the typical SAS2LP problem. P.S. Unraid should never be Internet facing, there are constant login attempts. Quote Link to comment
rikdegraaff Posted April 30, 2019 Author Share Posted April 30, 2019 (edited) Okay, thanks for the info, @johnnie.black. How do I set my server off the internet. So that only I can access it and use ruTorrent to dl. Hereby after the reboot the diag. rik-tower-diagnostics-20190430-2010.zip Edited April 30, 2019 by rikdegraaff Diag uploaded Quote Link to comment
JorgeB Posted April 30, 2019 Share Posted April 30, 2019 Disk is showing some warning signs, run an extended SMART test. 18 minutes ago, rikdegraaff said: How do I set my server off the internet. So that only I can access it and use ruTorrent to dl. Look for a VPN docker, there are several alternatives, though since I don't use it can't recommend a specific one. Quote Link to comment
rikdegraaff Posted May 1, 2019 Author Share Posted May 1, 2019 Okay I'll found one docker, called Binhex-rtorrentvpn. Is that what you meant? Here the extended SMART test of disk 6: Quote #Attribute NameFlagValueWorstThresholdTypeUpdatedFailedRaw Value 1Raw read error rate0x002f200200051Pre-failAlwaysNever2973 3Spin up time0x0027182180021Pre-failAlwaysNever5858 4Start stop count0x0032100100000Old ageAlwaysNever634 5Reallocated sector count0x0033200200140Pre-failAlwaysNever0 7Seek error rate0x002e200200000Old ageAlwaysNever0 9Power on hours0x0032074074000Old ageAlwaysNever19117 (2y, 2m, 7d, 13h) 10Spin retry count0x0032100100000Old ageAlwaysNever0 11Calibration retry count0x0032100253000Old ageAlwaysNever0 12Power cycle count0x0032100100000Old ageAlwaysNever43 192Power-off retract count0x0032200200000Old ageAlwaysNever9 193Load cycle count0x0032184184000Old ageAlwaysNever50730 194Temperature celsius0x0022117103000Old ageAlwaysNever33 196Reallocated event count0x0032200200000Old ageAlwaysNever0 197Current pending sector0x0032200200000Old ageAlwaysNever0 198Offline uncorrectable0x0030200200000Old ageOfflineNever0 199UDMA CRC error count0x0032200200000Old ageAlwaysNever0 200Multi zone error rate0x0008199186000Old ageOfflineNever595 FeatureValueInformation Offline data collection status:0x82Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status:113The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection:39840seconds. Offline data collection capabilities:0x7bSMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:0x0003Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:0x01Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:2minutes. Extended self-test routine recommended polling time:399minutes. Conveyance self-test routine recommended polling time:5minutes. SCT capabilities:0x7035SCT Status supported. SCT Feature Control supported. SCT Data Table supported. Model family:Western Digital Blue Device model:WDC WD30EZRZ-00Z5HB0 Serial number:WD-WCC4N5HP8HPR LU WWN device id:5 0014ee 2b78a3c74 Firmware version:80.00A80 User capacity:3,000,592,982,016 bytes [3.00 TB] Sector sizes:512 bytes logical, 4096 bytes physical Rotation rate:5400 rpm Device:In smartctl database [for details use: -P show] ATA version:ACS-2 (minor revision not indicated) SATA version:SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local time:Wed May 1 04:42:35 2019 CEST SMART support:Available - device has SMART capability. SMART support:Enabled SMART overall-health:Passed Quote Link to comment
JorgeB Posted May 1, 2019 Share Posted May 1, 2019 4 hours ago, rikdegraaff said: Here the extended SMART test of disk 6: Please attach the complete SMART report. Quote Link to comment
rikdegraaff Posted May 1, 2019 Author Share Posted May 1, 2019 Sorry, didn't knew where to find the full SMART report. Is it this file? rik-tower-smart-20190501-0442.zip Quote Link to comment
JorgeB Posted May 1, 2019 Share Posted May 1, 2019 3 minutes ago, rikdegraaff said: Is it this file? Yes, and like suspected the disk is failing: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 10% 19117 5584798408 Quote Link to comment
rikdegraaff Posted May 1, 2019 Author Share Posted May 1, 2019 (edited) Sh*t, need to replace the disk... I think so. Can you confirm @johnnie.black? Edited May 1, 2019 by rikdegraaff Quote Link to comment
Gatton Posted May 1, 2019 Share Posted May 1, 2019 Apart from those readings, can you tell the disk is failing by something else? Are you getting errors while trying to run stuff? Quote Link to comment
trurl Posted May 1, 2019 Share Posted May 1, 2019 2 hours ago, Gatton said: Apart from those readings, can you tell the disk is failing by something else? Are you getting errors while trying to run stuff? I don't understand the point of your question. Are you having problems yourself? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.