Debian Configuration :: Cant Mount Flashdrive ?
Jul 18, 2011Tried all usb ports and wont take, tried 2 types of flashdrives.
View 4 RepliesTried all usb ports and wont take, tried 2 types of flashdrives.
View 4 RepliesI am working on a production system on which it is not advisable to enable on-access scan with use of Dazuko. However, I want to do an automatic scan with clamscan when the flashdrive is mounted. As far as I know, Kudzu is arranging the automount of the flashdrives.
View 5 Replies View RelatedI can't get Redhat (Fedora) to mount my usb Flashdrive. My windows O/S has no problem with my usb flashdrive. I can mount my CD Drive and my Floppy drive. My mouse is pluged into one of my usb slots and it works. What am I doing wrong.
View 1 Replies View RelatedI am looking at installing Debian on a USB flash drive (not in a read only manner, but with configuration changes saved). I have read the eeepc usb stick installation guide, and just have a few remaining questions. Is there anyway to force the usb stick to stay in the same address (as it will be in a system with two sata drives, in hot swap caddies). Apart from having /tmp and /proc on ramdisks, is there anything else that is recomended to avoid excessive wear on the memory stick.
View 4 Replies View RelatedI've just made the switch from Ubuntu to Debian Squeeze and am having trouble connecting external media (be it a USB stick or an ext HD). The error I am getting when I connect anything via usb is the following:
Error mounting: mount exited with exit code 1: helper failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdc1, missing codepage or helper program, or other error.
I just installed debian and I love it so far. I'm trying to mount an ssd that I took from my previous window installation but it gives me this error:
Error mounting /dev/sdb1 at /media/meknoy/Fotoschijf: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdb1" "/media/meknoy/Fotoschijf"' 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/sdb1': Bewerking niet toegestaan
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.
How can I sort this out? The data on the disk is important and I can not lose it.
Then my SD card with photos on it has about the same problem.
It gives me this message:
Error mounting /dev/sde1 at /media/meknoy/NIKON D7100: Command-line `mount -t "exfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,namecase=0,errors=remount-ro,umask=0077" "/dev/sde1" "/media/meknoy/NIKON D7100"' exited with non-zero exit status 32: mount: unknown filesystem type 'exfat'
When I plug in a usb flash drive, my Debian mount it, but when i am going to write, mkdir, rename file or paste a file permission denied.
The result of Code: Select alldev/sdc1 /media/usb0 auto rw,user,noauto 0 0
is Access denied
I'm running sid, and doing weekly updates. Recently I've been unable to mount nfs shares on one of my home computers. I haven't changed any settings, and nfs works fine on the other computers on my small home network. I suspect an update messed something up with nfs.
View 9 Replies View RelatedSo after having spent the past half year preparing to abandon Windows and come over to Debian I finally made the switch last night only to realize I forgot one important thing... I didn't figure out how to map the network drive on my Windows server (currently learning to replace this with Debian as well) to my Debian system.
I have read about 15 links but keep getting the following error: Mount Error (6): No such device or address
Here is what I'm trying to enter into my terminal (with important bits removed for security of course)
mount -t cifs //xxx.xxx.xxx.xxx/Network_Storage/ -o username=xxx,password=xxx /mnt/cifs
I have Debian 7 running on RPi2 with Kodi. My NFS server is running on Slackware 14.1 which doesn't have full support for nfs4. I think this is causing some slowdowns/extra time when trying to stream video. Debian 7 by default mounts NFS as nfsv4, I would to like to disable this if possible. If so how?
View 1 Replies View RelatedA few days ago I upgraded from debian 7 to 8. First I update, upgrade and dist upgrade - change source list and again update, upgrade and dist upgrade.When inserting a USB disk on key, it works okay. When plugging my WD "My passport" backup USB disk it does not work. The automatic mount works, but the disk can be accessed.I tried to do it manually in a format that worked on debian 7..Manual mount fails too.
umount My passport
fdisk -l (to see device name)
mount -t vfat -o rw /dev/sdb1 /media/kuku/usb_mp4
dmesg | tail
[ 2381.080822] sd 9:0:0:0: [sdb] No Caching mode page found
[ 2381.080828] sd 9:0:0:0: [sdb] Assuming drive cache: write through
[code]....
I made a mistake in Gnome Disk utility tool. Instead of changing the options for a USB key, I changed the options of the root partition.
In Initial state, automatic options were desactivated. I just activated them. And after desactivacting them, I realized my mistake and switched back to "non automatic options".
By doing this, I suppose that defaults values were used since now, the system starts in command line mode and no more in graphic interface mode.
When I try the "startx" command, I get a "read-only" error.
With the command "sudo mount -o rw,remount /" the graphic interface is started.
Below is the configuration of the partition under the gnome disk utility tool :
"Mount at startup" is checked
"Show in user inteface" and "Require additional authorization to mount" are unchecked
Mount options : nosuid,nodev,nofail,x-gvfs-show
Mount point : /mnt/eb11d4d6-75db-XXXx-XXXx
Identify as : /dev/disk/by-uuid/eb11d4d6-75db-XXXx-XXXx
Filesystem type : auto
I do not want to change anything that could leat to a critical error. So what do you think I should do ?
Basically, I have no trouble booting off a really old kernel like 2.6.18-6. If I try to boot off the newest one installed with Lenny, I get errors such as "mounting /dev/ on /root/dev failed...ditto for /sys on /root/sys" almost as if it's failing to find the drive. This finishes up with "target filesystem doesn't have /sbin/init" and I'm dropped into a busybox shell.It's an ordinary SATA drive, which is being used as an OS drive only. It seems as if something has changed with the newer kernel, but I have no idea where to start or what to look for.
View 3 Replies View RelatedA windows server named SRV is sharing folders for each users in /share/From a Debian computer on network logged with the user session "foo" I can mount the remote directory /share/foo with:smbmount //SRV/share/$LOGNAME /remote_directorythen the prompt ask me for password and when I have gave it the remote directory is mounted correctly.Now I would like to make this at boot time.If I put the same command in the .bashrc, when I boot, the remote directory is not mounted when the session is opened but then if I open a console, it ask me for password and the directory is mounted.This way is not convenient and it would be better if the directory is mounted when the user open his session and using the same password.The point is that every user should have a his own remote directory mounted when the session is opened.
View 2 Replies View RelatedI'll start a fresh installation of a debian stable server and I would like to use LVM on this. So, I started to read lots of documents about LVM and found different flavors on partitioning with it. I'm thinking in a partition schema which might use LVM for those mount points that tends to grow in time, for instance:
/boot (primary partition)
/ (primary partition)
/home (lvm)
/usr (lvm)
/var (lvm)
swap (lvm)
Am I right on this schema?
I have Debian Testing. I am testing XFCE and LXDE and i want to use display manager other than GDM. I have tried SLIM and XDM but when i use them i can't mount partitions and USB through Thunar, PcMan or Nautilus - i get message that i am not authorized (if i do groups in terminal - adm dialout fax cdrom floppy tape audio dip video plugdev games fuse powerdev netdev lpadmin scanner sambashare). When i install GDM everything works fine. I have installed FUSE, HAL, Udev,...I have tried a lot of stuff from AcchLinux forums but nothing worked really.
View 4 Replies View RelatedWorking on Debian 7.2.0.
In a specific context I want to automatically make operationnal some USB WiFI devices, deploying automaticaly firwmare (may be not free packages) depending on device ID (vendor ID/product ID). Dev device is a Netgear WNA1000 (driver ath9k, with htc_9271.fw firmware).
I tried to reset the USB bus (modprobe -vr ehci_hcd; modprobe -v ehci_hcd) but it's not really reliable, with sometimes kernel panic.
Is there an "official" way to "mount" the device (the system create the device wlan0) just after deploying the firmware? Maybe using udev ?
I'm using Debian 8.2 from a very recent download of the latest NetInst (less than 2 weeks). I'm sort of new to Linux - More accurately, I've used Unix and Linux extensively in the past, so most of my knowledge is dated. In particular, the whole systemd / systemctl paradigm is completely new to me.
Problem: I've added an entry to /etc/fstab to mount a NAS drive as CIFS. When I do a system shutdown or reboot, the system hangs for 90 seconds trying to unmount the NAS. If I manually umount the NAS prior to shutdown / reboot everything works fine.
I've done a fair amount of investigation and web searches, but haven't found a fix yet. Apparently several people were encountering similar problems about a year back, and it seems pretty clear that the root cause what ordering of steps in the shutdown process, e.g., WLAN being turned off before unmounting filesystems. This seems to have been resolved for most users (no one is discussing it any more), but I'm now running into the same issue. Ugh.
I tried to add a shell script to /etc/rc0.d to umount the NAS first in the shutdown process. This had no effect. I assume this is because the new systemd / systemctl paradigm supplants the old /etc/rc model of runlevel control, though it is rather baffling (to me, at least) as to why /etc/rc* still exists if the system is no longer using it...?
Here's some things I'd like to try, but how to proceed:
1. In the new systemd / systemctl paradigm, how do I examine and change the ordering of steps in the shutdown process? I've seen a lot of documentation on systemd, but nothing tells me how to do what I used to be able to do with /etc/rc with a simple rename of a symlink. If I knew how to look at the order of shutdown and change that ordering, I'm fairly certain I could identify and resolve this issue.
2. Is there some other way to mount my CIFS NAS other than editing /etc/fstab? Is it possible that my manual edit to /etc/fstab is the cause of this issue? My research into systemd indicates that it IS supposed to be compatible with /etc/fstab. I have not yet found documentation describing how to mount a filesystem at boot WITHOUT editing /etc/fstab ...
is there a way to allow a program mounting a drive without requiring it to ask for sudo password (apart from running it with sudo)? To be more specific, I'm annoyed by the sudo password request by TrueCrypt whenever it needs to mount a volume.
I've thought about creating another user, allowing it to mount volumes and then running TrueCrypt as this user at boot. I don't know whether GNU/Linux allows for such policies... maybe I should look into SELinux?
EDIT: For the issue at hand (encrypted USB stick both on Windows and Linux), I'm investigating FreeOTFE. I'm still curious about the privileges issue, anyway.
I have successfully mounted my Win7 volume and my external hard drives NTFS volume as well. However, after modifying the fstab I seem to only be getting the win7 volume to auto-mount. Below is the contents of my fstab. /dev/sdf3 is not mounting. Again, it works no problem if I manually mount it.
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
[code]....
I`m unable to mount my second hard drive I use to store my music and pics and wonder if it is to do with the error "failed to initialise HAL!" which I get every time I start Debian Lenny (AMD64 architecture). I have had this since doing an install (fresh) a few hours ago.
The drive is an ntfs one but when I click its icon in the computer section it says it cannot mount it and gparted says it cannot read the file system.If so how would I get the error box to stop appearing and how do I mount the ntfs drive?
I am trying to create an encrypted file and later mount it as a filesystem.
KEY=`tr -cd [:graph:] < /dev/urandom | head -c 79`
echo $KEY | openssl aes-256-cbc > container.key
dd if=/dev/urandom of=~/container.img bs=1G count=10
losetup /dev/loop0 ~/container.img
[code]....
The luksOpen command asks me for my passphrase, but always rejects it. I have retried this several times and written down the passphrase - and even tried with a very simple one just to check. And I never can make it work.
Running Debian stable. I added the following command to rc.local and made it executable:mount -t cifs -o username=ted,password=computer,uid=mooreted,gid=users "//192.168.1.121/Storage Volume" /mnt/vortexAfter rebooting dmesg throws the following error:
[ 21.400697] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 21.400708] CIFS VFS: cifs_mount failed w/return code = -101
However, if I run the command as root after the system boots it works fine.Been using this method on other distros for over a year. No idea what the problem is.
I,ve upgraded Debian Testing to Gnome 3.18, acrivate from Online Accounts file integration of Google service.
In Nautilus left panel i see my Google Drive accounts but is impossible to mount , i have a generic error (impossible to mount position).
How i can fix this?
Same problem on Arch (Laptop).
I eventually gave up and migrated to mdadm. Works just fine. Having upgraded to jessie and solved one problem
[URL] ....
I find the next one. When I boot into jessie my RAID device (just a data partition not /) is not found causing the boot to fail as per problems reported here
[URL] ....
After booting I can mount my RAID device but if it's in the fstab when booting it fails. Also, I notice that some of my lvm device names have changed. After a bit of hunting around I found a couple of solutions pointing to running dmraid as a service during boot and changing the entry for the RAID device in fstab to use the UUID.
[URL] .....
This seems to work. However this seems to be a workaround and as the lvm device paths for my / and /usr partitions have also changed, I'm wondering if there is a bug here as mentioned in the second link?
The / and /usr paths changed to /dev/dm-2 and /dev/dm-3 from the /dev/mapper/ form.
I'm trying to mount a remove filesystem onto my own server. I am able to do this, however I can only access it as root, or if I chmod 777 the lot. Obviously I want to be as secure as possible, so I'd like to avoid either one of those options. Another option is to mount it directly into my home directory, but previously when I was trying out Ubuntu this caused Samba problems - and I was advised mounting in my home dir was a workaround rather than a proper fix.
I have root access with sudo on my own server. I've not set a root pasword, and until I need to I'll avoid it. I have a user account with full control over my own home directory on the remote server. I am mounting using fstab - sshfs#username@remoteserver:/media/sdk/home/username/ /media//remote/ fuse user,idmap=user 0 0
What I would like to do is without changing the permissions on the remote server change the permissions when they are mounted on my own server. I would like them to be in the group sambausers for example. Instead they are owned by root and in the group of 1024 (which I have not set). Additionally for this to work they would have to have 770 on my home server and 700 on the remote server....
I run a mediaserver on Archlinux, working perfectly (or almost). I have set up NFS v3 and that worked for me on these clients:
- Debian Lenny
- Archlinux 64bit
Now I've upgraded my Lenny-box to squeeze and I see that 2 of my 3 shared folders (tdone and twatch) are mounted like they should and the third one (media) doesn't come up. A 'mount -a' as root gives this error: mount.nfs4: access denied by server while mounting (null) My relevant fstab-lines:
[Code]....
how I can go about debugging this?
I am running Debian Testing (Squeeze). I have just one problem... It always shows "mount: / is busy" message while shutting down and/or rebooting, though it halts soon thereafter. Is this error message fatal, will it cause any problem in future? If so, is there any quick fix?Here are few details of my system settings:
fstab:
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
[code]...
How do I configure my Debian installation to mount external USB drives to mount points based on the volume names of the drives? For instance, if I have a thumb drive with the volume name of "SWORDFISH," how do I have Linux mount it at /media/SWORDFISH? I'm aware that this can be setup in FSTAB, but that requires that I know the UUID of the device beforehand and that I take the time to set each external device up in FSTAB first. That does nothing for me when I have a thumb drive that has never been plugged into my computer before.
This seems to be setup by default in Ubuntu/Kubuntu, but is not working for me with a fresh installation of Debian Squeeze and KDE4. I've spent the past 2 hours Googling for a solution and have turned up nothing. UPDATE: My results are inconsistent. Sometimes Debian mounts devices to mount points based on the volume names, and other times it gives them generic mount points (e.g. /media/usb1).
I am struggling with getting an sshfs mount mounted on system boot. I have a script that mounts the sshfs for "userA". When userA runs the script all is well - user A can access the remote filesystem, root user can't see it as expected. The basic command is: sshfs userA@remote host:/home/userA /home/userA/mountdir -p 21212 -o password_stdin < passwordfile. I can prepend the sshfs command in the script with su - userA -c and when I run this script logged in as root all is well, userA has access and all is well. If I then put this script in /etc/init.d and reference it properly in the rc. directories the mount doesn't happen. If I prepend the sshfs command with sudo, same thing. Logged in as root I can run the script and UserA has access. Run the script in /etc/init.d during startup and the mount doesn't happen. Echoing text to a log file shows that the script is being executed but no mount happens.
View 4 Replies View Related