My log is filling with these errors for an unassigned USB device that is not currently attached to the server.

 

Jan 13 09:28:53 MediaNAS kernel: Buffer I/O error on dev sdj1, logical block 44, async page read
Jan 13 09:29:03 MediaNAS ntfs-3g[17115]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Jan 13 09:29:03 MediaNAS ntfs-3g[17115]: Failed to read index block: Input/output error
Jan 13 09:29:03 MediaNAS kernel: Buffer I/O error on dev sdj1, logical block 44, async page read
Jan 13 09:29:13 MediaNAS ntfs-3g[17115]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Jan 13 09:29:13 MediaNAS ntfs-3g[17115]: Failed to read index block: Input/output error
Jan 13 09:29:13 MediaNAS kernel: Buffer I/O error on dev sdj1, logical block 44, async page read
Jan 13 09:29:24 MediaNAS ntfs-3g[17115]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Jan 13 09:29:24 MediaNAS ntfs-3g[17115]: Failed to read index block: Input/output error

I am currently running a correcting parity check to try and track down why every parity check results in 1 error.  However, the errors first appeared in the log yesterday and these errors are likely not related to the parity check.

 

There is currently no sdj device.  When I plugged in a 14TB Easystore USB 3 drive (which has one ntfs partition) on Saturday night to back up some shares to it, it was assigned to sdj.  The backup appeared to complete without issue and I disconnected the drive.  This morning, I looked at the log after starting the parity check and noticed all the errors which seem to have started yesterday morning at about 10:48am.  This is approximately the time the backup completed and I detached the drive.

 

Did it not unmount properly and unRAID is still looking for a drive that is no longer present?  Is a reboot necessary to halt the errors?

 

Diagnostics attached in case they are helpful.

 

 

medianas-diagnostics-20200113-0936.zip

1 minute ago, Hoopster said:

There is currently no sdj device. 

I've seen this before multiple times with NTFS devices, you'll need to reboot to stop the error.

6 minutes ago, johnnie.black said:

I've seen this before multiple times with NTFS devices, you'll need to reboot to stop the error.

Thanks.  I'll reboot when the parity check completes.  I started getting one parity error on every check when I installed a Dell H310 HBA into the server a few months ago.

 

Perhaps I have a cabling issue.  I attached the parity and all data drives to the HBA and got lots of CRC errors on the parity drive.  After reconnecting it via an MB SATA port, the CRC errors on the parity drive disappeared.  Perhaps one (or more) of the connectors on the breakout cables is bad and is causing the error.  I am using them all (except the one to which parity was attached) for the data drives and empty drive slots in the 8-bay hot swap cage in my server.

 

I am currently running a correcting check with all data drives on the HBA and parity attached to the MB. Then I'll run a non-correcting check to see if I get the usual 1 parity error again.