Unexpected errors in log: "critical medium error, dev sda": possible file corruption?

Help and Support
1

Hello!
Volumio ver: 3.435
RPi3B+ with Raspberry Pi DAC Pro
Source: USB Pendrive

I have got the following error messages in the log, wich indicates, that something went wrong with playback of some specific files and I suspect it could be some file corruption error involved.
I only used this USB Pendrive with my music files on it in my RPi3B+, since Volumio is installed, so if there’s any similar issue, like data corruption involved, that may likely be caused by the Volumio system (or the Pi device, or both together) itself.

Here’s a short extract of the log file that catches the error warnings (like: blk_update_request: critical medium error, dev sda, sector 6843456 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0)

Mar 21 11:23:22 volumio volumio[841]: info: CorePlayQueue::getTrack 72
Mar 21 11:23:22 volumio volumio[841]: verbose: STATE SERVICE {"status":"play","position":0,"seek":11,"duration":171,"samplerate":"44.1 kHz","bitdepth":"24 bit","channels":2,"random":false,"updatedb":false,"repeat":false,"bitrate":"256 Kb
Mar 21 11:23:22 volumio volumio[841]: verbose: CURRENT POSITION 72
Mar 21 11:23:22 volumio volumio[841]: info: CoreStateMachine::syncState   stateService play
Mar 21 11:23:22 volumio volumio[841]: info: CoreStateMachine::syncState   currentStatus play
Mar 21 11:23:22 volumio volumio[841]: info: Received an update from plugin. extracting info from payload
Mar 21 11:23:22 volumio volumio[841]: info: CoreStateMachine::pushState
Mar 21 11:23:22 volumio volumio[841]: info: CorePlayQueue::getTrack 72
Mar 21 11:23:22 volumio volumio[841]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Mar 21 11:23:22 volumio volumio[841]: info: CoreCommandRouter::volumioPushState
Mar 21 11:23:22 volumio volumio[841]: info: CoreStateMachine::pushState
Mar 21 11:23:22 volumio volumio[841]: info: CorePlayQueue::getTrack 72
Mar 21 11:23:22 volumio volumio[841]: info: CoreCommandRouter::volumioPushState
Mar 21 11:23:22 volumio volumio[841]: info: ------------------------------ 20ms
Mar 21 11:24:42 volumio kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Mar 21 11:24:42 volumio kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
Mar 21 11:24:42 volumio kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
Mar 21 11:24:42 volumio kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 68 6c 40 00 00 f0 00
Mar 21 11:24:42 volumio kernel: blk_update_request: critical medium error, dev sda, sector 6843456 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0
Mar 21 11:24:57 volumio kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Mar 21 11:24:57 volumio kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
Mar 21 11:24:57 volumio kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
Mar 21 11:24:57 volumio kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 68 6d e8 00 00 08 00
Mar 21 11:24:57 volumio kernel: blk_update_request: critical medium error, dev sda, sector 6843880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 21 11:24:58 volumio kernel: sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s
Mar 21 11:24:58 volumio kernel: sd 0:0:0:0: [sda] tag#0 Sense Key : 0x3 [current]
Mar 21 11:24:58 volumio kernel: sd 0:0:0:0: [sda] tag#0 ASC=0x11 ASCQ=0x0
Mar 21 11:24:58 volumio kernel: sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 68 6d e8 00 00 08 00
Mar 21 11:24:58 volumio kernel: blk_update_request: critical medium error, dev sda, sector 6843880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Mar 21 11:25:04 volumio volumio[841]: info:
Mar 21 11:25:04 volumio volumio[841]: ---------------------------- MPD announces system playlist update
Mar 21 11:25:04 volumio volumio[841]: info: Ignoring MPD Status Update
Mar 21 11:25:04 volumio volumio[841]: info:
Mar 21 11:25:04 volumio volumio[841]: ---------------------------- MPD announces state update: player
Mar 21 11:25:04 volumio volumio[841]: info: ControllerMpd::getState
Mar 21 11:25:04 volumio volumio[841]: verbose: ControllerMpd::sendMpdCommand status
Mar 21 11:25:04 volumio volumio[841]: error: updateQueue error: null
Mar 21 11:25:04 volumio volumio[841]: info: ------------------------------ 3ms
Mar 21 11:25:04 volumio volumio[841]: info: sendMpdCommand status took 2 milliseconds
Mar 21 11:25:04 volumio volumio[841]: verbose: ControllerMpd::parseState
Mar 21 11:25:04 volumio volumio[841]: info: ControllerMpd::pushState
Mar 21 11:25:04 volumio volumio[841]: info: CoreCommandRouter::servicePushState
Mar 21 11:25:04 volumio volumio[841]: info: CoreStateMachine::pushState
Mar 21 11:25:04 volumio volumio[841]: info: CorePlayQueue::getTrack 72
Mar 21 11:25:04 volumio volumio[841]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Mar 21 11:25:04 volumio volumio[841]: info: CoreCommandRouter::volumioPushState
Mar 21 11:25:04 volumio volumio[841]: info: CorePlayQueue::getTrack 72
Mar 21 11:25:04 volumio volumio[841]: verbose: STATE SERVICE {"status":"stop","position":null,"seek":null,"duration":null,"samplerate":null,"bitdepth":null,"channels":null,"random":false,"updatedb":false,"repeat":false,"bitrate":null,"is
Mar 21 11:25:04 volumio volumio[841]: verbose: CURRENT POSITION 72
Mar 21 11:25:04 volumio volumio[841]: info: CoreStateMachine::syncState   stateService stop
Mar 21 11:25:04 volumio volumio[841]: info: CoreStateMachine::syncState   currentStatus play

Could someone give any explanation to these error entries, and that what kind of issue it could be?

Thank you!

2

Even more likely is that your USB Pendrive is just dying.

3

I don’t think so. It’s an almost brand new Sandisk that have been only used on a Windows PC to copy the audio files to it. But sometimes if I remove it from the Pi and plug in to my PC, the Windows detects it as it has some file system issues and repairs it (that is also makes me suspicious regarding the Volumio system or/and the Pi). So any corruption happens with the data or the file system, it only could happen while plugged in to the Volumio device.

4

Are you shutting down the rPi when you pull the USB storage?

And you might try a different one than in the link you shared. I have thrown them all away (4 pieces). As those are very fragile and unstable. Have much better experience with the Cruzer fit.

5

I guess I don’t have to (theoretically) shut down the whole system before plugging out the USB device, just to use the “Safely remove media” option, and in Volumio to do this that’s selectable in the upper right corner “…” context menu where the device is listed.

Edit.: And of course that’s how I do it all the time. And can I count on any “experts” to revise and comment to my problem here?