Loki File(manager) error after Wine & VirtualBox installs

Discussion in 'Software & Applications' started by Tom Henry, Nov 21, 2016.

  1. Tom Henry

    Tom Henry Thread Starter
    Expand Collapse
    New Member

    Nov 20, 2016
    Likes Received:
    Okay, the good news is that for the first time ever (maybe 10 times over 5 years) I got vbox to install, establish a Win10 vm, and actually run a very old 32bit ms dos app ;)

    With WINE I was nowhere near as fortunate :(

    However, perhaps unrelated to those installations, I am now having problems with Files(mnager) and Dolphin

    Getting the following error message ...
    An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/sda1 at /media/tom/SYSTEM: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sda1" "/media/tom/SYSTEM"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0).
    Metadata kept in Windows cache, refused to mount.
    Failed to mount '/dev/sda1': Operation not permitted
    The NTFS partition is in an unsafe state. Please resume and shutdown
    Windows fully (no hibernation or fast restarting), or mount the volume
    read-only with the 'ro' mount option.

    This happens when trying to access the following "devices" : SYSTEM, OS, DATA, Toms_Stuff, and Box. ("DATA" is a Windows NTFS partition on the HDD, "Toms_stuff" is a folder on an NTFS partition, same for "Box") Same message for each attempt to enter on of those (non-linux-created) devices.

    The only devices NOT giving the error are the two disk partitions dedicated to the two linux distros that are installed (elementary OS and Xubuntu) in addition to Win10 on this HP / AMD64 desktop.

    To be complete, the error message pops up in Files... in Dolphin the program just becomes unresponsive for the same devices above that give the error message.

    Now it's intuitively obvious that he error message means noting that I fathom. Sooo, if anyone has a clue about where I can start, any clues would be greatly appreciated.

    BTW when this error began, I uninstalled VirtualBox (which I was more suspicious of because I hadn't (yet) seen the error following t he WINE install -- but the error persisted after killing VB.

    Sincere thanks for any guidance...

Share This Page