Udev auto mounting not recognising my labels

I have added the auto mounting rules to my udev config exactly as specified in the wiki:
http://wiki.archlinux.org/index.php/Ude … if_present
This works to the extend that I can see the devices being mounted under media, but, for most of my deviecs, I have labels defined in /etc/fstab/:
/dev/disk/by-uuid/74C7-B9D3 /media/android vfat noauto,users 0 0
/dev/disk/by-uuid/20A0-683F /media/cowon vfat noauto,users 0 0
/dev/disk/by-uuid/A036-C3DF /media/cowonsd vfat noauto,users 0 0
/dev/disk/by-uuid/00C6-17D0 /media/ipod vfat noauto,users 0 0
/dev/disk/by-uuid/68DB-1857 /media/cardreader vfat noauto,users 0 0
/dev/disk/by-uuid/72AD-2013 /media/acekard vfat noauto,users 0 0
For some reason, however, they are being mounted as /media/usbhd-sd*
What am I missing here?

dmesg says:
usb 1-6: new high speed USB device using ehci_hcd and address 8
scsi8 : usb-storage 1-6:1.0
scsi 8:0:0:0: Direct-Access COWON D2+ DAB 0100 PQ: 0 ANSI: 0
sd 8:0:0:0: Attached scsi generic sg5 type 0
scsi 8:0:0:1: Direct-Access COWON D2+ DAB 0100 PQ: 0 ANSI: 0
sd 8:0:0:1: Attached scsi generic sg6 type 0
sd 8:0:0:0: [sde] 32292864 512-byte logical blocks: (16.5 GB/15.3 GiB)
sd 8:0:0:0: [sde] Write Protect is off
sd 8:0:0:0: [sde] Mode Sense: 37 00 00 08
sd 8:0:0:0: [sde] Assuming drive cache: write through
sd 8:0:0:1: [sdf] 63438400 512-byte logical blocks: (32.4 GB/30.2 GiB)
sd 8:0:0:1: [sdf] Write Protect is off
sd 8:0:0:1: [sdf] Mode Sense: 37 00 00 08
sd 8:0:0:1: [sdf] Assuming drive cache: write through
sd 8:0:0:0: [sde] Assuming drive cache: write through
sde:
sd 8:0:0:1: [sdf] Assuming drive cache: write through
sdf: sdf1
sd 8:0:0:0: [sde] Assuming drive cache: write through
sd 8:0:0:0: [sde] Attached SCSI removable disk
sd 8:0:0:1: [sdf] Assuming drive cache: write through
sd 8:0:0:1: [sdf] Attached SCSI removable disk
Still only COWONSD that's mounted. That's really confused me. dmesg seems to only refer to COWON, but it's only COWONSD that gets mounted...

Similar Messages

Disable Auto-Mounting

Hi Everyone,
I have been searching forum after forum trying to find an answer to my question but am not having any luck. I have found one option but there has to be a better way. As I am taking a Computer Forensics major I need to disable auto-mounting of USB drives so I can manually mount the device with read-only options so I do not destroy evidence on drive I need to investigate.
About 3 versions ago in Ubuntu I was able to just uncheck a box in the system settings so it would not auto-mount. Then they decided to get rid of that option because it was not compatible with changes they made to other parts of the system. So to get around the auto-mounting I found that I could shutdown hal, plug the drive in, issue my mount command, then finally restart hal so network manager and other services that needed it could run right. This seems kind of pointless to have to shut down hal and break things just so I can mount a drive. Since I recently left Ubuntu behind and converted to Arch I thought I would see if you guys had any ideas.
I know I can add options to fstab but since I will get a different drive for every investigation this doesn't seem to be an option either.
Any help you guys could offer would be highly appreciated.
Thanks,
Timn
Last edited by Timn (2009-11-17 01:18:33)

It is probably your window manager that does the auto-mounting, not arch. If it's gnome, there is a key in the gconf "/apps/nautilus/preferences/media_autorun" which you would need to disable. I do use FluxBox as a WM which does not do any mounting. These are the only window managers for which I can provide specific inforamtion. But no matte what you use, KDE, XFCE or something else, there should be a configuration that allows you to disable it.
If that didn't help, please provide more specific information about your setup.

[SOLVED] Thunar (XFCE4) Does not Auto-mount USB Drive

After reading some posts related to USB auto-mounting in Thunar and yet still having the problem, I decided to post this. Thunar used to detect the USB drives and auto-mount them. These days (I GUESS after moving to systemd), It cannot do so. Still, there is the icon of USB drive on the left side panel, but when I click on it to browse it, I get this error:
Failed to mount "USB_LABLE".
Error when getting information for file
'/media/usbhd-sdc1': Transport endpoint is not connected.
I am still able to use "sudo mount..." and get the job done, but I would prefer the convenient way it used to work. Here are some information about my system:
command> cat ~/.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
exec startxfce4
command> loginctl show-session $XDG_SESSION_ID
Id=1
Timestamp=Sat, 2012-11-10 20:35:51 CET
TimestampMonotonic=34276379
DefaultControlGroup=name=systemd:/user/username/1
VTNr=7
Display=:0.0
Remote=no
RemoteUser=root
Service=slim
Leader=297
Audit=1
Type=x11
Class=user
Active=yes
State=active
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
command> systemctl status polkit
polkit.service - Authorization Manager
Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
Active: active (running) since ...
Docs: man:polkit(8)
Main PID: 305 (polkitd)
CGroup: name=systemd:/system/polkit.service
305 /usr/lib/polkit-1/polkitd --no-debug
command> dmesg
Attached scsi generic sg1 type 0
[sdc] 15470592 512-byte logical blocks: (7.92 GB/7.37 GiB)
[sdc] Write Protect is off
[sdc] Mode Sense: 23 00 00 00
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through sdc: sdc1
[sdc] No Caching mode page present
[sdc] Assuming drive cache: write through
[sdc] Attached SCSI removable disk
I'd rather not edit the /etc/fstab; the way Thunar used to behave, was working with every new USB. I wonder if anybody can shed some lights.
Last edited by Shahab (2012-11-10 21:56:24)

The error looks suspiciously like one I had not so long ago and it turned out I still had an 11-media-by-label-auto-mount.rule in /etc/udev/rules.d. Once I removed that and rebooted everything was fine again.

All downloads failing to mount and iTunes not recognising iPod!

My iBook G4 (Model No A 1055) needs alot of updates however i can't install anything. It downloads to the Desktop fine but when i go to open the attachment so i can actually install it a message comes up saing "The following disk images failed to mount" and the reason is a "corrupt image". I have tried to do this with Firefox, iTunes and Adobe and they all say the same!
I also now have issues with iTunes (7.2) which is all of a sudden not recognising my iPod shuffle (2nd gen). It doesn't come up in devices or anything when plugged in my iPod shuffle will just flash orange a few times and then nothing. I have tried to connect it to another (and much newer) Mac computer however it doesn't recognise it on there either.
Has technology just got so good my lappy is basically extinct and i need a new one or is there something i / Apple can do to help get me up to date with everything? Any help and feedback would be really appreciated.
Thanks
Louise

if you are running OS 10.3, it's pretty much obsolete
you can try getting OS 10.5 installed, but it can slow down the computer, 10.4 is not much use anymore either.

External Hard Drive connected to AEBS does not auto mount

Just upgraded from Tiger 10.4.11 to Leopard 10.5.5. I have a AEBS running 5.3.2 airport utility with a LaCie HD connected to it.
In Tiger, my external hard drive would auto mount onto the desktop every time the computer turned on or woke up from sleeping etc.
In Leopard, my external drive will not auto mount. It does not show up in the sidebar under devices. It does not show up in the disk utility. To access it, I have to go the the finder sidebar, select my AEBS under shared, then select my HD. Also, I did check show connected servers and external disk on the desktop in the finder preferences. Also, not sure if this matters but the icon on my external drive on my desktop is the blue drive with three people holding hands and not the brighter blue one with the wireless signal logo.
In tiger my external HD basically acted like any other folder that was always there and not like a networked drive that I had to go and connect to. I want to go back to that. I heard this has to do with leopord no longer having the airdisk utility??
thanks

Try making an alias of one of the top-level folders in your external (AEBS-connected) drive, drag it to the desktop, and then put it in your Login Items.
--> System Preferences/Accounts/Login Items
You can simply drag the folder alias into the Login Items window.
When you next log in, the folder will be automatically opened. Alas, it doesn't give you instant access to the entire external drive, but you can back out a level to see the entire drive. It isn't quite what you had with Tiger, but perhaps it will suffice.
If you leave the aliased folder on your desktop, you have a skinny approximation to the mounted volume that you had with Tiger.

DMG's not auto mounting after download

I've recently switched to using Safari as my main browser, and I'm having trouble with DMG's not mounting after I successfully download them.
I do have the option enabled 'Open "safe" files after downloading' turned on, and some files auto-open after downloading them, but not DMG's - and that seems to be what I most frequently download.
I even tried creating a com.apple.DownloadAssessment.plist file and added DMG to the safe list, as discussed here. But that didn't seem to make any difference either.
All in all I'm very happy with Safari, but have to get these darned DMG's to auto-mount like they are supposed to.
Any and all ideas welcomed.

Ok, I resolved this one myself.
FlashMount 1.5.2 was the problem. FlashMount is a killer alternative to Apple's Disk Image Mounter in OSX but for some reason with Safari DMG's don't auto mount. There is no problem with Camino, not sure why this is happening which is unfortunate since FlashMount looks to be deprecated.
FlashMount: Apple's Disk Image Mounter in OSX.

External drive not auto mounting (anymore)

i have a external HDD for which I made an entry in fstab. I worked perfectly till now. After i installed udisks and wrapper 'devmon' all the other drive are now auto mounted but the one which has entry in fstab does not !
i believe fstab mounts it during the boot up and devmon mounts it during the awesome start up since I made devmon entry in .xinitrc. is it the udisks thats conflicting with fstab ?!?! i mean its unlikely to happen right ?

Actually that is an interesting question. I have an external drive connected to my router and I share it on the router IP address (obviously fixed) via samba. Is it still a bad idea to use fstab in such case?
Sometimes but not always I have a re-mount problem coming back from hibernate or suspend. Will it be solved if I move mount to mtab?
Last edited by snovik (2012-05-22 10:48:29)

Server Shares will not Auto-Mount on Clients

Hi,
When I log onto my network, my server shares do not auto-mount.
Clients are able to log onto network. Connection to server on clients shows a
green light. When I go into finder and try to connect to shares network with
client user name /password it will not open shares. Shares will open with server
password, but I don't want to save server password on the clients.
All other services will setup and work as expected using client username / password.
I'm using Mountain Lion Server 10.8.2 and Mountain Lion Clients 10.8.2.
File sharing is turned on in the MLS Profile. Service access for clients File Sharing is checked.
I have tried restarting server clients.
Any ideas on how to fix this, short of a reinstall?
Thanks,
John

Imagine you want to enter your parents' house. You have a key for your house but it won't work on their locks. They won't give you their key and now you complain you can't get in with your own key. Same thing, server password and client password are two different keys for two different locks.

Won't mount, file system not recognised

I'm trying to download firmware from Netgear's website but when I try to mount the files they say the file system is not recognised.
I'm trying to get hold of Netgear as well but I thought someone here might have some suggestions too while I wait for a response from Netgear.
The two files I've tried so far are:
http://kbserver.netgear.com/release_notes/D102713.asp
ftp://downloads.netgear.com/files/dg834v2_1022.zip
http://kbserver.netgear.com/release_notes/D103044.asp
ftp://downloads.netgear.com/files/dg8343_0132.zip

My mistake. The file I was trying to mount isn't intended to be mounted. You're actually meant to upload this .img file directly to the modem.

CD does not mount on desktop and is not recognised by OSIRIX since moved over to Mavericks

Dicomm CD not recognised in Mavericks on desktop or by Osirix

System Preferences > CDs & DVDs > When you insert a blank CD > choose one
Same for DVD, assuming this is all the same for Leopard as for Tiger and you're talking about blank discs.

Latest Initrd not recognising USB storage devices?

Just installed 2.6.30 with all the necessary files. Everything seemed fine, except for one thing: my external USB hard drive is no longer recognised on boot. Here is my fstab and my mkinitcpio.conf.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs rw,noexec,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=139cf76d-425a-4c40-a5b1-bbbf22533d9a /boot ext4 defaults 0 1
UUID=4eddd177-23f6-49ab-a8ad-d3e1303133e0 / ext4 defaults 0 1
UUID=ED83-B8D4 /media/flash vfat rw,user,noauto 0 0
#UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /iomega ext4 rw,noexec,nosuid 0 1
UUID=ac46c6ae-d9eb-47d4-809b-19a2484b3133 /media/iomega ext4 rw,user,noauto 0 0
UUID=da9e741f-3525-47c6-8c7f-edf1ded00e7a swap swap defaults 0 0
As you can see from this, I originally had my external usb drive mounted on /iomega @ boot. However, since that no longer works, I have changed it to /media/iomega and let HAL mount it automatically when I fire up GNOME (the same way I have my flash drive set up). I used the original line with 2.6.29 with no problems.
The strange thing is, the device is there, because, when it fails, I go into single user mode, remount / read-write and then run mount -a and the device appears with no errors. If I change the line so it doesn't do an fsck on boot, it doesn't mount the device, but I do get an error saying the device is not there. I can then mount it manually at the command prompt.
The device is shown in /etc/blkid.tab and in /dev/disk/by-uuid.
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes, into the CPIO image, and additional
# binaries a given user may wish. This is run first, so may
# be used to override the actual binaries used in a given hook.
# (Existing files are NOT overwritten is already added)
# BINARIES are dependancy parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in anyway. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options,
# like so:
# FILES="/etc/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'modload' may be used in place of 'udev', but is not recommended
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
# This setup specifies all modules in the MODULES setting above.
# No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
# This setup will autodetect all modules for your system and should
# work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
# This is identical to the above, except the old ide subsystem is
# used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
# This setup will generate a 'full' image which supports most systems.
# No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
# This setup assembles an pata raid array with an encrypted root FS.
# Note: See 'mkinitcpio -H raid' for more information on raid devices.
# HOOKS="base udev pata raid encrypt filesystems"
# This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
HOOKS="base udev autodetect pata scsi sata usb keymap filesystems"
# COMPRESSION
# Use this to compress the initramfs image. With kernels earlier than
# 2.6.30, only gzip is supported, which is also the default. Newer kernels
# support gzip, bzip2 and lzma.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
This is essentially the same as I had it in 2.6.29. I did initially use LZMA, since that gives slightly faster compression & decompression, but changed it back in case it was a timing issue (and rebuilt initrd). No joy. I also tried usbdelay=10 on boot, but again no difference.
This isn't exactly a "show-stopper", since the device functions normally otherwise and everything else is fine, but it is annoying. I would much rather have this device available automatically on boot, so that it gets checked when the max mount count comes up.

This was the bug update I received today:
FS#15282 - [mkinitcpio] Latest initrd not recognising usb storage devices?
User who did this - Thomas Bächler (brain0)
You can never rely on external hard drives to show up "in time".
The difference was that adding the "usb" hook to mkinitcpio used to add a 6 second delay on boot by default, this doesn't happen anymore. I think external drives simply don't belong in fstab, because there's too many possible race conditions. If you insist, you can try to force the usb storage driver to scan for devices sooner after detection, see the delay_use parameter to the usb-storage module.
You're going to have to modify the delay_use parameter to get it to work. Be prepared for race conditions, though. I didn't bother myself as it wasn't a show stopper for me, so I've advised that it can be closed as a non-bug.
ETA: usbdelay=10 doesn't work as that flag is apparently no longer recognised for some reason.
ETTA: I've always used UUID in the fstab because udev can remap devices on boot (I've had fstab not recognising devices because of this).
In case some people don't know, to see what the uuid for a device is, use the following:
sudo tune2fs -l <device-name>
Last edited by jamesbannon (2009-06-28 18:30:23)

LG USB drive won't (auto)mount

Hi guys,
This is my first post, and I'm not sure if this thread goes here, but anyways, I have a problem with my LG USB External Drive.
Ok, this is what happened. When I connected the drive the activity LED turned on but the volume didn't appear in Thunar, so I went to check if it was at least detected but neither GParted nor lsusb show the USB disk listed. I connected the drive to a netbook with Xubuntu 9.10 and it automounts correctly, also in the same netbook with Windows 7. I've been looking for information about evdev, udev, HAL and Xorg but I couldn't fix the error. The drive worked sporadically one month ago, but I reinstalled Arch and now it won't work.
Here is all the additional data.
* Desktop Environment: XFCE 4.6.1
* lsusb:
Bus 002 Device 002: ID 043d:0057 Lexmark International, Inc. Z35 Printer
Bus 002 Device 004: ID 045e:070f Microsoft Corp.
Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 18e3:9101 Fitipower Integrated Technology Inc
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
* rc.conf: http://dpaste.com/163807/
* mkinitcpio.conf: http://dpaste.com/163810/
* xorg.conf: http://dpaste.com/163811/
* /etc/udev/rules.d/11-media-by-label-auto-mount.rules: http://dpaste.com/163815/
This is all I have (or I think so).
Thanks in advance

Hi scar,
This is the output.
sd 4:0:0:3: Attached scsi generic sg5 type 0
usb-storage: device scan complete
sd 4:0:0:0: [sdb] Attached SCSI removable disk
sd 4:0:0:1: [sdc] Attached SCSI removable disk
sd 4:0:0:3: [sde] Attached SCSI removable disk
sd 4:0:0:2: [sdd] Attached SCSI removable disk
EXT4-fs (sda2): mounted filesystem with ordered data mode
Adding 1951888k swap on /dev/sda3. Priority:-1 extents:1 across:1951888k
forcedeth 0000:00:07.0: irq 27 for MSI/MSI-X
fuse init (API version 7.13)
Seems to be the disk is at least detected. Maybe I need further HAL/Udev configuration, well, what do you think?
Last edited by Penguino (2010-02-24 20:39:06)

Disable Gnome auto mount for one specific UUID

I am using Gnome 3 (gnome disk utility,udisks,udev stack i think).
I have a device (Garmin Edge 800) that I am only going to use in Virtualbox so I want to prevent it from automatically mounting in Gnome. However I want other devices to auto mount as normal so disabling auto mount entirely isn't an option.
The device got two UUIDs and previously I could write a HAL fdi policy to ignore devices with those UUIDs, but now that HAL is deprecated I am not able to figure out how to do this.
Last edited by lessthanjake (2011-06-29 09:56:30)

There's probably a udev config file somewhere (udev wiki perhaps) but you can do it with fstab "noauto" that's what I do for partitions I don't want to auto mount.

Working auto-mount?

Hi all,
I have a xfce4 desktop installed. I want an automount service. I tried autoFS, with the following settings:
auto.master
/media /etc/autofs/auto.custom --timeout=15
auto.custom
disc -fstype=auto,ro,nodev,nosuid :/dev/cdrom
Backup -fstype=auto,user,rw,async,umask=000,gid=users,noatime,nodiratime :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
## Backup -fstype=ext4,user,rw,async,umask=000,gid=users,noatime,nodiratime :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
Shared -fstype=ntfs-3g,user,rw,async,umask=000,gid=users,noatime,nodiratime :/d ev/disk/by-uuid/565AF3085AF2E421
ReaderCard -fstype=vfat,flush,user,rw,async,umask=000,gid=users,noatime,nodirat
ime :/dev/disk/by-uuid/0102-0304
##ReaderInt -fstype=auto,async,nodev,nosuid,umask=000,gid=users :
## Other medium here
# floppy -fstype=auto,async,nodev,nosuid,umask=000 :/dev/fl
The files are formatted following the instructions. The partition Backup, however, does not come up ("no such file or directory", even when root).
Backup is ext4 and it's kept on an external hard drive, the same of Shared. Mounting it manually works. I have tried with simpler options (as simple as
Backup -fstype=auto :/dev/disk/by-uuid/f569bba5-8007-40f5-8b3c-36960c5796d5
with no results. Autofs won't do.
As an alternative I have tried xfce volume manager, but that doesn't work with ANY external device.
Please help. Thank you.

That would be a solution - if it worked. I tried that too. The Arch wiki just glances on the setup, solving the whole question with a one liner "Thunar-volman's automount doesn't work currently because of the hal to udev switch, Sept 2010"
The section on udev is obscure, mentioning to check policykit to "properly start your session".
However the policykit page is also obscure, containing no mention about starting X session properly or even improperly for what matters.
The default setting produces no result at all.
Nowhere I was able to find a five-lines working example of set up. I have used Linux daily since 2000 (and I know it should not take more than 5 line explanation to setup an auto-mount).
I am really embittered by this interpretation of "the arch way". The documentation on certain core tools such as policykit is completely insufficient and the defaults do not solve basic problems (hours to set up a basic auto-mount? incomplete wiki pages referring each other?).
Arch could be a perfect desktop distribution with just a pinch of attention to put the obvious features, when correctly disabled by default, at easy reach through complete examples. (Shutdown buttons? Same story: one line reference to policykit, dbus and other 10 tools with not the barest explanation about how to use them in synergy for the purpose. Result? Manual shutdown for the moment).
If you could provide a working setup for thunar volume manager I'll be happy to use and add it to the wiki.
Thank you.

System Profile not recognising known good 80GB ADM

I currently have 2 Xserve slot loading, running Mac OS Server 10.3.9. Drive bay 1 and 2 contain 2 mirrored drives. When I place the spare drive module in bay 3 it is not recognised in system profiler and will not mount. It has been working before for backups is this a known issue that may have been caused by an update ? I am currently running frimware version 5.1.7f1.
Xserve G5 slot loading Mac OS X (10.3.9)

First of all, unless you have 10.4 running and have your mirror set to auto-rebuild, your raid should now be degraded.
It is easy to repair anyway, but you should check the status with disk utility or diskutil command line.
I am assuming that unrecognized means that the drive doesn't even show up in disk utility? or does it say that the drive isn't recognized in the finder (with a message to format)?
The latter may be fixed with the usual tools like disk warrior or even the repair funtion in Disk Utility. If the drive is completely invisible, it may be something as simple as a loose connector inside the drive module (power or sata). Have not seen that though.
If you have Applecare, just try to get it exchanged...

Udev auto mounting not recognising my labels

Similar Messages

Maybe you are looking for