Unassigned Unmounted Device showing Reads

It is not a bug with either Unraid 6.9 or UD.  Something is reading from the disk.  If you have preclear installed, remove it and see if the reads stop.

Ingenious suggestion, @dlandon. However, Preclear is present and targetted on the DOM but not running (it offers a start button) and its log is empty.

 

I've removed the Preclear plugin but the reads continue. What makes you sure it's not a bug in 6.9 or Unassigned Devices?

 

MAIN offers me the option to "spin down the device". I'm not sure what a spun down DOM would look like. Is this an option you suggest I explore?

 

-- 

Chris

Edited December 31, 2020 by bidmead

The tracking of reads and writes on UD disks is the same logic as on the array disks.  I also do not see any of this behavior.  UD does not do any reading or writing of disks.  It only mounts/unmounts them.

 

How fast are the reads incrementing?

 

Spin down the UD disk and see if it is spun back up while being unmounted.

 

On your next post, include diagnostics.

I do need to point out that the UD disks are now monitored by Unraid just like array disks, so a small amount of reads will occur.  Unraid monitors disks for SMART issues and over temperature.  You've not seen this before because UD hasn't shown reads and writes until now.

Ah, OK, @dlandon. So UnRAID is in fact doing raw dd-style reads of unmounted, unassigned drives for diagnostics. That explains everything. Thanks.

 

-- 

Chris

Please mark this as solved.

Changed Status to Closed

Changed Priority to Other

I'm not sure about this. As there's no useful data to be gained from these reads of a non-S.M.A.R.T DOM (is there?) shouldn't the allocated disk slot be left alone?

 

Or is it perhaps the case that these reads are necessary to ensure that the device hasn't gone historic?

 

If so, would it be sensible to suggest (as a feature request) that there be a user option to mark a device as permanently historic, detaching it from its logical slot?

 

-- 

Chris 

Edited January 1, 2021 by bidmead
additional thoughts

It's also clear that there is a bug associated with this problem, although perhaps only cosmetic: the green button to the extreme left of the device in the Unassigned Devices list suggests that clicking the button will "spin down the device". I'm not clear how you would spin down a DOM but this button does nothing.

 

-- 

Chris

Edited January 1, 2021 by bidmead
grammar

Please report UD issues in the existing plugin support thread: