Opensuse 13.2 - usb disks not mounting after upgrade
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
but it doesn't mount in the map I used : /home/me/usbdisk (I can't see any files there)
there has been an error when adressing 'GARFIELD', the system gives the following erro: An unspecified error has occurred: Adding read ACL for uid 0 to `/run/media/root' failed: Invalid argument
Garfield = my usb-disk
Last edited by newtuxuser; 10-27-2016 at 04:44 PM.
...to reset it to something easier to find/remember.
Quote:
there has been an error when adressing 'GARFIELD', the system gives the following erro: An unspecified error has occurred: Adding read ACL for uid 0 to `/run/media/root' failed: Invalid argument
Garfield = my usb-disk
It seems it's seeing the device as /dev/sde, with a partion of /dev/sde1. Did you try to manually mount THAT? Are you trying to mount as root? What desktop GUI are you running? Are you trying to mount via GUI (applet, file manager, etc.), or via CLI (mount command)
Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 4304895 4302848 2,1G 82 Linux swap / Solaris
/dev/sda2 * 4304896 312578047 308273152 147G 83 Linux
Device Boot Start End Sectors Size Id Type
/dev/sdb1 88100864 3907028991 3818928128 1,8T 83 Linux
/dev/sdb2 2048 35246079 35244032 16,8G 83 Linux
/dev/sdb3 35246080 88100863 52854784 25,2G 83 Linux
Partitietabel-items liggen niet in schijfvolgorde.
Schijf /dev/sdd: 7,5 GiB, 8036285952 bytes, 15695871 sectoren
Eenheid: sectoren van 1 * 512 = 512 bytes
Sectorgrootte (logisch/fysiek): 512 bytes / 512 bytes
In-/uitvoergrootte (minimaal/optimaal): 512 bytes / 512 bytes
Schijflabeltype: dos
Schijf-ID: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdd1 44 15679439 15679396 7,5G b W95 FAT32
/dev/sdd3 24897 24897 0 0B 0 Empty
Device Boot Start End Sectors Size Id Type
/dev/sde1 2048 3907027115 3907025068 1,8T 7 HPFS/NTFS/exFAT
I can mount /dev/sdd1 (the Vfat) manually
Mounting /dev/sde1 (NTFS) remains impossible
Is there a way to make any of both work automatically again ?
This is the output of the NTFS :
linux-7fi6:/home/marc # mount /dev/sde1 /home/marc/UsbDisk-Toshiba
The disk contains an unclean file system (0, 0).
The file system wasn't safely closed on Windows. Fixing.
Last edited by newtuxuser; 10-27-2016 at 05:18 PM.
This is the output of the NTFS :
linux-7fi6:/home/marc # mount /dev/sde1 /home/marc/UsbDisk-Toshiba
The disk contains an unclean file system (0, 0).
The file system wasn't safely closed on Windows. Fixing.
The easiest solution to this is to plug this drive into a Windows machine (or VM,) allow it to clean/mark the FS clean and then plug it back into Linux. Don't forget to use safe eject on Windows.
Last edited by designator; 10-28-2016 at 12:18 PM.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,800
Rep:
Quote:
Originally Posted by newtuxuser
I can mount /dev/sdd1 (the Vfat) manually
Mounting /dev/sde1 (NTFS) remains impossible
Is there a way to make any of both work automatically again ?
I've also had "upgrades" to my 13.2 system and I'm having a similar problem. SD card was barely even getting detected upon insertion into the reader. Running "journalctl -f" showed that the USB subsystem was detecting something but it wasn't mounting it. Running "fdisk -l" didn't show it was present. Under KDE, clicking on the USB icon in the tray didn't show anything.
After a reboot, the device was showing up in journalctl output but it wasn't getting mounted. The USB icon in the KDE tray showed it was there -- it knew what the volume label was, showed me the standard three options of what I could do, etc. -- but trying any of those options just resulted in a message telling me it couldn't mount it. Running "fdisk -l" after the reboot showed it was there. I could mount it by hand as root. Then I could click on the USB tray icon and start a Dolphin session to copy files off of it.
This smells like some permissions screw-up was included with one of the recent patches as an unannounced "feature". I can attempt to umount the SD card using the tray icon but a pop-up dialog (unsurprisingly) informs me that someone else (that "root" fellow) mounted it. I'll post any fix if I come up with one.
I miss the days when you got release notes that you could read before you embarked on a patch session. They didn't warn you of 100% of what the patches were for but you at least had some idea of why the patches were being applied when you said "go" and when something went wrong you had an idea that it might be related to one of the patches.
I am having the same problem. I upgraded today, and the computer recognizes the usb stick and also the portable drive. Both were shut down correctly.
Error msg is:
Could not mount the following device .....
An unspecified error has occurred: Adding read ACL for uid 0 to `/run/media/root' failed: Invalid argument.
There are problems with this upgrade.
From root, a new desktop, and including my working desktop and all with the same results,
Need a fix for this problem.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,800
Rep:
Quote:
Originally Posted by rnturn
I'll post any fix if I come up with one.
Not my fix: TB0ne's link above did the trick. BTW, I noticed that all of the udev rules files in /usr/lib/udev/rules.d were dated "Oct 5" so that's either the date the patch team put together the "fix" or when I got around to downloading the patches.
At any rate: Note the warning at the top of the file referenced in the link. I found that placing the fix at the above link into a separate file works just fine:
Code:
# cd /etc/udev/rules.d
# vi 81-udisks2-local.rules
i
# Use /media, not /run/media/<username>
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{UDISKS_FILESYSTEM_SHARED}="1"
<ESC>
wq
# udevadm control --reload
Putting the fix under /etc makes it far, far less likely that you'll have redo the fix should a future patch replace files in /usr/lib/udev/rules.d.
This thread was very useful and informative, but as a relative newcomer, I find the rules file a bit opaque and I don't like "tinkering" unless I understand what I'm doing.
For those of similar mind, please note that the problem was fixed this morning by an update to the kernel desktop.
Distribution: openSUSE, Raspbian, Slackware. Previous: MacOS, Red Hat, Coherent, Consensys SVR4.2, Tru64, Solaris
Posts: 2,800
Rep:
Quote:
Originally Posted by docrob
This thread was very useful and informative, but as a relative newcomer, I find the rules file a bit opaque and I don't like "tinkering" unless I understand what I'm doing.
I agree. documentation for some of these things is sparce and what's out there is a bit confusing to anyone not on the team that wrote the code. I learned a bit about the udev rules when writing my own rules for mounting cameras, CF/SD cards, etc. But I was putting things in "local" rules files the /etc/udev tree to avoid fooling around with the vendor-shipped files. And to avoid having them over-written by an update. If I screw something up, I merely "hide" the "local" file and reload the rules to undo my error.
Quote:
For those of similar mind, please note that the problem was fixed this morning by an update to the kernel desktop.
Q: Do you still having working sound? I've lost that feature on my main desktop system due (I think) to a recent patch. (Edit: never mind about this one. It appears that one of the patches may have muted my sound but running alsamixer and resetting the level cured the problem.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
