Disk read error


Recommended Posts

I'm receiving errors on my server. Any help would be great.

 

md: disk12 read error, sector=4099723704
md: disk12 read error, sector=4099723712
md: disk12 read error, sector=4099723720
md: disk12 read error, sector=4099723728
md: disk12 read error, sector=4099723736
md: disk12 read error, sector=4099723744
md: disk12 read error, sector=4099723752
sd 2:0:1:0: [sdj] tag#4112 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 2:0:1:0: [sdj] tag#4112 Sense Key : 0x3 [current]
sd 2:0:1:0: [sdj] tag#4112 ASC=0x11 ASCQ=0x0
sd 2:0:1:0: [sdj] tag#4112 CDB: opcode=0x88 88 00 00 00 00 00 f4 5c d1 20 00 00 00 d0 00
print_req_error: critical medium error, dev sdj, sector 4099723552
md: disk12 read error, sector=4099723488
md: disk12 read error, sector=4099723496
md: disk12 read error, sector=4099723504
md: disk12 read error, sector=4099723512
md: disk12 read error, sector=4099723520
md: disk12 read error, sector=4099723528
md: disk12 read error, sector=4099723536
md: disk12 read error, sector=4099723544
md: disk12 read error, sector=4099723552
md: disk12 read error, sector=4099723560
md: disk12 read error, sector=4099723568
md: disk12 read error, sector=4099723576
md: disk12 read error, sector=4099723584
md: disk12 read error, sector=4099723592
md: disk12 read error, sector=4099723600
md: disk12 read error, sector=4099723608
md: disk12 read error, sector=4099723616
md: disk12 read error, sector=4099723624
md: disk12 read error, sector=4099723632
md: disk12 read error, sector=4099723640
md: disk12 read error, sector=4099723648
md: disk12 read error, sector=4099723656
md: disk12 read error, sector=4099723664
md: disk12 read error, sector=4099723672
md: disk12 read error, sector=4099723680
md: disk12 read error, sector=4099723688

 

#	ATTRIBUTE NAME	FLAG	VALUE	WORST	THRESHOLD	TYPE	UPDATED	FAILED	RAW VALUE
1	Raw read error rate	0x000f	118	090	006	Pre-fail	Always	Never	185652816
3	Spin up time	0x0003	095	093	000	Pre-fail	Always	Never	0
4	Start stop count	0x0032	095	095	020	Old age	Always	Never	5767
5	Reallocated sector count	0x0033	100	100	010	Pre-fail	Always	Never	336
7	Seek error rate	0x000f	073	060	030	Pre-fail	Always	Never	24203337
9	Power on hours	0x0032	077	077	000	Old age	Always	Never	20960 (2y, 4m, 21d, 8h)
10	Spin retry count	0x0013	100	100	097	Pre-fail	Always	Never	0
12	Power cycle count	0x0032	100	100	020	Old age	Always	Never	483
183	Runtime bad block	0x0032	100	100	000	Old age	Always	Never	0
184	End-to-end error	0x0032	100	100	099	Old age	Always	Never	0
187	Reported uncorrect	0x0032	096	096	000	Old age	Always	Never	4
188	Command timeout	0x0032	100	099	000	Old age	Always	Never	1 1 1
189	High fly writes	0x003a	035	035	000	Old age	Always	Never	65
190	Airflow temperature cel	0x0022	071	058	045	Old age	Always	Never	29 (min/max 17/34)
191	G-sense error rate	0x0032	100	100	000	Old age	Always	Never	0
192	Power-off retract count	0x0032	100	100	000	Old age	Always	Never	68
193	Load cycle count	0x0032	051	051	000	Old age	Always	Never	99166
194	Temperature celsius	0x0022	029	042	000	Old age	Always	Never	29 (0 12 0 0 0)
197	Current pending sector	0x0012	100	099	000	Old age	Always	Never	24
198	Offline uncorrectable	0x0010	100	099	000	Old age	Offline	Never	24
199	UDMA CRC error count	0x003e	200	200	000	Old age	Always	Never	0
240	Head flying hours	0x0000	100	253	000	Old age	Offline	Never	4250h+12m+19.153s
241	Total lbas written	0x0000	100	253	000	Old age	Offline	Never	21172257942
242	Total lbas read	0x0000	100	253	000	Old age	Offline	Never	217201527283

 

Edited by WhazZzZzup17
Link to comment
15 minutes ago, itimpi said:

Assuming that SMART report is for the disk mentioned in the syslog snippet I would say the disk is in a bad way.    It has a significant number of reallocated sectors and a non-Zero value for Pending sectors - both of which are bad signs.

In other words, I should backup the files and replace the drive?

 

Is there a chance that any of the files are corrupt?

Link to comment
16 minutes ago, WhazZzZzup17 said:

n other words, I should backup the files and replace the drive?

Just replacing the drive should be enough.   As to whether you should backup the drive contents that is independent of whether you are going to replace the drive - you should always be backing up any important files regardless.   

 

18 minutes ago, WhazZzZzup17 said:

Is there a chance that any of the files are corrupt?

Impossible to be certain unless you have backups (or at the very least file checksums) that they can be compared against.   In normal operation one can expect a drive itself to detect corruption, but once a drive starts to fail I am not sure how reliable that detection actually is.

Link to comment
5 minutes ago, itimpi said:

Just replacing the drive should be enough.   As to whether you should backup the drive contents that is independent of whether you are going to replace the drive - you should always be backing up any important files regardless.   

 

Impossible to be certain unless you have backups (or at the very least file checksums) that they can be compared against.   In normal operation one can expect a drive itself to detect corruption, but once a drive starts to fail I am not sure how reliable that detection actually is.

I have never had a failed hard drive. Would you recommend that before I replace the drive, I copy the contents to the new hard drive and then replace, or should I just remove the failed drive and the parity should re-create the contents from the removed damage drive?

 

I also have offsite backups of the drive, however, my backup is about a month old and there are new files that I haven't backed up.

Link to comment
5 minutes ago, WhazZzZzup17 said:

I have never had a failed hard drive. Would you recommend that before I replace the drive, I copy the contents to the new hard drive and then replace, or should I just remove the failed drive and the parity should re-create the contents from the removed damage drive?

 

I also have offsite backups of the drive, however, my backup is about a month old and there are new files that I haven't backed up.

I would just remove the drive so that Unraid starts ‘emulating’ it from the combination of the other drives plus parity.    You can then look at the contents of this emulated drive to check that they look OK, as that is what will end up on any rebuilt disk.

 

keep the removed drive intact as that is your fallback.     One of the strengths of Unraid is that each disk is a self-contained filing system that can be mounted and read outside of the array which can be a great help if any data recovery is needed.

Link to comment
15 minutes ago, itimpi said:

I would just remove the drive so that Unraid starts ‘emulating’ it from the combination of the other drives plus parity.    You can then look at the contents of this emulated drive to check that they look OK, as that is what will end up on any rebuilt disk.

 

keep the removed drive intact as that is your fallback.     One of the strengths of Unraid is that each disk is a self-contained filing system that can be mounted and read outside of the array which can be a great help if any data recovery is needed.

Thank you for the help. I will do as suggested.

 

My one concern is I have no idea how to verify if any files are corrupted. I have so many pictures and it will be hard to review each file upon the completion of the re-build. How do you go about comparing thousands of files with their checksums? I used RCLONE in the past to backup my data offline. Does rclone do this?

Edited by WhazZzZzup17
Link to comment

The normal way is to create checksums of both sets of files.     You can then easily compare the two sets of checksums to see which files do not have the same checksum in both the live and backup copies.     However creating the checksums in the first place is a non-trivial task.    In practise you may just have to assume the rebuilt drive is fine with the ability to check specific files against your backups on demand.

Link to comment
23 minutes ago, itimpi said:

The normal way is to create checksums of both sets of files.     You can then easily compare the two sets of checksums to see which files do not have the same checksum in both the live and backup copies.     However creating the checksums in the first place is a non-trivial task.    In practise you may just have to assume the rebuilt drive is fine with the ability to check specific files against your backups on demand.

Thank you for your help.

Link to comment

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.