[Resolved] syslog flooded with device /dev/sdX problem getting size


Recommended Posts

I upgraded my main system from 6.3.5 to 6.4.0_rc14 today, woot!

 

Whenever the array is stopped, the log is flooded with these errors:  

Nov 23 12:16:36 Tower emhttpd: error: get_device_size, 1417: No medium found (123): open: /dev/sdd
Nov 23 12:16:36 Tower emhttpd: device /dev/sdd problem getting size
Nov 23 12:16:36 Tower emhttpd: error: get_device_size, 1417: No medium found (123): open: /dev/sde
Nov 23 12:16:36 Tower emhttpd: device /dev/sde problem getting size
Nov 23 12:16:36 Tower emhttpd: error: get_device_size, 1417: No medium found (123): open: /dev/sdb
Nov 23 12:16:36 Tower emhttpd: device /dev/sdb problem getting size
Nov 23 12:16:36 Tower emhttpd: error: get_device_size, 1417: No medium found (123): open: /dev/sdf
Nov 23 12:16:36 Tower emhttpd: device /dev/sdf problem getting size
Nov 23 12:16:36 Tower emhttpd: error: get_device_size, 1417: No medium found (123): open: /dev/sdc
Nov 23 12:16:36 Tower emhttpd: device /dev/sdc problem getting size

This is related to my multi-slot card reader, which is currently empty. The reader is similar to this:
  https://smile.amazon.com/SIIG-Multi-Slot-Reader-Writer-JU-MR0C12-S1/dp/B007B5VTOI/

 

tower-diagnostics-20171123-1231.zip

tower-diagnostics-20171123-1231.zip

Edited by ljm42
Link to comment
  • 4 weeks later...
On 12/15/2017 at 10:26 PM, ljm42 said:

This is still a problem in 6.4.0_rc16b, updated diags attached.

tower-diagnostics-20171215-2223.zip

 

Right this is just a noisy message.  What's happening is this.  In 6.4 we moved from single-threaded emhttp to multi-threaded nginx http server.  Used to be on each webgui page load, emhttp would "refresh status" synchronous with each http request.   In context of this issue, if the array is Stopped and you hot-plugged or hot-removed a storage device, you only have to click refresh on Main page and the change would be reflected.  In moving to nginx we can't be doing a complete "refresh status" on each request or else would be really slow.  How it works now is, when array is Stopped, background thread wakes up every second to evaluate the storage device config, checking to see if you added/removed any devices.  What you are seeing is the code complaining there is a storage device without any medium and hence reading the size is failing (because there's no device).  What we'll do to fix this is filter out "No medium found" and handle that specially.

 

@Bigdady92 not sure if this is what you're seeing.  Do you also have a card reader or maybe some kind of external enclosure without a device installed in it?

  • Like 1
Link to comment
  • 2 weeks 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.