Cannot mount cifs filesystems [solved]

I have a usb drive plugged into my router that I have set up to mount via autofs. However, it is failing because for some reason my system suddenly cannot recognize cifs filesystems. cifs-utils is installed and the latest version
mount error: cifs filesystem not supported by the system
Last edited by tlmiller (2012-03-24 05:02:36)

BAH...
I could have SWORN I had rebooted already after doing an update, apparently I was mistaken.

Similar Messages

Shutdown hang if a mounted cifs filesystem is not responding

I sometimes mount a filesystem over CIFS (quite often a virtual machine). Sometimes I shutdown the virtual (or physical) machine forgetting to unmount the cifs folder. In this situation if I try to shutdown the linux machine, it hangs trying to unmount filesystem, forcing me to do an unclean shutdown (via hardware of the Ctr-Alt-Syst-O key). I suppose the same behaviour will happen if for whatever reason the CIFS server is not responding, so the ability to cleanly shutdfown the machine depends on the fact of having a reliable internet connection and the remote server responding properly. Is there not a possibility to force unmounting an unresponding cifs server? If yes, should it not be a good idea to include it in the archlinux shutdown script.
Last edited by olive (2012-06-08 15:53:50)

We already do this in the netfs rc.d script.

Mount CIFS filesystem permissions

Hi , i have a very strange issue. 3 servers with OEL 5.6 installed; 2 for OFM forms &report the last for OBIEE all 11g.
Need to mount 2 cifs file systems provided by a windows share in read-write.
The first 2 servers are mounting the shares but none except root can write on them (755), same shares mounted on OBIEE servers are mounted writable for all users (777). I do not remember to have done anything to obtain this. What can i serach for ?
Thanks.

Hi, first of all thanks for your answer i'll read your doc. But the situation in quite different, i have to mount the same file system from 3 dirrerent server, when i mount the share form server 1 and 2 i have the mount point and all descending folders owned by user root with 755 permission, when i mount the same share from server number 3 i have the mount point owned by root but with 777 permission and i have done nothing different between those servers.

Fresh btrfs root partition cannot boot/unknown filesystem [solved]

Just reformatted my SSD with 3 partitions.
1) EFI
2) /boot (ext4)
3) / (btrfs)
I copied over my systefrom tars, adjusted the new fstab to use btrfs, I rebuilt my kernel images, and rebuilt grub.cfg in the chroot. When I reboot, I get:
Welcome to grub!
error: unknown filesystem
Entering rescue mode...
grub rescue>
Per the wiki, there should be no special setup steps to boot to a btrfs root with grub. When did I f-up?
/etc/fstab
LABEL=arch64 / btrfs defaults,discard,noatime,ssd,compress=lzo 0 0
LABEL=boot /boot ext4 defaults,discard,noatime 0 2
Excuse the short post, typing in a phone.
Last edited by graysky (2013-07-29 01:24:47)

Yes, it is dropped to a GRUB rescue shell. I can boot if I manually type the following but WTF?! Why isn't grub doing this by itself?
grub rescue> set prefix=(hd0,2)/grub
grub rescue> insmod (hd0,2)/grub/x86_64-efi/linux.mod
grub rescue> set root=(hd0,2)
grub rescue> linux /vmlinuz-linux-ck root=/dev/sda3
grub rescue> initrd /initramfs-linux-ck.img
grub rescue> boot
Link to my autogenerated /boot/grub/grub.cfg
Last edited by graysky (2013-07-29 00:28:58)

Mounting ZFS filesystems: (1/10)cannot mount directory is not empt(10/10

Hi
in zone:
bash-3.00# reboot
[NOTICE: Zone rebooting]
SunOS Release 5.10 Version Generic_144488-17 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Hostname: dbspfox1
Reading ZFS config: done.
Mounting ZFS filesystems: (1/10)cannot mount '/zonedev/dbspfox1/biblio/P622/dev': directory is not empt(10/10 )
svc:/system/filesystem/local:default: WARNING: /usr/sbin/zfs mount -a failed: exit status 1
Nov 4 10:07:33 svc.startd[12427]: svc:/system/filesystem/local:default: Method "/lib/svc/method/fs-local" fa iled with exit status 95.
Nov 4 10:07:33 svc.startd[12427]: system/filesystem/local:default failed fatally: transitioned to maintenanc e (see 'svcs -xv' for details)
For sure the directory in not empty, but the others too are not empty.
bash-3.00# zfs list
NAME USED AVAIL REFER MOUNTPOINT
zonedev 236G 57.6G 23K /zonedev
zonedev/dbspfox1 236G 57.6G 1.06G /zonedev/dbspfox1
zonedev/dbspfox1/biblio 235G 57.6G 23K /zonedev/dbspfox1/biblio
zonedev/dbspfox1/biblio/P622 235G 57.6G 10.4G /zonedev/dbspfox1/biblio/P622
zonedev/dbspfox1/biblio/P622/31mars 81.3G 57.6G 47.3G /zonedev/dbspfox1/biblio/P622/31mars
zonedev/dbspfox1/biblio/P622/31mars/data 34.0G 57.6G 34.0G /zonedev/dbspfox1/biblio/P622/31mars/data
zonedev/dbspfox1/biblio/P622/dev 89.7G 57.6G 50.1G /zonedev/dbspfox1/biblio/P622/dev
zonedev/dbspfox1/biblio/P622/dev/data 39.6G 57.6G 39.6G /zonedev/dbspfox1/biblio/P622/dev/data
zonedev/dbspfox1/biblio/P622/preprod 53.3G 57.6G 12.9G /zonedev/dbspfox1/biblio/P622/preprod
zonedev/dbspfox1/biblio/P622/preprod/data 40.4G 57.6G 40.4G /zonedev/dbspfox1/biblio/P622/preprod/data
bash-3.00# svcs -xv
svc:/system/filesystem/local:default (local file system mounts)
State: maintenance since Fri Nov 04 10:07:33 2011
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://sun.com/msg/SMF-8000-KS
See: /var/svc/log/system-filesystem-local:default.log
Impact: 33 dependent services are not running:
svc:/system/webconsole:console
svc:/system/filesystem/autofs:default
svc:/system/system-log:default
svc:/milestone/multi-user:default
svc:/milestone/multi-user-server:default
svc:/application/autoreg:default
svc:/application/stosreg:default
svc:/application/graphical-login/cde-login:default
svc:/application/cde-printinfo:default
svc:/network/smtp:sendmail
svc:/application/management/seaport:default
svc:/application/management/snmpdx:default
svc:/application/management/dmi:default
svc:/application/management/sma:default
svc:/network/sendmail-client:default
svc:/network/ssh:default
svc:/system/sysidtool:net
svc:/network/rpc/bind:default
svc:/network/nfs/nlockmgr:default
svc:/network/nfs/client:default
svc:/network/nfs/status:default
svc:/network/nfs/cbd:default
svc:/network/nfs/mapid:default
svc:/network/inetd:default
svc:/system/sysidtool:system
svc:/system/postrun:default
svc:/system/filesystem/volfs:default
svc:/system/cron:default
svc:/application/font/fc-cache:default
svc:/system/boot-archive-update:default
svc:/network/shares/group:default
svc:/network/shares/group:zfs
svc:/system/sac:default
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Fri Nov 04 10:07:31 2011
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: man -M /usr/share/man -s 1M gssd
Impact: 17 dependent services are not running:
svc:/network/nfs/client:default
svc:/system/filesystem/autofs:default
svc:/system/webconsole:console
svc:/system/system-log:default
svc:/milestone/multi-user:default
svc:/milestone/multi-user-server:default
svc:/application/autoreg:default
svc:/application/stosreg:default
svc:/application/graphical-login/cde-login:default
svc:/application/cde-printinfo:default
svc:/network/smtp:sendmail
svc:/application/management/seaport:default
svc:/application/management/snmpdx:default
svc:/application/management/dmi:default
svc:/application/management/sma:default
svc:/network/sendmail-client:default
svc:/network/ssh:default
svc:/application/print/server:default (LP print server)
State: disabled since Fri Nov 04 10:07:31 2011
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 1 dependent service is not running:
svc:/application/print/ipp-listener:default
svc:/network/rpc/smserver:default (removable media management)
State: uninitialized since Fri Nov 04 10:07:32 2011
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: man -M /usr/share/man -s 1M rpc.smserverd
Impact: 1 dependent service is not running:
svc:/system/filesystem/volfs:default
svc:/network/rpc/rstat:default (kernel statistics server)
State: uninitialized since Fri Nov 04 10:07:31 2011
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: man -M /usr/share/man -s 1M rpc.rstatd
See: man -M /usr/share/man -s 1M rstatd
Impact: 1 dependent service is not running:
svc:/application/management/sma:default
bash-3.00# df -h
Filesystem size used avail capacity Mounted on
/ 59G 1.1G 58G 2% /
/dev 59G 1.1G 58G 2% /dev
/lib 261G 7.5G 253G 3% /lib
/platform 261G 7.5G 253G 3% /platform
/sbin 261G 7.5G 253G 3% /sbin
/usr 261G 7.5G 253G 3% /usr
proc 0K 0K 0K 0% /proc
ctfs 0K 0K 0K 0% /system/contract
mnttab 0K 0K 0K 0% /etc/mnttab
objfs 0K 0K 0K 0% /system/object
swap 2.1G 248K 2.1G 1% /etc/svc/volatile
fd 0K 0K 0K 0% /dev/fd
swap 2.1G 0K 2.1G 0% /tmp
swap 2.1G 16K 2.1G 1% /var/run
zonedev/dbspfox1/biblio
293G 23K 58G 1% /zonedev/dbspfox1/biblio
zonedev/dbspfox1/biblio/P622
293G 10G 58G 16% /zonedev/dbspfox1/biblio/P622
zonedev/dbspfox1/biblio/P622/31mars
293G 47G 58G 46% /zonedev/dbspfox1/biblio/P622/31mars
zonedev/dbspfox1/biblio/P622/31mars/data
293G 34G 58G 38% /zonedev/dbspfox1/biblio/P622/31mars/data
zonedev/dbspfox1/biblio/P622/dev/data
293G 40G 58G 41% /zonedev/dbspfox1/biblio/P622/dev/data
zonedev/dbspfox1/biblio/P622/preprod
293G 13G 58G 19% /zonedev/dbspfox1/biblio/P622/preprod
zonedev/dbspfox1/biblio/P622/preprod/data
293G 40G 58G 42% /zonedev/dbspfox1/biblio/P622/preprod/data
What i missed? what happen with zfs dev directory?
thank you
Walter

Hi
I finally found the problem.
ZFS naming restrictions:
names must begin with a letter
Walter

[SOLVED] Cannot "mount swap"

Hi
I cannot mount my swap partition! It stopped working some time ago (I don't know when exactly, I just saw this now).
When I try to mount it manually, I receive this error message: "Unknown filesystem type 'swap'".
Here is my fstab (I'm synchronized with the stable repo):
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /media/cdrom auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
UUID=1137358e-63f7-4d63-a98a-34d03ac5be0b /boot ext2 defaults,noatime 0 1
UUID=1ce2a0be-3cb7-45f1-aef9-83214ceb3d6a swap swap defaults
UUID=8e33d82d-b7bb-4ea4-aa58-99806a705328 /home reiserfs defaults,noatime 0 1
UUID=954fcd95-c5cc-452d-bd1c-efb8b76aeb22 / reiserfs defaults,noatime 0 1
Thanks in advance.
Last edited by Kknd (2008-08-04 15:19:00)

Wow even I accidentally disabled swap somehow and I tried everything, but it would not work ( http://bbs.archlinux.org/viewtopic.php?id=52252 ) . But, changing the line in fstab worked like a charm. Thanks!
(Maybe this is some sort of a bug? )

[SOLVED] cannot mount vfat usb

When I plug in my usb device an error is shown:
Error mounting /dev/sdc1 at /run/media/toni/BE40-9797: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=100,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sdc1" "/run/media/toni/BE40-9797"' exited with non-zero exit status 32: mount: unknown filesystem type 'vfat'
How can I solve this?
Last edited by toni (2013-12-11 20:59:11)

So, why did the reboot work ? (asked rhetorically)
Unlike some other famous operating systems,it is not likely that you machine had reached some unstable state requiring a restart to put it into a known state.
In your case, you probably updated the kernel. When this happens, the kernel modules on disk for the running kernel are replaced by those for the new kernel. After you did the upgrade, you plugged in your USB device. The kernel looked for its modules, but they were gone -- replaced by those for the new kernel. After rebooting, you are now running the kernel that matches the installed modules.

[SOLVED] mount: unknown filesystem type 'ext2'

I probably have the most complicated first-time arch setup that you'll ever hear a n00b post. XD
I just finished setting up an encrypted arch box with a usb boot drive (it contains the key-file), but when I go to boot, the system reports the following:
mount: unknown filesystem type 'ext2'
Of all the things to break! Ext2???!
This is for the default boot mode, when boot into the fallback initramfs mode, the arch box boots up fine (although it takes 2 whole minutes). I think that the issue is that I'm missing a module in my mkinitcpio.conf file.
/etc/fstab file:
UUID=1245ASDF / btrfs discard,autodefrag,compress=lzo,rw,relatime,ssd,space_cache 0 0
UUID=2245ASDF /boot ext2 rw,noatime 0 2
UUID=3245ASDF none swap defaults 0 0
/etc/mkinitcpio.conf file:
HOOKS="base btrfs udev autodetect modconf block encrypt lvm2 filesystems keyboard fsck"
/etc/default/grub file:
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda:enc cryptkey=/dev/sdb2:ext2:/keyfile crypto=sha512:twofish-xts-plain64:512:0:"
Last edited by a-jamesregan (2015-04-13 19:15:48)

Wow, there was literally a note about the exact issue I was having on the wiki...
https://wiki.archlinux.org/index.php/Mkinitcpio#MODULES
Note: If using reiser4, it must be added to the modules list. Additionally, if you will be needing any file system during the boot process that is not live when you run mkinitcpio — for example, if your LUKS encryption key file is on an ext2 file system but no ext2 file systems are mounted when you run mkinitcpio — that file system module must also be added to the MODULES list. See Dm-crypt/System configuration#cryptkey for more details.
PS: How do I mark an issue as solved?
Last edited by a-jamesregan (2015-04-13 10:28:20)

[SOLVED] mount.cifs failing to mount after update to 3.8.x

When trying to mount a CIFS share in Arch with kernel 3.8.3-2-ARCH, I get this:
mount error(22): Invalid argument
dmesg shows this:
FS-Cache: Loaded
FS-Cache: Netfs 'cifs' registered for caching
Key type cifs.spnego registered
Key type cifs.idmap registered
For clarity, I'm running this command (and have tried many others):
sudo mount.cifs //desktop/mydata /mnt/mydata -o user=me
Also, I am able to browse this share properly with smbclient, and I'm also able to mount it in distributions using older kernels.
I tested this on Ubuntu 13.04 as well, and the same problem happens there (also has kernel 3.8.x, so it seems likely that this is a kernel issue). From what I understand, portions of the mount.cifs client code were moved into the kernel recently, and the argument parser was overhauled at the same time (I found similar bug reports for Fedora, Gentoo, etc). Any ideas?
SOLVED:
The fix is to add "sec=ntlm" to the -o flag:
sudo mount.cifs //desktop/mydata /mnt/mydata -o user=me,sec=ntlm
Last edited by willroberts (2013-03-22 03:32:46)

While the "Permission denied" error seems completely different from an "Invalid argument" error, adding sec=ntlm to my -o flag fixed my issue as well.
For the record, I did search for my error message via Google, and got this:
https://www.google.com/search?q=site%3A … today&tbm=
No results for my "invalid argument" problem, but maybe that thread hasn't been indexed by Google yet. I'll try the built-in search next time. Most sites have notoriously awful built-in search, so I didn't even try.

Major Problem - Cannot Mount Filesystem

Hi,
I was experiencing a problem with my gnome configuration, so I asked a friend (who knows a LOT about Arch) suggested removing the .xxx files in my user account, as logging in (using gdm) on my root account worked.
After doing this, I restarted the computer but could no longer access anything. It hangs on 'Mounting local filesystems', I left it for 15mins but nothing happened. It doesn't produce any errors, just hangs.
I tried using the CD, but running arch boot=/dev/hda3 noinitrd rc (whatever the CD suggests using), which has worked for me in the past, doesn't, it still hangs on /dev/hda3.
What can I do? Formatting my computer is not an option, I have important documents on that drive! I tried running the cd, as if to install, but instead of running the /arch/setup, i made a temporary directory and tried mount /dev/hda3 /tmpDir but it did not work, just hung there.
fsck /dev/hda3 (using the setup cd) just returns the version immediately, it does not check anything.
What can I do? Are there tools available for me to check if there is a problem with the drive? Is it my configuration? What! I would not have though removing all .xxx folders would have made a difference. I do not remember what else I was doing, maybe modifying /etc/rc.conf, but I cannot see how anything on the drive is causing problems, as the drive cannot even be mounted.
Please help!!!
Btw, I am using Lilo, and Arch 0.7.2.

I knew that much hehe
I fixed it!
I loaded ubuntu in a live cd, ran:
sudo fsck /dev/hda3
fsck scanned hda3 and said i needed to run something else:
fsck.reiserfs --reconfigure-tree /dev/hda3 or something like that, i do that and it worked!
Thanks for your suggestion Mr. Green

Cannot mount multiple CIFS shares in /home

I have 2 users, Joe and Fred, who each have their own directory in /home. I also have a Netapp filer with a CIFS share called CorpData, which has subdirectories for Joe and Fred.
On the Arch Linux box, I have this for my fstab:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda1
UUID=d93def89-7611-43c8-a74f-e20bee64bd7e / ext4 rw,relatime 0 1
//10.1.1.141/CorpData/joe /home/joe cifs credentials=/etc/credentials,noserverino,_netdev,uid=joe,gid=users 0 0
//10.1.1.141/CorpData/fred /home/fred cifs credentials=/etc/credentials,noserverino,_netdev,uid=fred,gid=users 0 0
The problem is that at boot time, Joe's directory will be mounted, but Fred's will not. The reverse is true if I reverse the two entries in fstab.
If I issue the "mount -a" command after logging in, the second mount does get mounted, but also generates this error message:
mount error(16): Device or resource busy
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
I did refer to man mount, but since only the second mount is failing, I don't know what I could try differently. There are many more directories in CorpData, so I don't want to just mount that entire share on /home.

Looking into this further, it seems that the server is not able to accept the second request so quickly after the first. Is there any way to insert a delay or sleep command between the two mount entries in fstab?

Kinit mounts root filesystem as read only [HELP][solved]

hello
I've being messing around with my mkinitcpio trying to optimize my boot speed, i removed some of the hooks at the beginning i couldn't boot, but then now i can boot but the root filesystem mounts as read only, i tried everything my fstab looks fine, / exists with defaults i tried to mount it referencing by it's uuid or by it's name and i get the same results, it mounts the filesystem as root only all the time no mather what i do.
There is not logs since i started playing with mkinitcpio, or anything i searched everywhere in this forum and around the internet, and i can't find any solution that would work, i restored all the hooks and modules on mkinitcpio and the result it's still the same. i also changed the menu.lst in grub to vga=773 but that's about it.
Can anyone help with this please i can't seem to boot properly.
Regards
Last edited by ricardoduarte (2008-09-14 16:16:25)

Hello
Basically what happens it's that it loads all the uDev events then the loopback, it mounts the root read only, then when it checks filesystems it says
/dev/sda4: clean, 205184/481440 files, 1139604/1920356 blocks [fail]
************FILESYSTEM CHECK FAILED****************
* Please repair manually and reboot. Note that the root *
* file system is currently mounted read-only. To remount *
* it read-write: mount -n -o remount,rw / *
* When you exit the maintenance shell the will *
* reboot automatically. *
Now what bugs me its that i can do that mount -n -o remount,rw / with no problems and when i do
e2fsck -f /dev/sda4
it doesn't return any errors just says that 0.9 non continuous.
none of this makes sense to me!! thats why i though that the problem could be coming from mkinitcpio or something
any ideas
Thanks for your help, btw thanks for the quick reply
Regards
Last edited by ricardoduarte (2008-09-14 15:48:49)

[SOLVED] Cannot mount kindle

I have looked up at different posts on this topic but am still at a loss. I cannot mount a kindle
dmesg
[29881.943452] usb 2-1.5: new high-speed USB device number 75 using ehci-pci
[29882.049006] usb-storage 2-1.5:1.0: USB Mass Storage device detected
[29882.049194] scsi host18: usb-storage 2-1.5:1.0
[29883.051858] scsi 18:0:0:0: Direct-Access Kindle Internal Storage 0100 PQ: 0 ANSI: 2
[29883.061942] sd 18:0:0:0: [sdb] Attached SCSI removable disk
ls -l /dev/disk/by-id/
lrwxrwxrwx 1 root root 9 1. Jän 13:59 usb-Kindle_Internal_Storage_90231702303604DT-0:0 -> ../../sdb
But both mount and fdisk do not see it
fdisk -l /dev/sdb
fdisk: cannot open /dev/sdb: No medium found
Last edited by snovik (2015-01-01 16:41:25)

I have a Gen 2 connected right now, it most definitely uses UMS. I have a Gen 4 at home that also uses UMS. I've got to assume your Gen 3 would as well.
Does it go to the "USB Drive Mode" screen when you plug it in?
Edit: Do remember having an issue one time where it would not go into USB mode. Rebooting the Kindle fixed it. On my Gen 2, you would go to the Home screen, then hit menu and settings, hit menu again and there's an option for "Restart".
Last edited by Scimmia (2015-01-01 15:25:07)

Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

After modifying my time/date setup (setting the hardware clock to UTC, and using a custom timezone file) I started to get a [FAIL] message during boot (after the system had resynched to drive times to the system time), and shutdown.
@ boot time
Mounting local filesystem
Ext3-fs: barriers not enabled
kjournal starting. Commit interval 5 seconds
Ext3-fs (sda4): using internal journal
Ext3-fs (sda4): mounted filesystem with ordered data mode
[FAIL]
@ shutdown
Unmounting Filesystem [FAIL]
Nothing seems to be negatively affected, and the boot and shutdown processes continue without even pausing, and sda4 (my /home directory) certainly seems to by mounted (since I'm using it now).
I've run fsck at boot a couple times, but the drives keep coming back clean. I've tried using my old timezone setup, but the fail message persists. I've successfully unmounted and mounted sda4 as Root, trying to generate an error message of some kind, but all I get is a successfully unmounted, or mounted, drive. I've unmounted sda4 priod to shutdown as well, but the message persists.
The only place in the logs the [FAIL] message shows up is in /var/log/boot:
Mounting local filesystem [BUSY] [FAIL]
I'm at a loss. I would like to fix this, if only to be sure that it's not a symptom of a larger problem. At the very least, I'd like to know what is causing it.
Last edited by uxrs75 (2011-08-02 06:40:31)

You interpret correctly, Logicien. BIOS is set to UTC; HARDWARECLOCK="UTC". Time and date are a-ok.
I ran mkinitcpio -p kernel26, but the message persists. I also tried using the live cd, and mounting each of the drives in turn. All of them mounted successfully, with no error messages. To verify that it is sda4, I commented the sda4 line out in fstab, and rebooted the machine. I got:
Mounting Local Filesystems [FAIL]
but none of the Ext3-fs stuff, and the boot process continued successfully. I'm wondering if it's something else.
I'll try adding quiet to the kernel boot line later this evening and see what that brings about.
rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="PST"
KEYMAP="uk"
CONSOLEFONT="ter-116n.psf.gz"
#CONSOLEMAP="8859-1"
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="darkstar"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network !netfs crond alsa mpd)
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#none /proc/bus/usb usbfs auto,busgid=101,busmode=0775,devgid=101,devmode=0664 0 0
/dev/sr0 /media/sr0 auto ro,users,noauto,unhide 0 0
/dev/sr1 /media/sr1 auto ro,users,noauto,unhide 0 0
#/dev/sda1 /boot ext2 defaults 0 1
#/dev/sda2 swap swap defaults 0 0
#/dev/sda3 / ext3 defaults 0 1
#/dev/sda4 /home ext3 defaults 0 1
UUID=597bd99a-173b-4b23-947d-b8a50859bcdd /boot ext2 defaults 0 1
UUID=a51a3b55-7c5c-45bb-96eb-79cfd1a77f54 swap swap defaults 0 0
UUID=c6ecf0fe-d2c4-4743-b639-1550295b65c6 / ext3 defaults 0 1
UUID=ff7030b8-890a-4673-bd1c-f502ca5efb2b /home ext3 defaults 0 1
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdc1 /media/sdc1 auto noauto,owner,users 0 0
/dev/sdd1 /media/sdd1 auto noauto,owner,users 0 0
/dev/sde1 /media/sde1 auto noauto,owner,users 0 0
/dev/sdf1 /media/sdf1 auto noauto,owner,users 0 0
fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 208844 104422 83 Linux
/dev/sda2 208845 738989 265072+ 82 Linux swap / Solaris
/dev/sda3 738990 103153364 51207187+ 83 Linux
/dev/sda4 103153365 976768064 436807350 83 Linux
dumpe2fs -h /dev/sda1
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 597bd99a-173b-4b23-947d-b8a50859bcdd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype sparse_super
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 26208
Block count: 104420
Reserved block count: 5221
Free blocks: 84721
Free inodes: 26177
First block: 1
Block size: 1024
Fragment size: 1024
Reserved GDT blocks: 256
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2016
Inode blocks per group: 252
Filesystem created: Fri Apr 30 20:35:47 2010
Last mount time: Thu Aug 19 05:44:48 2010
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:23:24 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:24 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Default directory hash: half_md4
Directory Hash Seed: f5f22ff8-0cb1-4c30-a172-ead082f0ad8a
dumpe2fs -h /dev/sda3
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: c6ecf0fe-d2c4-4743-b639-1550295b65c6
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 3203072
Block count: 12801796
Reserved block count: 640089
Free blocks: 10487133
Free inodes: 3000642
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1020
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:35:51 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 07:22:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:22:14 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:22:14 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 262152
Default directory hash: half_md4
Directory Hash Seed: 08e3f2db-7bb4-41fc-9364-9a9f637951ff
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0007df4e
Journal start: 1
dumpe2fs -h /dev/sda4
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: ff7030b8-890a-4673-bd1c-f502ca5efb2b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 27303936
Block count: 109201837
Reserved block count: 5460091
Free blocks: 80860937
Free inodes: 27074933
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 997
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:36:07 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 25
Last checked: Mon Aug 1 07:23:25 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:25 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: e8dbb219-f7fe-4878-96b6-9137361ce1e2
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0011b560
Journal start: 1
Last edited by uxrs75 (2011-08-02 06:19:11)

Auto mount CIFS

I know that there are many post and solutions regarding how to auto mount CIFS shares.... but for some reason I cannot get any of them to work.
Here is what I know.
1) I used to use fstab. But not fstab requires root access to mount CIFS Shares
2) I have tried smbnetfs as described here: [url= https://wiki.archlinux.org/index.php/sa … c_mounting ] Samba . This results in extremely slow browsing to the network share and my credentials being denied. It is possible that I have not set up the ~/.smb/smbnetfs.auth file correctly. I also get the message:
WARNING: Unkown libsmbclient version: 4.1.6
SMBNetFS may not work as expected.
3) I have tried autofs Autofs with no luck.
4) I would be willing to mount from the terminal or a script file. However, when I mount with
sudo mount -t cifs //networkstorage/01_media /home/user/Network/01_media -o username=xxxx,password=xxxxx
I do not get rear/write privileges.
5) I know the CIFS share is set up correctly. Because if I brows to the share using thunar I can mount the location (with password and username) and get full read write access.
Can anyone suggest what is the best method for mounting. So that I can begin trying to fiqure out how to make it work for my system. Or if I could get some advice on what I am doing wrong in the terminal so that I could get R/W privileges.
Thanks!

You tried the fstab, but you didn't specify what youactually put in the fstab. There is an option which should enable you to mount the cifs filesystem as a normal user... it is the same option as any other filesystem. Have a look at the mount man page, as it has the information you are looking for.
I don't know what smbnetfs is or how one would use that, but from a quick gander at the package info it appears to be a fuse filesystem. You also didn't give even a hint of what happened when you tried autofs, or in what way you failed.
I think what you might really be looking for is an automounting daemon though. I'm not sure how they work with network shares that require a password, but you might want to have a look. This would be how the DEs handle automounting. In particular, there is udev{,2} that seems to be the most common solution.

Cannot mount cifs filesystems [solved]

Similar Messages

Maybe you are looking for