Assessment on this disk error message

Help and Support Vero 4K / Vero 4K +
1

Hello folks,

A week ago I had TV recordings failing on me - and my quick fix - was just to reboot the Vero.
Recording the next days - completed fine without issues.

The drive in question is connected directly to the Vero - and among other things acting as storage for TV recordings.

Yesterday - I had to do another reboot - and got hung on this below message for a while:

failed-unmounting
failed-unmounting1920Ɨ317 75.9 KB

I just let the message sit there - until it finally timed out.
Now I am wondering if its because the connected drive is about to go bad.

How would I investigate the health of the disk further?

I canā€™t reproduce the issue in question - so I donā€™t know how useful the log will be - here we go anyway: https://paste.osmc.tv/aterifonef

If more info is needed - please let me know - thanks in advance :wink:

2

You could run a smartctl test (we can provide further advice) if the enclosure supports it.
I do wonder if some other services just crashed or brought some instability to the system however

Sam

3

Hi Sam.

Sounds interesting running a smartctl test!
The enclosure is an icy-box - more specifically - this one
At the bottom of the page (above link) there is a data sheet - with more specs.

Regarding other service.
I have a Raspberry Pi running Volumio.
My music library is stored on this drive as well (although having a NAS - itā€™s not on 24/7/365 - due to ridiculous electricity prices here in Denmark) - as itā€™s always on - and Iā€™m a heavy user of Volumio.

In fact it was due to the fact that Volumio stopped playing music the other day - it froze up - endlessly searching for music.
Turned out that it lost access to the music library.

I ended up restarting the Vero - in order to re-establish connection to the library - and got the screen with ā€œfailed umountingā€ as seen in my first post of this thread.

4

Give it a try, while with the SSD information via the USB enclosure will be limited.
Assume you know how to access the cli
sudo apt install smartmontools
sudo smartctl -d auto -a /dev/sda

9

@fzinken - yeah I am familiar with accessing the cli.

Here is the output - when running the suggested command:

osmc@Dagligstue:~$ sudo smartctl -d auto -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-4.9.269-62-osmc] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: Connection timed out
osmc@Dagligstue:~$

10

OK that could indicated that the USB enclosure is not playing well with this version of snartctl.

I suggest just to keep an eye on it and only when it happens again to dig deeper.

11

Or try to hard overwrite the device protocol:

sudo smartctl -d sat -a /dev/sda

Just a try but it does not cost more than some seconds of time.

12

@fzinken - thanks for your input and suggestion.

For now I am considering setting backup for (important) files on the disk.

@JimKnopf

Here is the output - when I run the command you suggested:

osmc@Dagligstue:/$ sudo smartctl -d sat -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-4.9.269-62-osmc] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported scsi opcode

A mandatory SMART command failed: exiting. To continue, add one or more ā€˜-T permissiveā€™ options.

13

Thank you for this information. As fzinken already mentioned, it looks like this device, or rather the USB bridge used in it, isnā€™t supported by smartctl. You can also try the device type parms -d sntjmicron or -d usbjmicron but this is as the last try just on trial and error basis.
If this is an original JMicron device, you might still find online articles by entering the model name and smartctl on how to get the two to communicate with each other, or a special tool from the manufacturer that you can use to test the drive under Windows/Linux.
If you installed the hdd/ssd in an enclosure yourself, I would recommend trying a different enclosure.

14

Thanks for elaborating Jim.

Yeah I installed the disk in the enclosure myself.
It was a spare disk I had sitting in my drawer - and bought the enclosure for another project.
At some point the enclosure ended up in the same drawer - and I thought why not bring it to use.

Tried your suggestions:

sudo smartctl -d sntjmicron -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-4.9.269-62-osmc] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: Connection timed out

sudo smartctl -d usbjmicron -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-4.9.269-62-osmc] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported field in scsi command

A mandatory SMART command failed: exiting. To continue, add one or more ā€˜-T permissiveā€™ options.

:::::::::::::

Donā€™t waste more time on this Jim - I was just trying to be proactive and see if could get some useful information on the health of the drive.
Maybe itā€™s time to see if the drawer holds another spare drive - that could be useful.

1 Like
15

:smile:

1 Like