Volumes not mounting

I've got two xserver XSAN controllers, one XRAID array,
and an emulex FC switch. The servers, xraid, and FC switch
are connected on a private ethernet network, 192.168.1.x.
I'm trying to get the volumes defined in the SAN mounted on
both servers. The SAN volumes mount on one server but not
the other. I'm running 10.4 and the just recently released
XSAN version.
On xserver 1 the SAN is visible (via SAN admin) and the volumes mount on the desktop. Everything is happy.
On xserver 2 I can see the san, and both servers show
up in the clients/participants list. I can see the volumes defined
in the SAN listed in the SAN components window. However
I can't mount the volumes defined in the SAN. Both the xservers
are defined as controllers, with xserver 2 defined as the medium
priority failover.
I'm seeing these error messages in /var/log/system.log ("Video" and "Outside" are the volume names) on xserver 2:
Nov 15 23:19:17 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:19:17 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:19 faster kernel[0]: Can not get FSM address for filesystem 'Outside'
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: RESTART FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: Starting FSS service 'Outside[1]' on host 192.168.1.17.
Nov 15 23:19:27 faster fsmpm[336]: PortMapper: FSS 'Outside'[1] (pid 428) at 192.168.1.17:49215 is registered.
Nov 15 23:23:13 faster servermgrd: xsan: [46/133F290] ERROR: getfsmvol_atindex: Could not connect to FSM because File System Manager "Video" on 192.168.1.17 is on standby.
Nov 15 23:23:13 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: FSS 'Video' disconnected.
Nov 15 23:23:17 faster KernelEventAgent[43]: tid 00000000 received VQ_NOTRESP event (1)
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:23:17 faster kernel[0]: No FSS registered with PortMapper on host 192.168.1.17, retrying...
Nov 15 23:23:17 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:27 faster fsmpm[336]: PortMapper: RESTART FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:27 faster fsmpm[336]: PortMapper: Starting FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:28 faster fsmpm[336]: PortMapper: FSS 'Video'[1] (pid 450) at 192.168.1.17:49266 is registered.
Nov 15 23:23:28 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:30 faster fsmpm[336]: PortMapper: Initiating activation vote for FSS 'Video'.
Nov 15 23:23:36 faster kernel[0]: Could not mount filesystem Video, cvfs error ' Timeout' (25)
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: FSS 'Video' disconnected.
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: Rescanning for available CVFS volumes.
Nov 15 23:23:37 faster fsmpm[336]: PortMapper: QUEUEING RESTART of FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:39 faster kernel[0]: Can not get FSM address for filesystem 'Video'
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: RESTART FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: Starting FSS service 'Video[1]' on host 192.168.1.17.
Nov 15 23:23:47 faster fsmpm[336]: PortMapper: FSS 'Video'[1] (pid 452) at 192.168.1.17:49271 is registered.
Any ideas? Shouldn't I be seeing other messages attempting contact with the other controller?

I'm not sure about your emulex FC switch, because I use Qlogic, but for the rest of it, I know I can comment.
In my previous attempts to make volumes mount I found it was usually due to either bad DNS (improper name of machine) and/or bad network connection (metadata network connections not working either due to bad cable, or bad NIC or bad switch port).
Check the name of the machine, whether it resolves properly, and also check your IP networks (if you're using two, or just metadata).
I hope that helps.
-x

Similar Messages

USB 3 external drive volume not mounting on restart

I've bought an external USB 3 full size hard drive enclosure case and put in a 2TB drive. The drive is partitioned into 3 volumes. I've noticed from time to time that the volumes have gotten dismounted some how. If I unplug the USB cable and plug it back in the volumes mount again. After a long time I finally figured it out that what's really happening is that the volumes are not mounting when I do a restart, I just didn't notice it before. Once the volumes are mounted they stay mounted until the next restart. I replaced the enclosure and cable with a different and more expensive brand but that didn't make a difference. No matter what I do the volumes never mount on restart.

I think this might be due to the fact that my iMac as a fusion drive and it boots so fast that the exteranl drive isn't finished starting up when OS X is looking for drives durring it's bootup.

Xraid Volumes not mounting

Our Xserve will not mount a raid volume. If the Fiber connection is pplugged into another xserve the mounts appear. On the problem xserve the volumes do not even appear in the disk utility. Any ideas on how to find them would be greatly appreciated. I do not think the Fiber card is bad due to the fact that the Xraid admin says the link is up.

It'll only take a few minutes to try swapping the fibre cards, and if the problem goes away, or when you open up the problem box you see the card not seated right you'd be done.
Roger

How to make volume NOT mount automatically?

Good morning:
I have a 75 gig drive in an Indigo iMac running 10.3.9. The drive is partitioned into two volumes.
Is there any way to flag the non-boot volume so it will not mount when the system starts? I only want it to be available to one or two admin users; they can mount it using Disk Utility as needed.
Thanks for any ideas!

Hi DWJ,
You could enable fstab in NetInfo and flag the partition not to auto mount. I think an easier solution is to set the permissions on the partition so other users do not have access or better yet create a virtual drive with an encrypted disk image.

Intel xserve with hardware raid. Volume not mounting but drives show good

So this morning we came in and found that our intel xserve with the hardware raid is not booting.
Booted from OS X Install DVD and Raid Utility shows the Raidset good and all drives good.
Open disk utility and no volume form the raid will show up.
ANY IDEAS!??!

New information.
So out of the blue the Volume decided it needed to run an initializing run.
Apple care says I have to just wait until its done and see if the volume mounts.
Very strange since everything was green (good) until just then.
UPDATE:
Next day, the initializing has finished and now the Volume says (good) but the Raid Set is now "in transition". Applecare says I have to just wait till its done and see if the volume mounts.

Time Capsule Volume Not Mounted when waking from Sleep Mode

Hello all
Time Capsule 500GB, unibody MBP, 802.11n WPA2 encryption
Question: I setup Time Machine to use the disk on Time Capsule. I entered the password then locked the Time Machine preferences. Time Machine backs up to Time Capsule successfully.
I've started to noticed in particular when using Sleep mode often when the machine wakes up (appears to be random) it loses connection to the disk on Time Capsule despite it being locked in preferences. So I would have to unlock preferences, then click on Change Disk, click on TC's disk and enter the password and it connects successfully.
My question is...what is causing Time Machine to unable to mount TC's disk? I have a full strength wireless signal once the laptop wakes up from sleep. I can browse the Internet, use the Airport Utility, etc. however randomly Time Machine can't find TC's disk.

After upgrading to 7.4.1 firmware it fixed my problem

Our XServe-RAID volume does not mount anymore...

Our XServe-RAID volume does not mount anymore.
On /var/log/system.log I could find the following.
Feb 22 09:52:29 ogre kernel: jnl: open: journal magic is bad (0xf433f != 0x4a4e4c78)
Feb 22 09:52:29 ogre kernel: hfs: early jnl init: failed to open/create the journal (retval 0).
It appears the the journaling is badly screwed.
I tryed to disable the journaling with no success.
Here is what I get.
ogre:/var/log root# diskutil disablejournal disk2s3
The selected journaling request does not appear to be valid
After some googling I foud this :
--- QUOTE ---
The more serious problem occurs when the contents of the journal file are corrupted in such a way that the operating system does not proceed to mount the volume. Fortunately, this problem is extremely rare (I have seen three reports of corrupted journal files at the MacFixIt Forums and Apple Discussion Forums since journaling was introduced).
Starting the journaling process is one of the first things that happens when a volume is recognized by the operating system. There appears to be no way to intervene in single-user mode before the journal file is examined. A message about �bad journal magic� appears. Unfortunately, every tool that can turn off journaling requires that the volume already be mounted.
If the Macintosh can boot under Mac OS 9, dealing with a corrupted journal file involves restarting under Mac OS 9 and using a utility (such as our free TechTool Lite 3.0.4) to make visible these two invisible files at the root level of the volume:
/.journal
/.journalinfoblock
Once these files are made visible, they can be deleted. Mac OS 9 does not support journaling, and recognizes nothing special about these files. Neither of these files can be seen in Terminal or in single-user mode in Mac OS X, because they are considered part of the disk directory.
If the Macintosh cannot boot under Mac OS 9, but the drive has Mac OS 9 drivers installed, the drive can be put into a Macintosh that can boot under Mac OS 9, or an ATA/IDE drive can be put into a suitable FireWire enclosure.
The possibility that you may need to remove these two journaling files under Mac OS 9 is a good reason for making sure that all volumes you use have Mac OS 9 drivers installed. The drivers must be installed when the drive is formatted.
--- [END] QUOTE ---
Well, my disk is part of a RAID 5 matrix.... so the solution proposed does not work.
Does any one of you has any idea ?
XServe Mac OS X (10.3.9)

I've seen an article about volumes not mounting and was wondering if this relates to your problem;
http://discussions.apple.com/thread.jspa?messageID=1239224&#1239224
The thread doesn't refer to journalling but may be of use?
HTH

NEED HELP Xsan volume is not mounted (strange problem)

I ask the help in solving the volume mount problem. (advance I am sorry for my english)
All began with the fact that the MDC is rebooted and on the two LUNs were gone XSAN label. I relabeled these LUNs using commands:
cvlabel -c >label_list
then in the file label_list I corrected unknown disks on the label with a same names that were. Then I ran the cvlabel label_list command. Finally I got the correct label on all drives.
# cvlabel -l
/dev/rdisk14 [Raidix meta_i          3365] acfs-EFI "META_I"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk15 [Raidix QSAN_I          3365] acfs-EFI "QSAN_I"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
/dev/rdisk16 [Raidix meta_ii         3365] acfs-EFI "META_II"Sectors: 3906830002. Sector Size: 512. Maximum sectors: 3906975711.
/dev/rdisk17 [Raidix 2k_I            3365] acfs-EFI "2K_I"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk18 [Raidix 2k_II           3365] acfs-EFI "2K_II"Sectors: 31255934943. Sector Size: 512. Maximum sectors: 31255934943.
/dev/rdisk19 [Raidix QSAN_II         3365] acfs-EFI "QSAN_II"Sectors: 7662714619. Sector Size: 4096. Maximum sectors: 7662714619.
The volume [2K] starts successfully.
but not mounted on the MDC and client.
I ran a volume check:
sh-3.2# cvfsck -wv 2K
Checked Build disabled - default.
BUILD INFO:
#!@$ Revision 4.2.2 Build 7443 (480.8) Branch Head
#!@$ Built for Darwin 12.0
#!@$ Created on Mon Jul 29 17:01:44 PDT 2013
Created directory /tmp/cvfsck3929a for temporary files.
Attempting to acquire arbitration block... successful.
Creating MetadataAndJournal allocation check file.
Creating Video allocation check file.
Creating Data allocation check file.
Recovering Journal Log.
Super Block information.
FS Created On               : Wed Oct 2 23:59:20 2013
Inode Version               : '2.7' - 4.0 big inodes + NamedStreams (0x207)
File System Status          : Clean
Allocated Inodes            : 4022272
Free Inodes                 : 16815
FL Blocks                   : 79
Next Inode Chunk            : 0x51a67
Metadump Seqno              : 0
Restore Journal Seqno       : 0
Windows Security Indx Inode : 0x5
Windows Security Data Inode : 0x6
Quota Database Inode        : 0x7
ID Database Inode           : 0xa
Client Write Opens Inode    : 0x8
Stripe Group MetadataAndJournal             ( 0) 0x746ebf0 blocks.
Stripe Group Video                          ( 1) 0x746ffb60 blocks.
Stripe Group Data                           ( 2) 0xe45dfb60 blocks.
Inode block size is 1024
Building Inode Index Database 4022272 (100%).
   4022272 inodes found out of 4022272 expected.
Verifying NT Security Descriptors
Found 13 NT Security Descriptors: all are good
Verifying Free List Extents.
Scanning inodes 4022272 (100%).
Sorting extent list for MetadataAndJournal pass 1/1
Updating bitmap for MetadataAndJournal extents 21815 ( 0%).
Sorting extent list for Video pass 1/1
Updating bitmap for Video extents 3724510 ( 91%).
Sorting extent list for Data pass 1/1
Updating bitmap for Data extents 4057329 (100%).
Checking for dead inodes 4022272 (100%).
Checking directories 11136 (100%).
Scanning for orphaned inodes 4022272 (100%).
Verifying link & subdir counts 4022272 (100%).
Checking free list. 4022272 (100%).
Checking pending free list.
Checking Arbitration Control Block.
Checking MetadataAndJournal allocation bit maps (100%).
Checking Video allocation bit maps (100%).
Checking Data allocation bit maps (100%).
File system '2K'. Blocks-5784860352 free-3674376793 Inodes-4022272 free-16815.
File System Check completed successfully.
check not helping
sh-3.2# cvadmin
Xsan Administrator
Enter command(s)
For command help, enter "help" or "?".
List FSS
File System Services (* indicates service is in control of FS):
1>*2K[0]                located on big.local:64844 (pid 5217)
Select FSM "2K"
Created           :          Wed Oct 2 23:59:20 2013
Active Connections:          0
Fs Block Size     :          16K
Msg Buffer Size   :          4K
Disk Devices      :          5
Stripe Groups     :          3
Fs Blocks         :          5784860352 (86.20 TB)
Fs Blocks Free    :          3665561306 (54.62 TB) (63%)
Xsanadmin (2K) > show
Show stripe groups (File System "2K")
Stripe Group 0 [MetadataAndJournal] Status:Up,MetaData,Journal,Exclusive
Total Blocks:122088432 (1.82 TB) Reserved:0 (0.00 B) Free:121753961 (1.81 TB) (99%)
MultiPath Method:Rotate
    Primary Stripe [MetadataAndJournal] Read:Enabled Write:Enabled
Stripe Group 1 [Video] Status:Up
Total Blocks:1953495904 (29.11 TB) Reserved:270720 (4.13 GB) Free:129179 (1.97 GB) (0%)
MultiPath Method:Rotate
    Primary Stripe [Video] Read:Enabled Write:Enabled
Stripe Group 2 [Data] Status:Up
Total Blocks:3831364448 (57.09 TB) Reserved:270720 (4.13 GB) Free:3665432127 (54.62 TB) (95%)
MultiPath Method:Rotate
    Primary Stripe [Data] Read:Enabled Write:Enabled
I checked the availability of LUNs on MDC and client, there also all right.
But, unfortunately, the Volume is not mounted
xsanctl mount 2K
mount command failed: Unable to mount volume `2K' (error code: 5)
Please help me to figure out this situation, I will be grateful for any information.
Thanks

That looks like an I/O error. You may have an issue with one or more of the data LUNs. Check the system log for errors.

Oddball client not mounting XSan Volumes

Background: My client, a TV News broadcast station, had Apple and a third-party design and install a Apple based XSan storage and network. They ran all new fiber and gigabit ethernet to each station to use the XSan. It has been working great, with the exception noted below.
Setup: 2 MD Controllers, 1 XServe, 4 XRaids, each make up two 2 large TB volumes (raid 5, stripped together).
XServe, XRAID, MD controllers, and all clients are all connected together on a Fibre and Fiber Optic network using QLogic switches. SUBNET: 10.200.1.x.
Ethernet Network, also connected all the above together on HP Gigabit Switches. SUBNET: 10.100.1.x The public WAN is made available on this subnet by a connection to the HP switches. Still getting details on how this was done.
Everything is running OS X 10.4.8 or better, XSan File System 1.4.
Setup
There are 8 workstations (edit bays) that act as infusion and editing stations. Each station has two XSans volumes mounted NEWS01 and NEWS02. They have the odd numbered bays use NEWS01 and the even numbered bays use NEW02.
PROBLEM
All bays mount the XSan volumes, except one. FCP08 will not mount the XSan volumes. We have rebooted the workstation, and even went to the extreme of shutting down the entire setup all bays and MD controllers, File Servers, etc.. then bringing everything backup up. Same problem.
Based on some forum discussion, we have tried the following:
* Ensured that there is no empty mount point in /Volumes
* Uninstalled all XSan Software and resinstalled v1.4 from Apple's website.
* Removed the client from the XSan Admin, and readded it, made sure to enter valid serial number, etc..
* Verified that all fibers are working, all link lights look good, and you can ping across the MD network.
When you use the XSan admin from either FCP08 (edit bay 08) or from the server, and you add both MD XSans to it, you see the client, and you click on the client and click either Mount (read-only) or Mount (Read/write).
It will show "Mounting..." and then it will flip back to "not mounted". The only feedback we have received so far is "ACCESS DENIED". All affinity setting are set to rwxrwxrwx (wide open), and all the volumes and workstation logins all have the same access to the volumes. I can not find any restrictive permissions anywhere.
I plan on trying to move them away from a /etc/hosts type setup to a proper DNS Server running on their XServe using the DNS Server function of OS X Server. But currently all edit bay stations have the same /etc/hosts file installed, which accounts for MD and ethernet networks.
ANY IDEAS what is wrong with this workstation? With the setup?
I have had extreme ideas from some who have said that we need to blitz the entire client, and reinstall the operating system. I am not willing to go down that route, since each edit bay was built manually without an image (another aspect I will remedying soon). It will take sometime to rebuild this edit bay client if I that is the only solution.
The only this question I have if that is the popular opinion, is what is different from a client OS install and the existing one regarding the XSan? This are edit bays, not private workstations, and no one installs any extra software or surfs the net, etc.. They are used for ingest and editing only.
HELP!
Mac OS X (10.4.10)

Hi,
You could check if it is Fibre Channel related:
from a terminal do a cvlabel -l
this should give you a list of the lun's in your volume.
When this tool does not show luns, you might have a zoning issue.
Regards
Donald

Time Machine backup volume will not mount

Once I goy Time Machine up and running over almost two years ago, I have had little cause for concern. A few lengthy backups here and there but I have been able to restore without any problems whatsoever. It has been extremely useful many times.
A couple of days ago, I noticed that the backup volume was not mounted (I backup to one of my four internal drives) and launched Time Machine. I got the error:
The storage location for Time Machine backups can't be found.
When I run Disk Utility the generic disk icon is in the left hand pane but not the volume. None of the tasks are available except Erase and Partition - there is no option to Verify Disk, Repair Disk, Verify Disk Permissions or Repair Disk Permissions.
According to my logs, the last backup at 18:12 on 20th November was successful. I didn't notice that the volume had not mounted the until the next day.
I'm very concerned that I have lost almost two years of data security. Is there any way I can repair the disk or recover the backups?
Thanks.

If Disk Utility can't see any partitions, it's not good.
First, turn TM off.
Then try ejecting, disconnecting and powering the drive off for a few minutes, then reattaching it. Then try again with Disk Utility. If still no help, the drive is likely dead.
There's a very small chance that +Disk Warrior+ (version 4.1.1 or 4.2 only), or another heavy-duty disk repair app can fix it, if you already have one. But I wouldn't suggest spending the $$ for one unless you think you'll need it in the future -- DW is about $100.
Most likely, your disk is dead. There's a small chance that a +Data Recovery+ app such as +Data Rescue+ can recover some of the data. Check via Google, VersionTracker.com, or MacUpdate.com for +Data Recovery.+ There are services and apps, none cheap. Some of the apps have a free demo or test mode that will tell you if there's anything that can be recovered, and perhaps actually recover a single file; then you pay for it and recover whatever else can be recovered. You'll need another external disk to receive the recovered items.
You won't get the normal Time Machine folder structure, though, just "raw" files. Even if you do recover files, you'll most likely have to figure out what goes where and copy them to the right places manually.
So I'd suggest immediately getting a new drive and doing a new TM backup to it, so you have something. Put a second partition on it that you can use for the recovered files if and when you do that.
If those are your only backups, I'd recommend getting a second external, perhaps a portable one, and using CarbonCopyCloner or SuperDuper to make a full "bootable clone" to it, then take it to your safe deposit box, workplace, relative's house, or other secure location. And/or, you might want to look at Mozy, Carbonite, or other online backup services.

Volume will NOT mount

We have much the same issue as others here in other threads have spoken about - after a reboot a raid volume will not mount.
Disk Utility can 'see' the drive and array, but will not mount it. RAID Admin reports no problems. I tried updating the firmware to no avail.
Then I tried a new FC card in the server, a different controller card in the xRAID, different cables and connecting the FC cable to a different XServe. No mount with any of these attempts.
XServe 2 ea 2.3Ghz G5, 2GB RAM, 1 80GB drive (cluster node config)
OSX Server 10.3.9
7 ea 180GB drives, RAID5; 1 TB array
RAID Admin 1.5 (controller firmware - now: 1.5/1.50f)
Any ideas what to try next? And no we don't have 100% backups, close but no... ;-( so any ideas worth trying appreciated!
Tks, Mark

Mark,
We recently had a similar problem. We have an XServe RAID fully populated -- split into 2 volumes. One volume would mount the other would not (after a reboot). Tried swapping fibre channel cables, re-seating fibre channel cards, etc. Our solution was replacing the PCI-Fibre card in the XServe.
Another thing we have had happen is, after reboot, one volume mounts and the other mounts about 15 mins later -- after completing fsck.
Hope this helps.
--Bonnie

[SOLVED] pam_mount will not mount truecrypt volume on login.

Hello.
I did system upgrade yesterday and encountered some problems with mounting my Truecrypt volume with pam_mount. I use pam_mount to mount my encrypted /home partionion at login. After first reboot and loging in I was dropped to / directory, with my /home partition clearly not mounted. I acknowledged the message from udev in pacman, that in some circumstances adding 'loop' to MODULES array in /etc/mkintcpio.conf is required and for a moment I thought it was it, but I tried this and it didn't help. Suprisingly, after another reboot I was placed im my home directory afer login, but it appears to be empty - I can see only dotfiles of few programs I used after the upgrade:
$ls -A ~/
.bash_history .links .qingy .viminfo .wicd
but my /home partition is obviously still not mounted. My relevant config files:
/etc/security/pam_mount.conf.xml
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">

<pam_mount>

<debug enable="0" />




<mntoptions allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other" />

<mntoptions require="nosuid,nodev" />

<logout wait="0" hup="0" term="0" kill="0" />

<cryptmount>truecrypt --text --protect-hidden=no --keyfiles="/etc/home.key" %(VOLUME) %(MNTPT)</cryptmount>
<cryptumount>truecrypt -d</cryptumount>
<volume user="schirase" fstype="crypt" path="/dev/sda7" mountpoint="/home" options="fsck,relatime" />
<mkmountpoint enable="1" remove="true" />
</pam_mount>
/etc/pam.d/login
#%PAM-1.0
auth required pam_securetty.so
auth requisite pam_nologin.so
auth required pam_unix.so nullok
auth required pam_tally.so onerr=succeed file=/var/log/faillog
auth optional pam_mount.so
# use this to lockout accounts for 10 minutes after 3 failed attempts
#auth required pam_tally.so deny=2 unlock_time=600 onerr=succeed file=/var/log/faillog
account required pam_access.so
account required pam_time.so
account required pam_unix.sof
#password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3
password optional pam_mount.so
#password required pam_unix.so sha512 shadow use_authtok
session required pam_unix.so
session optional pam_mount.so
session required pam_env.so
session required pam_motd.so
session required pam_limits.so
session optional pam_mail.so dir=/var/spool/mail standard
session optional pam_lastlog.so
session optional pam_loginuid.so
-session optional pam_ck_connector.so nox11
-session optional pam_systemd.so
/etc/pam.d/qingy
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_console.so
Any ideas how to make it work again?
[EDIT] OK, I've looked into it a little more and I realised that I should try loging in without qingy. I tried on agetty console and it worked as before. It looks like qingy upgrade changed my /etc/pam.d/qingy file into default one. The one above is and obviously unsuitable for use with pam_mount and I failed to see that at first. It should look similar to the example file for slim in the wiki article on pam_mount:
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth required /lib/security/pam_unix.so
auth optional /lib/security/pam_mount.so
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_unix.so
password required /lib/security/pam_unix.so
password optional /lib/security/pam_mount.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_mount.so
session optional /lib/security/pam_console.so
Sorry for the trouble, maybe at least it will help someone.
Last edited by Schirase (2012-03-25 17:49:21)

Having looked again, hal fails to start. I have it in rc.conf DAEMONS. When i try to start Hal manually, it also fails to start ...
Last edited by whitetimer (2010-11-09 16:45:46)

XServe RAID volume does not mount

Without any modification to the system, a panic log from our XServe indicates:
"Thu Jan 18 17:28:58 2007
panic(cpu 0): HFS: corrupt VH on PBSRaid1, sig 0x4100, ver 0, blksize 0"
The volume PBSRaid1 does not mount anyway from that date.
Diskutil reports:
"Verifying volume “disk2s3”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Invalid extent entry
The volume PBSRaid1 needs to be repaired.
Volume check failed."
DiskUtil is unable to repair the volume.
My configuration is:
XServe bi-G3 1GHz, MacOSX Server 10.3.9
XServe RAID with 5 disks RAID5 on the left side (OK) and 4 disks RAID5 on the right side (the bad volume)
All the controls are "green" and nothing wrong appeared in the events log obtained via RAID ADmin.
Any suggestion to repair are welcome, as we have many data from confocal microscopy on that volume.
Thanks
Jean-Pierre
XServe bi G3-1GHz (oct 2003)+ XServe RAID Mac OS X (10.3.9)

Right, Dave.
DW 4 rebuilt a preview folder which contains all the files in correctly named folders.Only 3 files among thousands has been saved in a Rescue folder !
It also restored the right volume label, lost in DiskUtil, fsck, pdisk and others.
Very nice tool.
While DW was building its preview, the disk 9 lighted red and a lot of failures of the controler 2 appear in the events log of the XServe RAID.
At this time, the RAID is rebuilding with our spare disk.
I think we have to change both the disk 9 and the controler 2 despite it lights green currently.
Jean-Pierre
XServe RAID (2003- 5xIBM 180Go RAID 5) +(2005 -4xHitachi 250Go RAID5) Mac OS X (10.3.9)

Xsan 4 will not mount volume on client

I recently upgraded my MDC and my client computer to Yosemite. I went through the migration process the best I could and created a Configuration Profile on my MDC for my client computer. I installed the profile successfully but the volume will not mount on the client computer. On the client computer within Profiles, the Xsan Configuration Profile has in red "Unsigned" underneath it, is that what is causing the problem?
Also a few notes: there are two other client computers that haven't been upgraded and are running Maverick and the volume does mount to those computers. The volume is also mounted on the MDC and if I go to Disk Utilities on the client computer I do see the volume, just not mounted.
Any help would be great! Thank you.

Thank you Claudio,
After doing much research and testing I believe you are onto something with my fsmpm or my .auth_secret file not being created. After using Server.app on the MDC I used the configure profile within Server.app. After installing the profile on my client computer it didn't mount and when looking within the Library/Preferences/Xsan folder there was no files (including the hidden .auth_secret file). So I then I used the web profile interface to create the configuration profile and this time it installed the fsnameservers and config.plist files but not the hidden auth_secret file and still no mount.
To answer some of you questions, I did try several times the "sudo xsanctl mount Volume Name" but had no success. I was previously running 10.9 on the MDC and my client computer. I am not sure if the MDC already had an Open Directory Master before upgrading and I did have a little bit of problems activating Xsan, because some of my DNS settings had changed. I got that all squared away and Xsan started working.
The reason I believe it is a fsmpm issue is because when I executed the command "sudo xsanctl i" (views the volumes connected to Xsan) I go a message reading "fsmpm not running error3". So after reading this forum Xsan: "fsmpm not running" message in Xsan Admin - Apple Support I copied the .auth_secret from the MDC to my client and still no mount. I tried again with all the files within Library/Preferences/Xsan folder and nothing. I then got the .auth_secret file from another client computer running 10.9 and still no mount, BUT when I copied all the files within the 10.9 client's Library/Preferences/Xsan the volume appeared! YEAH! But I'm not sure if this is a fix I should be happy with or continue to figure out why its not working the proper way? That way in the future I'm not running into this issue over and over again.
So I need to figure out either how to get my fsmpn running in 10.10 or figure out why my my Server.app on the MDC won't create the auth_sect file. I read somewhere that within the Xsan screen in the Sever app it should show the Authentication Secret, but I do not see this on my Xsan screen. Should it be there and if so is this where my problem steams from? Any thoughts? Thank you so much!

Could not mount Volume "Lacie Disk" HELP!

I have had a Lacie disk plugged into my Airport Extreme and have used it for wireless transfers and backups just fine since April...
I have an alias of the Lacie on my Desktop and clicking this has allowed the drive to mount.
Today, for some unknown reason I get MOUNT FAILED, could not mount volume "Lacie Disk".
Can someone please help trouble shoot? I have tried restarting the computer and restarting the drive and Airport Extreme. I don't know what hapened.
Help is greatly appreciated...!!
Bill

Hen,
Just thought I'd drop by for an unsolicited essay on this kind of problem. In my experience, computer don't have luck (and they're low on the food chain relative to vacuum cleaners).
However, always suspect an Apple enhancement if you've just upgraded & fixed permissions. Upgrades change things, but they also patch vulnerabilities that were there: be paranoid. They also add bulk (usually), and a resource-started computer can react in strange ways.
So, did you check your previous network settings for accuracy first?-for, dare I say it here, some 'trojan horses' change these. (I always treat a new problem first as a security problem.) If not, you should check them in a week and assure yourself they're what you typed in.
My LaCie drive, though a DVD burner, just quit after the last 10.4.11 upgrade (or iTunes or Quicktime upgrade). On my other Mac, upgrading Quicktime & iTunes caused downloaded virtual disc images to fail to mount, with no error message in any log. The second I traced to a new Apple intolerance for home-made typefaces, three of which I removed from the 'computer collection' (where they shouldn't have been anyway). The first problem is proving more elusive. I fear a conflict with a so-called 'third-party' device driver.
The professionals' second maxim (after 'take the defaults') is, 'when trouble strikes, reboot'. (This is for the 5-minute corporate repair; they dump to logs & perform essential postmortems after hours.) Your solution is a variety of the second. (As is the deleting of preference files when trouble strikes.) Even if this fix is permanent, check your network settings now, to see whether they've been changed.
Bruce

Volumes not mounting

Similar Messages

Maybe you are looking for