sudo exfat.util -m disk2s1 broken, osx exfat.util -m disk2s1 broken on 10.6.8

Question

sudo exfat.util -m disk2s1 broken, osx exfat.util -m disk2s1 broken on 10.6.8

external 1tb usb drive works on other computers win or osx

current machine mcb and drive works on win 7, mounts, read/write

but will not now work with 10.6.8, it worked with original OSX but when updated it is now broken

diskutil finds the drive but cannot mount it, repairs, etc nothing works, drive will not mount

sudo exfat.util -k disk2s1

returns UUID of

422B6F52-A47C-4917-9B87-1B3668853FB9

sudo exfat.util -m disk2s1 /Volumes/EX removale writable

returns this

usage: exfat.util action_arg device_arg [mount_point_arg] [Flags]

action_arg:

-p (Probe)

-m (Mount)

-u (Unmount)

-k (Get UUID)

-s (Set UUID)

device_arg:

device we are acting upon (for example, 'disk0s2')

mount_point_arg:

required for Mount and Force Mount

Flags:

required for Mount, Force Mount and Probe

indicates removable or fixed (for example 'fixed')

indicates readonly or writable (for example 'readonly')

Examples:

exfat.util -p disk0s2 fixed writable

exfat.util -m disk0s2 /my/hfs removable readonly

so what's up with this?

MacBook, Mac OS X (10.6.8)

Posted on Dec 4, 2011 6:39 AM

Reply

Answer 1

Dec 4, 2011 6:41 AM in response to painter_landscapes

also i manually created fstab but OSX ignores it or is broken w

Reply

Answer 2

Linc Davis

Level 10

209,547 points

Dec 4, 2011 8:24 AM in response to painter_landscapes

You're trying to mount the wrong slice, and you should not be trying to mount anything manually in the Volumes directory. That directory is reserved for automounts.

Delete the fstab file.

If the volume doesn't mount automatically, it's damaged, notwithstanding the fact that it still mounts in Windows. If you can't repair it with Disk Utility, erase it and restore from one of your backups.

Reply

Answer 3

Camelot

Level 9

54,333 points

Dec 5, 2011 12:18 PM in response to painter_landscapes

Independent of whether or not the volume should automount, man exfat.util states:

The -m and -u options are deprecated. The preferred way to mount an

ExFAT volume is to let diskarbitrationd(8) mount it automatically when

the device is discovered, or use the diskutil(8) command to explicitly

mount a device

Therefore:

sudo diskutil mount disk2s1

would likely have more success.

Reply

Answer 4

Linc Davis

Level 10

209,547 points

Dec 5, 2011 12:30 PM in response to Camelot

You have to specify a mountpoint, which must be an existing node. It's not created automatically.

Reply

Answer 5

Dec 5, 2011 12:38 PM in response to painter_landscapes

Mounted: No

File System: ExFAT

Type: exfat

Name: ExFAT

Partition Type: Windows_NTFS

Bootable: Not bootable

Media Type: Generic

Protocol: USB

SMART Status: Not Supported

Volume UUID: 422B6F52-A47C-4917-9B87-1B3668853FB9

Total Size: 1.0 TB (1000200994816 Bytes) (exactly 1953517568 512-Byte-Blocks)

Volume Free Space: 0 B (0 Bytes) (exactly 0 512-Byte-Blocks)

Read-Only Media: No

Read-Only Volume: Not applicable (not mounted)

Ejectable: Yes

Whole: No

Internal: No

the i added mountPoint

diskutil mount -mountPoint /Users/me/drive disk2s1

it returns

Volume on disk2s1 failed to mount

is there any way to verify whether the fuse driver is conflicting with OSX driver?

Reply

Answer 6

Dec 5, 2011 12:40 PM in response to painter_landscapes

i did these as root, sudo

Reply

Answer 7

Dec 5, 2011 12:42 PM in response to Linc Davis

it mounts on the latest mcb pro with lion, ok.

Reply

Answer 8

Linc Davis

Level 10

209,547 points

Dec 5, 2011 1:14 PM in response to painter_landscapes

is there any way to verify whether the fuse driver is conflicting with OSX driver?

Yes. Uninstall it, or boot in safe mode.

Reply

Answer 9

Dec 5, 2011 2:45 PM in response to Linc Davis

uninstall didn't work as booting into single user mode, reported a driver error with fuse.

does osx keep a hidden driver cache somewhere for boot devices that needs to be flushed out?

i tried this

dscacheutil -flushcache

and

sudo periodic daily weekly monthly

but no joy

Reply

Answer 10

Camelot

Level 9

54,333 points

Dec 5, 2011 3:15 PM in response to Linc Davis

You have to specify a mountpoint, which must be an existing node. It's not created automatically.

Actually, according to man diskutil:

If a -mountPoint is specified, then that path, rather than the standard path of /Volumes/VolumeName, will be used as the view into the volume file content

In other words, if you want it to mount at a specific mountpoint you need to say so, otherwise, if you use the form I used, it mounts under /Volumes.

Reply