Airport Extreme USB Hard Drive

[evansj57]

I can browse the hard drive connected to my Airport Extreme wifi router from the X windows file manager after I changed the settings in the AE to allow guests to access the drive, so no password needed.

However, I can't seem to be able to mount the drive using the command line. The drive is an 2Tb HF+ formatted Iomega and is called Iomega HDD. Maybe the space is causing the problem.

The file manager lists the drive as

Code: Select all

smb://airportextreme/Iomega%20HDD

From the command line I tried:

Code: Select all

sudo mount.cifs //airportextreme/Iomega%20HDD /media/IomegaHDD -o username=any,password=XXXXXX

I have also tried replacing %20 with 040 or with a space enclosing the path in single quotation marks.

However, I always get:
"mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)"

If I just enter:

Code: Select all

 sudo mount.cifs //airportextreme/Iomega%20HDD/Share /media/IomegaHDD

It asks me for the password (?), which I enter, but I get the same error message.

Any suggestions?

[SirLagz]

Just a stab in the dark, but tried with just -o username=any ?
or -o username=any,password=

[evansj57]

Thanks for responding

When I tried with just -o username=any, the system asks me for a password, which I enter or enter nothing, and then it gives the same error

When I tried with -o username=any,password= it gives the error straight away:
mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

[evansj57]

OK, managed to get it working by using the Airport Extreme's IP address rather than its name. I had tried this before but it didn't seem to work.

So this worked:

Code: Select all

 sudo mount.cifs //192.168.1.4/'Iomega HDD' /media/IomegaHDD -o password=xxxxxx

Then amended fstab so that it mounts automatically. Had a few problems trying to get access, so added gid= and uid=

So I have entered this into fstab:

Code: Select all

//192.168.1.4/Iomega\040HDD /media/IomegaHDD cifs password=xxxxxx,_netdev,rw,uid=pi,gid=users,defaults 0 0

The \040 represents a space. You can't use %20 or quotation marks in fstab it seems. The _netdev'' indicates that the drive requires network to be available.

Success at last.

[mkr*]

I've been trying to mount my Airport Extreme Drive also in fstab and finally got it working.

I've been using evansj57 syntax, but it doesn't work for me. Always I got the message Permission Denied (13). Finally I got it working checking a Ubuntu Forum that says append 'sec=ntlm' and that was the deal.

So here is my full command as a mount and also as fstab for automount on boot. I'm hoping its helping someone maybe:)

manual mount (even if you use an drive password you have to enter any user, be creative):

Code: Select all

sudo mount.cifs //AiportIP/Share /media/Media -o username=any,password=xxxxxx,sec=ntlm

This mounted my Drive temporary.

Other way in /etc/fstab:

Code: Select all

//AirportIP/Share /media/TimeCapsule cifs username=any,password=xxxxx,sec=ntlm

With this Code the Airport drive mounts on boot and you can use it by Browsing your root file system in xbmc.

I'll hope I could help someone. This Thread also helped me:)

Sorry for my english;)

[anerni]

Hey guys

Thanks a lot for these valuable instructions. Initially, automatically mounting didn't work for me but now it's resolved. Since it cost me some time, I would like to share my experience, possibly helping others.

Manually mounting worked fine from beginning:

Code: Select all

sudo mount.cifs //10.0.1.1/WD_2GB /media/WD_2GB -o user='pi',pass='XXXXXX',sec=ntlm

Verifying:

Code: Select all

ls /media/WD_2GB
sudo mkdir /media/WD_2GB/testDir
ls /media/WD_2GB

Unmounting:

Code: Select all

sudo umount /media/WD_2GB 

Trying to port the same lines as above to fstab:

Code: Select all

sudo nano /etc/fstab
proc            /proc           proc    defaults          0       0
/dev/mmcblk0p1  /boot           vfat    defaults          0       2
/dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
//10.0.1.1/WD_2GB                               /media/WD_2GB   cifs    user='pi',pass='XXXXXX',sec=ntlm
UUID=2b8e5a88-ba38-440a-a1aa-49611b44e797       /mnt/usb_WD_1TB   ext4   nofail,defaults    0   0
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that

sudo mount -a
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

dmesg | tail
[ 2532.335862] Status code returned 0xc000006d NT_STATUS_LOGON_FAILURE
[ 2532.335909] CIFS VFS: Send error in SessSetup = -13
[ 2532.336356] CIFS VFS: cifs_mount failed w/return code = -13

After fiddeling around a bit, I learned that the '' work for command line, but not within config scripts. Omitting them resolved the issue:

Code: Select all

sudo nano /etc/fstab
proc            /proc           proc    defaults          0       0
/dev/mmcblk0p1  /boot           vfat    defaults          0       2
/dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
//10.0.1.1/WD_2GB                               /media/WD_2GB   cifs    user=pi,pass=XXXXXX,sec=ntlm
#//10.0.1.1/WD_2GB                               /media/WD_2GB   cifs    user='pi',pass='XXXXXX',sec=ntlm
UUID=2b8e5a88-ba38-440a-a1aa-49611b44e797       /mnt/usb_WD_1TB   ext4   nofail,defaults    0   0
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that

sudo umount /media/WD_2GB 
ls /media/WD_2GB/
sudo mount -a
ls /media/WD_2GB/

Probably any UNIX/LINUX intermediate knows about about these restrictions, but being relatively new (as perhaps lots of Raspbians) it was not too obvious to me.

Good luck!
anerni

PS: In case anybody knows a way how to replace the explicit IP address of Airport Extreme by its hostname, I would be grateful. Up to now, I only found threads stating that it didn't work with the hostname and they were marked resolved after using the IP. But since my network uses dynamic IP's, this is not the preferred solution (since I use several Airport Extreme in the same network, it might be possible that the IP address of one device might chance at a later time).