Error mounting system managed device

1. Error mounting system-managed device
   

   Hello everybody.

   First of all let me state clearly that i am a noob in linux.

   I have an Acer 6930ZG laptop which originally had two patritions in its disk, one with Vista and one for storage, «DATA», both ntfs. I installed ubuntu 13.04 in the vista partition, kept using the other for storage and everything worked fine until i tried to install the latest nvidia driver from their site. Probably my bad(?) because there has been a kernel update recently. Then i installed 13.04 again on the same partition but now the second partition cant be mounted and i get this error message
   Screenshot from 2014-03-13 14:11:00.png

   I did some research and found this http://ubuntuforums.org/showthread.php?t=1688937 but i think it is way more complicated than what i want since it involves dual OS, different bootloaders etc and i didnt get what the solution was. I just want to mount the partition and use it as storage without losing my files.

   sudo blkid outputs this

   Code:

   billy@billy-PC:~$ sudo blkid
   /dev/sda1: UUID="197340b2-f58d-4bb5-b1c4-26eafbe20bea" TYPE="ext4" 
   /dev/sda2: LABEL="DATA" UUID="FC54D24254D1FF78" TYPE="ntfs" 
   /dev/sda3: UUID="1c614f81-d62f-4a9a-a0f4-0fd50f29354d" TYPE="swap"

   sudo fdisk -lu outputs this

   Code:

   billy@billy-PC:~$ sudo fdisk -lu
   
   Disk /dev/sda: 250.1 GB, 250059350016 bytes
   255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
   Units = sectors of 1 * 512 = 512 bytes
   Sector size (logical/physical): 512 bytes / 512 bytes
   I/O size (minimum/optimal): 512 bytes / 512 bytes
   Disk identifier: 0x00042005
   
      Device Boot      Start         End      Blocks   Id  System
   /dev/sda1   *        2048   256780287   128389120   83  Linux
   /dev/sda2       256780288   480964607   112092160    7  HPFS/NTFS/exFAT
   /dev/sda3       480964608   488394751     3715072   82  Linux swap / Solaris

   sudo parted -l outputs this

   Code:

   billy@billy-PC:~$ sudo parted -l
   Model: ATA Hitachi HTS54322 (scsi)
   Disk /dev/sda: 250GB
   Sector size (logical/physical): 512B/512B
   Partition Table: msdos
   
   Number  Start   End    Size    Type     File system     Flags
    1      1049kB  131GB  131GB   primary  ext4            boot
    2      131GB   246GB  115GB   primary  ntfs
    3      246GB   250GB  3804MB  primary  linux-swap(v1)

   fstab looks like this

   # /etc/fstab: static file system information.
   #
   # Use ‘blkid’ to print the universally unique identifier for a
   # device; this may be used with UUID= as a more robust way to name devices
   # that works even if disks are added and removed. See fstab(5).
   #
   # <file system> <mount point> <type> <options> <dump> <pass>
   # / was on /dev/sda1 during installation
   UUID=197340b2-f58d-4bb5-b1c4-26eafbe20bea / ext4 errors=remount-ro 0 1
   # /media/DATA was on /dev/sda2 during installation
   UUID=FC54D24254D1FF78 /media/DATA ntfs defaults,umask=007,gid=46 0 0
   # swap was on /dev/sda3 during installation
   UUID=1c614f81-d62f-4a9a-a0f4-0fd50f29354d none swap sw 0 0

   I suppose that the answer is somethere in the above but i cant see it.

   Thank in advance

   Last edited by billy_kailas; March 13th, 2014 at 10:53 PM.

   ---

2. Re: Error mounting system-managed device
   

   I ran sudo ntfsfix /dev/sda2 and this is the output

   Code:

   billy@billy-PC:~$ sudo ntfsfix /dev/sda2Mounting volume... ntfs_mst_post_read_fixup_warn: magic: 0x6f2d6366  size: 4096   usa_ofs: 26740  usa_count: 29284: Invalid argument
   Actual VCN (0x322d353232303231) of index buffer is different from eaxpected VCN (0x3).
   FAILED
   Attempting to correct errors... 
   Processing $MFT and $MFTMirr...
   Reading $MFT... OK
   Reading $MFTMirr... OK
   Comparing $MFTMirr to $MFT... OK
   Processing of $MFT and $MFTMirr completed successfully.
   Setting required flags on partition... OK
   Going to empty the journal ($LogFile)... OK
   ntfs_mst_post_read_fixup_warn: magic: 0x6f2d6366  size: 4096   usa_ofs: 26740  usa_count: 29284: Invalid argument
   Actual VCN (0x322d353232303231) of index buffer is different from expected VCN (0x3).
   Remount failed: Input/output error

   Anybody??

   ---

3. Re: Error mounting system-managed device
   

   Hello again,

   I continued to search and found this post http://ubuntuforums.org/showthread.php?t=2171003, created a Windows Recovery Disc from a laptop with Win 8 and UEFI (don’t have another with BIOS). Unfortunately i got a «Non System Disk» error. Maybe a conflict between UEFI and BIOS?

   After that i downloaded Minitool Partition Wizard boot CD which looks very good and powerful tool, with all the pros and cons that come with that, regarding these kind of programs . For some reason that i don’t know the Check Disks option was not available to me. So i tried the Partition Recover Wizard but it didn’t fix my problem. Nonetheless it probably changed something, for the better or for the worse, because now i get a slightly different error message when i try to mount the partition in Ubuntu.

   Screenshot from 2014-03-25 18:41:37.png

   One good thing is that my files are still on the disc. I browsed the with Minitool Partition Wizard boot CD. Now i am thinking to try the Allign Partition from Minitool Partition Wizard boot CD but i don’t understand exactly what it does and i don’t want to destroy my data.

   Please help!!!!

   ---

4. Re: Error mounting system-managed device
   

   Hello again,

   I am wondering if anybody reads what i am writing, but i found a solution to my problem and i will post it, hoping to be helpful for someone else in the future.

   I used the command «dd» which performs a low level back up and more specific

   «dd if=/dev/sda2 of=/dev/sdc» which backed up everything from my damaged partition to a USB external drive. WARNING «dd if=/dev/sda2 of=/dev/sdb» deletes all the data, which may exist on the destination drive. Then i plugged in the USB drive to a windows pc and executed «chkdsk /f» which fixed everything. Then i formatted my damaged partition and pasted my data.

   One another solution i think would work, would be to format my damaged partition and try to recover the data with testdisk or another data recovery software.

   ---

Thread: Error mounting system-managed device

Thread Tools

Display

Error mounting system-managed device

First of all let me state clearly that i am a noob in linux.

I have an Acer 6930ZG laptop which originally had two patritions in its disk, one with Vista and one for storage, «DATA», both ntfs. I installed ubuntu 13.04 in the vista partition, kept using the other for storage and everything worked fine until i tried to install the latest nvidia driver from their site. Probably my bad(?) because there has been a kernel update recently. Then i installed 13.04 again on the same partition but now the second partition cant be mounted and i get this error message
Screenshot from 2014-03-13 14:11:00.png

I did some research and found this http://ubuntuforums.org/showthread.php?t=1688937 but i think it is way more complicated than what i want since it involves dual OS, different bootloaders etc and i didnt get what the solution was. I just want to mount the partition and use it as storage without losing my files.

sudo blkid outputs this

sudo fdisk -lu outputs this

sudo parted -l outputs this

fstab looks like this

# /etc/fstab: static file system information.
#
# Use ‘blkid’ to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#

# / was on /dev/sda1 during installation
UUID=197340b2-f58d-4bb5-b1c4-26eafbe20bea / ext4 errors=remount-ro 0 1
# /media/DATA was on /dev/sda2 during installation
UUID=FC54D24254D1FF78 /media/DATA ntfs defaults,umask=007,gid=46 0 0
# swap was on /dev/sda3 during installation
UUID=1c614f81-d62f-4a9a-a0f4-0fd50f29354d none swap sw 0 0

I suppose that the answer is somethere in the above but i cant see it.

Last edited by billy_kailas; March 13th, 2014 at 10:53 PM .

Re: Error mounting system-managed device

I ran sudo ntfsfix /dev/sda2 and this is the output

Re: Error mounting system-managed device

I continued to search and found this post http://ubuntuforums.org/showthread.php?t=2171003, created a Windows Recovery Disc from a laptop with Win 8 and UEFI (don’t have another with BIOS). Unfortunately i got a «Non System Disk» error. Maybe a conflict between UEFI and BIOS?

After that i downloaded Minitool Partition Wizard boot CD which looks very good and powerful tool, with all the pros and cons that come with that, regarding these kind of programs . For some reason that i don’t know the Check Disks option was not available to me. So i tried the Partition Recover Wizard but it didn’t fix my problem. Nonetheless it probably changed something, for the better or for the worse, because now i get a slightly different error message when i try to mount the partition in Ubuntu.

One good thing is that my files are still on the disc. I browsed the with Minitool Partition Wizard boot CD. Now i am thinking to try the Allign Partition from Minitool Partition Wizard boot CD but i don’t understand exactly what it does and i don’t want to destroy my data.

Re: Error mounting system-managed device

I am wondering if anybody reads what i am writing, but i found a solution to my problem and i will post it, hoping to be helpful for someone else in the future.

I used the command «dd» which performs a low level back up and more specific «dd if=/dev/sda2 of=/dev/sdc» which backed up everything from my damaged partition to a USB external drive. WARNING «dd if=/dev/sda2 of=/dev/sdb» deletes all the data, which may exist on the destination drive. Then i plugged in the USB drive to a windows pc and executed «chkdsk /f» which fixed everything. Then i formatted my damaged partition and pasted my data.

One another solution i think would work, would be to format my damaged partition and try to recover the data with testdisk or another data recovery software.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

Error mounting system-managed device

Error mounting system-managed device

Post by Cyan » Tue Jun 16, 2015 5:39 pm

I’m having this problem with my ext4 partition in which I put my Steam library. I do NOT have this problem at all with Ubuntu 15.04(which is on another partition on the same hard drive as my Mint 17.1 partition.)

When I click on my Linux Steam partition in the file manager, I get this text in a pop-up window:

Re: Error mounting system-managed device

Post by altair4 » Tue Jun 16, 2015 6:04 pm

Get rid of the option.

It’s only purpose is to provide an icon on the desktop and in your file manager for the partition. The same thing will happen if you were to mount it as /media/d282d014-3329-46b3-bbeb-285500b4c8f8 and it will do that naturally without x-gvfs-show.

Re: Error mounting system-managed device

Post by Cyan » Fri Jun 19, 2015 6:14 pm

Should I use a «#» on the entire line containing «gvfs-show» or do I merely delete that text from the line?

By Icon, what exactly do you mean? Will I still be able to select the partition within my file manager? My main goal is to set it to automount, so I don’t have to select it within Steam settings every time.

Re: Error mounting system-managed device

Post by altair4 » Fri Jun 19, 2015 7:08 pm

You will still be able to select it from the file manager it’s a question of how quickly you can go to it. But it’s easy to fix that.

To be honest I don’t think much of the Disks utility so I’d rewrite both lines manually but if you want to use it just unselect «show in user interface». That will remove the «x-gvfs-show» option from the line.

Then go to /mnt/d282d014-3329-46b3-bbeb-285500b4c8f8 and the other one and bookmark them. It will then show up on the left side panel in your file manager and every other application.

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Error mounting filesystem via either Disks or fstab

[SOLVED] Error mounting filesystem via either Disks or fstab

Post by jiawen » Fri Mar 22, 2013 1:43 am

Re: Error mounting filesystem via either Disks or fstab

Post by altair4 » Fri Mar 22, 2013 6:30 am

Step 1: Don’t use the Disks utility.

Step 2: Fix your /etc/fstab

Note: You might want to run the following command to make sure it really has that UUID number and that it is in fact formatted to ext3:

** If the partition is currently mounted unmount it.

** Then run the following command to test for syntax errors and if there are none mount the partition:

Re: Error mounting filesystem via either Disks or fstab

Post by jiawen » Mon Mar 25, 2013 7:30 pm

Re: Error mounting filesystem via either Disks or fstab

Post by johnywhy » Wed Jun 03, 2015 11:15 pm

Re: [SOLVED] Error mounting filesystem via either Disks or f

Post by CinnamonRoll » Wed Feb 03, 2016 4:16 pm

Re: [SOLVED] Error mounting filesystem via either Disks or f

Post by altair4 » Wed Feb 03, 2016 4:39 pm

x-gvfs-show will do something never intended. It will create a link on the side panel of your file manager and on the desktop if you allow that sort of thing for partitions that are not mounted under /media or $HOME.

Back in the olden days you mounted something under /mnt when you didn’t want it to show up on the side panel or on the desktop. Makes no sense to put it under /mnt then add x-gvfs-show. And if you wanted to change how it displayed you changed it’s LABEL.

It’s made worse in Disks because it asks you if you want it to:

The new user will look at that and say . well of course I do. That’s why I’m mounting it. What kind of a daft question is that? Selecting that option inserts x-gvfs-show.

I’m going to be uncharacteristically generous here and suggest that «Disks» isn’t buggy it’s that Mint isn’t ready for it yet. Disks was written and designed to fit within the whole systemd / brave-new-world udev/udisks universe. When Mint goes to version 18 all the backend pieces will be in place to have this goofy option work.

BTW, This thread is 3 years old. The OP may have gone to the dark side and is a happy MacBook user today.

Источник

Arch Linux

You are not logged in.

#1 2014-08-09 18:18:55

So I’ve been encountering this annoying issue with Arch so far that I haven’t been able to figure out. I have two extra internal hdds that do not mount at bootup. If I click on them in files, it prompts me to enter in my user password and then it will mount them in media as new volume and new volume1.

I edited my FSTAB to include the correct UUID and defaults under the options. However they do not mount at boot. I have to mount them manually which works fine, it’s just annoying as my dropbox folder is synced to my extra hdd, and it complains every time I login. Is there something I’m doing wrong? Thanks in advanced!

Last edited by 15goudreau (2014-08-10 17:46:00)

#2 2014-08-09 18:21:30

Post your /etc/fstab file contents and also the output of the «mount» command.

Edit: Also post the output of «lsblk -fs»

Last edited by headkase (2014-08-09 18:23:16)

#3 2014-08-09 18:45:03

for mounting I would use

Last edited by 15goudreau (2014-08-09 18:45:44)

#4 2014-08-09 18:48:23

You need to be using ntfs-3g as the filesystem type.

No, it didn’t «fix» anything. It just shifted the brokeness one space to the right. — jasonwryan
Closing — for deletion; Banning — for muppetry. — jasonwryan

#5 2014-08-09 19:03:12

For the mount command, just:

By itself. Post the output of that.

#6 2014-08-09 20:57:17

@slithery are you sure for I just tried removing ntfs-3g and an fstab entry with type ntfs worked on boot.
The two failing ntfs mounts are under /run/media. So do the two mount points exist at the time the mounts are attempted.
There should be two failed mount units from systemd’s attempt to mount the filesystems

Should list the units so you can get the names and then

#7 2014-08-09 21:06:20

sudo systemctl —failed

changing to ntfs-3g didn’t work.

Last edited by 15goudreau (2014-08-09 21:10:08)

#8 2014-08-09 21:18:37

If you change one of the missing ntfs mounts mountpoints to /mnt just as a test does that allow it to mount on boot?

#9 2014-08-09 22:27:59

@ loqs. That did work. So why can’t I mount it to /media like arch wants. hmmm

#10 2014-08-09 22:29:02

the other drive that I tried to mount within the fstab gives me an error when trying to access it now.

#11 2014-08-09 22:47:35

@ loqs. That did work. So why can’t I mount it to /media like arch wants. hmmm

From your mount listing

/run being tmpfs (which is normal ) means it starts as an empty directory then populated with some entries by tmpfiles.d the rest of its contents comes from programs executing later in boot
So at the point the fstab is parsed and mount attempted it seems /run/media/taylor/New Volume and /run/media/taylor/New Volume1 do not exist so the mount fails.
From udisks2 looks like udisks2 is creating the paths and doing the mounting
Hope that explains it a little better
Edit:
If the new error is still occurring:
What command produced the new error?
Can you post /etc/fstab as it is now

Last edited by loqs (2014-08-09 23:16:47)

#12 2014-08-10 01:26:46

The error was occurring whenever I tried to mount it in fstab like that. I forgot to mention it in the OP. So is there nothing that can be done? It seems like a huge hassle to have to enter in a password to access my harddrives and on top of that have to relink dropbox each startup.

fstab as it is now

#13 2014-08-10 01:28:46

You do know that «ntfs» is built-into the kernel and provides read-only access. «ntfs-3g» is a separate package you install and provides both read and write access.

#14 2014-08-10 01:47:29

I understand headkase, but it didn’t work with ntfs or ntfs-3g. I can worry about read/write access after I get the drives to mount properly. Although with what loqs said above I’m not sure if I can.

#15 2014-08-10 01:54:58

You are putting the mount directly onto the /mnt folder, which is wrong.

Create a folder (before mounting) in /mnt, like say «/mnt/name» where «name» is your choice. Then in the fstab entry instead of «/mnt» replace that with «/mnt/name» so it doesn’t take the entire folder but rather mounts on the sub-folder.

#16 2014-08-10 01:58:31

You are mounting within your run/media/taylor folder. When the fstab is parsed, early in boot, this folder may not exist yet — it may only exist when you log into your user later on in the boot process. Try making a folder in /mnt, as instructed above, for this mountpoint too and changing the mountpoint to that folder. Because /mnt will always exist where the /run/media/* is not always guaranteed to exist.

#17 2014-08-10 02:04:34

right, but if I mount the drive to /mnt/folder, (I understand that it needs a folder «name») that will at least allow it to be mounted in the same place, which I guess is good for dropbox but then instead of having access through the File manager Devices I have to sift through computer>mnt>file. I know it seems like it is splitting hairs, and maybe I am just being difficult, but I feel like this isn’t the easiest most streamline way to get my drives mounted so that they can be seen under Devices, and I do not have to enter in my password each time.

#18 2014-08-10 02:08:37

Mountpoints need an empty folder to mount onto. So, /mnt/folder1 where «folder1» is empty then in your fstab you would have /mnt/folder1 as the location and when mounted the contents of folder1 would change from empty to whatever the contents of the mount had.

You can also put the mountpoints inside of your home folder if you like, just mount them onto some empty folders there. It might not matter but make sure / is first in fstab, followed by /home, and then followed by the mountpoints you could put in your home folder.

Depending on how your desktop environment mounts folders you could also edit your sudoers file so that «sudo mount» and «sudo umount» do not need a password. Again, depending on your environment, that might work.

Edit: put this in your sudoers (using visudo!):

Replace «bill» (my username) with your own.

Last edited by headkase (2014-08-10 02:11:09)

#19 2014-08-10 02:11:31

Mount them in a location that will exist during the boot process (/mnt can work, but creating a /media might be better and more flexible). Then just configure your file manager to display those folders in the side pane like it does folders under /run/username/media.

«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman

Online

#20 2014-08-10 02:23:28

That should work. It’s unfortunate that this is the workaround but it’ll will suffice for my purposes. Thanks guys for the help.

#21 2014-08-10 02:27:16

You’re welcome but you should see your thread through to fully solved. And when it is solved, not before, edit your first post and put «[Solved]» on the beginning of the title without quotes.

Last edited by headkase (2014-08-10 02:27:39)

#22 2014-08-10 09:57:56

If its enough that the filesystems are available on user login this should see the filesystems mounted where you want them under /run/media and probably show in your filemanager as expected
Create a script file or append this to one thats already executed on login

edit /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy
in the block starting

change allow_active to yes (from a script it may need allow_any instead not tested this)

This will stop udisksctl from producing a popup prompting for your password but obviously relaxes security on udisksctl

Last edited by loqs (2014-08-10 10:26:28)

#23 2014-08-10 17:45:49

Alright, so what I did was I created the directories /media/volume1 and /media/volume2 I edited my fstab to mount the drives there with the ntfs-3g (thanks headkase!). The nautilis file manager found the drives after I edited its configuration file. So now I can access the drives without being prompted for a password and dropbox links up without having to relink on reboot. Thanks all for the different suggestions and helping me troubleshoot! — marked solved.

Источник

Страницы: [1] 2  Все   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1] 2  Все   Вверх

Return to “Troubleshooting”