READ ERRORS AFTER UPGRADING TO 6.9.2


5 posts in this topic Last Reply

Recommended Posts

Hello,

my box has been on for about 6 months without problems, the last 120 days continuously without reboots, with version 6.8.0.
A couple of weeks ago I added two new SSDs, without having any problem after.
Yesterday I decided to upgrade to 6.9.2 to be able to create a new pool from those new SSDs.
I finished the update at 9:30 am.
At 18:47 read errors appeared on 2 disks in the array.
I stopped and started the array and everything came back ok.
At 4:40 this morning the same errors came back again.
What can it be? Cables haven't moved in weeks, I just ran the firmware update.
Log extract:

Jun 10 18:47:09 UnraidOne kernel: blk_update_request: I/O error, dev sdj, sector 8658750032 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Jun 10 18:47:09 UnraidOne kernel: md: disk3 read error, sector=8658749968
Jun 10 18:47:09 UnraidOne kernel: md: disk3 read error, sector=8658749976
Jun 10 18:47:28 UnraidOne kernel: blk_update_request: I/O error, dev sdi, sector 8658750032 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Jun 10 18:47:28 UnraidOne kernel: md: disk2 read error, sector=8658749968
Jun 10 18:47:28 UnraidOne kernel: md: disk2 read error, sector=8658749976

Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=10819129544
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=10819129552
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=10819129544
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=10819129552
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=3071308800
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=3071308800
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=8659420560
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=8659420568
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=8659420560
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=8659420568
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=13125536760
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=13125536768
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=13125536760
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=13125536768
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=5124345600
Jun 10 18:47:31 UnraidOne kernel: md: disk3 read error, sector=5124345608
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=5124345600
Jun 10 18:47:31 UnraidOne kernel: md: disk2 read error, sector=5124345608
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=10737989584
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=10737989592
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=10737989584
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=10737989592
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=15073962112
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=15073962120
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=15073962112
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=15073962120
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=66463488
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=66463496
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=66463488
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=66463496
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=2867337032
Jun 10 18:47:32 UnraidOne kernel: md: disk2 read error, sector=2867337040
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=2867337032
Jun 10 18:47:32 UnraidOne kernel: md: disk3 read error, sector=2867337040
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=2147483760
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=2147483760
Jun 10 18:47:33 UnraidOne kernel: XFS (md3): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x80000070 len 8 error 5
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=2147483768
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=2147483776
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=2147483784
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=2147483792
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=2147483768
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=2147483776
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=2147483784
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=2147483792
Jun 10 18:47:33 UnraidOne kernel: XFS (md3): metadata I/O error in "xfs_imap_to_bp+0x5c/0xa2 [xfs]" at daddr 0x80000078 len 32 error 5
Jun 10 18:47:33 UnraidOne kernel: XFS (md3): xfs_do_force_shutdown(0x1) called from line 296 of file fs/xfs/xfs_trans_buf.c. Return address = 00000000a255120b
Jun 10 18:47:33 UnraidOne kernel: XFS (md3): I/O Error Detected. Shutting down filesystem
Jun 10 18:47:33 UnraidOne kernel: XFS (md3): Please unmount the filesystem and rectify the problem(s)
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=8594112408
Jun 10 18:47:33 UnraidOne kernel: md: disk2 read error, sector=8594112416
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=8594112408
Jun 10 18:47:33 UnraidOne kernel: md: disk3 read error, sector=8594112416
Jun 10 18:47:34 UnraidOne kernel: md: disk2 read error, sector=6445608232
Jun 10 18:47:34 UnraidOne kernel: md: disk2 read error, sector=6445608240
Jun 10 18:47:34 UnraidOne kernel: md: disk3 read error, sector=6445608232
Jun 10 18:47:34 UnraidOne kernel: md: disk3 read error, sector=6445608240
Jun 10 18:47:37 UnraidOne kernel: md: disk2 read error, sector=7027070920
Jun 10 18:47:37 UnraidOne kernel: md: disk2 read error, sector=7027070928
Jun 10 18:47:37 UnraidOne kernel: md: disk3 read error, sector=7027070920
Jun 10 18:47:37 UnraidOne kernel: md: disk3 read error, sector=7027070928
Jun 10 18:47:40 UnraidOne kernel: md: disk2 read error, sector=15552251080
Jun 10 18:47:40 UnraidOne kernel: md: disk2 read error, sector=15552251088
Jun 10 18:47:40 UnraidOne kernel: md: disk3 read error, sector=15552251080
Jun 10 18:47:40 UnraidOne kernel: md: disk3 read error, sector=15552251088
Jun 10 18:47:49 UnraidOne kernel: md: disk2 read error, sector=13563909008
Jun 10 18:47:49 UnraidOne kernel: md: disk2 read error, sector=13563909016
Jun 10 18:47:49 UnraidOne kernel: md: disk3 read error, sector=13563909008
Jun 10 18:47:49 UnraidOne kernel: md: disk3 read error, sector=13563909016
Jun 10 18:47:50 UnraidOne kernel: md: disk2 read error, sector=15552251112
Jun 10 18:47:50 UnraidOne kernel: md: disk2 read error, sector=15552251120
Jun 10 18:47:50 UnraidOne kernel: md: disk3 read error, sector=15552251112
Jun 10 18:47:50 UnraidOne kernel: md: disk3 read error, sector=15552251120
Jun 10 18:47:51 UnraidOne kernel: md: disk2 read error, sector=8594212960
Jun 10 18:47:51 UnraidOne kernel: md: disk2 read error, sector=8594212968
Jun 10 18:47:51 UnraidOne kernel: md: disk3 read error, sector=8594212960
Jun 10 18:47:51 UnraidOne kernel: md: disk3 read error, sector=8594212968
Jun 10 18:47:51 UnraidOne kernel: md: disk2 read error, sector=6788889192
Jun 10 18:47:51 UnraidOne kernel: md: disk2 read error, sector=6788889200
Jun 10 18:47:51 UnraidOne kernel: md: disk3 read error, sector=6788889192
Jun 10 18:47:51 UnraidOne kernel: md: disk3 read error, sector=6788889200
Jun 10 18:47:54 UnraidOne kernel: md: disk2 read error, sector=9252934224
Jun 10 18:47:54 UnraidOne kernel: md: disk3 read error, sector=9252934224
Jun 10 18:47:54 UnraidOne kernel: XFS (md2): metadata I/O error in "xfs_da_read_buf+0x9e/0xfe [xfs]" at daddr 0x227849250 len 8 error 5
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Jun 10 18:47:54 UnraidOne kernel: md: disk2 read error, sector=9254111360
Jun 10 18:47:54 UnraidOne kernel: md: disk2 read error, sector=9254111368
Jun 10 18:47:54 UnraidOne kernel: md: disk2 read error, sector=9254111376
Jun 10 18:47:54 UnraidOne kernel: md: disk2 read error, sector=9254111384
Jun 10 18:47:54 UnraidOne kernel: md: disk3 read error, sector=9254111360
Jun 10 18:47:54 UnraidOne kernel: md: disk3 read error, sector=9254111368
Jun 10 18:47:54 UnraidOne kernel: md: disk3 read error, sector=9254111376
Jun 10 18:47:54 UnraidOne kernel: md: disk3 read error, sector=9254111384

unraidone-diagnostics-20210611-0943.zip

Thank for your help.

image.jpeg

Link to post

Thank you @JorgeB

checking the logs I saw that the errors are immediately after these log lines:

unassigned.devices: Issue spin down timer for device '/dev/sdi'.

So could be the case.

Maybe disabling spindown could help too as a temporary fix.

Link to post
1 hour ago, NapalmZ said:

So could be the case.

Maybe disabling spindown could help too as a temporary fix.

 

I doubt the Unassigned Devices plugin touches anything Array or Pool related.

@dlandon should be able to confirm this.

 

What is the version of the plugin you have installed ?

Link to post
54 minutes ago, ChatNoir said:

 

I doubt the Unassigned Devices plugin touches anything Array or Pool related.

That's correct.  All it does is issue the standby command the to the UD device.

Link to post

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.