sshfs fails to mount on OS X 10.9.3 (SSH-2.0-OpenSSH_6.2: command not understood)

[Aaron Harding]

Hi OSXFUSE,

I'm trying to use sshfs to mount an FTP server that is hosted on an Android device and I get the following error:

I've tried to connect on two devices and these are the logs for each device. The first, AaronsPhone, is the Android device, and the second, Sophie's Phone, is an iPhone.

Running SSHFS version 2.5 (OSXFUSE SSHFS 2.5.0) with OSXFUSE library version: FUSE 2.7.3 / OSXFUSE 2.6.0. Can anyone shed any light?

Thanks

[Aaron Harding]

If it helps, it's also fails to mount in bash:

Sophies-MacBook-Pro:~ sophiegunter$ sshfs sophie:sop...@192.168.1.12:/ ~/mountpoint -o defer_permissions,port=2121,sshfs_debug

SSHFS version 2.5

remote host has disconnected

mount_osxfusefs: failed to mount /Users/sophiegunter/mountpoint@/dev/osxfuse0: Operation not permitted

And nothing is being reported in Console.app when this fails to mount

[Sam Moffatt]

Can you SSH normally into the device? Does scp work properly?

Sam Moffatt
http://pasamio.id.au

--
You received this message because you are subscribed to the Google Groups "OSXFUSE" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osxfuse-grou...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Aaron Harding]

I can't SSH normally into the device although I can SSH into other external hosts, sdf.org for example. UPnP is enabled and I'm just trying to find out wether this router has WiFi isolation turned on, as that could be the problem.

--
You received this message because you are subscribed to a topic in the Google Groups "OSXFUSE" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osxfuse-group/aJElhuRInR4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osxfuse-grou...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

aaron

[Sam Moffatt]

If you can't use SSH to get into the device, how do you expect SFTP to work? Unless you mean plain old boring FTP, in which case Mac OS X supports mounting FTP directories natively. Just use Finder -> Go -> Connect to Server and put in ftp://192.168.1.2:2121

Sam Moffatt
http://pasamio.id.au

[Aaron Harding]

I only found out that I couldn't directly SSH into the device from your suggestion—within the last couple of minutes!—sorry I should have mentioned this. I can successfully mount the FTP server using Finder, but the application I'd like to use this volume with doesn't find the FTP server as a volume, neither does diskutil. "diskutil list" for example, shows the MacBook hard drive and not the FTP server.

However, I may have solved my problem. I've mounted the server through finder and then created a disk image of the server through the Disk Utility app. Will report back my findings.

[Aaron Harding]

Hi Sam & all,

Creating a disk image of the ftp mount didn't work so I am going to go back to using sshfs.

I am now able to SSH into my android device successfully however sshfs still isn't working. There is slight progress though, as it at least now asks me for the android device's password. This is now the Terminal:

As you can see, I can successfully ssh into my device:

Any help would be appreciated.

--

aaron

[Sam Moffatt]

diskutil isn't going to list the FTP mount point because it's not a disk or disk image - it's a network file system. You can create a disk image in Disk Utility of any folder. Without knowing what you're actually trying to achieve it's hard to give any guidance.

So let's take a step back: what are you trying to achieve?

Cheers,

Sam

Sam Moffatt
http://pasamio.id.au

[Aaron Harding]

Thank you for your patience.

What I am really trying to do recover some data from the internal storage of my HTC One Mini. I wiped my phone and didn't realise that some photos and videos were saved onto my internal storage, I thought they were all saved onto the sdcard. I was going to use PhotoRec (http://www.cgsecurity.org/wiki/PhotoRec) to recover the files, something I've used successfully in the past, and so I'm trying to find a way of mounting the internal storage of the device onto my MacBook so PhotoRec can scan the disk/image. Currently, PhotoRec does not discover my phone or it's internal storage when it is plugged in through USB because of the MTP that HTC uses with the USB connections. From this, the internal storage is not recognised as a drive i.e. the internal storage is not mounted or given a drive letter.

So I have come to sshfs to attempt to mount the internal storage. My next move would be installing a WebDAV server, although I'd rather use sshfs. Other options would be using dd to make a copy of the internal storage, once I have access to it, like in this tutorial: http://forum.xda-developers.com/showthread.php?t=2143188

Many thanks.

[Aaron Harding]

Small update, this morning I have been given a different error. Currently it is now "Operation not supported on socket":

Sophies-MacBook-Pro:~ sophiegunter$ sshfs -p 2222 -C ro...@192.168.1.14:/storage/emulated ~/sshfs

ro...@192.168.1.14's password:

Sophies-MacBook-Pro:~ sophiegunter$ mount_osxfusefs: failed to mount /Users/sophiegunter/sshfs@/dev/osxfuse0: Operation not supported on socket

--

aaron

[Aaron Harding]

Update:

I'm able to scp files from my MacBook to the Android device:

> Sophies-MacBook-Pro:~ sophiegunter$ ls
> Aaron Documents Movies Public sshfs
> Applications Downloads Music git
> Desktop Library Pictures hello-world.txt
> Sophies-MacBook-Pro:~ sophiegunter$ scp hello-world.txt ro...@192.168.1.14:/storage/sdcard0/
> SSHDroid
> Use 'root' as username
> Default password is 'admin'
> ro...@192.168.1.14's password:
> TRACE (8366): enter sign_key_free
> TRACE (8366): enter dsa_key_free
> TRACE (8366): leave dsa_key_free
> TRACE (8366): enter rsa_key_free
> TRACE (8366): leave rsa_key_free
> TRACE (8366): leave sign_key_free
> hello-world.txt                               100%   13     0.0KB/s   00:00
> Sophies-MacBook-Pro:~ sophiegunter$ ssh ro...@192.168.1.14
> SSHDroid
> Use 'root' as username
> Default password is 'admin'
> ro...@192.168.1.14's password:
> TRACE (8383): enter sign_key_free
> TRACE (8383): enter dsa_key_free
> TRACE (8383): leave dsa_key_free
> TRACE (8383): enter rsa_key_free
> TRACE (8383): leave rsa_key_free
> TRACE (8383): leave sign_key_free
> root@m4:/ # ls
> acct                     firmware_radio           ramdump
> cache                    fstab.m4                 root
> config                   init                     sbin
> cwkeys                   init.network.sh          sdcard
> d                        init.power.rc            seapp_contexts
> data                     init.rc                  sepolicy
> default.prop             init.target.rc           storage
> dev                      init.target.recovery.rc  sys
> devlog                   init.trace.rc            system
> etc                      init.usb.rc              tombstones
> file_contexts            mnt                      ueventd.rc
> firmware_dsps            proc                     ueventd.target.rc
> firmware_q6              property_contexts        vendor
> root@m4:/ # cd storage/sdcard0/
> root@m4:/storage/sdcard0 # ls
> Alarms               Movies               _nero_sync
> Albums               Music                amazonmp3
> Android              Notifications        ftpsvr
> AndroidHtcSync.apk   Pictures             hello-world.txt
> AndroidHtcSync1.apk  Podcasts             kindle
> AndroidHtcSync2.apk  Ringtones            nmdsdcid
> DCIM                 TWRP                 superuser.zip
> Download             Undelete
> root@m4:/storage/sdcard0 #

From above, hello-world.txt copied over successfully.

Unsure if this is related, however I have the most successful mount when the mount drive is within the "home" folder of the Mac user. See the difference between attempting the mount on the root of the Macbook, against folders within the user's directory:

Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ / -p 2222 -o auto_cache,volname=Android,reconnect
mount_osxfusefs: failed to mount /@/dev/osxfuse0: Operation not permitted
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ ~/ -p 2222 -o auto_cache,volname=Android,reconnect
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ mount_osxfusefs: failed to mount /Users/sophiegunter@/dev/osxfuse0: Operation not supported on socket
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ /Volumes -p 2222 -o auto_cache,volname=Android,reconnect
mount_osxfusefs: failed to mount /Volumes@/dev/osxfuse0: Operation not permitted
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ ~/sshfs -p 2222 -o auto_cache,volname=Android,reconnect

ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ mount_osxfusefs: failed to mount /Users/sophiegunter/sshfs@/dev/osxfuse0: Operation not supported on socket

Many thanks to anyone still with me. 

--

aaron

[Aaron Harding]

A verbose log using the last of the commands in the previous e-mail:

Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ ~/sshfs -p 2222 -odebug,sshfs_debug,loglevel=debug
SSHFS version 2.5
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-oPort=2222> <-ologlevel=debug> <-2> <ro...@192.168.1.14> <-s> <sftp>
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug1: Connecting to 192.168.1.14 [192.168.1.14] port 2222.
debug1: Connection established.
debug1: identity file /Users/sophiegunter/.ssh/id_rsa type -1
debug1: identity file /Users/sophiegunter/.ssh/id_rsa-cert type -1
debug1: identity file /Users/sophiegunter/.ssh/id_dsa type -1
debug1: identity file /Users/sophiegunter/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version dropbear_0.53.1
debug1: no match: dropbear_0.53.1
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: sending SSH2_MSG_KEXDH_INIT
debug1: expecting SSH2_MSG_KEXDH_REPLY
debug1: Server host key: RSA 86:c3:f3:ce:89:39:9c:4b:91:30:dd:05:18:af:67:6a
debug1: Host '[192.168.1.14]:2222' is known and matches the RSA host key.
debug1: Found key in /Users/sophiegunter/.ssh/known_hosts:3
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received

SSHDroid
Use 'root' as username
Default password is 'admin'

debug1: Authentications that can continue: password
debug1: Next authentication method: password
ro...@192.168.1.14's password:
debug1: Authentication succeeded (password).
Authenticated to 192.168.1.14 ([192.168.1.14]:2222).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LC_CTYPE = UTF-8
debug1: Sending subsystem: sftp
TRACE (9280): enter sign_key_free
TRACE (9280): enter dsa_key_free
TRACE (9280): leave dsa_key_free
TRACE (9280): enter rsa_key_free
TRACE (9280): leave rsa_key_free
TRACE (9280): leave sign_key_free
Server version: 3
Extension: posix-...@openssh.com <1>
Extension: sta...@openssh.com <2>
Extension: fsta...@openssh.com <2>
unique: 0, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.8
flags=0x00000000
max_readahead=0x00100000
remote_uid = 0
   INIT: 7.8
   flags=0x00000000
   max_readahead=0x00100000
   max_write=0x01000000
   unique: 0, error: 0 (Undefined error: 0), outsize: 40
unique: 0, opcode: STATFS (17), nodeid: 1, insize: 40
[00002] EXTENDED
  [00002]         STATUS       42bytes (7ms)
   unique: 0, error: -102 (Operation not supported on socket), outsize: 16

mount_osxfusefs: failed to mount /Users/sophiegunter/sshfs@/dev/osxfuse0: Operation not supported on socket

sent:               1 messages, 45 bytes
received:           1 messages, 42 bytes
rtt min/max/avg:    7ms/7ms/7ms
num connect:        1
Sophies-MacBook-Pro:~ sophiegunter$ debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
Transferred: sent 2488, received 1848 bytes, in 0.1 seconds
Bytes per second: sent 21318.7, received 15834.8
debug1: Exit status 0

--

aaron

[Benjamin Fleischer]

Am 11.08.2014 um 20:26 schrieb Aaron Harding <hiits...@googlemail.com>:

What I am really trying to do recover some data from the internal storage of my HTC One Mini. I wiped my phone and didn't realise that some photos and videos were saved onto my internal storage, I thought they were all saved onto the sdcard. I was going to use PhotoRec (http://www.cgsecurity.org/wiki/PhotoRec) to recover the files, something I've used successfully in the past, and so I'm trying to find a way of mounting the internal storage of the device onto my MacBook so PhotoRec can scan the disk/image.

What you are trying to accomplish is not possible over SSHFS. PhotoRec or any other recovery solution working in a similar fashion needs raw disk access. Recovery tools need to be able to scan the unused/freed space on a disk to recover deleted files that are still intact. SSHFS works on a higher level. I will not give you access to the unused space on your phone’s internal storage.

That said, there are special tools for recovering deleted files on Android phones. PhotoRec seems to be able to recover files from the internal storages of your Android Phone if you plug your phone into your computer and enable USB debugging (on your phone). See http://www.cgsecurity.org/wiki/PhotoRec_FAQ#How_to_enable_the_USB_mass_storage_mode for details. I hope this helps.

Unsure if this is related, however I have the most successful mount when the mount drive is within the "home" folder of the Mac user. See the difference between attempting the mount on the root of the Macbook, against folders within the user's directory:

Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ / -p 2222 -o auto_cache,volname=Android,reconnect
mount_osxfusefs: failed to mount /@/dev/osxfuse0: Operation not permitted
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ ~/ -p 2222 -o auto_cache,volname=Android,reconnect
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ mount_osxfusefs: failed to mount /Users/sophiegunter@/dev/osxfuse0: Operation not supported on socket
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ /Volumes -p 2222 -o auto_cache,volname=Android,reconnect
mount_osxfusefs: failed to mount /Volumes@/dev/osxfuse0: Operation not permitted
ro...@192.168.1.14's password:
Sophies-MacBook-Pro:~ sophiegunter$ sshfs ro...@192.168.1.14:/storage/ ~/sshfs -p 2222 -o auto_cache,volname=Android,reconnect

Your user needs to own the mount point otherwise mounting will fail. Usually you would create a new directory in /Volumes:

mkdir /Volumes/sshfs

sshfs ro...@192.168.1.14:/storage /Volumes/sshfs -p 2222 

Regards,

Benjamin 

[Aaron Harding]

Benjamin,

Many thanks for your reply. I was unaware that shhfs is unable to access the unused space on the device. If so, would it be true that using dd and ssh would also fail to copy over the empty space of the device? If I could make a raw image of the device in this way it would be possible to use PhotoRec to scan for lost files. Regardless, I'm still having trouble accessing the internal storage using this method:

ssh ro...@192.168.1.14 "dd if=/storage/emulated/0 -1 -" | dd of=~/android.img

Sophies-MacBook-Pro:~ sophiegunter$ ssh ro...@192.168.1.14 "dd if=/storage/emulated/0 -1 -" | dd of=~/android.img

SSHDroid
Use 'root' as username
Default password is 'admin'
ro...@192.168.1.14's password:

TRACE (15533): enter sign_key_free
TRACE (15533): enter dsa_key_free
TRACE (15533): leave dsa_key_free
TRACE (15533): enter rsa_key_free
TRACE (15533): leave rsa_key_free
TRACE (15533): leave sign_key_free
BusyBox v1.21.0 (2013-07-08 16:00:47 CEST) multi-call binary.
Usage: dd [if=FILE] [of=FILE] [ibs=N] [obs=N] [bs=N] [count=N] [skip=N]
[seek=N] [conv=notrunc|noerror|sync|fsync]
Copy a file with converting and formatting
if=FILE Read from FILE instead of stdin
of=FILE Write to FILE instead of stdout
bs=N Read and write N bytes at a time
ibs=N Read N bytes at a time
obs=N Write N bytes at a time
count=N Copy only N input blocks
skip=N Skip N input blocks
seek=N Skip N output blocks
conv=notrunc Don't truncate output file
conv=noerror Continue after read errors
conv=sync Pad blocks with zeros
conv=fsync Physically write data out before finishing
Numbers may be suffixed by c (x1), w (x2), b (x512), kD (x1000), k (x1024),
MD (x1000000), M (x1048576), GD (x1000000000) or G (x1073741824)
0+0 records in
0+0 records out
0 bytes transferred in 1.779195 secs (0 bytes/sec)
Sophies-MacBook-Pro:~ sophiegunter$

Back to sshfs: you were right that it was just permissions that caused the above errors. It only gave "Operation not permitted" when mounting to a directory that was owned by root and not sophiegunter.

That said, there are special tools for recovering deleted files on Android phones. PhotoRec seems to be able to recover files from the internal storages of your Android Phone if you plug your phone into your computer and enable USB debugging (on your phone). See http://www.cgsecurity.org/wiki/PhotoRec_FAQ#How_to_enable_the_USB_mass_storage_mode for details. I hope this helps.

I have tried this already and this doesn't work. Perhaps this Wiki is underdeveloped, but the Android internal storage (where my photos and videos were saved) does not mount and uses the MTP protocol. Media Transfer Protocol  "[allows] the contents of /sdcard to show on a compatible device (running a compatible OS) without unmounting it"1. These articles may be of help to understand MTP and Android:

http://teamw.in/DataMedia

Because the "internal sdcard" is not a true FAT file system, you can't mount it via USB storage. Well, that's not technically true, but the vast majority of people use Windows computers and Windows doesn't recognize ext4. If we were to allow you to mount the data partition via USB storage, Windows would claim that the device wasn't formatted and offer to format it for you, which, as you can imagine, would be a disaster. The whole ext4 setup is another reason that Android switched to using MTP for transferring files. Most of these devices don't have the necessary kernel configuration to even support USB storage mode, so it's not very easy to enable USB storage if we even wanted to try. Unfortunately at this time, MTP isn't available in recovery, so if you have no other option, you will have to use adb to push and pull files to/from your device.

http://mohammadag.xceleo.org/mounting-your-android-devices-internal-storage/

FAT/FAT32 filesystems lack permissions, so naturally, some other filesystem was used (again, probably ext3/4). To maintain compatibility/abstraction/whatever, /sdcard would now become a fake fuse mount that lacks permissions, the actual data however, is in /data/media (permissions still applied there).
The issue here is, you can’t unmount /data (and since /sdcard is /data/media, you can’t unmount /sdcard alone). Besides possible data loss, unmounting /data would probably cause your device to reboot (or soft reboot, I’m not really sure how it would react).
This meant Google had to change to a different USB protocol to get the device to show up on your PC, and this protocol was, MTP (Media Transfer Protocol). This would allow the contents of /sdcard to show on a compatible device (running a compatible OS) without unmounting it.

Following on, with my phone plugged into my laptop, with USB debugging enabled, you can see that PhotoRec does not discover the phone:

 

The internal storage of my phone is 16gb. Here is the output of "diskutil list" with the phone plugged in (to show that the internal storage does not mount):

So really, my quest is really: how can I make a raw image, including the empty space, of the internal storage of my Android phone, located at /storage/emulated/0, that I am enable to scan with recovery software.

Thanks again for all your time, if possible, I am open to new suggestions to how I could recover my data. The photos are of sentimental value to me, so all help is hugely appreciated.

Many thanks.

--

You received this message because you are subscribed to a topic in the Google Groups "OSXFUSE" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osxfuse-group/aJElhuRInR4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osxfuse-grou...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

aaron

[Sam Moffatt]

I would suggest contacting some of the Android community as they'd be better positioned to help you out. I must admit I'm not entirely familiar with how Android works under the hood though potentially if you have actual access to the raw device you could use cat and an SSH pipe to copy the raw device out though it'd obviously not be a consistent copy.

To echo earlier comments, SSHFS is likely not the solution to your problem in this case.

Cheers,

Sma

Sam Moffatt
http://pasamio.id.au

--

You received this message because you are subscribed to the Google Groups "OSXFUSE" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osxfuse-grou...@googlegroups.com.

[Aaron Harding]

Sam,

Thanks for your reply. I've signed up to the xda forums and will go from there. The good news is that I've managed to make a clone of my device's internal storage with dd and ssh, however PhotoRec wasn't able to recover any old photos. In fact it only found Android stock data on the device: tutorials on how to set up the device, default Android OS files, and so on. Perhaps I'm not running PhotoRec correctly or this laptop didn't mount the ndif image I received from dd correctly? Although I do know it copied over the empty / unused space since the final image matched my internal storage at 12.21GB in size (gzipped at ~347.6mb). So really, this isn't solved ~yet~.

If anyone is looking at this thread wondering how I did it, I had my device connected through USB, used adb shell to get into the device, used mount to locate where the phone's internal storage is:

~ # mount | grep /data
/dev/block/mmcblk0p35 on /data type ext4 (rw,seclabel,relatime,data=ordered)

Then I ran:

~ # dd if=/dev/block/mmcblk0p35 | gzip -1 - | ssh Aa...@192.168.1.10 dd of=/Users/Aaron/HTC\ One/dd/system.gz

Where 192.168.1.10 was the IP of my laptop on the same network. Then I waited for maybe 30 minutes to an hour for it to copy across and found the .gz file in ~/HTC\ One/dd/.

Thanks.

[Sam Moffatt]

I'd pull off all of the block devices on the phone and try each of them to see where the files actually were.

Cheers,

Sam

Sam Moffatt
http://pasamio.id.au