Problems mounting fat drives

Whenever I try and mount either my floppy drive or my memory stick in my clie I am told that there is either a bad block or wrong file type.
I have fat (vfat) compiled into the kernel, but it still doesn't work. I'm confident there isn't a problem with the drives.
Can anyobne suggest anything? This is quite frustrating...

Check dmesg to see if the stick is recognized as /dev/sda. If it is, run fdisk /dev/sda to see what partitions are on it.
If there are several partitions, mount the stick with
mount -t vfat /dev/sda /mnt/usbstick
I used to mount my stick with /dev/sda (even though it held 4 different partitions! Found that out afterwards), but today I had to repartition and format the thing, so I made one big (256MB) FAT16 partition which I now have to mount with /dev/sda1.

Similar Messages

Problem mounting network drive after upgrading router firmware

Hi guys,
It's been a while since I last posted a question of my own here, but I'm at my wits end. As I may have mentioned, I live in France, and my ISP is Free (no, not free, Free...). I've got what they call a "box" here, i.e. a sort of super-modem that will let you connect to the Internet via xDSL (and soon VDSL2), receive hundreds of TV channels, read BluRay discs, store files (videos, music, photos, what have you) on a integrated NAS, place and receive phone calls, whether via a landline (DECT) or, since recently, through a femtocell.
All in all, the package is impressive and works flawlessly. But...
(Of course, there had to be a "but)
... Yesterday, I let my "box" (it's called a Freebox Revolution, or Freebox V6--for Version 6--by the way) upgrade its firmware, reboot as it always does in such circumstances, and since that, the NAS won't mount in the Finder the way it used to under the Shared left pane.
Now, every time I reboot my Mac, I have to open a browser windows and type "smb://mafreebox.freebox.fr" in order mount the NAS in the Finder. I've saved the credentials (login, no password) in the keychain, hoping it would help, but it doesn't. I've got a PC running Windows 8.1 Preview at the moment, and created a shortcut to the NAS on the Desktop. Guess what? I double-click on the shortcut, and sure enough, I can access the content of the NAS from Windows, but not from the Mac.
I must add that I haven't changed anything on the Mac since, or before, upgrading the "box" firmware.
Any ideas?

OK, you must think I'm going bananas, but my issue is gone... For now...
Seriously, what do you guys think about this problem with network drives mounting or not, depending on, I don't know, the weather, maybe?

Problems mounting USB drives

I am having some problems getting USB flash drives to (auto) mount on my system.
In the past, when I plugged in the device (a simple USB flash drive), it showed up in Thunar and I could click on it to mount it. Now nothing shows up in thunar when I plug in the device. dmesg shows the following, so I know the device is being recognized:
usb 2-2: new high speed USB device using ehci_hcd and address 14
but it isn't being assigned to /dev/sd*. fdisk -l also doesn't show the device. lsusb shows the following for the device:
Bus 002 Device 014: ID 0781:b6b7 SanDisk Corp.
I added a udev rule to automount in /media, as per the udev wiki instructions, but that didn't do anything. Installing udisks and udiskie was similarly unhelpful. I tried this with multiple USB drives (which I both confirmed were working on other machines) so it doesn't seem to be a HW problem.
Thanks in advance.

You might try reformatting the usb drive using Disk Utility. Use MacOS Extended(Journaled). That might help.
lenn

Problem mounting ntfs drives

[svs@mugen media]$ ls -l
total 104
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 cd
drwxr-xr-x 2 root root 4096 2008-06-17 19:44 d1
drwxr-xr-x 7 svs root 8192 1969-12-31 16:00 disk
drwxrwxrwx 1 root root 32768 2008-06-19 18:56 disk-1
drwxrwxrwx 1 root root 40960 2008-06-24 11:01 disk-2
drwxrwxrwx 1 root root 8192 2008-06-24 10:51 disk-3
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 dvd
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 fl
I have few doubts ..
1.Why disk-1,2,3 have root as their owner(they r NTFS , disk is FAT) & disk doesnt
2.
[svs@mugen media]$ sudo chown -c svs disk-1
Password:
changed ownership of `disk-1' to svs
[svs@mugen media]$ ls -l
total 104
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 cd
drwxr-xr-x 2 root root 4096 2008-06-17 19:44 d1
drwxr-xr-x 7 svs root 8192 1969-12-31 16:00 disk
drwxrwxrwx 1 root root 32768 2008-06-19 18:56 disk-1
drwxrwxrwx 1 root root 40960 2008-06-24 11:01 disk-2
drwxrwxrwx 1 root root 8192 2008-06-24 10:51 disk-3
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 dvd
drwxr-xr-x 2 root root 4096 2008-03-10 15:20 fl
this means chown is not working ....
3.wen i hiberbate windows i cant access my ntfs drives , y?
p.s disk-1,2,3 are coloured "green" instead of "blue" in terminal as if sticky bit is set

/media is a dynamic directory, unlike /mnt, that's probably why chown doesn't work.
Changing contents of a drive mounted in some OS while it is hibernated can be dangerous. That's why Windows drives are unmounted when you hibernate Linux and that's probably why you can't access your ntfs drives if Windows is hibernated.

Problems mounting ntfs drives

hidar, all. new arch user says hi.
i'm attempting to mount an ntfs drive at /dev/sda1 to /media/Data
i'm using ntfs-3g, and wrote an entry in fstab for the drive
however, i can't launch fuse to run ntfs-3g
when i run modprobe fuse i get the error
could not load /lib/modules/2.6.33-ARCH/modules.dep: no such file.
now the problem here is that i'm running 2.6.34, so
/lib/modules/2.6.34-ARCH/modules.dep should be the place modprobe is looking for the file, but it isn't.
how can i fix this?

oh, man, gg. i'm a noob.
solution here. it involves restarting.
http://bbs.archlinux.org/viewtopic.php?id=3314

Puzzling problem mounting some partitions from drive connected via airport

I have an external drive with three partitions connected to my airport. Under Tiger, the mounting process for all those partitions was seamless and never failed. As soon as I upgraded to Leopard, however, everything fell apart. Now I can't mount two of the three partitions at all.
When the external drive is connected directly to my MacBook Pro, each partition mounts routinely. When I connect it via my Airport Extreme, the finder window shows that I am connected; but when I attempt to access the partitions on the drive, I get this error message: 'The operation cannot be completed because the original item cannot be found.' I get the same error message for each of the first two partitions on the drive and can mount only the last partition.
When I attempt to mount the partitions manually via the Go menu in the finder, I get essentially the same result: error messages for the first two partitions saying that they cannot be mounted and a normal mounting of the third partition.
Any ideas or clues as to what is actually happening here would be most appreciated. It's very frustrating to have lost access to my backup drive purely by upgrading to Leopard and not find any obvious way to regain it.

Thanks, but I have no problem accessing the drive. All I have to do is plug it directly into my laptop using either USD or Firewire. The problem is with accessing it via Airport so I can run my normal backup routine as I did under Tiger without first a lot of fiddling with cables. After all, the result of installing Leopard shouldn't have been to decrease functionality, should it?
With a direct connection, everything functions normally. With an Airport connection, nothing functions. None of the partitions show up on the desk top, none show up when I run disk utility, and -- as explained before -- I cannot even mount two of the three partitions manually. I've also noticed now that, when I do mount the one partition that will mount, it freezes the finder when I try to unmount it. After that I have to relaunch the finder in order to regain functionality.
It seems pretty obvious that the whole mess is a function of Leopard and Airport somehow, but I'm just at a loss to narrow the problem down any further.

Mounting IFS-Drive...Problem

We have successfully installed Ifs 1.1 on a sun solaris machine.
We tried to mount the Ifs Drive in Windows NT, with no success. The Samba server is running on the IFS machine, as we have seen.
Until now we had no problems to mount the ifs drive. The difference was that IFS was installed on a NT machine.
What do we have to look for when we want to mount the IFS drive on (Ifs is on solaris)
with Windows NT?
Second question:
Is it possible to mount the drive via Internet?

But if we shut down the samba server, we aren4t able to access the IFS-Drive via Windows NT, or? What we mean is the Samba-Server of IFS.<<
Ok sorry, I thought you where using samba and iFS on the same machine (BTW: iFS has nothing to do with samba. It has it's own implementation of the smb protocol). What is your exact problem ? I just installed iFS on a Solaris 7 machine and hat almost no problems integrating it into my windows environment. The only problem I had was that the iFS server isn't visible in my Network Neighborhood. But I was able to search (and find) the computer with the 'search computer dialog'.
Regards
Roger
null

Fast User Switching with Mounted Network Drive?

I have a headless G4 Cube running 10.5.8 with a 2TB firewire drive plugged in for storage accessable to any of my macs here at home. I can access it fine with my 2 desktops over ethernet and wirelessly. Recently we decided to consolidate our 2 desktops into one using the muliple users feature. Seems to work fine, and both accounts can access the shared drive. They are logging in with the cube's admin credentials, and the shared drive is set to ignore permissions. I have the drive set to mount on login with a startup item in the system login items prefs. As long as I logout before switching users, everything is good.
The problem arises with Fast User Switching which we'd love to be able to use. I can't figure out how to connect to the drive in one account without the 2nd account then seeing it as a volume without proper permissions, then that account creates a new volume mount for it (which doesn't work with iTunes properly and seems to cause other wierd issues).
Example: So say 'user1' logs in, mounts the drive 'Jukebox'. everything seems OK so far. 'Jukebox' is on the desktop and iTunes finds the music. Now I fast user switch to 'user2' and there is a 'Jukebox' on the desktop with the red minus icon indicating I don't have permissions to access it. If I then browse the network and mount the drive, I end up with ANOTHER 'Jukebox' on the desktop. BUT iTunes doesn't see it properly. If I look in the /Volumes/ folder with the Terminal, I see a mountpoint for 'Jukebox' (with the owner of 'user1' group 'staff') and now a new mountpoint called 'Jukebox-1' (with the owner of 'user2' group 'staff').
It seems when you mount a AFP drive, it creates the Volume with the current user and staff group, but switching to another user then can't access that when it sees it in the /Volumes folder. You try to mount again and it creates a NEW mountpoint, names it with a '-1' at the end and you can use that (but iTunes cant).
So... how does one use a shared drive that you want on BOTH users desktops with Fast User Switching turned on? Is there a way to have the drive mounted BEFORE either user logs in, such that it will be seen as any other local drive (which doesn't have the issue)??
Or is there some other way I can attach to the network volume in each account on login so both have access to music and videos with full permissions?
I'm really stumped here after 2 hrs of googling, searching here and trying things.
TIA

I've not had any luck with the suggestions in the link either.
Here's two other approaches I've tried and failed with:
1. Creating a new share point on the cube itself so that one user can mount it as a different volume. Then the issue is that I still don't have a volume named "Jukebox" available to each user when switching. I DO have access now to the data from both accounts, but under 2 different mount points (volume names) and the xml file for iTunes is hard coded with the path for each mp3 including the "Jukebox" volume name... so no go.
2. Tried figuring out a way I could script a mounting of the share with the terminal thinking I could then run that shell script at startup. Can't seem to get the sytax right. If I create a directory in /Volumes and mount and afp share to it, it takes on the ownership of root/wheel which I can't access in the finder and can't seem to change.
BUT I'll keep playing with both these ideas a bit... the first one might be overcome with a bit of logic and the 2nd if I can get the syntax right to mount the share with afp_mount and give it the correct ownership/permissions such that when a user logs in she/he sees the volume on the desktop and has full r/w access to it.
thanks again. if you offhand know the syntax for that, let me know

How can i restrict access to a mounted smb drive?

Hope someone can help this is bugging me! i'm running this apple script as a student logs in to mount the students share folder, located on a MS2003 server, and a share drive on an Xserve to their desktop:
set student_name to (do shell script "echo $USER")
property stu_password : ""
-- displays the password dialog box and stores the result in stu_password
repeat while stu_password is ""
display dialog "enter your password to access the share" default answer stu_password with hidden answer
set stu_password to text returned of result
end repeat
-- mounts the network share to the desktop
tell application "Finder"
open location "smb://servername/stuhome/" & student_name & "/"
open location "afp://" & student_name & ":" & stu_password & "@servername/Share/"
end tell
It works fine and mounts the drives however... finder then defaults the network location so the student has access to all the folders on /servername/stuhome/ I just want it to mount /servername/stuhome/username/ with no backwards access. I cant set permissions from a server folder level (i don't think!) as its a windows server. any suggestions? why does finder do this? ta.
Intel XServe Mac OS X (10.4.10)
Intel XServe Mac OS X (10.4.10)

I've done a work round i'm not 100% happy with but it will do! If anyone else has this problem feel free to mail me.

Disk Utility 13 problem with USB drives

There appears to be a problem with Disk Utility 13 (part of OS X 10.9). At least, so far as I can tell, everything traces back to this app, or possibly OS X 10.9 itself.
I recently upgraded my MacBook Air to OS X 10.9 (reformatted hard drive, installed system from scratch, updated with all the latest Apple updates). I pre-checked all my third party software to make sure it was 10.9 compatible before installing it after the system cleanup, so everything I’m running supposedly has been approved as safe for 10.9. But I’m seeing a problem formatting USB drives that I do not encounter when running under 10.8.
I have a Seagate STAA500101 (“FreeAgent GoFlex”) drive connected via Seagate’s USB3 adapter that I’ve used for some time as a Time Machine backup. Post-overhaul, I decided to erase the backup and start fresh. When I attempt to format it (single GUID partition) with Disk Utility, I see the following messages go by:
Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled 1
Could not mount disk1s2 with name (null) after erase
Then there’s a pause, and the format appears to conclude fine. But if I run a “Verify Disk” immediately, I get this:
Verifying partition map for “Seagate FreeAgent GoFlex Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Volume on disk1s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
Problems were found with the partition map which might prevent booting
Error: Partition map needs repair because a data partition needs loader space.
As the drive has just been formatted, that seemed odd. I took it over to another Mac still running 10.8.5 and formatted it there — it worked just fine. Verified just fine. Took the drive back to my MacBook Air and tried to verify the disk — same failure.
I wanted to rule out bad media, so I took a Lexar 16GB USB flash drive and tried to format it with Disk Utility 13 — got the same problem.
The only success I’ve had formatting USB drives under 10.9 is to boot up into OS X Recovery. Disk Utility there formatted my Seagate drive without an error. But once I booted back into normal 10.9 operating mode, the drive once again fails to verify; it makes me leery about using it as a Time Machine backup.
I suppose it’s possible there could be some background component like Sophos causing problems when formatting drives, but if I format a drive via OS X Recovery or another Mac under 10.8, that wouldn’t explain why the drives fail to verify.
Anyone got any other observations on this issue?

Problem resolved. I'm posting this note for anyone else who might run into this situation and come across this discussion.
It actually did turn out to be Sophos -- Cloud, that is. I'd been using Sophos' free Mac antivirus software on a variety of systems but forgot that I was now testing out Sophos Cloud on my own MacBook, which is their new endpoint solution, and supposed to be compatible with OS X 10.9 (although the Mac version is listed as "beta") Sophos Cloud includes a new feature called Device Control which allows you to create a company-wide policy to control access to hardware such as USB drives, optical drives, etc. But apparently it's still pretty buggy. I had my Device Control configured with the default setting of "monitor but do not block" but it was most definitely gumming up the system. With Sophos Cloud installed, here's what happens if I try to run "Verify Disk" on any attached drive. Note on the left side how "disk2s2" shows as a sub-volume for each hard drive.
So if I uninstall Sophos Cloud, reboot and rescan, here's what I get:
Works fine. Note that the "disk2s2" subvolumes are also gone. This is the way Disk Utility also appears on a 10.8 or 10.9 system, even if you have the standard free Sophos for Mac software installed. It's only Sophos Cloud that's not playing nice. It also appears to have stopped me from being able to play DVDs from an attached Apple USB SuperDrive -- that problem was likewise solved by removing Sophos Cloud.

[SOLVED] DBUS boot problems - Mounting system devices as a normal user

I have the [testing] and [community-testing] repositories enabled. A few days ago, probably due to an update, I started having trouble mounting devices and the shutdown/reboot options don't show up anymore on the LXDE exit menu.
I use gvfs for mounting devices as a normal user with PCManFM or Thunar. The error message is "Authentication is required".
After some testing, I found out that by restarting dbus, I could start mounting devices again:
/etc/rc.d/dbus restart
So my guess is that there's some problem with dbus startup. I have it in DAEMONS of rc.conf, as well as .xinitrc, the daemon seems to start correctly on boot, and it worked previously, so I have no idea of what could be wrong.
My ~/.xinitrc:
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
eval 'dbus-launch --sh-syntax --exit-with-session'
fi
numlockx && exec ck-launch-session dbus-launch startlxde
My /etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="ca_AD.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Andorra"
KEYMAP="es"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="localhost"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(hwclock syslog-ng network crond alsa dbus cupsd)
Thanks!
Last edited by gamezelda (2011-11-08 19:28:04)

I solved it.
The Wiki page for Mounting for normal users with PCManFM tells to create a "/etc/polkit-1/localauthority/50-local.d/55-myconf.pkla" file specifying the privileges to grant to the user. The problem is that it does not include the privilege needed to mount internal drives (which was what I was trying to mount). To fix it, I added:
;org.freedesktop.udisks.filesystem-mount-system-internal
To the "Action=..." line.
(Though I have no idea why it worked before it broke, or why restarting dbus after initializing my WM fixed it.)
As for the power issues, I've concluded that it was working, but restarting dbus after initializing my WM broke it (my bad for not checking it before restaring dbus). So it all works now.

Big problems after hard drive failure - Please help.

About 2 weeks ago, my Macbook seized, and was sent to Apple to repair.
It was found that the hard drive failed, and 2 weeks later I received my macbook back with a new hard drive.
Luckily I had backed up my home drive and was able to restore it using backup.
Now this is where my problems start.
My home drive is not the same name ( I think - I can'r remember too well what it was called previously )
I have my entire music library backed up to an external hard drive, and mounting this hard drive is a REAL pain in the *** now.
Sometime it loads up, sometime it just doesn;t get recognised, and I can put the USB connection in and out 10 times before it mounts.
I have verified the disk, and nothing is wrong.
Does anyone know what this problen could be ?
I have left the external hard drive in during the night, and after the macbook goes to sleep, I will go back to it in the morning, and the hard drive has been unmounted, and I repeat the exercise over again of trying to mount the drive.
Its so annoying, and I just dont know wht to do.
If anyone can help, I;d really appreciate it.
Griff

SMART status is a pretty reliable indicator of what is going on. You should back up your irreplaceable files as soon as possible.

[Solved-sortof] Mounting dvd drive /dev/hdc

My dvd drive is not mounting for some reason, I thought maybe I just needed to restart and that it would mount again but no luck, this is what I get:
mount /dev/hdc /test
mount: no medium found
I put the same DvD in my cdrom/dvd drive and it mounts so i know it's not the dvd. I thought well, this is a dell shipped dvd drive so maybe it died, I'll give it a test. I slap the dvd in the drive, since it's the master cd drive it shoudl load a cd at bootup and it does, loads Fedora dvd image easily. I did upgrade something this morning, mostly gnome stuff, so I am thinking it's one of the packages assuming I don't have /dev/hdc on my computer. Is there a way to see what's going on?
Quick Edit
I did a quick edit to see what exactly was going on, I am far from a linux pro, but I do have some common sense. I took gdm / hal off my daemons list and rebooted. Now from command linue I logged into root and tried to mount the drive /dev/hdc and it worked perfectly flawless, no errors. So I am guessing this has to do with a hal problems that was caused during an update. Any further help would be much appreciated though because I don't know where to go from here.
Edit again
I solved my little "issue" apparently it was just the dvd I was trying, for some odd reason my dvd drive was refusing to auto-load the dvd movie. Yes I burned a dvd movie, I do own the original copy, I just burn a backup incase of dmg / loss. The original dvd loads fine with no mounting issues. The dvd I burned works in a dvd player, and on my secondary dvd/rw drive, I don't like watching movies on the dvd/rw drive though because of the fact that it's read capabilities is much slower. I am still puzzled on why my dvd drive doesn't like to mount / read it correctly.

mzneverdies wrote:
not sure, but in order to mount cds/dvds, I think you must use the -o loop flag
sudo mount -t iso9660 -o loop /dev/cdrom /media/cdrom
The loop flag is for mounting ISOs.

Pcmanfm is "Not Authorized" to mount usb drives

Hi,
I recently installed arch linux it's a nice distro but I got a few problem with it.
The biggest one is that I am actually not able to mount usb drives with pcmanfm this means that I am not able to use my old debian /home so far.
I tired multiple thinks (some of them are still active) e.g for example I used to setup a udev rules which wasn't helpful at all (and even after deleting this rule I always see server empty folder in /media (but that's another problem)).
Any ideas why I am not able to mount encrypted and not encrypted USB drives in arch linux?
Last edited by 42sec (2011-12-28 13:21:41)

wonder wrote:paste ck-list-sessions output, uname -r and cat /etc/pam.d/login
[sec42@archlinux ~]$ ck-list-sessions
Session1:
unix-user = '1000'
realname = ''
seat = 'Seat1'
session-type = ''
active = FALSE
x11-display = ''
x11-display-device = ''
display-device = '/dev/tty1'
remote-host-name = ''
is-local = TRUE
on-since = '2011-12-28T14:28:01.840505Z'
login-session-id = '1'
idle-since-hint = '2011-12-28T14:28:32.462384Z'
[sec42@archlinux ~]$ uname -r
3.1.5-1-ARCH
[sec42@archlinux ~]$ cat /etc/pam.d/login
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.so
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so

Cannot mount external drives

Hi all!
I have an 2010 imac i5 32GB RAM, running on 10.9.2.
All of a sudden my machine does not mount ANY extrenal hard drive. It recognises them in Disk Utility, but they appear greyed and cannot be mounted. Not even disk repair. Last week though the drives were mounting on the system without any problems.
Yesterday I have upgraded the OS to 10.9.2. (from 10.6.8). Still the same problem, the drives are recognisable in DU but cannot be mounted.
All of the disks I've tried are NTFS format (originally formatted on a pc). Funny thing is I have VMware Fusion on my mac runing a virtual Windows 7 pc. Windows do recognise the drives and mount them without problem, but not the mac.
Also note that I'm using Tuxera NFS to work with these drives with no problem so far, until now.
Also checked the cables, I'm connecting the drives though USB ports, they are ok.
Any suggestions?

just guessing you are using USB to mount the external. you may need to use two usb ports to mount the drive. that means a cable with two usb connectors which should provide enough power to the external.

Problems mounting fat drives

Similar Messages

Maybe you are looking for