Disk error disabled... Confirm it's bad?

JimPhreak

By JimPhreak
in General Support

Recommended Posts

JimPhreak Enthusiast

JimPhreak

Posted
Posted

So last night one of my disks reported a bunch of read/write errors and UnRAID disabled the disk and currently my array is unprotected.  Is there any recommended procedure for confirming the disk is bad before I replace it?

 

Syslog of the errors is here:

 

Jan 29 23:57:15 SPE-UNRAID kernel: sd 2:0:5:0: [sdj] Synchronizing SCSI cache
Jan 29 23:57:15 SPE-UNRAID kernel: sd 2:0:5:0: [sdj] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Jan 29 23:57:15 SPE-UNRAID kernel: scsi 2:0:5:0: [sdj] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00
Jan 29 23:57:15 SPE-UNRAID kernel: scsi 2:0:5:0: [sdj] CDB: opcode=0x88 88 00 00 00 00 01 13 dc 8b 10 00 00 02 00 00 00
Jan 29 23:57:15 SPE-UNRAID kernel: blk_update_request: I/O error, dev sdj, sector 4628187920
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187856
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187864
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187872
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187880
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187888
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187896
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187904
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187912
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187920
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187928
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187936
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187944
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187952
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187960
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187968
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187976
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187984
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628187992
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188000
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188008
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188016
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188024
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188032
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188040
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188048
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188056
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188064
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188072
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188080
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188088
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188096
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188104
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188112
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188120
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188128
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188136
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188144
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188152
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188160
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188168
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188176
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188184
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188192
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188200
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188208
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188216
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188224
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188232
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188240
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188248
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188256
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188264
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188272
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188280
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188288
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188296
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188304
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188312
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188320
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188328
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188336
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188344
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188352
Jan 29 23:57:15 SPE-UNRAID kernel: md: disk4 read error, sector=4628188360
Jan 29 23:57:15 SPE-UNRAID kernel: mpt2sas0: removing handle(0x000f), sas_addr(0x5001e677b7db5fed)
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187856
Jan 29 23:57:22 SPE-UNRAID kernel: md: recovery thread woken up ...
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187864
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187872
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187880
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187888
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187896
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187904
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187912
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187920
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187928
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187936
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187944
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187952
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187960
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187968
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187976
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187984
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628187992
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188000
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188008
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188016
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188024
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188032
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188040
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188048
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188056
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188064
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188072
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188080
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188088
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188096
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188104
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188112
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188120
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188128
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188136
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188144
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188152
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188160
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188168
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188176
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188184
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188192
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188200
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188208
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188216
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188224
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188232
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188240
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188248
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188256
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188264
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188272
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188280
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188288
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188296
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188304
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188312
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188320
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188328
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188336
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188344
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188352
Jan 29 23:57:22 SPE-UNRAID kernel: md: disk4 write error, sector=4628188360
Jan 29 23:57:22 SPE-UNRAID kernel: write_file: write error 4
Jan 29 23:57:22 SPE-UNRAID kernel: md: could not write superblock from /boot/config/super.dat
Jan 29 23:57:22 SPE-UNRAID kernel: md: recovery thread has nothing to resync

Link to comment
JimPhreak Enthusiast

JimPhreak

Posted
  • Author
Posted

Without at least a SMART report it’s difficult to say.

 

Unfortunately I removed the drive so I can't run a smart report from within UnRAID.  I did however run short and extended tests in WD Data Lifeguard (drive is a WD Red 3TB drive) and both tests passed.

 

Smart data shown below:

 

SmartData_zpserms7gt2.jpg

 

If I determined the disk was ok, how do I re-enable it after UnRAID automatically disabled?

Link to comment
  • 11 months later...

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing