Virt-install cannot mount nfs directory

Hi all,
I'm trying to use ovms but I cannot create any virtual machine.
I successfully installed OVMS; I disabled iptables to avoid network problems.
I created a dvd from Oracle Unbreakable EL 5.0 cds on a different machine.
The dvd image is shared by a linux CentOS box. The ISO image is inside /opt/tmp_os_isos/50 so I did
service nfs start
mkdir /mnt/dvd50
chmod a+rwx /mnt/dvd50
mount -o ro,loop /opt/tmp_os_isos/50/Enterprise-R5-GA-Server-i386-dvd.iso /mnt/dvd50/
exportfs *:/mnt/dvd50
and on the ovms server I did:
[root@ovms ~]# virt-install
What is the name of your virtual machine? giallo2
How much RAM should be allocated (in megabytes)? 512
What would you like to use as the disk (path)? /virtpcs/dischi/giallo
How large would you like the disk (/virtpcs/dischi/giallo2) to be (in gigabytes)? 30
Would you like to enable graphics support? (yes or no) no
What is the install location? nfs:10.10.10.242:/mnt/dvd50
And I always end up with the error
That directory could not be mounted from the server.
If I try to run
[root@ovms ~]# mount.nfs 10.10.10.242:/mnt/dvd50 /mnt/50
it works!
I also tried to build adifferent dvd iso, or to uso a OEL 4.4 dvd iso (taken from an original working oracle dvd) but I always end up with the same error
Where am I wrong?
thanks, andrea

I realized this problem was somehow related with the ovms installation: the pc I installed ovms on has two network card; when I installed ovms I configured eth0 via DHCP (eth0 is linked to the office network and to internet) and I configured eth1 with a static IP (eth 1 is connected to a "private" network made by 2 more pc).
I also choosed to manage ovnms via eth1 (the network card witch has a statis ip), and everything regardind ovms has always been done via eth1.
Now I reinstalled ovms and I choosed to manage it via eth0 (si I put a static ip address on eth0) and everything seems working: I'm just installing OEL5.0 via nfs without any problem (I hope... :-) )
andrea

Similar Messages

Can ssh into client iMac but cannot mount home directory ...

I've got a server running 10.4.11 and a bunch of client iMacs (10.5.n). If I ssh into a client iMac it lets me log in but cannot mount my home directory (which lives on the server). Obviously ssh is getting my credentials from the server but isn't getting (or cannot get) the information to mount my disk. If I log in through the gui on the client it all works fine. I suspect this is less of an error and more of a design. Is there a way to get the clients to mount my home when logging in with ssh? If not then Apple presumably has a reason for disallowing this behaviour. Is there a way around this? Perhaps with mount_afp?
We want to be able to log into many client iMacs at once to run computations on them. Eventually we want to do this on a suite of XServes and XGrid. This is all very easy with linux and nfs and I was expecting the same sort of ability through OS X. I know that I can export everything from the server with nfs (though that may not solve my problem) but I only have the one system and multiple users and I can't really experiment while they are connected.
Suggestions? Comments? If there are obvious examples of this elsewhere please point me toward them.

Well it's never worked that way for me. Do you actually use this method to log in?
I've gone through all of the server logs, watching what gets added as I log on to a client. I don't see anything there that suggests it is even attempting to mount the home directory. I also watched on the client and didn't see any errors. When I ssh into a client I see the following message on the terminal, "Could not chdir to home directory /Network/Servers/server.some.place/Volumes/R1/UsersR1/username: Unknown error: 118" This suggests that the client knows where my home should be but doesn't know how to mount it.
I have enabled the basic setup on my server. User accounts have Home URLs like "afp://server.some.place/UsersR1/username" and Full Paths like "/Network/Servers/server.some.place/Volumes/R1/UsersR1" (R1 is a RAID disk). UsersR1 has been made into a Share Point and Server Admin tells me that the disk "will be automatically mounted using the AFP protocol as /Network/Servers/R1 on client machines". This part doesn't seem to be true as when I log into a client through the GUI the actual path that is mounted as my home is /Network/Servers/server.some.place/R1" (pwd in my home directory returns /Network/Servers/server.some.place/Volumes/R1/UsersR1/username which is a actually rather inconvenient).
Under the Advanced tab in the Workgroup Manager, Accounts pane, I've got "Allow simultaneous login on managed computers". This seems to work but also seems only to apply to the GUI, that is I can log onto several clients at once.
How do I ask a client machine what home directory information it is getting from the server for any particular user? Is there some setup on the client machines that will enable automatic mounting of homes through ssh? On the clients, the Directory Utility, which I have used to connect the client to a Directory Server, has a Mounts pane which allows me to "Edit automatic NFS mounts for this computer". I am not exporting any NFS from the server, but perhaps this is the way to make it work?
Perhaps what I want to requires Kerberos? I don't have that enabled.
When I have done this on a cluster of linux machines I exported the home directory from the server with NFS (exportfs) and then, using NIS and automount on the clients it "just worked". It was very simple. If it is supposed to work with Macs and OS X, it may be simple but it's not obvious.

Grub-install: "cannot find EFI directory" (CSM mode)

Hi,
I'm trying to install grub on the mbr with 'grub-install /dev/sdb', but I get "cannot find EFI directory'. I have an Asus laptop with secure boot disabled and CSM enabled (I *need* CSM because otherwise - I don't know the reason - I can't boot from USB/disk). I have Windows 7 installed (/dev/sdb2) and I know there's a small partition (/dev/sdb1) which was created during Windows 7 installation which contains a 'Boot' directory, a 'bootmgr' file and other stuff. Now, my purpose is to dual boot Windows 7 and Arch while the BIOS is in CSM mode. The problem is that a simple grub-install /dev/sdX does not work as expected (under Gentoo, it simply worked out-of-the-box). By now, I can chroot into my fresh Arch installation (/dev/sdb3). Another thing: possible targets for grub-install are 'i686-pc' and 'x86_64-efi'; when running grub-install the program automatically selects 'x86_64.efi' as target. I don't know if it's correct (I do have an AMD64 laptop, just to clarify). Thanks in advance.

tant0c1b0 wrote:Hi,
I'm trying to install grub on the mbr with 'grub-install /dev/sdb', but I get "cannot find EFI directory'. I have an Asus laptop with secure boot disabled and CSM enabled (I *need* CSM because otherwise - I don't know the reason - I can't boot from USB/disk). I have Windows 7 installed (/dev/sdb2) and I know there's a small partition (/dev/sdb1) which was created during Windows 7 installation which contains a 'Boot' directory, a 'bootmgr' file and other stuff. Now, my purpose is to dual boot Windows 7 and Arch while the BIOS is in CSM mode. The problem is that a simple grub-install /dev/sdX does not work as expected (under Gentoo, it simply worked out-of-the-box). By now, I can chroot into my fresh Arch installation (/dev/sdb3). Another thing: possible targets for grub-install are 'i686-pc' and 'x86_64-efi'; when running grub-install the program automatically selects 'x86_64.efi' as target. I don't know if it's correct (I do have an AMD64 laptop, just to clarify). Thanks in advance.
You are telling the system to act like it is a BIOS system as far as the boot process goes but I don't think you are using a disk with a MBR, master boot record partition table. Is your disk actually GPT? This is a common gotcha when trying to use CSM mode on a UEFI based system since UEFI systems come with GPT disks. I believe this describes Grub installation in your configuration.
https://wiki.archlinux.org/index.php/GR … structions
To be clear though, I don't think this is a good direction to go. This isn't keeping things simple though that may have been why you chose to do it. I don't have enough information to know but it sounds like your disk expected to be in a UEFI system and was created with a GPT partition scheme. I would use it that way for Arch and for Windows if you choose to have that installed. I think it creates unneeded complexity to create a hybrid UEFI/BIOS configuration. I would always have all disks using the same partition scheme (the reason you can't boot "USB/disk" may be that you need GPT) and all OS's booting UEFI on a UEFI system.

Cannot mount NFS shares using the Finder

Hello all!
I have a directory structure on a OpenSuse NFS Server which I like to browse/read using my MAC OSX 10.5.6. It works like a joy when I am mounting the NFS share on the command line using "sudo":
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
However, this is kind of unconvenient as I need to start Terminal and sudo always asks me for the root password. I would appreciate to mount the NFS share just as I mount afp shares using the Finder. But the NFS share is neither searchable using the Finder nor does it show up in the list of host in the side bar of the Finder.
Does anyone has an idea how to solve that? Thx for your information!

The problem is most likely that your NFS server requires that connections come from reserved ports but you can't connect that way from the Finder GUI.
Your example:
sudo mount -o resvport nfshost:/full/path/NFS/share /My/mount/point
shows that you need to use "-o resvport" and that you need to do the mount as root. (This is because the networking stack requires you to be root to get a reserved port.) When you try to mount it via the Finder, you can't specify any mount options like "-o resvport" and even if you could the mount would fail because the Finder isn't running as root.
My first suggestion would be to change the configuration of your server to not require clients to use reserved ports for the NFS protocol. Unfortunately, Linux chooses to call that option "insecure" even though requiring the use of reserved ports (using "secure") doesn't actually make NFS more secure.
Alternatively, you could configure the mount to be performed by something that does do the mount as root - e.g. automount/autofs. You can do this by configuring the mount on Directory Utility's "Mounts" section... you'll want to add "resvport" to the "Advanced mount options" field.
HTH
--macko

Cannot mount nfs shares

Hello,
since Sunday I'm unable to mount NFS shares:
mount.nfs: No such device
The server-side is working fine, I can mount all shares from my FreeBSD Desktop machine.
I'm using netcfg and start rpcbind and nfs-common upong connection before mounting NFS shares (via netfs). Is this maybe related to some recent pacman updates? It was working flawless just until Sunday.

As it turns out, It now works. I did load the nfs module manually during my troubleshooting but it was already loaded or built into the kernel or whatever.
The thing that made it work is changing the nfs mount lines in /etc/fstab from the hostname of the server to the ip address of the server. I don't know why that worked on both machines since I could ping the hostname of the nfs server which is a Freenas server and it always worked before.
@ jasonwryan
rc.d start rpcbind && rc.d start nfs-common
start fine after stopped and restarted. Have you replaced portmap with rpcbind in pacman? rpcbind superceded portmap a while back. gl.
@.:B:.
lol, snide remark succesfully detected. In my defense I was half guessing and half sniding (or some percentage thereof). I have to admit I do get a bit snippy over this since nfs is necessary for my little clients to run mpd and I gets a bit cranky when I gots no musics! Fueling my frustration, it seems I have to chase down nfs problems frequently after "pacman -Syu".

New zshell terminal always opens in mounted NFS directory

Whenever I add NFS share in /etc/fstab, every time I open new terminal urxvt (zshell) it automatically goes to NFS share directory instead of ~. What could it be? Thanks in advance!

Without any of your config files, it is impossible to tell.
Please read How To Ask Questions The Smart Way and pastebin the relevant files if you want assistance.
Moving to NC...

Virt-install does not find mount

Trying to use virt-install and mount the iso.
After mounting the iso and answering virt-install prompts
i see
Starting install.....
mount : can't get address for /134.154.231.244
umount /var/lib/xen/xennfs.ayxrcl:not mounted
unable to mount NFS location!
I can mout it manually.

Trying to use virt-install and mount the iso.
After mounting the iso and answering virt-install
prompts
i see
Starting install.....
mount : can't get address for /134.154.231.244
umount /var/lib/xen/xennfs.ayxrcl:not mounted
unable to mount NFS location!
I can mout it manually.1) make sure you are installing a paravirt vm, i.e.
-- paravirt
1) check the --location parameter, it should look like,
--location=nfs:134.154.231.244:/mnt/el5
2) make sure the para installation kernel exists in your mount point. i.e.
there must be a dir images/xen/ under /mnt/el5

Virt-install by nfs

Currently I install the RedHat Enterprise Linux 5 and after using virt-install command, i successfully go in to the install menu, but I facing a problem "That directory could not be mounted from the server" when I choosed the nfs as the installation method.
Anybody can tell me what's wrong with it????????
Thank you.

I realized this problem was somehow related with the ovms installation: the pc I installed ovms on has two network card; when I installed ovms I configured eth0 via DHCP (eth0 is linked to the office network and to internet) and I configured eth1 with a static IP (eth 1 is connected to a "private" network made by 2 more pc).
I also choosed to manage ovnms via eth1 (the network card witch has a statis ip), and everything regardind ovms has always been done via eth1.
Now I reinstalled ovms and I choosed to manage it via eth0 (si I put a static ip address on eth0) and everything seems working: I'm just installing OEL5.0 via nfs without any problem (I hope... :-) )
andrea

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

Cannot import from NFS directory: tree not expandable

I am using Lightroom 4.3 on Mac OS X Mountain Lion (10.8.1).
I am unable to import files from an NFS-mounted directory because the folders lack rocker nodes, so I can't navigate through the tree to my existing Photos directory. It isn't practical or desirable to import the entire NFS filesystem.
I originally had the filesystem mounted with these options:
freenas:/mnt/vol_home/nfs_home on /Volumes/home (nfs, nodev, nosuid, automounted, nobrowse)
And while I can see the root of the filesystem in the left side of the import window, and while the directories have little folder icons next to them, the little triangular rockers next to them are greyed out. If I picked a directory, and checked "include subfolders", then Lightroom would recurse through the tree and show me all of the pictures. But I don't want to import my entire filesystem. I need to navigate down the tree to my photo directory, but the rockers are "greyed out". It's difficult to see them greyed out when the background is grey too, but they are there, faint as they are.
So, I thought maybe the "nobrowse" option had something to do with the inability to navigate. I used "NFS Utility" to remove the "nobrowse"option, and remounted the filesystem. It is now mounted with these options:
freenas:/mnt/vol_home/nfs_home on /Volumes/home (nfs, nodev, nosuid, noatime)
And while I can see the root of the filesystem in the left side of the import window, and while the directories have little folder icons next to them, [most of] the rockers next to them are still greyed out. Here is a screenshot of the import window, alongside a Finder window, which of course lets me open the rockers and navigate just fine. The fact that Finder works implies to me that it isn't a permissions problem. Of course I can also "cd" using the terminal commandline. The navigation problem appears to be limited to the Lightroom application.
Hopefully you can see from this screenshot, that only the "rbrown" folder has a working rocker. The other rockers are greyed out (which is really difficult to see). I need to navigate below "rbrown", but cannot. Finder can open the "family" rocker, and can open the subfolders under "rbrown" just fine.
Why does lightroom refuse to let me open these folders?
Thanks in advance.

I have discovered a way to get Lightroom to navigate my NFS directory! Using the help I learned here:
http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_3_import_from_and_to_nfs _mounted_filesystem_does_not_work
I discovered that not only did I need to use a nonstandard mount point (I ultimately chose "/nas"), but that I also needed to mount with the "rdirplus" option (aka "Use ReaddirPlus NFSv3 feature"). I was using the German 3rd party package "NFS Manager" to help me mount and unmount quickly, while enabling and disabling options left and right to try to figure this problem out. It also allows me to specify it as an "automount". Prior to Mac OS X 10.8 (mountain lion), there was a GUI in Disk Utility to allow me to specify NFS mounts, but as of mountain lion, the button is gone, for reasons unclear.
Anyway, I got lightroom to navigate my NFS server by mounting on /nas, and by specifying the 'rdirplus' option in the mount command.

Reshare mounted NFS Home Directory

Hi there,
I have a XServe with Leopard Server 10.5.8 installed.
Open Directory works fine, I mean users are known through the network and they can log on every computer with ssh, their home directory is well automounted by clients. Their home dirs are stored locally on the server.
I would try something new in order to win space:
1. create user dirs locally on the clients
2. export them on the network
3. mount them through NFS or AFP on the server and reshare it on the network as user dir.
item 1. is done : the local user get the uid and gid of the network user, permissions are OK on his home dir.
item 2. is OK : via NFS
item 3. seems OK because I mkdir /AFP-Users where I mount via NFS remote user dir (e.g. bob). Then I export /AFP-Users as automatic Users Home Dirs in addition to /Volumes/External/User where native OD accounts are.
I have specified in OD that Home dir of bob is nfs://server/AFP-Users/bob.
It works fine if I make a su - bob on the server : files are here and bob is able to write.
bob is able to ssh on every computer on the network, no error msg on login but no files! And no permissions to write.
If someone has an idea...
Thanks,
joe

Hello,
in the meantime, I have looked for Internet for my solution, nobody speaks about this precise problem.
I tried to simply mount AFP directory from a client to another, but unable to have permissions on the Terminal because the owner of the mounted AFP is local admin instead of the OD user...
I would very appreciate if anyone has an beginning of an idea.
Thanks,
joe

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 root during Solaris install on SPARCengine ULTRA axi

I use boot cdrom which sucessfully formats swp partition and copies files to hd. But then when I reboot I get the following:
SPARCengine(tm)Ultra(tm) AXi (UltraSPARC-IIi 440MHz), PS/2 Keyboard
OpenBoot 3.10.10 ME, 512 MB memory installed, Serial #10660686.
Ethernet address 8:0:20:a2:ab:4e, Host ID: 80a2ab4e.
ok boot disk4
Boot device: /pci@1f,0/pci@1/scsi@1/disk@4,0 File and args:
SunOS Release 5.8 Version Generic_108528-11 64-bit
Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved.
Cannot mount root on /pci@1f,0/pci@1/scsi@1/disk@4,0:a fstype ufs
panic[cpu0]/thread=10408000: vfs_mountroot: cannot mount root
0000000010407970 genunix:vfs_mountroot+70 (10435c00, 0, 0, 10410920, 10, 14)
%l0-3: 0000000010435c00 00000000104391c8 000000002f000000 0000000010435dc0
%l4-7: 0000000000000000 00000000104136b8 00000000000b7bf6 0000000000001bf6
0000000010407a20 genunix:main+94 (10410168, 2000, 10407ec0, 10408030, fff2, 1004
ef88)
%l0-3: 0000000000000001 0000000000000001 0000000000000015 0000000000000ea5
%l4-7: 0000000010428c28 0000000010462320 00000000000cd920 0000000000000540
skipping system dump - no dump device configured
rebooting...
Resetting ...
PS: I have recently reset the NVRAM on this machine not sure if there are any env settings I should have setup in OBP (I reset HOST ID and MAC-ADDRESS).

disk@0,0:a is slice/partition 0
disk@0,0:b is slice/partition 1
I'm not sure where you told it your swap slice was going to be. Looks like slice 1. Mini-root gets installed in slice 1 and then the install begins from there.
In the future, if you just "boot cdrom" from disk 1 of 2 you won't run into these issues.

Cannot mount ITU floppy at install

When I try and update the sd driver at install time, all it says is "cannot mount floppy".
Motherboard is a Asus P5GD1
2GB RAM
Adaptec 2810SA
6x250gb Drives
I am using Solaris 10 1/06.
Any help would be greatly appreciated.

Have you tried to put the following in /etc/PolicyKit/PolicyKit.conf
<?xml version="1.0" encoding="UTF-8"?> 
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.power-management.*">
<return result="yes"/>
</match>
</config>

Cannot mount disk from a Sol8 system via nfs

Hi All
I have Sol10 up and running. I noticed that it was not very easy to mount a linux disk with nfs. I found out that I had to add -o vers=3. Now I would like to mount a disk from a Sol8 system
So far I only managed to get:mount sol8sys:/storage /mnt/sol8sys
nfs mount: sol8sys:/storage: Permission deniedThis gives me the impression something is not configured well on the Sol8 system.
Well here is some info about that $ exportfs
- /storage rw=serv1:serv2:sol10sys,ro=serv3 "Storage Array"
sol10sys represents the system I'm trying to mount on.......
Any suggestions why I cannot mount this disk ? or give me some hints on how to proceed solving this problem!
Thanks a lot
LuCa

The reverse resolution has to match exactly. Most machines are in DNS, so the reverse resolution will be a name, not an IP address. Therefore they won't match.
Also, how were you specifing the IP address? You can't just throw an IP address in an access list. From the share_nfs man page we can see that an access list contains:
hostname, netgroup, domain name suffix, or network. 'IP address' isn't a valid member.
Darren

Virt-install cannot mount nfs directory

Similar Messages

Maybe you are looking for