Cannot mount volume

Hi
I have a server connected to a MDC.
The MDC is running 10.4.8 server, XSan 1.4.1.
The MDC can mount the SAN correctly.
The client is running 10.4.8 server, XSan 1.4.1
The client cannot mount the SAN.
What I've tried:
Re-installing XSAN
Re-installing the 10.4.8 combo update
Re-installing the 2006-007 security update
Changing from Controller, medium to client and back.
mount -t ... /Volumes/SAN
Every time I get this in the syslog:
Dec 13 13:54:35 xsanclient kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
any ideas

More from the log:
Dec 13 22:17:51 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:18:37 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:18:53 multimedia sudo: admin : TTY=ttyp1 ; PWD=/Users/admin ; USER=root ; COMMAND=/usr/bin/tail -f /var/log/system.log
Dec 13 22:19:01 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)
Dec 13 22:19:23 multimedia servermgrd: xsan: [39/36E6F0] ERROR: getfsmvol_atindex: Could not connect to FSM because Admin Tap Connection to FSM failed. - Operation timed out
Dec 13 22:19:24 multimedia kernel[0]: Could not mount filesystem SAN, cvfs error ' Timeout' (25)

Similar Messages

Gnome "cannot mount volume"

Gnome doesn't want to mount my USB pen drive. I get the following message:
Cannot mount volume.
Error org.freedesktop.DBus.Error.AccessDenied.
A security policy in place prevents this sender from sending this message to the recipient...
I have hal,dbus & fam in my DAEMONS and I have added myself to the optical and storage groups. I have also logged off and on and tried restarting, but I still get this error.

I am having this same issue. However, I have added myself to both groups and logged out and back in again. I cannot get this to work on either my laptop or my desktop. Any other suggestions?
**Solved on my laptop: You have to restart dbus.
Log out of your DE, and go to a console
/etc/rc.d/dbus restart
/etc/rc.d/hal restart
Should work now
Last edited by Mais (2008-10-19 22:50:57)

Z10 cannot mount volumes

New connection but z10 not recognised and mount volumes does not work. Play book threads suggest top/ip not running but mine is windows 7, any simple help appreciated Chris

uninstall BlackBerry Device Services and then plug in Z10 and wait for about 5 min to install drivers
I did this on my 64 bit 7 os
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Cannot mount volume - device offline

Hi everyone,
I am trying to setup OSB on a Linux box (CentOS).
I could configure the tape library and tape drives as explained in the installation/admin guide but could not get the tape volume mounted. It keeps giving the errors:
can't mount volume in tape1 - device offline
It seems that the volume is offline. How can we get it online?
The error log for the tape drive shows:
Oracle Secure Backup hardware error log for "tape1", version 1
QUANTUM DLT-S4, prom/firmware id 1414, serial number 236ER89482
Tue May 13, 2008 at 22:05:23.748 (IST) devtype: 15
obrobotd: core-ora:/dev/sg2, args to wst__exec: handle=0x1
accessed via host core-ora: Linux 2.6.9-42.ELsmp #1 SMP Tue Aug 15 10:35:26 BST 2006
op=18 (log_sense), buf=0x54b0b00, count=44 (0x2c), parm=0x3e0
cdb: 4D 00 3E 00 00 00 00 00 2C 00 log_sense, cnt=44, pc=0, page_code=0x3e
sense data:
70 00 05 00 00 00 00 18 00 00 00 00 24 00 00 00
00 00 00 00 00 00 00 00 00 00 00 48 00 00 00 00
ec=0, sk=ill req, asc=24, ascq=0
error is: illegal request
flags: (none)
returned status: code=illegal request,
resid=0 (0x0), checks=0x0 []
obtool user admin password oracle
ob> lsdev -lvg
lib1:
Device type: library
Model: [none]
Serial number: [none]
In service: yes
Debug mode: no
Barcode reader: yes
Barcodes required: yes
Auto clean: no
Clean interval: (not set)
Clean using emptiest: yes
Unload required: yes
Ejection type: auto
Min writable volumes: 0
UUID: 9ac064fe-01fb-102b-8a2e-0015175b4124
Attachment 1:
Host: core-ora
Raw device: /dev/sg1
Connection type: SCSI
Inquiry data:
Vendor: ADIC
Product: Scalar 24
Firmware: 0402
Serial number: ADICJaya
Element counts / addresses:
1 mte: 1
2 se : 4096 - 4097
0 iee
1 dte: 256
Moves:
From mte, to: mte 0 se 1 iee 0 dte 0
From se, to: mte 0 se 1 iee 0 dte 1
From iee, to: mte 0 se 0 iee 0 dte 0
From dte, to: mte 0 se 1 iee 0 dte 1
Ok_ops: move=1, reserve=1 sense_dev=1, sense_ele=1, unload_any=1, sense_dev_range=1
Device characteristics: two_d=0, is_120=0, fake_mte=0, fake_iee=0, one_target=0
State of barcode reader: present
Display: none
Dte 1: target * lun * name tape1 (raw device name /dev/sg2)
Warning: bus info unknown or drive not installed
tape1:
Device type: tape
Model: [none]
Serial number: [none]
In service: yes
Library: lib1
DTE: 1
Automount: yes
Error rate: 8
Query frequency: 1024KB (1048576 bytes) (from driver)
Debug mode: no
Blocking factor: (default)
Max blocking factor: (default)
Current tape: 1
Use list: all
Drive usage: none
Cleaning required: no
UUID: 371b7330-ffe9-102a-8a2e-0015175b4124
Attachment 1:
Host: core-ora
Raw device: /dev/sg2
Connection type: SCSI
Inquiry data:
Vendor: QUANTUM
Product: DLT-S4
Firmware: 1414
Serial number: 236ER89482
Tape state: online
Hardware compression: on
Last read was: uncompressed
Maximum block size: 1048576
Remaining tape: 73728 (uncompressed) blocks (75.50MB
Looking for comments/suggestions.
Thanks!

I created a file system backup job. The backup job is pending with the status "pending resource availability".
ob> lsjob all long
7:
Type: dataset Dataset1
Level: full
Family: MediaFamily1
Encryption: off
Scheduled time: 05/15.14:00
State: processed; host backup(s) scheduled
Priority: 0
Privileged op: no
Run on host: (administrative server)
Attempts: 1
7.1:
Type: backup core-ora
Level: full
Family: MediaFamily1
Encryption: off
Scheduled time: 05/15.14:00
State: pending resource availability
Priority: 0
Privileged op: no
Run on host: core-ora
Attempts: 0
ob> catxcr --level 0 7
Error: unable to open transcript for 7 - No such file or directory
Error: unable to open transcript for 7.1 - No such file or directory
I also tried to do some operations on the tape device (load, identify, import… ) but the commands take forever to finish and return with errors.
ob> lsvol library lib1 long
Inventory of library lib1:
in mte: vacant
in 1: barcode JK1112, oid 100
in 2: barcode JK1111, oid 101
in 3: barcode JK1113, oid 102
in 4: vacant
in 5: vacant
in dte: vacant
ob> loadvol drive tape1 mount write force 1 > (took around 10 mins to return)
Error: can't execute command - drive didn't come online; check configuration/hardware
I could see that the drive loaded into the tape immediately after issuing the command (from the Dxi GUI) but the loadvol command returned after a long time.
The log file for the obrobotd when the above command was issued shows:
[root@core-ora lib1]# pwd
/usr/local/oracle/backup/admin/log/device/lib1
[root@core-ora lib1]# tail -f obrobotd
2008/05/15.14:53:05 ***0 wst__dev_state...
2008/05/15.14:53:05 ***0 wst__exec: op=0 (nop), buf=0x0, count=1 (0x1), parm=0x0
2008/05/15.14:53:05 ioctl_op=0x3, to=300, datalen=0x0, buf=0x0, cdb: 00 00 00 00 00 00 tur
2008/05/15.14:53:05 ***0 wst__exec: rval=0, status.code/resid/checks=0x0/0x0/0x0
2008/05/15.14:53:05 ***0 wst__dev_state: no sense, status 0x0
2008/05/15.14:53:05 ***0 wst__exec: op=2 (sense), buf=0x54a970, count=32 (0x20), parm=0x0
2008/05/15.14:53:05 ioctl_op=0x5, to=30, datalen=0x20, buf=0x54a970, cdb: 03 00 00 00 20 00 sense, cnt=32
2008/05/15.14:53:05 ***0 wst__exec: rval=0, status.code/resid/checks=0x0/0x0/0x0
2008/05/15.14:53:05 ***0 wst__get_sense(int) cmd = 0, sense data:
2008/05/15.14:53:05 70 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 0C 00 80 00 00 00 00
ec=0, sk=no sense, asc=0, ascq=0, rem=0x30020000 (805437440)
flags: (none)
2008/05/15.14:53:05 ***0 wst__exec: op=7 (readpos), buf=0x7fbfffe1d0, count=20 (0x14), parm=0x0
2008/05/15.14:53:05 ioctl_op=0x5, to=180, datalen=0x14, buf=0x54aa78, cdb: 34 00 00 00 00 00 00 00 00 00 read_pos
2008/05/15.14:53:05 ***0 wst__exec, raw position: B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
2008/05/15.14:53:05 ***0 wst__exec: rval=0, status.code/resid/checks=0x0/0x10/0x0
2008/05/15.14:53:05 ***0 wst__exec: op=18 (log_sense), buf=0x54a9f0, count=44 (0x2c), parm=0x3e
2008/05/15.14:53:05 ioctl_op=0x5, to=180, datalen=0x2c, buf=0x54a9f0, cdb: 4D 00 3E 00 00 00 00 00 2C 00 log_sense, cnt=44, pc=0, page_code=0x3e
2008/05/15.14:53:05 ***0 wst__exec: op=2 (sense), buf=0x54a970, count=32 (0x20), parm=0x0
2008/05/15.14:53:05 ioctl_op=0x5, to=30, datalen=0x20, buf=0x54a970, cdb: 03 00 00 00 20 00 sense, cnt=32
2008/05/15.14:53:05 ***0 wst__exec: rval=0, status.code/resid/checks=0x0/0x0/0x0
2008/05/15.14:53:05 ***0 wst__get_sense(int) cmd = 4D, sense data:
2008/05/15.14:53:05 70 00 05 00 00 00 00 18 00 00 00 00 24 00 00 00
00 00 00 00 00 00 00 00 00 0C 00 80 00 00 00 00
ec=0, sk=ill req, asc=24, ascq=0, rem=0x30020000 (805437440)
error is: illegal request (OB scsi device driver)
flags: (none)
2008/05/15.14:53:05 ***0 wst__exec: rval=-1, status.code/resid/checks=0x20008113/0x0/0x0
2008/05/15.14:53:05 ***0 wst__dev_state: state=0x1 (online, not at bot)
2008/05/15.14:53:05 ***0 wst__wait: from dev_state: state=0x1, code=0x0
Thanks!

Cannot mount volume, security policy problem

ive never seen this before until today, but i can no longer access CDs or my USB thumbdrives through Nautilus by clicking on their respective icons. i get the following error dialog
i dont know much about dbus or hal, but the error dialog mentions those. what kind of other info, if any, would you guys need to help me solve something like this?

I believe you need to add the respective user to the "storage" group. Give this a try: as root run
gpasswd -a USERNAME storage
restart udev or simply reboot. This fixed my problem.

Cannot mount Xsan volume on Mac Pro

Hi,
I installed a new workstation - a first Mac Pro in our PPC Xsan deployment. I installed Xsan, then latest updates. However, I cannot mount an Xsan volume on this workstation. This is an abstract from the log:
May 16 19:06:14 Mac-Pro kernel[0]: Xsan Client Revision 2.7.201 Build 7.23 Built for Darwin 8.0 Created on Mon Nov 13 11:53:07 PST 2006
May 16 19:06:14 Mac-Pro sudo: root : TTY=unknown ; PWD=/Library/Filesystems/Xsan/debug ; USER=root ; COMMAND=/sbin/kextload -v -s /Library/Filesystems/Xsan/debug /System/Library/Extensions/acfsctl.kext
May 16 19:06:14 Mac-Pro /Library/Filesystems/Xsan/bin/fsmpm: NSS: No FS Name Servers file - NAME SERVICE DISABLED.
May 16 19:06:14 Mac-Pro fsmpm[246]: Portmapper: ComputerInfo: computer_name = "Mac Pro", hostname = "Mac-Pro"
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume Meta on device: /dev/rdisk1 (blk 0xe000003 raw 0xe000003) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018365' serial # '5000393000018365L0' Size: 490190848 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Left on device: /dev/rdisk2 (blk 0xe000004 raw 0xe000004) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018A78' serial # '5000393000018A78L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID2_Right on device: /dev/rdisk3 (blk 0xe000005 raw 0xe000005) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018805' serial # '5000393000018805L0' Size: 5860554719 Sector Size: 512
May 16 19:06:14 Mac-Pro fsmpm[246]: PortMapper: CVFS Volume RAID1_Right on device: /dev/rdisk4 (blk 0xe000006 raw 0xe000006) con: 2 lun: 0 state: 0xf4 inquiry [APPLE Xserve RAID 1.50] controller # '5000393000018319' serial # '5000393000018319L0' Size: 5860554719 Sector Size: 512
May 16 19:06:15 Mac-Pro servermgrd: xsan: [52] main: Waited 21 secs for fsmpm to start (now running)
May 16 19:06:15 Mac-Pro fsmpm[246]: PortMapper: Local FSD client is registered.
May 16 19:06:17 Mac-Pro servermgrd: xsan: [52] Done waiting for fsmpm to start
May 16 19:06:40 Mac-Pro servermgrd: xsan: [52/358E60] ERROR: mountvolumenamed(EditSAN): Cannot mount volume, file system does not know about it.
I tried reinstalling Xsan on this workstation, re-entering a licence key to the Xsan admin and rewriting Xsan settings, with no success.
All of the other 10 PowerMac workstations can access the Xsan volume with no problems.
Your help would be highly appreciated.

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

Kanaka Client unable Mount volume

I have OES11SP2 on SLES 11 SP3 on which I am running KANAKA ENGINE to mount volumes on MAC Client from servers running under same Tree.
Created eDirectory user account which have rights on volumes from two servers under the same tree.
example: 1) abc (volume) under Server1 (Running Kanaka engine)
2) xyz (volume) under Server2
Note: Tested AFP connectivity working without issues for both the volumes from MAC OS, also eDirectory users can map both volumes on windows machine with Novell client login.
Issue is I cannot mount volume from Server2 using KANAKA Client on MAC OS. However Server1(running kanaka engine) can able to mount.
any help is highly appreciated.

01 2014-12-14 20:03:42 10800 1 0001 13780 7f5258c2c760 Engine::SignalHandler() - Invoked. Signal = {SIGTERM} 15.
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 WD: Engine mainline thread is leaving the Watch Dog function...
82 2014-12-14 20:03:45 10800 0 ff08 13780 7f524e12c700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:45 10800 0 ff09 13780 7f524e12c700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Engine is shutting down...
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Terminating the HTTPx Server subsystem...
01 2014-12-14 20:03:45 10800 5 0001 13780 7f524e92d700 ML: Terminating the User Index Manager subsystem...
01 2014-12-14 20:03:45 10800 5 0007 13780 7f524e92d700 Index Manager: Shutting Down...
01 2014-12-14 20:03:45 10800 5 0007 13780 7f524e92d700 Index Manager: Waiting for Scheduler Thread to Terminate...
01 2014-12-14 20:03:46 10800 5 0007 13780 7f524e92d700 Index Manager: Waiting for All Worker Threads to Terminate...
01 2014-12-14 20:03:46 10800 5 0007 13780 7f524e92d700 Index Manager: Shut Down Complete...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Configuring the Novell XPLAT environment to no longer perform logging...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saving state information...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saving the Salt state information...
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Saved the Salt state information, bResult = 1.
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Completed saving state information, bOK = 1.
01 2014-12-14 20:03:46 10800 5 0001 13780 7f524e92d700 ML: Engine has shut down. Thread is terminating...
01 2014-12-14 20:03:46 10800 0 8001 13780 7f524e12c700 Shutting down the Logger. Closing log file "/var/opt/novell/kanaka/engine/log/novell-kanakaengined-20141202-132804.log".
81 2014-12-14 20:03:46 10800 0 8001 13780 7f524e12c700 <LOGFILECLOSE/>
81 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 <LOGFILEOPEN/>
81 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 <LOGGER><VERSION>1</VERSION><APPNAME>novell-kanakaengined</APPNAME><TZBIAS>10800</TZBIAS><OSVERSIONINFO>Kernel Name: Linux, Architecture: x86_64, Kernel Release: 3.0.76-0.11-default, Kernel Version: #1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990), Machine HW Name: x86_64</OSVERSIONINFO><OSBITS>64</OSBITS><APPBINARYFILESPEC>/opt/novell/kanaka/engine/bin/novell-kanakaengined</APPBINARYFILESPEC><APPBITS>64</APPBITS><AppVersion/><PROCESSID>10919</PROCESSID><THREADID>139987961149184</THREADID><LOGFILEPARAMS><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMAX></LOGFILEPARAMS><LOGLEVELNAMEMAP><ENTRY><LEVEL>0</LEVEL><NAME>Logging Disabled</NAME></ENTRY><ENTRY><LEVEL>1</LEVEL><NAME>Fatal</NAME></ENTRY><ENTRY><LEVEL>2</LEVEL><NAME>Critical</NAME></ENTRY><ENTRY><LEVEL>3</LEVEL><NAME>Error</NAME></ENTRY><ENTRY><LEVEL>4</LEVEL><NAME>Warning</NAME></ENTRY><ENTRY><LEVEL>5</LEVEL><NAME>Informational</NAME></ENTRY><ENTRY><LEVEL>6</LEVEL><NAME>Success</NAME></ENTRY><ENTRY><LEVEL>7</LEVEL><NAME>Verbose</NAME></ENTRY><ENTRY><LEVEL>8</LEVEL><NAME>Debug</NAME></ENTRY></LOGLEVELNAMEMAP><CATEGORYNAMEMAP><ENTRY><CATEGORY> 1</CATEGORY><NAME>Engine Watchdog</NAME></ENTRY><ENTRY><CATEGORY>3</CATEGORY><NAME>Engine Global Class</NAME></ENTRY><ENTRY><CATEGORY>4</CATEGORY><NAME>UI Session Manager</NAME></ENTRY><ENTRY><CATEGORY>5</CATEGORY><NAME>Web UI Session Manager</NAME></ENTRY><ENTRY><CATEGORY>6</CATEGORY><NAME>Client Manager</NAME></ENTRY><ENTRY><CATEGORY>7</CATEGORY><NAME>Index Manager</NAME></ENTRY><ENTRY><CATEGORY>8</CATEGORY><NAME>Login Script Parser</NAME></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><NAME>Logger</NAME></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><NAME>FSTools</NAME></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><NAME>DSTools</NAME></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><NAME>HTTPxServer</NAME></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><NAME>HTTPxClient</NAME></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><NAME>TaskMgr</NAME></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><NAME>NWXPlat</NAME></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><NAME>Storage Resources</NAME></ENTRY><ENTRY><CATEGORY>32777</CATEGORY><NAME>Security</NAME></ENTRY><ENTRY><CATEGORY>32778</CATEGORY><NAME>Thread</NAME></ENTRY><ENTRY><CATEGORY>32779</CATEGORY><NAME>OS Util</NAME></ENTRY><ENTRY><CATEGORY>32780</CATEGORY><NAME>Scheduling Service</NAME></ENTRY></CATEGORYNAMEMAP><LOGFILELOGLEVELMAP><ENTRY><CATEGO RY>0</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>5</LEVEL></ENTRY></LOGFILELOGLEVELMAP><CONERRLOGLEVELMAP><ENTRY><CATE GORY>0</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>5</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>5</LEVEL></ENTRY></CONERRLOGLEVELMAP><SYSLOGLOGLEVELMAP><ENTRY><CATEG ORY>0</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>3</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>4</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>5</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>6</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>7</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>8</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>2</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>2</LEVEL></ENTRY></SYSLOGLOGLEVELMAP><EVENTLOGLOGLEVELMAP><ENTRY><CAT EGORY>0</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>0</LEVEL></ENTRY></EVENTLOGLOGLEVELMAP><DEBUGPORTLOGLEVELMAP><ENTRY>< CATEGORY>0</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>1</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32769</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32770</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32771</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32772</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32773</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32774</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32775</CATEGORY><LEVEL>0</LEVEL></ENTRY><ENTRY><CATEGORY>32776</CATEGORY><LEVEL>0</LEVEL></ENTRY></DEBUGPORTLOGLEVELMAP><SYSLOGPARAMS><SYSLOGLEVEL>1</SYSLOGLEVEL><SYSLOGFACILITY>1</SYSLOGFACILITY><SYSLOGLEVELMAP><ENTRY><LEVEL>1</LEVEL><PRIORITY>2</PRIORITY></ENTRY><ENTRY><LEVEL>2</LEVEL><PRIORITY>2</PRIORITY></ENTRY><ENTRY><LEVEL>3</LEVEL><PRIORITY>3</PRIORITY></ENTRY><ENTRY><LEVEL>4</LEVEL><PRIORITY>4</PRIORITY></ENTRY><ENTRY><LEVEL>5</LEVEL><PRIORITY>5</PRIORITY></ENTRY><ENTRY><LEVEL>6</LEVEL><PRIORITY>5</PRIORITY></ENTRY><ENTRY><LEVEL>7</LEVEL><PRIORITY>6</PRIORITY></ENTRY><ENTRY><LEVEL>8</LEVEL><PRIORITY>7</PRIORITY></ENTRY></SYSLOGLEVELMAP></SYSLOGPARAMS><EVENTLOGPARAMS><EVENTLOGTYPE>0</EVENTLOGTYPE><EVENTLOGTYPEMAP/></EVENTLOGPARAMS></LOGGER>
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 Initializing Logger, re-opening existing log file "/var/opt/novell/kanaka/engine/log/novell-kanakaengined-20141202-132804.log".
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 This Logger class instance [0xadae90] was initialized at 2014:12:14:20:03:49 in Process ID # 10919.
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 OS Version Info = "Kernel Name: Linux, Architecture: x86_64, Kernel Release: 3.0.76-0.11-default, Kernel Version: #1 SMP Fri Jun 14 08:21:43 UTC 2013 (ccab990), Machine HW Name: x86_64", OS Bits = 64, Application binary file spec = "/opt/novell/kanaka/engine/bin/novell-kanakaengined", Application Bits = 64, Application Version = "".
01 2014-12-14 20:03:49 10800 0 8001 10919 7f517cb27700 This is the first time that a Logger thread has been started for this class instance.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Thread has started.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Configuring the client logging subsystem [Phase I]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the client logging subsystem [Phase I], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase I]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine's instance name = "".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting configuration path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting configuration path information, Result = 0, bOK = 1, path = "/etc/opt/novell/kanaka/engine/config".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting program path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting program path information, bOK = 1, path = "/opt/novell/kanaka/engine/bin".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase I], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Initializing the Configuration...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the reports data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the reports data path, sPathSpec = "/var/opt/novell/kanaka/engine/data/reports", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the rtconfig reports data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the rtconfig reports data path, sPathSpec = "/var/opt/novell/kanaka/engine/data/reports/rtconfig", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the client log data path...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the client log data path, sPathSpec = "/var/opt/novell/kanaka/engine/log/client", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Validating data path information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed validating data path information, Data Path = "/var/opt/novell/kanaka/engine/data", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed initializing the Configuration, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Configuring the Logging subsystem [Phase II]...
82 2014-12-14 20:03:49 10800 0 ff04 10919 7f517cb27700 <CONFIG><LOGPATH>/var/opt/novell/kanaka/engine/log</LOGPATH></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff05 10919 7f517cb27700 <CONFIG><LOGFILEBASENAME/></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff05 10919 7f517cb27700 <CONFIG><LOGFILEBASENAME>novell-kanakaengined</LOGFILEBASENAME></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff08 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:49 10800 0 ff07 10919 7f517cb27700 <CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMAX></CONFIG>
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the Logging subsystem [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed configuring the client logging subsystem [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase II]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the XML Message Signature object...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the XML Message Signature object, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the SSL/TLS certificate file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the SSL/TLS certificate file, sFileSpec = "/etc/opt/novell/kanaka/engine/config/server.pem", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the storage resources file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the storge resources file, sFileSpec = "/var/opt/novell/kanaka/engine/data/storage-resources.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the user index file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the user index file, sFileSpec = "/var/opt/novell/kanaka/engine/data/userindex.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Setting the client list file...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed setting the client list file, sFileSpec = "/var/opt/novell/kanaka/engine/data/clients.dat", bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is determining its own DNS host name...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed determining its own DNS host name, Result = 0, bOK = 1, Name = "kanakasrvkaia".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed determining its own DNS host name, Result = 0, bOK = 1, Name = "kanakasrvkaia".
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting O.S. version information...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting O.S. version information, Result = 0, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine is getting file version information for itself ["/opt/novell/kanaka/engine/bin/novell-kanakaengined"]...
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Engine completed getting file version information for itself ["/opt/novell/kanaka/engine/bin/novell-kanakaengined"], Version = "2.7.1.8", Result = 0, bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase II], bOK = 1.
01 2014-12-14 20:03:49 10800 5 0001 10919 7f517d328700 ML: Getting Operational Data [Phase III]...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Engine is finished preparing DS Context, eDir Tree Name = "KTREE", Result = 0, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed getting Operational Data [Phase III], bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Configuring the Novell XPLAT environment to perform logging...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed configuring the Novell XPLAT environment to perform logging, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Initializing the HTTPx Server subsystem...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed initializing the HTTPx Server subsystem, bOK = 1.
82 2014-12-14 20:03:51 10800 0 ff08 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2014-12-14 20:03:51 10800 0 ff09 10919 7f517cb27700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loading saved state information...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loading the Salt state information...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Loaded the Salt state information, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed loading state information, bOK = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Successfully authenticated as the Proxy Account.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Base schema appears to be properly extended.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Collaborative Homedirectory attribute ccx-FSFManagedPath is available.
01 2014-12-14 20:03:51 10800 5 0003 10919 7f517d328700 GL: Kanaka AFP Volume name attribute cccKanakaAFPVolumeName is available.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Attempted validate accounts, Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Successfully authenticated as the Proxy Account.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Attempted to Generate new SALT and Proxy Password, Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadStorageResourcesFromCache(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadClientManager(), Result = 0.
01 2014-12-14 20:03:51 10800 3 0001 10919 7f517d328700 ML: Called LoadMountPointManager(), Result = 53.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadIndexManager(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0007 10919 7f517d328700 Index Manager: Starting Scheduler Thread...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called IndexManager::StartIndexingScheduler(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0007 10919 7f517991c700 Index Manager [ST]: Next User Index Rebuild will happen in 14169 seconds.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Called LoadKanakaPolicy(), Result = 0.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Starting the HTTPx Server subsystem...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed starting the HTTPx Server subsystem, bResult = 1.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 ML: Completed initialization. Engine is now running.
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 WD: Engine mainline thread is entering the Watch Dog function...
01 2014-12-14 20:03:51 10800 5 0001 10919 7f517d328700 WD: Engine is running...
01 2014-12-14 20:04:50 10800 5 0004 10919 7f5172c9f700 UI: admin.kaia [192.168.1.180] LOGIN SUCCESS

Backup Controller cannot mount XSAN Volume

Hi Guys,
I've really have a big problem regarding the XSAN that I've just setup: There are 3 Xserves connected to the SAN - one for the main controller, one for backup and another one for fileserver. After a fresh install of the Leopard Server 10.5.6 on all servers and fresh install of Xsan 2.0 updated to 2.1.1, I tried creating an SAN from the main controller, I added first the main and backup controllers, authenticated them properly and was successful adding them to the SAN. After this, I created the volume and it mounted properly on the main controller. What I don't understand is that whenever I try to mount the volume to the backup controller, it is saying unable to mount and even I tried forcing it to mount in terminal using the command xsanctl mount VOLNAME, its giving me an error saying
"unable to mount volume, Cannot mount XSAN volume error code: 5"
What is that error message? When I tried typing cvadmin to the main controller, it only gave me this message:
Main Controller:
File System Services (* indicates service is in control of FS)
1>*XSAN[0] located on 10.0.0.101:49930 (pid 317)
Select FSM "XSAN"
When I type the same cvadmin to the backup controller, it gave me this message:
Backup Controller:
File System Service (* indicates service is in control of FS)
1> XSAN[1] located on 10.0.0.102:50384 (pid 331)
No FSSs are active
Select FSM "none"
What is happening? both servers are having a DNS name. Before I created the SAN, from the authenticate window, the server name is just the IP address of the Ethernet 0 (first ethernet port). Now whenever I fire up Xsan Admin, both controllers are now offline and if you authenticate them, the server name info suddenly changed from IP address to a DNS Name (e.g. from 194.170.34.12, changed to hct-mdc.ad.hct.ac.ae) which even if I type my admin username and password cannot authenticate saying "server not found in network"
I really don't know now what to do and they need to fix the issue asap.
I would really appreciate your help guys!
Thanks.
jantoniophi

Hi,
I am accessing this WS via ARD, so public LAN is definitely there. I have not connected the "Xsan" network (but it should be no problems communicating the Xsan traffic over this single LAN connection).
With the firewall, the situation is more strange. When I try to open the Firewall settings on Sharing, there is a dialog "Other firewall software is running on this computer." I googled this and it seems that this was a common problem on 10.3. They suggest to delete com.apple.sharing.firewall.plist file but it is not there on 10.4.
"sudo ipfw list" shows this:
00001 allow udp from any 626 to any dst-port 626
65535 allow ip from any to any
Any ideas on how to make Firewall behave as expected? I will try to reinstall if I don't receive a reply.
Thanks.

POL-4104 cannot mount database with a duplicate volume

Using a Oracle Lite database when performing a seond sync... I get this error
POL-4104 cannot mount database with a duplicate volume
Also changed the database id values in ODBC.ini still enountering the same problem
Please help!!! urgent!!!
Thanks

I have used DBINFO and also made sure that my id values are different in ODBC.ini but still encountering the same problem,
Second sync is nothing but in our project we use the oracle9ilite for synchroniztion of multiple databases at different locations so we do a sync process at different locs.
Now at my local system iam doing this sync for multiple databases asuming my box is at different locations....Then, iam encountering this problem of POL 4104. I made sure in my C:/WINDOWS/ODBC.ini that the database ids are different but no use..Pls help

Xsan2.2 client cannot mount StorNext3.5.2 volume

Hello,
On an OSX 10.6.4 system , I am trying to mount a Stornext3.5.2 filesystem, whose MDC is a Linux system.
On the MAC I can see all the LUNs,
I can somehow see the fylesystem:
+sh-3.2# xsanctl list+
+snfs01 - not mounted+
I cannot mount it:
+sh-3.2# xsanctl mount snfs01+
+mount command failed: Unable to mount volume `snfs01' (error code: 5)+
I would like to know what +error code: 5+ means, and whether anybody can help me in mounting the filesystem.

Apple's XSAN enterprise support claims error code 5 is proprietary.
Quite frustrating.
From our experience with the same set up (RHEL MDCs running Storenext 3.5.x) typically error code 5 on clients after an xsanctl mount command means: reboot the computer and try again.. the computer will automount the san volume(s) 60% of the time.
mcacciagrano- have you had any success deciphering what error code 5 is actually a complaint about?
It is not a unique serial number issue (verified through the system's config.plist).
It's not a fibre issue (we can see the LUNs)
It's NOT a ghosted mount point folder issue (from early xsan days)
It IS a (VERY COSTLY) annoyance, that's for sure.

I cannot mount my hard drive volume!

Began a standard install of OS 9.2.2 and then my hard drive icon disappeared from the desktop. I opened drive setup from the utilities folder of the 9.2.2 cd and I cannot mount the volume no matter what. I can only start up from the cd holding down the c key and that's as far as I can go. Is this it for this powerbook? Trash time? HELP!

monkybiz,
If initialization failed, there is a problem with the HD. However, there is a process that may correct the problem or it will definitively tell you the HD is bad. HDs can fail at any time so it just may be coincidence the problem arose when trying to install software.
Since initializing the HD failed, apparently the computer can now see the HD. Boot to your MacOS 9.x CD and open the folder that says Utilities and launch Drive Setup. Highlight your HD's name in the window, then move up to the menu bar. Under Functions, select Initialization Options, then check the box for 'zero all data'. Also select MacOS Extended Format when that window appears. When the process has completed (it will take awhile), select 'Test Disk' under Functions (it will also take a while). If zeroing fails or Test Disk fails, try again to zero and then run Test Disk.
If successful, install software; if the above fails, your HD is hosed. By the way, once Drive Setup has been launched, Drive Setup Help is available from the menu bar.

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command S, I get a looping "cannot mount errno = 19" message.

Disk Utility says everything's fine, but Install disk doesn't find my internal drive as a possible destination. When I startup with Command + S, I get a looping "cannot mount errno = 19" message.
Problem started when I used Tech Tool Pro 6 to "de-fragment volume". Had to cancel that process before it finished because I ran out of time. Thereafter, when I startup my machine normally, I get the gray Apple logo at first, but it changes to a prohibited symbol (circle with a slash thru it) and hangs.
When I startup holding the Option key, I can see my internal drive, but I get the same results as above.
When I startup using the MacBook OSX Install DVD, it does not find my internal drive as possible destination.
When I startup using the MacBook OSX Install DVD and then run Disk Utility, it finds my drive, allows me to "repair" and says everything is fine.
When I startup with Command + S, I get a looping error message "errno = 19" and cannot stop it to do anything else.
When I startup from Disk Warrior v4.4, it does not find my internal drive to do any repairs.
When I startup from Tech Tool Pro 6 and run the "computer check" diagnostics, everything passes but the Volume Structure, which fails at "Volume Extents (B-tree)." When I use TTP's "Tools" option to run "volume repair" it will show my internal drive and allow me to click the GO button, but nothing happens and nothing changes.
I have a Time Machine backup on an external USB drive, but for as long as the internal drive doesn't mount, I can't use the backup to restore.

It's a false report and should be ignored.
I would not rely on TT as I've already said earlier even before Grant posted similar advice.
I really think the Rigid Disk Block may be corrupted. This holds the partition map and could prevent a volume from being unmounted. Unfortunately, there is no way to fix that without repartitioning the drive which will remove everything. So, before going down this road I hope you have backups or can make a backup.
Drive Partition and Format
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Quit DU and return to the installer. Proceed with reinstalling OS X.
5. Download and install Mac OS X 10.6.8 Update Combo v1.1.

Cannot mount USB disk in SIngle-user mode (solaris 10)

Hi all ,
I need some help please :
I can read/write to my USB disks when i'm in muti-user mode but when to I swith to single-user mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management daemon :
#/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have this error: < mount : not a UFS magic number ( 0x0) , dev/dsk/c2t0d0p0 is not of this fstype.
My system recognizes the USB device though in single-user mode:
This is an output of #iostat -En
c2t0d0 Soft Errors: 1 Hard Errors: 0 Transport Errors: 0
Vendor: BUFFALO Product: ClipDrive Revision: 2.00 Serial No:
Size:0.07GB <65339392 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 1 Predictive Failure Analysis: 0

Hi ,
thanks for your advice. My problem is resolved.
The USB drive was actually a FAT filesystem.
so I did # mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint and everything went fine
I can read/write to my USB disks when i'm in
muti-user mode but when to I swith to single-user
mode ( init S ), I cannot mount it.
in Single-user mode , i started volume management
daemon :
/etc/init.d/volgmt start
#volcheck
but i'm still not able to mount it.It probably requires other items to be started
first.
I tried to mount manually:
#mount /dev/dsk/c2t0d0p0 /testpoint , i have
this
error: < mount : not a UFS magic number ( 0x0) ,
dev/dsk/c2t0d0p0 is not of this fstype.
Looks like it's assuming UFS. If this is a pcfs
filesystem, give it the type on the mount line.
# mount -F pcfs /dev/dsk/c2t0d0p0 /testpointYeah, this was the right command, I had to specify option < -F pcfs >.
but I read somethere on this forum i had to specify :c as the drive for FAT at the end of c2t0d0p0 , so the full command was:
# mount -F pcfs /dev/dsk/c2t0d0p0:c /testpoint
>
DarrenThanks,
Sakolan.

10.9: cannot mount westerndigital drive usb3 external, but in 10.8 yes

please why is my text shown on white background? can i change this?
i could not mount my 2 external wd drives (mypassport 2,5" 2TB)
(USB3.0) since install of 10.9 on my 2 brand new macs. (imac 27" i5 late 2013 and mbair i7 mid 2013)
before, with 10.8 it worked fine!
i thought the wd drive is faulty, so i got a new one by warranty, and sent the "old" back. it took only 5 days to get the swap by wd.
i could not mount the new drive either under 10.9
but today i installed techtool pro 7.0.2, did nothing but a reboot and after that, i plugged it into my imac with 10.9, it mounted correctly on my imac, the first time ever! and showed a techtool symbol as drive symbol instead of the orange colored usb symbol.
appearantly techtool pro 7.0.2 installed something into 10.9 which helps the system mount discs?
- i never did lock the drive with the wd security app
- before that, i tried to remove all wd related stuff and uninstalled every single wd app and driver, still no mount !
- before that, apple disctools under 10.9 did not show the drives in the left column, as no other harddisc app did. (drive genius)
- i can mount both drives on the old mbair with 10.8, my wife´s mac
- wd drive utilites would show the disc, but not mount, if i tried to format it, it showed an error after 1min: cannot format disc,
as it cannot be mounted. (or so..)
- now, after install of techtool pro 7.0.2, when i plug the drive into my imac, it is mounted correctly, but there is
always another volume mounted by default "wd drive unlock volume" which says "your wd drive is not locked, so you can not unlock it)
weird?
i still cannot mount the wd drive on my new macbook air with 10.9,
etre check lists as difference:
imac:
Kernel Extensions:
com.wdc.driver.USB.64.10.9 (1.0.1 - SDK 10.9) (today mount possible for the first time since weeks)
macbook air:
no wd driver at all (and no mount possible)
any idea?
thanks
Message was edited by: peppermint

first, you should try reinstalling 10.5.4. download the [combo update|http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1054com boupdate.html] and run it. If that doesn't fix the issue, you can use full system restore from TM to go back to a time before the troubles started. to do that boot from the leopard install dvd, once past the language screen go to the Utilities menu at the top and choose "restore from backup".

Cannot mount external USB drive

During a recent update I remember pacman asking about replacing some package with another package to handle disk mounting. I think the added package was "gnome-volume-manager" or "gnome-disk-utility" (or both). I didn't see any postings describing problems with doing this, so went ahead and allowed the change. Now it's a few days later and I find I cannot mount an external USB hard drive anymore. It has an entry in fstab, and although I have tried mutiple edits of the device to associate the drive with, nothing works.
The disk used to associate with /dev/sdb1. Now this device no longer exists. Here is what has happened to my /dev/sd* entries:
brw-rw---- 1 root disk 8, 0 2009-10-27 11:08 /dev/sda
brw-rw---- 1 root disk 8, 3 2009-10-27 11:08 /dev/sda3
brw-rw---- 1 root disk 8, 1 2009-10-27 11:08 /dev/sda1
brw-rw---- 1 root disk 8, 2 2009-10-27 11:08 /dev/sda2
brw-rw---- 1 root disk 8, 4 2009-10-27 11:08 /dev/sda4
brw-rw---- 1 root storage 8, 16 2009-11-04 13:00 /dev/sdb
Trying to force association with "/dev/sdb" "/dev/sda5" (or some other number not in use) or "sdb1" (or 2,3,4, whatever) just yields "special device ... does not exist".
Does anybody know how to deal with this?
Does anybody know what package(s) I replaced when the update in question took place? I think I'd like to reverse whatever happened.
And on another note, I think another gnome-based package also recently replaced a package relating to printing. Yesterday I discovered I have printing problems too:
At first there were no printers found. Although cups is supposed to start according to rc.conf, cupsd was not running. I started it manually and then all the printers showed up again, though I cannot print duplex (again, worked fine before). What is going on with these gnome packages?!? Anyone know which package(s) I need to remove (and then what to put back) to make printing work like it used to also?
thanks much.

oddly, fdisk -l shows nothing, even for disks which are mounted (eg. /dev/sda4). when I insert a standard USB thumb drive, the following show up properly:
brw-rw---- 1 root storage 8, 32 2009-11-05 10:50 /dev/sdc
brw-rw---- 1 root storage 8, 33 2009-11-05 10:50 /dev/sdc1
and I am able to mount and use the drive as usual.
The external drive I've been struggling with has xfs for filesystem type. After using the thumb drive, /dev/sdb showed up spontaneously, but no /dev/sdb1. attempting to mount gives:
mount: /dev/sdb is not a valid block device
or
mount: special device /dev/sdb1 does not exist
depending on which device is specified in fstab.
I am thinking that either a) my ability to mount xfs filesystems has somehow been hosed, or b) there is something wrong with drive, which must have spontaneously failed very recently (it is less than 1 yr old, but this happens from time to time).
If the drive is okay, any ideas about how mounting xfs filesystems could have been broken by recent upgrades?
btw, the fstab entry (which worked fine until a couple days ago) is: /dev/sdb1 /mnt/external_1 xfs rw,noauto,user,exec 0 0

Cannot mount volume

Similar Messages

Maybe you are looking for