New answers tagged

0

It turns out that adding x-gvfs-show to the mount options does the job.


0

What you're seeing is normal. The file data is kept in RAM just in case it's needed again. If more free RAM is needed, the cache will just be discarded.


0

Well I discovered webmin(http://www.webmin.com/), and the SAMBA(https://www.samba.org/) option to do exactly what I required, also a good video on this is https://www.youtube.com/watch?v=RDwoDj2cW6c With a fresh install of ubuntu 16.04 during the install (via disk image) you have the option to add SAMBA in the software section, which was a bonus. Now i ...


0

After investigating, it seems I have been affected by a bug as described here: http://serverfault.com/questions/491464/directories-shown-as-files-when-sharing-a-mounted-cifs-drive It seems there is a bug when "resharing" with samba: Directories are shown as files because of a bug. Samba uses the inode count to determine this and cifs sets this to zero. So ...


0

First thing always check if user has access to share and not only permissions to folder also use domain option and use -v to check debug messages.


0

You can organize your btrfs volumes in a different way to avoid this automatic mount (by not mounting btrfs / onto your system / but a btrfs subvolume like /rootfs onto your system / instead. Only btrfs subvolumes named /rootfs/foo/bar will be auto-mounted as /foo/bar in this case). But this is not a very easy task and you can have difficulties to reboot ...


1

thanks to @andlrc, this has solved the problem using the fstab: hope someone get used of it fstab or file system table is used by the system to get information about partitions to automatically mount when run used: sudo gedit /etc/fstab to open it added the following to make the system automatically mount the /proc /path/to/chroot/proc /proc auto -o,bind ...


0

Solved, Use GParted then select the partition that you can't mount then right click and choose "Check" and It will find the problem and solve it automatically.


0

It's likely that the HFS volume is not mounting because the HFS partition is wrapped in a CoreStorage volume (the default since OS X 10.10). You can verify if this is the case with the output of fdisk -l: HFS+ uses two volume headers, one 1024 into the device and the secondary 1024 from the end of the device. Per the spec, when mounting a partition the ...


0

An important step is to have mdadm scan for the disk prior to attempting to mount anything: mdadm --detail --scan I can't recall from memory but the --assemble flag may be necessary but try the above first then try mounting via: mount /dev/md# /path/to/mount


0

I had the same problem, but with vmware workstation 12 and ubuntu server. It WASN'T solved by typing sudo mount /dev/sr0 /mnt/cdrom because for whatever reason the iso was on a different drive. The solution- after clicking on install/upgrade VMware Tools type blkid -c /dev/null The above command shows all mounted and unmounted drives. I saw /dev/sr1: ...


0

Well this is 3 years old question but in case anybody came here, You can now use this portable utility: WinCEEmu portable I have used it on Win 7 x64 and it's OK. It also works on Win Server 2K3.


0

You can't have the same performance with httpfs2, because of HTTP overhead. For 10 MB of file you have ~100 requests, each of one asking for ~100 KB of data (source: wireshark) and latency will kill performance. You could probably tune FUSE in order to get bigger chunks, but it will probably consume more memory. Another option would be start asking the next ...


1

Medium errors mean that your computer fails to read your disk. It usually happens when the drive is underpowered or damaged. Try to connect it with a different USB cable (and preferably to a different USB port) to address the first problem. If it doesn't help, you may want to go to the website of your HDD manufacturer and download whatever rescue tools and ...


1

From you post it seems like you are trying to set file system for the disk with creating partition. Please follow the steps below and check. Check wheather the disk is listing using fdisk -l once confirmed disk list then select the disk and create partion selecting --> fdisk /dev/sdc checking wheather partion created previously using print "P"...


0

Apparantly the fault lies within the vagrant file. I used the following: config.vm.synced_folder "./", "/vagrant", type: "nfs", :mount_options => ['nolock,vers=3,udp,noatime,actimeo=1'] Which apparantly does not work with windows 10, so I updated it to: config.vm.synced_folder "./", "/vagrant", type: "nfs", :mount_options => ['dmode=777','fmode=777'...


0

Why did you use exfat? The manual does not recognize any such filesystem type; instead, it states: -t, --types vfstype The argument following the -t is used to indicate the filesystem type. The filesystem types which are currently supported include: adfs, affs, autofs, cifs, coda, coherent, cramfs, debugfs, devpts, efs, ext, ext2, ext3, ext4, hfs, ...


0

(Overmind posted his answer while I was composing my longer one.) I'm sure there are fancy ways to cope with mountpoints, but maybe a simple symlink in your homedir (or wherever) will be enough for you: ln -s /media/username/02c18b8b-ae30-46d5-a351-b5525857XYZ ~/mynewdrive Notes: Final part of the original path is the partition UUID; it won't change ...


0

Make a symlink: ln -s /media/username/02c18b8b-ae30-46d5-a351-b5525857XYZ MediaNewDrive


0

I had a patriot UFD. I used an RMB-flip application for the controller of that UFD to convert it to a non-removable drive. Then mounted it to a Hyper-V VM as a passthru disk and booted from it.


0

You can download the exe and install it. You can configure this tool to auto-mount the partition. Check this out: http://www.techgainer.com/how-to-mount-and-access-linux-partitions-ext4ext3ext2-in-windows-explorer-easily/ Edited: This is how you can accomplish this: 1) Open disk management --> Action --> More Action and Attach VHD 2) Once you ...


0

You'll need a third party ext3 driver to be able to open an ext3 filesystem as Windows cannot natively read it. An example: http://www.ext2fsd.com/


0

Seems Disk3 was actually Disk1b -> a part of the first ISO adding them as disk1, disk3 then disk2 worked.


1

First, try -o vers=1. The kernel's SMB2 client has only very recently gained Kerberos support – in Ubuntu 14.04, only the 4.4.x kernel will have it. Second, check if the request-key and cifs.upcall binaries are installed and that the latter is mentioned in /etc/request-key.conf (or /etc/request-key.d/): create cifs.spnego * * /usr/bin/cifs.upcall %k ...


0

/dev/sdX nodes are not supposed to be numbered always the same. They are added as and when the system "sees" them appear. If two devices take about the same time to start up, there may be a kind of race condition in the attribution of device nodes. Your method is the good one. One may as well use label, id, or hardware path, see ls /dev/disk/by-*



Top 50 recent answers are included