Systemd transition vfat mount error

i transitioned over to systemd on one of my laptops, and now im running into a problem that i cant seem to solve
on /dev/sda6 its a shared(dual boot) home drive on a vfat partition (ntfs), right after converting to systemd, it fails to mount.
[FAILED] to mount /home
[DEPEND] dependence failed for local file systems.
i ahve no way of copy and pasting fstab but ill type it out here
tempfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 /boot ext2 defaults 0 2
/dev/sda4 / ext3 defaults 0 1
/dev/sda5 swap swap defaults 0 0
/dev/sda6 /home vfat defaults 0 2
#note i tried pass 0 also on /dev/sda6
i have installed dosfstools but not sure how to use it
the first error in journalctl -xb regarding this issue is as follows
Mounted /boot.
boot.mount has finished starting up
the start-up result is done
mount: wrong fs type, bad option, bad superblock on /dev/sda6
missing codepage or helper program or other error
home.mount mount process exited, code=exited status-32
FAT-fs (sda6): bogus number of reserved sectors
FAT-fs (sda6): cant find valid FAT filesystem
Failed to mount /home
Unit home.mount has failed
The result is failed.
Dependency failed for Local File Systems
I think this "bogus number of reserved sectors" has been there since initial installation about 6 months ago, but since upgrading to systemd, its becoming a fatal problem, whereas before when in initscripts it wasnt an issue. 
I tried runing parted, but couldnt see any problems, and didnt know where to go from there.  It is an MBR type table.
I am able to run my network connection from maintenance mode, and install what i need to.  I was able to get past the maintenance mode and get the system to boot up by running
mount -t ntfs-3g /dev/sda6 /home
but when i do that i get an empty home drive
The funny thing is when i am in  maintenance mode, i can access the home drive no problems.  So it is mounted.
Last edited by wolfdogg (2013-02-03 21:42:44)

this was great info, thanks for that.  it really looked promising to me, and it led me to trying things i have not tried before, and taught me a few new things. However, no matter what i try i cant get the users home directories mounted properly on ntfs.  Its probably over the top for me to reach into the AUR and and add another program to solve a problem that's getting over complicating to solve what deceivingly seems to be a rather simple issue.  so i tried your examples of fstab every other way without bind, i even installed what i thought was bindfs, under the name 'bind', all i got to say for that is oops, it installed (Berkeley Internet Name Domain).  As far as the taboo of mounting users homes to ntfs, i am able to reconfigure my system at anytime after i achieve this, but for right now i would rather go through the pains of mounting the user directories residing on sda6 than i would to reformat the drive to another file system type that wont be accessible to windows.  this is mainly for a learning experience, to try it on for size, and to realize for myself why i would or would not want this in the next build. 
in the mean time,  what i tried hasn't work, i have only been able to use the ntfs file system as root, and not able to alter the permissions at that.  looking at my fstab below you can see what i am trying to accomplish, the 'miker' entry has dmask and fmask entries from a root test just to see what it will yield, so ignore that one, but the last 2 entries of users are the way i would like it to be.  can i accomplish this using fstab without having to install bindfs through the AUR?
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda2 /boot ext2 defaults 0 2
/dev/sda4 / ext3 defaults 0 1
/dev/sda5 swap swap defaults 0 0
/dev/cdrom /mnt/dvd iso9660 ro,user,noauto,unhide,iocharset=utf8 0 0
#/dev/sda6 /home ntfs-3g agid=users,dmask=022,fmask=133 0 0
/dev/sda6 /mnt/ntfs ntfs-3g auto,dmask=022,fmask=133 0 0
#/mnt/ntfs/miker /home/miker ntfs-3g auto,uid,1002,gid=users,dmask=022,fmask=133 0 0
/mnt/ntfs/liaml /home/liaml ntfs-3g auto,uid=1002,gid=users,umask=027 0 0
/mnt/ntfs/ellal /home/ellal ntfs-3g auto,uid=1001,gid=users,umask=027 0 0
as you can see, the fstab wont work because /mnt/ntfs isnt a block device, but its just where i gave up and am asking for more ideas...
Last edited by wolfdogg (2013-02-07 06:40:21)

Similar Messages

  • Cifs mount error(56): Invalid request code

    I am trying to cifs mount my Arch server (called server) to an SMB disk on a router (experia). This keeps throwing me error messages. Invalid request code.
    So I decided to test this on my Arch client (called kastje). Same issue:
    [david@kastje ~]$ sudo mount -v -t cifs //experia/testshare /mnt/temp -o username=testuser,password=testpass
    mount.cifs kernel mount options: ip=192.168.178.1,unc=\\experia\testshare,user=testuser,pass=********
    mount error(56): Invalid request code
    Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    However, mounting through gvfs-smb (PCmanFM) works fine, so it seems that both my client and the router are configured correctly but I am failing at using mount.cifs. But I just cannot find out what. Searching for the mount error(56) turns up some result but none are really helpful, as they do not solve the issue .
    I hope someone can point me in the right direction.

    From my fstab:
    //Server/Shares /mnt/Shares cifs guest,uid=1000,x-systemd.automount,iocharset=utf8,file_mode=0777,dir_mode=0777 0 0
    //Server/Homes /home/pat/Server cifs credentials=/home/pat/.smbcredentials,x-systemd.automount,iocharset=utf8,sec=ntlm 0 0
    Does your router have a smb.conf? Or, I should be asking, is a samba server running on your router? You may find that an NFS share might work better than samba, especially if you don't have a setup like mine.

  • Mount error when installing xcode 3 and iOS 4

    Hi,
    I ran into mount error when installing xcode 3.2.6 and iOS 4.3 downloaded from https://developer.apple.com/devcenter/download.action?path=/Developer_Tools/xcod e_3.2.6_and_ios_sdk_4.3__final/xcode_3.2.6_and_ios_sdk_4.3.dmg.
    I work on Mac mini with Mac OS X 10.6.
    Could anyone help? Thanks!
    Regards,
    Emily

    Hi Ken,
    Thanks for your advice! I would try to clean up for more free space. I just downloaded one dmg from another website linking to apple. I could successfully install that one, but very often the content in gdb window is empty. Even if the gdb works for some time initially, after loading some specific project, the gdb doesn't provide info any longer :-( Any idea?
    It might be the best season in Shenzhen now. It is sunny, but not hot, with temperature from 25 degree centigrade to 30.
    Regards,
    Emily

  • Mount error when mounting Windows Server share

    Trying to mount a share on a Windows Server I have in my home.
    When I use:   
    smbclient -L SERVERNAME -U administrator
    and I enter the password after the prompt
    It returns a list of all the shares in the server like so:
    Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
    Sharename Type Comment
    SHARE1 Disk Shared folder
    SHARE2 Disk Shared folder
    SHARE3 Disk Shared folder
    Domain=[SERVERNAME] OS=[Windows Server 2003 3790 Service Pack 2] Server=[Windows Server 2003 5.2]
    Server Comment
    Workgroup Master
    but when I try to mount of the shares with
    # mount -t cifs //SERVERNAME/SHARE1 /mnt/mountpoint -o user=administrator,password=password
    it returns an error
    mount error: could not resolve address for SERVERNAME: Unknown error
    Am I doing something wrong?
    Thanks,

    the SERVERNAME in these commands is a netbiosname and can differ from the  hostname.
    Smbclient seems to use it's own method to resolve netbiosnames, possibly the mount command uses a different method.
    Try the mount command with the ip-address of the server instead of SERVERNAME to verify mounting the share works.
    If the share can be mounted by //ip-address/SHARE1 , you may need additional options for the mount command to make netbios name resolution work correctly.
    check man mount.cifs .
    edit : typo's
    Last edited by Lone_Wolf (2013-08-10 12:40:47)

  • ASM Disk Mount Error

    Hi,
    I am consistently getting the following error since yesterday while mounting the ASM disk.
    1. I created the ASM disks successfully and created the appropriate ASM DiskGroups using asmca utility.
    2. I was able to see the diskgroups as mounted from asmcmd tool.
    3. All of a sudden, all the diskgroups were dismounted yesterday and I see the following error in the alert logs for all the
    diskgroups.
    4. This is using ASM11g
    As I exhausted all my avenues to fix, I have turned to you for further assistance. Please do the needful.
    SQL> /* ASMCMD */ALTER DISKGROUP DataVSPSI MOUNT
    NOTE: cache registered group DATAVSPSI number=3 incarn=0x7934bf5d
    NOTE: cache began mount (first) of group DATAVSPSI number=3 incarn=0x7934bf5d
    NOTE: Assigning number (3,0) to disk (ORCL:D01_VSP_SI)
    Thu Dec 27 17:38:29 2012
    NOTE: start heartbeating (grp 3)
    kfdp_query(DATAVSPSI): 11
    kfdp_queryBg(): 11
    NOTE: cache opening disk 0 of grp 3: D01_VSP_SI label:D01_VSP_SI
    NOTE: F1X0 found on disk 0 au 2 fcn 0.0
    NOTE: cache mounting (first) external redundancy group 3/0x7934BF5D (DATAVSPSI)
    NOTE: starting recovery of thread=1 ckpt=2.1 group=3 (DATAVSPSI)
    WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
    AU:4 disk_offset(bytes):4333568 io_size:122880 operation:Read type:asynchronous
    result:I/O error process_id:32162
    WARNING: IO Failed. group:3 disk(number.incarnation):0.0xeae44fae disk_path:ORCL:D01_VSP_SI
    AU:4 disk_offset(bytes):4202496 io_size:131072 operation:Read type:asynchronous
    result:I/O error process_id:32162
    ORA-15080: synchronous I/O operation to a disk failed
    ERROR: ASM recovery failed to read ACD
    NOTE: cache initiating offline of disk 0 group DATAVSPSI
    NOTE: process 32162 initiating offline of disk 0.3940831150 (D01_VSP_SI) with mask 0x7e in group 3
    WARNING: Disk D01_VSP_SI in mode 0x7f is now being taken offline
    NOTE: initiating PST update: grp = 3, dsk = 0/0xeae44fae, mode = 0x15
    kfdp_updateDsk(): 12
    kfdp_updateDskBg(): 12
    ERROR: too many offline disks in PST (grp 3)
    WARNING: Disk D01_VSP_SI in mode 0x7f offline aborted
    Thu Dec 27 17:38:29 2012
    NOTE: halting all I/Os to diskgroup DATAVSPSI
    NOTE: crash recovery signalled OER-15130
    ERROR: ORA-15130 signalled during mount of diskgroup DATAVSPSI
    NOTE: cache dismounting (clean) group 3/0x7934BF5D (DATAVSPSI)
    NOTE: lgwr not being msg'd to dismount
    NOTE: cache dismounted group 3/0x7934BF5D (DATAVSPSI)
    Also, I think the lower level disk is fine as I am able to write to the disk as follows :
    [oracle@rmanqa01 trace]$ dd of=/dev/sdp1
    Test Test
    0+1 records in
    0+1 records out
    10 bytes (10 B) copied, 4.97435 seconds, 0.0 kB/s
    [oracle@rmanqa01 trace]$ id
    uid=500(oracle) gid=500(oinstall) groups=6(disk),500(oinstall),501(dba),502(oper),503(asmadmin),504(asmdba),505(asmoper),506(horcm)
    [oracle@rmanqa01 trace]$ ls -l /dev/sdp1
    brw-rw---- 1 root disk 8, 241 Dec 28 11:59 /dev/sdp1
    [oracle@rmanqa01 trace]$
    The oracleasm also lists the disk D01_VSP_SI as follows :
    [root@rmanqa01 log]# /etc/init.d/oracleasm listdisks
    A01_VSP_SI
    ADSK01
    ARCH_AMS_SI
    D01_VSP_SI
    DATA_AMS_SI
    DDSK01
    DEMO_ARCH
    DEMO_DATA
    L01_VSP_SI
    RDSK01
    REDO_AMS_SI
    You have new mail in /var/spool/mail/root
    [root@rmanqa01 log]# /etc/init.d/oracleasm querydisk D01_VSP_SI
    Disk "D01_VSP_SI" is a valid ASM disk
    [root@rmanqa01 log]#
    kfed tool was giving proper data till yesterday.
    Today, I am getting the following :
    ./kfed read /dev/oracleasm/disks/D01_VSP_SI
    kfbh.endian: 84 ; 0x000: 0x54
    kfbh.hard: 101 ; 0x001: 0x65
    kfbh.type: 115 ; 0x002: *** Unknown Enum ***
    kfbh.datfmt: 116 ; 0x003: 0x74
    kfbh.block.blk: 1936020512 ; 0x004: T=0 NUMB=0x73655420
    kfbh.block.obj: 2147486324 ; 0x008: TYPE=0x8 NUMB=0xa74
    kfbh.check: 2886846267 ; 0x00c: 0xac11c73b
    kfbh.fcn.base: 0 ; 0x010: 0x00000000
    kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
    kfbh.spare1: 0 ; 0x018: 0x00000000
    kfbh.spare2: 0 ; 0x01c: 0x00000000
    ERROR!!!, failed to get the oracore error message
    [oracle@rmanqa01 bin]$
    Please help.
    Thanks
    V V
    Edited by: user13479556 on Dec 28, 2012 12:00 PM

    Thanks Berx for pointing that out.
    I deleted the ASM disks and the diskgroups and re-created a fresh and was able to start the ASM instance and mount the DGs.
    Now the mount is persistent, but the dbca fails with the following error in the alert log. Under what situations can this error be seen ?
    NOTE: Loaded library: System
    SUCCESS: diskgroup DATAAMSSI was mounted
    SUCCESS: diskgroup ARCHAMSSI was mounted
    ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.DATAAMSSI.dg*ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.ARCHAMSSI.dg*Mon Dec 31 20:25:25 2012
    SUCCESS: diskgroup LOGAMSSI was mounted
    Mon Dec 31 20:25:25 2012
    ERROR: failed to establish dependency between database R3AMSSI and diskgroup resource ora.LOGAMSSI.dg
    Mon Dec 31 20:25:25 2012
    Successful mount of redo thread 1, with mount id 784925673
    Completed: Create controlfile reuse set database "R3AMSSI"
    MAXINSTANCES 8
    MAXLOGHISTORY 1
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 100
    Datafile
    '+DATAAMSSI/R3AMSSI/system01.dbf',
    '+DATAAMSSI/R3AMSSI/sysaux01.dbf',
    '+DATAAMSSI/R3AMSSI/undotbs01.dbf',
    '+DATAAMSSI/R3AMSSI/users01.dbf'
    LOGFILE GROUP 1 ('+LOGAMSSI/R3AMSSI/redo01.log') SIZE 51200K,
    GROUP 2 ('+LOGAMSSI/R3AMSSI/redo02.log') SIZE 51200K,
    GROUP 3 ('+LOGAMSSI/R3AMSSI/redo03.log') SIZE 51200K RESETLOGS
    Stopping background process MMNL
    Stopping background process MMON
    Starting background process MMON
    Starting background process MMNL
    Mon Dec 31 20:25:28 2012
    MMON started with pid=17, OS id=10452
    ALTER SYSTEM enable restricted session;
    Mon Dec 31 20:25:28 2012
    MMNL started with pid=18, OS id=10454
    alter database "R3AMSSI" open resetlogs
    RESETLOGS after incomplete recovery UNTIL CHANGE 945183
    Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
    ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
    ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
    Errors in file /u01/app/oracle/diag/rdbms/r3amssi/R3AMSSI/trace/R3AMSSI_ora_10434.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '+LOGAMSSI/r3amssi/redo01.log'
    ORA-17503: ksfdopn:2 Failed to open file +LOGAMSSI/r3amssi/redo01.log
    ORA-15173: entry 'redo01.log' does not exist in directory 'r3amssi'
    Mon Dec 31 20:25:29 2012
    Checker run found 5 new persistent data failures
    Mon Dec 31 20:27:07 2012
    I can verify from asmcmd that the redologs mentioned above as missing is very much present in '+LOGAMSSI/R3AMSSI'
    Thanks
    V V

  • Mount error: ...not superuser and mount.cifs not installed SUID

    I'm trying to automount Samba shares but get this everytime I try to mount the partition:
    mount error: permission denied or not superuser and mount.cifs not installed SUID
    I have this entry in the fstab:
    //192.168.2.1/Capsule /media/capsule cifs auto,noserverino,username=xxx,password=xxx,workgroup=WORKGROUP,iocharset=utf8,file_mode=0777,dir_mode=0777,suid,users 0 0
    I tried different options (suid,users or without them) same results.
    I also tried to chown like this:
    chmod u+s mount.cifs
    But still no luck
    Need help please.

    It seems that mount.cifs will only let you mount at directory that you are the owner of.  I think this may be changeable with the UID option but I have not figured it out.

  • Mount Error Message

    Hello, when I plug in my USB stick, thunar-volman throws up this error:
    A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
    I haven't changed any of the files in /etc/dbus-1/
    I belong to the following groups:
    disk wheel games dbus hal network video audio optical storage scanner users shutdown
    Much appreciated, thanks.
    Last edited by Manifold (2007-01-28 21:54:01)

    i also tried this how to
    the cd work good but not the usbstick
    fdisk -l
    Disk /dev/sda: 120.0 GB, 120033041920 bytes
    255 heads, 63 sectors/track, 14593 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 2550 20482843+ 7 HPFS/NTFS
    /dev/sda2 14533 14593 489982+ 82 Linux swap / Solaris
    /dev/sda3 2551 13579 88590442+ f W95 Ext'd (LBA)
    /dev/sda4 14047 14532 3903795 83 Linux
    /dev/sda5 2551 13324 86542123+ 7 HPFS/NTFS
    /dev/sda6 13325 13579 2048256 b W95 FAT32
    Partition table entries are not in disk order
    Disk /dev/sdb: 254 MB, 254803968 bytes
    16 heads, 32 sectors/track, 972 cylinders
    Units = cylinders of 512 * 512 = 262144 bytes
    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 972 248816+ 6 FAT16
    Last edited by dids22 (2007-02-21 23:54:20)

  • SMB mount error

    I am trying to mount a Windows share either through Finder or from the command line. Finder gives me an error message:
    Sorry the operation cound not be completed because an unexpected error occurred (Error code -50).
    Finder connects to the server, asks for my password, but then give the error message. From the command line trying to mount using mount_smbfs, I get the password prompt and then a mount error message:
    syserr = Invalid argument
    I checked dmesg and the following line appeared after trying to mount either way:
    mount version mismatch: kernel=103200, mount=103600
    Anyone know what this means and how to fix it? I am running a PB 1.5 with OSX 10.4.6 with all the updates applied.

    try using
    mount smb: //ip.addr.of.svr/sharename
    If you are trying to connect to an Active Directory share or a windows network that has security set to LSA 3 or higher, you will not be able to connect without 3rd party software, as OS X does not supprt LSA 3 or higher.

  • Disk image could not be mounted - error

    Ok, I've been using TC (Time Capsule) for a week now, and it was working great. Then in the middle of the week I decided to change the password for TC. Now when I reboot my iMac, TM (Time Machine) will not back up and it gives me a failed - "the backup disk image could not be mounted" error. Then if I go to the AirPort Utility and reboot TC, all of the sudden TM works. Couple of days go by and when I reboot the iMac again, I have to do the whole process again of rebooting TC to get TM to work. Has anyone encountered this issue? I think I explained it well...

    This happened to me too.
    I called Apple (they'll talk to you for 90 days after you buy your Time Capsule and solve all your problems.)
    The solution was to rename the Time Capsule. Here's how:
    Open Time Capsule in System Preferences, click on Change Disk, and choose None from the list.
    Open Airport Utility (choose Go from the Finder Menu, choose Utilities from the list, then Airport Utility), highlight your Time Capsule when its picture appears in the left side bar. Click Manual Setup in the main window, then the Disk icon on the top. Highlight the lower of the two names Time-Capsule Disk and change it to something short and one word, like Disk. Click Update, then close Airport Utility after your Time Capsule restarts.
    Go back to Time Capsule Preferences and click on the Choose Disk button in the center of the main part of the window, then choose your newly-named Time Capsule (If you see more than one Time Capsule name there, restart your computer first).
    This solved it for me. The guy on the phone said that in the tech help people's experience the Time Machine program doesn't like long names or ones with "higher" ascii characters in them.
    Good luck.
    jmb

  • Live Upgrade grub and mount errors on 11/06

    Hi,
    Whilst creating an initial BE on 10 11/06 I got some mount errors ...
    invalid option 'r'
    usage: mount [-o opts] <path>
    ..which subsequently left my BEs a bit messed up. I could lustatus just fine, but couldn't remove the copy. I discovered there was no ICF.2 file, so created it with what should have been the correct information. Now I get a different message:
    ERROR: No suitable candidate slice for GRUB menu on boot disk:
    I'm using SVM, and the second BE is basically a detached mirror.
    What I'd like to do now is just clear the whole lot up and start again.
    So, is there a manual way of clearing up LU? Like, removing lutab and the information under /etc/lu, for example?
    BTW, I applied 10_x86_Recommended, and then removed and installed SUNWluu, lur, and luzone from snv_66 - which appears to have removed the 'mount' errors.
    Any help gratefully received!
    Thanks,
    --Mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    Hi,
    Whilst creating an initial BE on 10 11/06 I got some mount errors ...
    invalid option 'r'
    usage: mount [-o opts] <path>
    ..which subsequently left my BEs a bit messed up. I could lustatus just fine, but couldn't remove the copy. I discovered there was no ICF.2 file, so created it with what should have been the correct information. Now I get a different message:
    ERROR: No suitable candidate slice for GRUB menu on boot disk:
    I'm using SVM, and the second BE is basically a detached mirror.
    What I'd like to do now is just clear the whole lot up and start again.
    So, is there a manual way of clearing up LU? Like, removing lutab and the information under /etc/lu, for example?
    BTW, I applied 10_x86_Recommended, and then removed and installed SUNWluu, lur, and luzone from snv_66 - which appears to have removed the 'mount' errors.
    Any help gratefully received!
    Thanks,
    --Mark                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • "Volume Fails To Mount" Error

    I have Leopard 10.5.8 and am trying to connect to a Windows Vista share via SMB. The two systems can communicate and authenticate without issue. After using Finder's Go To Server and connecting via SMB, I am prompted for a username and password. Once given, the Vista machine authenticates and presents me with a list of shared folders to chose from. At this point, when I select a folder, Leopard immediately returns with the "Volume Fails To Mount" error and I am returned to the list of shares after closing the dialog box. Thinking it might be an issue with Finder, I found and downloaded an application, AutomountMaker. Its results were the same. I can connect from the Vista machine to Leopard with no issues whatsoever, so I know the machines are working together. I have been unable to find any explanation for this error message nor how to correct the issue. I would appreciate it if anyone can offer some ideas.
    As a bit of additional information, I have another machine that is running Windows 7 and I was able to connect to a share on its drive from Leopard without a problem.

    This page may help http://www.ifelix.co.uk/tech/3022.html

  • QFS problem: Error: mount_samfs: mount() error: Device busy

    Hi:
    I setup the QFS on my two nodes sun cluster 3.2 environment. Everything works fine. But when i reboot both nodes, the QFS system cann't be mounted. it shows following error:
    Error: mount_samfs: mount() error: Device busy
    Following is my setup procedure:
    *2. Create the mcf file (on both nodes)*
    #cd /etc/opt/SUNWsamfs/
    #vi mcf
    # Equipment Eq Eq Family Device Additional
    # Identifier Ord Type Set State Parameters
    archive 2 ma archive on shared
    /dev/did/dsk/d5s4 20 mm archive on
    /dev/did/dsk/d5s3 21 mr archive on
    *3. Create the hosts file (on both nodes)*
    #cd /etc/opt/SUNWsamfs/
    #vi hosts.archive
    #HostName NetworkInterface ServerPriority Unused Server
    xenon 172.16.0.129 1 0 server
    arsenic 172.16.0.130 1 0
    *4. modify the /etc/vfstab file (on both nodes)*
    #vi /etc/vfstab
    #device device mount FS fsck mount mount
    #to mount to fsck point type pass at boot options
    archive - /archive samfs - no shared,notrace
    *5. create the mount point (on both nodes)*
    #mkdir /archive
    #chmod 755 archive
    *6. create the file system (on the server node)*
    [root@xenon:/etc/opt/SUNWsamfs #]samd config
    Configuring SAM-FS
    [root@xenon:/etc/opt/SUNWsamfs #]sammkfs -S -a 64 archive
    Building 'archive' will destroy the contents of devices:
    /dev/did/dsk/d5s4
    /dev/did/dsk/d5s3
    Do you wish to continue? [y/N]y
    total data kilobytes = 68525248
    total data kilobytes free = 68525184
    total meta kilobytes = 1044224
    total meta kilobytes free = 1043680
    *7. mount the file system*
    on server side
    [root@xenon:/etc/opt/SUNWsamfs #]mount /archive
    [root@xenon:/etc/opt/SUNWsamfs #]chown �R oracle:dba /archive
    On client side
    [root@arsenic:/etc/opt/SUNWsamfs #]mount /archive
    mount_samfs: Configuring file system
    *8. Create the QFS metadata server (MDS) resource group for high availability.*
    From xenon do:
    # clresourcetype register SUNW.qfs
    # clresourcegroup create -p nodelist=xenon,arsenic archive-rg
    # clresource create -t SUNW.qfs -g archive-rg -p QFSFileSystem=/archive archive-rs
    # clresourcegroup online -emM archive-rg
    Actually, i did not do the step 8 (Create the QFS metadata server (MDS) resource group for high availability).
    then i reboot both nodes, the QFS failed to be mounted
    I found one doc is related to my problem.
    http://sunsolve.sun.com/search/document.do?assetkey=1-25-90055
    It suggests to restart the samfs-qfs Resource Group to fix the problem. But the problem is i haven't setup the "samfs-qfs Resource Group ".
    How can i do now? any advices?
    Many many thanks!
    Larry chen
    Edited by: chenjg00 on Nov 13, 2007 12:38 PM

    It looks like you have the wrong entries in your hosts.archive file.
    On a cluster, these should always reference the clusternode-priv names, e.g.
    -bash-3.00# cat hosts.rac_data
    pgyruss1 clusternode1-priv 1 0 server
    pgyruss2 clusternode2-priv 1 0
    These resolve to slight different addresses to the ones you are using and that might be the cause of your problem.
    -bash-3.00# getent hosts clusternode1-priv
    172.16.4.1 clusternode1-priv
    Try that and see if it works. You might have to fiddle about a bit and may need to run "samd config" again.
    Tim
    ---

  • Strange USB mount error: Solved

    when I plug in my SD card reader I get the following message.
    It works as root and the last time I tried it worked as user.
    Using KDE and testing.
    solved by adding my user to the storage group 
    A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.Hal.Device.Volume" member "Mount" error name "(unset)" destination "org.freedesktop.Hal")
    I did a more careful forum search.
    :oops:

    ataraxia wrote:
    You have no swap configured? Konqueror and Firefox are both huge memory hogs. You could easily use all your memory doing ordinary things (especially if you use KDE or other large things).
    Configure some swap. If you have no free partitions, but a little free space, you can swap to a file: http://www.netadmintools.com/art1.html I suggest at least 1 GB of swap.
    a was forgoten activate the swap .
    1 0x00 1 1 0 0x83 254 63 1023 63 20000862
    2 0x00 254 63 1023 0x83 254 63 1023 20000925 80003700
    3 0x00 254 63 1023 0x82 254 63 1023 100004625 996030 << that is the swap
    4 0x00 254 63 1023 0x83 254 63 1023 101000655 524136690
    thankz
    PD: sorry for my english

  • Systemd nfs client mount share ???

    Just installed systemd, systemd-arch-units and initscripts-systemd  as per the wiki and all went well except mounting a nfs share from my server. (networking is OK!)
    This is the old working mount command run from rc.local before installing systemd;
    mount -t nfs4 -o rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 192.168.0.250:/ /media/SERVER_NYTT &
    Did not mount at all with systemd, not even when run manually from command line. From systemd log netfs and nfs-common failed to start.
    So I tried from fstab instead;
    192.168.0.250:/ /media/SERVER_NYTT nfs rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp 0 0
    This did work but 'mount' showed that systemd had mounted with nfs default options instead of mine (wsize, rsize ...). Still errors from systemd starting netfs and nfs.
    So I disabled netfs and nfs-common/rpcbind from rc.conf and created this systemd file (/etc/systemd/system/192.168.0.250.mount);
    [Unit]
    Description=ServerNfs
    Wants=network.target rpc-statd.service
    After=network.target rpc-statd.service
    [Mount]
    What=192.168.0.250:/
    Where=/media/SERVET_NYTT
    Type=nfs
    Options=rw,hard,async,intr,rsize=49152,wsize=49152,proto=tcp
    DirectoryMode=0777
    StandardOutput=syslog
    StandardError=syslog
    From the sparce wiki and 'man systemd.mount'. Now nothing happens. With my limited understanding I thought it would start neccessary services (wants) and replace the entry in fstab.
    I will now enable systemd services rpcbind, rpcstatd and see what happens.
    Overall the transition to systemd went very well indeed; slim, openbox, network, .xinitrc, e4rat all started OK much to my surprise! There's still some fine-tuning to do like nfs, and possibly automounting and at last weeding out unneccessary services.
    But any help with this nfs client problem is much appreciated.

    swanson wrote:
    Do you use any of this;
    Alternatively, you can mark these entries in /etc/fstab with the x-systemd.automount and x-systemd-device-timeout= options (see systemd.mount ..
    I did read the man for systemd.mount but couldn't make out what to put in the fstab line.
    By the way, I renamed the mountfile to the target mountpoint but no success. I then reactivated the fstab line, with the new mountpoint in /mnt and that worked fine with mount -a. Except the mount options are not as I want, as they are in fstab. They were before systemd, and now they are as default for nfs4.
    have a look here regarding the x-systemd-automount option. I seem to be only one who has noticed a problem with this option, comment=systemd.automount works fine for automounting though. I haven't changed the wiki because I'm still not sure if the problem is on my side.

  • Systemd has problems mounting efi

    As you can see here [https://www.dropbox.com/s/2dzfssgnwtqs6 … .37.33.jpg] I'm having troubles booting from systemd because of the efi partition.
    I don't get why it says that the fstype is wrong since vfat works well with sysvinit, anyone is able to help me get out of this?
    Thanks!

    Nope it was auto generated by genfstab...
    Here is my fstab
    # UUID=d7caefba-6d79-4ec2-a2fb-3d5957911b34
    /dev/sda3               /               ext4            rw,relatime,data=ordered        0 1
    # UUID=7beb1ed3-370d-4435-b8ad-e408cfa844d7
    /dev/sda4               /home           ext4            rw,relatime,data=ordered        0 2
    # UUID=1ed0f133-eb01-4f63-8c0a-962d53eb7476
    /dev/sda2               /boot           ext2            rw,relatime     0 2
    # UUID=70D6-1701 LABEL=EFI
    /dev/sda1               /boot/efi       vfat            rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro  0 2
    /swapfile               none            swap            defaults        0 0
    Last edited by ewaves (2012-10-09 09:13:53)

Maybe you are looking for