Cannot mount or run fsck on filesystem

Yesterday, our helpdesk crew had to shutdown our systems due to overheating in our lab. After bringing up one of our servers, one of its filesystems could not be found. Below is what I see from the /var/adm/messages:
Apr 10 12:41:54 unode2 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinf
o@0
Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
4,1 (glm3):
Apr 10 12:41:55 unode2 SCSI bus DATA IN phase parity error
Apr 10 12:41:55 unode2 glm: [ID 663555 kern.warning] WARNING: ID[SUNWpd.glm.pari
ty_check.6010]
Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
4,1 (glm3):
Apr 10 12:41:55 unode2 Target 0 reducing sync. transfer rate
Apr 10 12:41:55 unode2 glm: [ID 923092 kern.warning] WARNING: ID[SUNWpd.glm.sync
widebackoff.6014]
Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
4,1/sd@0,0 (sd45):
Apr 10 12:41:55 unode2 SCSI transport failed: reason 'tran_err': retrying comma
nd
Apr 10 12:41:56 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : PCI IO 2.0 (Rev Id
= c1) Found
Apr 10 12:41:56 unode2 pcipsy: [ID 370704 kern.info] PCI-device: network@1,1, hm
e0
Apr 10 12:41:56 unode2 genunix: [ID 936769 kern.info] hme0 is /pci@1f,4000/netwo
rk@1,1
Apr 10 12:42:01 unode2 genunix: [ID 454863 kern.info] dump on /dev/md/dsk/d2 siz
e 5724 MB
Apr 10 12:42:01 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiv
er Selected.
Apr 10 12:42:01 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : 100 Mbps Full-Du
plex Link Up
Apr 10 12:42:07 unode2 scsi: [ID 243001 kern.warning] WARNING: /pci@6,4000/SUNW,
qlc@3/fp@0,0 (fcp0):
Apr 10 12:42:07 unode2 Failed to create nodes for pwwn=216000c0ff884ad2; error=
5
Apr 10 12:42:08 unode2 scsi: [ID 243001 kern.warning] WARNING: /pci@6,4000/SUNW,
qlc@3/fp@0,0 (fcp0):
Apr 10 12:42:08 unode2 Failed to create nodes for pwwn=256000c0ffc84ad2; error=
5
Apr 10 13:00:35 unode2 pseudo: [ID 129642 kern.info] pseudo-device: tod0
Apr 10 13:00:35 unode2 pseudo: [ID 129642 kern.info] pseudo-device: tod0
Apr 10 13:00:35 unode2 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Apr 10 13:00:35 unode2 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
Apr 10 13:00:36 unode2 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Apr 10 13:00:36 unode2 pseudo: [ID 129642 kern.info] pseudo-device: pm0
Apr 10 13:00:36 unode2 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Apr 10 13:00:36 unode2 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
Apr 10 13:00:38 unode2 There are no devices (controllers) in the system; nvutil
terminated.
Apr 10 13:00:38 unode2 Array Monitor initiated
Apr 10 13:00:38 unode2 RDAC daemons initiated
Apr 10 13:00:39 unode2 /usr/lib/osa/bin/arraymon: [ID 712306 user.error] No RAID
devices found to check.
Apr 10 13:00:39 unode2 rdriver: [ID 400281 kern.notice] ID[RAIDarray.rdaemon.100
1] RDAC Resolution Daemon locked in memory
Apr 10 13:00:39 unode2 rdriver: [ID 400281 kern.notice] ID[RAIDarray.rdaemon.100
1] RDAC Resolution Daemon locked in memory
I cannot run fsck or mount back to what it suppose to be. Looking at previous reports, this is how the file structure use to look:
/dev/dsk/c68t216000C0FF884AD2d0s0 62493372 2142901 59725538 4% /disk6
/dev/vx/dsk/rootdg/vol02 7559245 1602962 5880691 22% /disk1
/dev/md/dsk/d3 4032504 734383 3257796 19% /opt
/dev/vx/dsk/rootdg/vol01 7559245 3388798 4094855 46% /disk0
/dev/vx/dsk/rootdg/vol03 33263336 22259082 10671622 68% /disk2
/dev/md/dsk/d5 6552557 1813979 4673053 28% /export/home
How can I resolve this issue?

As it turns out, someone had turned off the storage array during the shutdown on sunday and no one ever powered back up. So when the server connected to the storage device was booted up, it could not see the file system. But even when I turned on the storage array, the server still could not mount to the filesystem residing there. The server had to be rebooted to re-sync with the storage array.
Our database users can now access the filesystem. Thank you all for your help.

Similar Messages

Cannot mount storage disk after running "reboot -- -r"

I have a server installed Solaris Sparc u4 and integrated with a storage. When executing "reboot -- -r" or "init 6", the storage disk cannot be mounted after system startup again. The output of console said "
obtaining access to all attached disks
mount: /dev/md/emads/dsk/d50 or /home, no such file or directory
I really added item into /etc/vfstab which is "/dev/md/emads/dsk/d50 /dev/md/emads/rdsk/d50 /home ufs 2 yes global,logging ".
But, if I use "reboot" instead, the storage disk can be mounted normally.
I'm so confused. Could you please tell me the cause and solution? Well, I don't wanna use "mountall" every time after the system is rebooted.

in single user mode, I cannot mount it manually
ema31166# mountall
/dev/rdsk/c1t3d0s3 is clean
/dev/md/rdsk/d6 is clean
/dev/rdsk/c1t3d0s1 is clean
/dev/rdsk/c1t1d0s1 is clean
/dev/md/rdsk/d12 is clean
checking ufs filesystems
/dev/md/emads/rdsk/d50: No such device
Can't open /dev/md/emads/rdsk/d50: No such device
/dev/md/emads/rdsk/d50: CAN'T CHECK FILE SYSTEM.
/dev/md/emads/rdsk/d50: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

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

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

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

I can´t run fsck /dev/sda6 is mounted

How I can enter on unique user mode to umount my partition and run fsck. A day before I had it this problem with my archive system, my archlinux was working ok but after shutdown my computer and turn on again I had it this problem. Please I need help with this problem, i´m going insane with this.

Inxsible wrote:
learn to use the edit functionality instead of posting consecutively.
Read the forum rules and abide by them.
joelvilabringuez wrote:is my home partition but anyway it doesn´t work mate
This is the most useless comment. What doesn't work? Were there any errors? Please don't post half assed answers.
In addition, I think posting the exact commands you used would be helpful.

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)

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

[SOLVED] /dev/mapper/ dm : UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY

I'm trying to boot my system from multiple machines using only a USB. I have a PC & MacBook Pro. When I have built & configued my system correctly from my MacBook Pro, I have tried to boot it from PC as well to make sure the boot process has no errors.
Booting from MacBook Pro is completely fine (1st boot). After that, I have tried to boot from a PC and the boot process is also fine (2nd). However, when I went back to MacBook Pro to boot my system again (3rd boot), I get an error:
systemd-fsck: /dev/mapper/<dm_name>: Superblock last mount time (Tue Dec 3 15:25:41 2013,
systemd-fsck: now = Sat Jan 19 18:29:54 2013).
systemd-fsck: /dev/mapper/<dm_name>: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
systemd-fsck: (i.e., without -a or -p options)
I did run fsck and it says:
fsck from util-linux 2.24
e2fsck 1.42.8 (20-Jun-2013)
/dev/mapper/<dm_name> is mounted.
e2fsck: Cannot continue, aborting.
However, when I just run reboot, the error has disappeared but everytime I switch to PC and then go back to MacBook Pro, I get that error and it disappear after I reboot.
Can anyone explain to me why I get that error? is the problem related to time configuration? how to configure it so that it wont get that error again.
I appreciate your help :)
Last edited by heyom (2013-12-03 18:29:52)

Yes, it's related to time config. Apparently, the clock on your PC is correct but the clock on your Mac is very incorrect (Jan 2013). You need to synchronize the clocks.

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.

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.

How to run fsck.vfat for USB-stick during cRIO-9030 boot?

Hi all,
we have a cRIO-9030 with a USB-stick. Sometimes after power loss the USB-stick filesystem (FAT32) gets corrupted and has to be checked/fixed. How can I configure cRIO LinuxRT to do that?
I've checked /etc/fstab, but it looks that the USB-stick is mounted somewhere else. I run mount - here is the line:
/dev/sdc1 on /media/sdc1 type vfat (ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
It would be nice if I can run fsck.vfat /dev/sdc1 every boot or when an error is detected.
Thanks in advance,
Nikolai

Hi NickViz,
My name is Ed form National Instruments Technical Support, I have researched into the topic and found that it is possible to use the 'System Exec.vi' to complete the command during the initialization of your RT application.
You simply need to input your commands as a string just as you would to command prompt/terminal (depending on OS), you can also execute commands via SSH however this is one way communication between the RT application and the command shell.
I have included some links below to articles which describe the methodology as well as give some further explanation into the NI Linux Real-Time OS.
http://digital.ni.com/public.nsf/allkb/AFCAC25164CDBD4C86257C6A00545CD5?OpenDocument
http://digital.ni.com/public.nsf/allkb/9822A3A39B1D0CBB86257C55006B962A
http://www.ni.com/white-paper/14626/en/
I hope this is helpful and you achieve what it is you need, do note you will need to enable SSH scripting as described in the article on using PuTTY for your Real Time device.
Kind Regards,
Ed

Problem running fsck

Hi all,
I have this problem.
When I am trying to run fsck -y on a faulted filesystem I get thos error messeges:
WARNING: /pci@1c,600000/scsi@2 (glm0):
Resetting scsi bus, got incorrect phase from (0,0)
WARNING: /pci@1c,600000/scsi@2 (glm0):
got SCSI bus reset
WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd3):
auto request sense failed (reason=reset)
CANNOT READ: DISK BLOCK 6105626: I/O error
CONTINUE? Y
WARNING: /pci@1c,600000/scsi@2 (glm0):
Resetting scsi bus, got incorrect phase from (0,0)
WARNING: /pci@1c,600000/scsi@2 (glm0):
got SCSI bus reset
WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd3):
auto request sense failed (reason=reset)
I run iostat -En and get the following output:
c0t1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: SEAGATE Product: ST373207LSUN72G Revision: 045A Serial No: 0545332X9K
Size: 73.40GB <73400057856 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
c0t0d0 Soft Errors: 0 Hard Errors: 2 Transport Errors: 2
Vendor: SEAGATE Product: ST373207LSUN72G Revision: 045A Serial No: 054332Z6YR
Size: 73.40GB <73400057856 bytes>
Media Error: 1 Device Not Ready: 0 No Device: 1 Recoverable: 0
Illegal Request: 0 Predictive Failure Analysis: 0
It looks like c0t0d0 has error, can it be a hardware failure?
Thanks ALL!!!

Hi,
Didn't tought about it..
But I can't even query the partition...when I trying to check the fs type it send me all those error messeges again!
I guess it is an hardware failure...!
Thanks..!

Cannot mount certain partitions: /dev/ entries do not exist

Hello all. Strange problem here. First I will describe my disk layout. I triple boot Gentoo, Arch, and FreeBSD. My partitions look like this:
/dev/hda = MAXTOR 6L040J2, ATA DISK drive 40GB
hda1 = shared '/boot' partition
hda2 = gentoo '/' partition
hda3 = gentoo '/usr/' partition
hda4 = gentoo '/home' partition
/dev/hdb = SAMSUNG SP0802N, ATA DISK drive 80GB
hdb1 = shared music partition mounted as /home/music on both Gentoo and Arch
hdb2 = shared swap partition
hdb3 = FreeBSD partition
hdb4 = logical Partition
hdb5 = archlinux '/' partition
hdb6 = shared video partition mounted as /home/music/video on both Gentoo and Arch
Now both gentoo and arch use devfs. From gentoo I can see all partitions in the /dev directory and mount accordingly, however, from Arch I cannot mount my gentoo partitions on /dev/hda, and in fact they do not even exist in the /dev directory. Only /dev/hda1 is visible (the shared boot partition which holds all my kernels regardless of distro).
Running fdisk -l /dev/hda from arch gives me this puzzling output:
Disk /dev/hda: 40.0 GB, 40027029504 bytes
255 heads, 63 sectors/track, 4866 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 4111 33021576 55 EZ-Drive
So it would seem that fdisk thinks that /dev/hda1 takes up the entire drive, and is labeled as 'EZ-Drive'?!?!?!?!?!? I can assure you that running the same command from gentoo gives me the correct partitions and disklabels ie: id 83 Linux
Does anyone have a clue as to what is going on here? This isn't really a big deal at this point, just an interesting annoyance that I would like to discover the cause of.
TIA

I don't know how it could be that the kernels interpret the partition table differently, and I'm certainly not sure that this is what's going on. That's why I suggested loading Arch with the Gentoo kernel. I wouldn't expect the system to be its true self, but merely satesfy the curiosity by checking whether it would see the right partitions (a.k.a. trouble-shooting).
It shouldn't be a problem to test this, unless your Arch root uses a file system that is not built into your Gentoo kernel. If for instance hdb5 is reiserfs and your 2.4 kernel has that as a module, you're probably out of luck regarding my suggestion. If this is the case, you could also try the Arch 2.4 kernel. It can coexist with your current kernel because the kernel packages for the two trees have different names.
pacman -S kernel
Hope this helps,
-bogo

Cannot mount any firewire/USB external drive after software update 10.5.4

After the last software update on 10.5.4 it did not complete the installation, and get stuck at the last step of running installation script for hours. So I have to restart the computer, and it restarted fine. Then I use Disk Utility to check my hard disk, and discovered some file system inconsistency error, so I repaired it (in target disk mode by another Mac). After it is repaired, the file system passed with no error.
But ever since then, I cannot mount any external firewire drive or USB drive. I cannot use Time Machine to backup my disk. I think my firewire and USB ports are fine because I can restart my iMac in target mode and connect to my MacBook via firewire, so the hardwire ports are functional, except that it seems 10.5.4 cannot detect or mount any external drive after the failed software update.
Does anyone encounter similar problem? How can I fix it? I have my disk backed up by TimeMachine but I cannot restore it if it won't let me mount my TimeMachine disk. Is there any other way other than completely reinstall 10.5 from scratch?

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".

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.

Cannot mount or run fsck on filesystem

Similar Messages

Maybe you are looking for