| View previous topic :: View next topic |
| Author |
Message |
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
 Posted: Tue, Apr 01 2008, 11:57pm Post subject: |
 |
|
| atuor wrote: | Hi,
The only workaround I found is, after booting, log in as root in a terminal
ans issue these commands
mount.cifs //192.168.x.x/Data /mnt/N -o user="user",pass="pass"
echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled
mount.cifs //192.168.x.x/Data /mnt/N -o user="user",pass="pass"
The first occurence of mount... has the effect, I think of loading something for Samba (module or so); before trying a mount, you can't change the value of /proc/fs/cifs/LinuxExtensionsEnabled' to 0 since this 'entry' doesn't exist. |
You may also try :
| Code: | # modprobe cifs
# echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled
# mount.cifs //192.168.x.x/Data /mnt/N -o user="user",pass="pass" |
Which should help automate the process, if you put the 2 first commands in some startup script (but it may not be good if you need also access to other servers for which that wouldn't fit).
Hope this helps, |
|
| Back to top |
|
 |
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Wed, Apr 02 2008, 12:14am Post subject: Troubleshooting commands |
|
|
In any case, here are some commands to try and troubleshoot SMB/CIFS connections. I hope they're useful.
The docs on the iomega support site suggest it :
| Code: | # findsmb
*=DMB
+=LMB
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
---------------------------------------------------------------------
192.168.0.15 STORAGE-3806 [WORKGROUP] [] [] |
... at least on my network, it's like that (you may not have the same output... it changed after I installed the most recent FW : now I have K104.W11)
| Code: | # smbclient -N -L '//STORAGE-3806'
Domain=[WORKGROUP] OS=[] Server=[]
Sharename Type Comment
--------- ---- -------
PUBLIC Disk
IPC$ IPC
Domain=[WORKGROUP] OS=[] Server=[]
Server Comment
--------- -------
Workgroup Master
--------- ------- |
... since I have a "PUBLIC" dir exported...
The -N is to disable password prompt for smbclient.
Update :
"Weak authentication" may be disabled for clients in your Distro... as it is on mine (Debian testing).
So if you try the following command (or alike) and get an error with authentication, then there may be something to try.
Symptom :
| Code: | # smbclient -W WORKGROUP '//STORAGE-3806/PUBLIC'
Password:
Domain=[WORKGROUP] OS=[] Server=[]
Server requested LANMAN password (share-level security) but 'client use lanman auth' is disabled
tree connect failed: SUCCESS - 0 |
Workaround :
So try copying /etc/samba/smb.conf (or similar, I'm on Debian) to for example /root/imega-cmb.conf, and add, in the section these two lines (or changing existing lines) :
| Code: |
client plaintext auth = yes
client lanman auth = yes
|
Now, | Code: | | smbclient -s iomega-smb.conf -W WORKGROUP '//STORAGE-3806/PUBLIC' |
will accept your password
Stay tuned for more tips 
Last edited by olberger on Sun, Apr 13 2008, 10:54am; edited 1 time in total |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Sun, Apr 06 2008, 11:59am Post subject: Also accessible with nautilus through smb:// |
|
|
I've struggled with trying to access the drive in Nautilus using smb:// URI.
It wouldn't work on my Debian system since "weak" authentication was disabled in the samba default configuration file.
I've found a way to access it anyway.
You first have to create a file named ~/.smb.smb.conf.append, and add the following inside it :
| Code: |
[global]
client plaintext auth = yes
client lanman auth = yes
|
Then you will be able to access it through URI like : smb://WORKGROUP:guest:xxxx@192.168.0.2/PUBLIC in Nautilus
(assuming you put your password instead of the xxxx) or smb://WORKGROUP:guest@192.168.0.2/PUBLIC, and answer the password prompt (which will be stored in the gnome keyring).
Hope this helps. |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Sun, Apr 13 2008, 10:56am Post subject: Linux 2.6.24 oops when attempting to mount as CIFS (Debian) |
|
|
FYI, I have experienced a kernel oops when trying to mount as CIFS on my Debian testing desktop with a 2.6.24 kernel.
See more details at : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463402 |
|
| Back to top |
|
|
CrazyIvanMN
Member
Joined: 28 Apr 2008
Posts: 1
|
| Posted: Tue, Apr 29 2008, 8:42am Post subject: |
|
|
I too got the exact same kernel oops with gentoo (using the gentoo-sources patchset on the 2.6.24 kernel) on with the k104.w11 firmware.
I downgraded the firmware to k102.w11, and now no problems.. There is clearly a problem with the k104.w11 firmware. Keep in mind downgrading the firmware resets the homestorage 500gb nas thingy to factory settings (you'll have to re-setup your ip and name settings.)
The link to the previous firmware is in this post: http://www.iomegasupportforums.com/phpbb2/viewtopic.php?p=27663#27663
What I find odd is the k104.w11 firmware does seem to work with the gnome-vfs (gnome 2.22.0) just you can't use the mount -t cifs command without the kernel freaking out as described in the previous post. This kernel problem then prevents you from shutting down (shutdown -r now), and you have to do a hard reset.
It implies to me that it's both a problem with the kernel and the firmware. (the kernel shouldn't freakout due to a bad samba implementationin the firmware, and the firmware shouldn't cause a kernel oops)
Anyway, now running the k102.w11 firmware and now I can use the mount -t cifs command without a kernel oops. So I'm happy now.
edit: I did discover I do still have to do :
echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled
before it will mount even with the downgraded firmware..
edit2: the mount option "nounix" has the same effect I believe as
echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled.
i.e. mount -t cifs -o nounix //server/volume /mnt/cifsmountpoint
found the option in /usr/src/linux/fs/cifs/README |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Wed, Apr 30 2008, 6:11am Post subject: |
|
|
| CrazyIvanMN wrote: |
It implies to me that it's both a problem with the kernel and the firmware. (the kernel shouldn't freakout due to a bad samba implementationin the firmware, and the firmware shouldn't cause a kernel oops)
|
The kernel problem was reported to http://bugzilla.kernel.org/show_bug.cgi?id=10451 , FYI... with not much effect 
Thanks for your report. I'll try and downgrade to see how it goes. |
|
| Back to top |
|
|
iomegageoff
Member
Joined: 30 Jan 2008
Posts: 8
|
| Posted: Sun, May 04 2008, 3:11pm Post subject: Re: linux problems with latest firmware |
|
|
| olberger wrote: |
Hmm... that link doesn't work |
Oh dear - guess the iomega folks removed it. I wonder why. I still have it somewhere. Let me know if you still need it. |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Fri, May 23 2008, 1:21pm Post subject: Another way to access the drive : smbnetfs (fuse based) |
|
|
Hi.
There is another way to access the drive, reported by "Daniel" at http://www.olivierberger.com/weblog/index.php/2008/04/06/101-using-iomega-home-network-disk-drive-500-gb-with-gnu-linux-debian-testing#c44902 :
| Quote: | Hi! I found a great workaround for this issue. I have the same harddisk and I mount it as user with smbnetfs which is using fuse as backend. Works just great!
Install just with
sudo apt-get smbnetfs
In my ~/.kde/Autostart I now have a script with just the line:
smbnetfs ~/fusesmb/
And when I want to access it, I go to URL ~/fusesmb/STORAGE-4699 (in my case)
Hope that is a good workaround for you, too! |
... and it seems to work.
Thanks Daniel, and hope this helps. |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Sat, May 24 2008, 9:40am Post subject: Re: Another way to access the drive : smbnetfs (fuse based) |
|
|
| olberger wrote: | ... with just the line:
smbnetfs ~/fusesmb/
And when I want to access it, I go to URL ~/fusesmb/STORAGE-4699 (in my case)... |
Note that to use that, you also need to create a "~/.smb/smb.conf.append" file containing :
| Code: | [global]
client plaintext auth = yes
client lanman auth = yes |
Otherwise, authentication by libsmb won't be possible |
|
| Back to top |
|
|
olberger
Member
Joined: 01 Apr 2008
Posts: 13
|
| Posted: Thu, Mar 19 2009, 5:42am Post subject: |
|
|
| olberger wrote: | | CrazyIvanMN wrote: |
It implies to me that it's both a problem with the kernel and the firmware. (the kernel shouldn't freakout due to a bad samba implementationin the firmware, and the firmware shouldn't cause a kernel oops)
|
The kernel problem was reported to http://bugzilla.kernel.org/show_bug.cgi?id=10451 , FYI... with not much effect
Thanks for your report. I'll try and downgrade to see how it goes. |
Note that the bug is fixed by a patch, so that it no longer crashes... still it doesn't work fully when trying to write on the drive, from the tests I've been able to conduct |
|
| Back to top |
|
|
|
Forum FAQs
Search Posts
Member Directory
Usergroups
Create a Username
Edit My Profile
Log in
