Duplicate Mount Point "Documents 1" after improper reboot

Hi, I recently cold rebooted my SR-MBP (running 10.5.6), and on logging back in, I discovered to my utter surprise that my desktop had been restored to Factory State with all my preferences lost.
I have my HDD set up with two partitions. Partition 1 - "Macintosh HD" is the Leopard partition, and Partition 2 - "Documents" is where I had moved my HOME folder, and therefore contains all my Preferences, Documents, etc.
On closer examination, using Disk Utility I found that the "Documents" Partition had been renamed to "Documents 1", and my Home folder was mapped to /Volumes/Documents/Home. I remapped it to /Volumes/Documents \1/Home (the current renamed location) and it didn't solve the issue.
I found Apple's help on the issue http://support.apple.com/kb/TA24241?viewlocale=en_US . It suggests among other things to move the contents of the false Mount Point to /
[quote]Type this command, followed by Return, to move the contents of the false mount point:
mv "Documents 1" / [/quote]
I am not too sure of this step, does this move the contents (which would take forever for me since I have a 400 GB partition - nearly full), or just create a mount point? If it actually moves the contents, I would rather reinstall Leopard, as that would be faster for me. But I guess I am lost here... how does this work? Any help would be highly appreciated.

Just to add some detail here, in case this help those who come across this thread:
1. If the duplicate mount point is associated with an external drive, eject the drive or restart the Mac with the drive powered off.
2. Go to Finder by toggling Command + Tab across available selections.
3. Select Go > Go to Folder... (or press Shift + Command + G)
4. If necessary, type /Volumes in the displayed dialog box, and press Go.
5. You should see a folder in the displayed list with the offending name; right-click it, and select Move to Trash.
That should do it!
Good luck!

Similar Messages

Repair of duplicate mount points in /Volumes

I have an external Maxtor (with 4 partitions)
After installing the Security Update 2008-001 the drive will not mount.
Opened disk utility and partitions would not mount or unmount
Opened a terminal session and found a duplicate mount point in /Volumes
From terminal session:
kdavis-MacBookPro:/Volumes kdavis$ pwd
/Volumes
drwxrwxrwt 8 root admin 272 Mar 4 20:24 .
drwxrwxr-t 32 root admin 1190 Mar 4 15:41 ..
drwxr-xr-x 15 kdavis kdavis 612 Feb 25 14:16 Backup
drwxr-xr-x 14 kdavis kdavis 578 Jan 10 15:34 Data
lrwxr-xr-x 1 root admin 1 Mar 4 15:41 MAC HD -> /
drw------- 3 root admin 102 Feb 28 21:21 Media
drwxr-xr-x 16 kdavis kdavis 646 Feb 25 12:45 Media 1
drwxr-xr-x 10 kdavis kdavis 442 Jan 24 13:46 Storage
What do I do?
Apparently the security update assigned 'root' to the Media partition
Any help here is appreciated

Unfortunately, I don't have a fix, but I have the same problem with a shared volume from OS X server. I have three copies of the volume 'Shared Files 2'. Two of the copies are there even when the volume is not mounted and the actual mount gets names 'Shared Files 2-2'. This causes some things not to work properly. For example, applications will not return to the previously selected directory on that volume. I noticed the duplicate soon after this problem began (when there was only one duplicate), and now there are two duplicates.

Mount point permission problems after LU

I've upgraded 3 6800 domains from Solaris 9 12/02 to 12/03 in the past few days. I'm seeing a problem on each one after the upgrades. If a normal user enters a filesystem, /var for example, and runs pwd, they get back:
pwd: cannot determine current directory!
If they df -k they get: df: cannot canonicalize .: Permission denied
The problem seems to be based on the permissions of the underlying directories for those mount points. I was able to boot single-user, umount -f /var and ls showed the permissions to be 700. I changed them to 755 and everything works fine.
Has anyone run into this before? I'd like to know how to prevent it. Now I'm going to have to boot cdrom in order to change the permissions of /usr and others, it kind of defeats the purpose of live upgrades if you just have to take it down again to change the permissions.

I'm experiencing a similar issue on a few of our servers that were recently Live Upgraded from Solaris 8 to Solaris 9.
MmmK $ ls -l / | grep var
drwxr-xr-x 44 root sys 1024 Jul 25 17:24 var
MmmK $
MmmK $ cd /var ; pwd
/var
MmmK $
MmmK $ cd /var ; df -k .
df: cannot canonicalize .: Permission denied
MmmK $
MmmK $ cd /var ; sudo df -k .
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s4 2054529 1432220 560674 72% /var
MmmK $
I haven't been able to procure a maintenance window yet to try bringing up the server in maintenance mode and verifying the mount point permissions.
This is just another example of why I dislike upgrades..
Cheers,
Mark

New-Partition assignes driver letter to mount point after reboot.

Trying to create a series of mount points using powershell on Server 2012 R2. When I have used diskpart in the past I could initialize the disk, create a partition, format a volume and assign a mount point without assigning a driver letter to the drive.
When I try to do the same thing in Powershell on Server 2012 R2, everything looks great until I reboot. Every partition I created and assigned as a mount mount gets a driver letter added to it... I am using mount points to avoid drive letters. Is there a way
to prevent this behavior. The following is an example:
Get-Disk 3 | Initialize-Disk -PartitionStyle GPT
Get-Disk 3 | new-Partition -UseMaximumSize -AssignDriveLetter:$False | Format-volume -confirm:$False
Add-Partitionaccesspath -DiskNumber 3 -Partition 2 -AccessPath c:\someFolder
Everything looks good at this point with no driver letter assigned. Rebooting adds a driver letter to the volume with no impact on the mount point... Is there a way to suppress the driver letter assignment?

Figured it out... It appears that this part works fine:
Get-Disk 3 | Initialize-Disk -PartitionStyle GPT
$Part = Get-Disk 3 | new-Partition -UseMaximumSize -AssignDriveLetter:$False
$Part | set-partition -NoDefaultDriveLetter:$True
$Part | Format-volume -confirm:$False
If you look at the output of Get-Partition the NoDefaultDriveLetter value is TRUE. After running Add-PartitionAccessPath it changes to FALSE. You can set it back with the Set-Partition command:
Get-Partition -DiskNumber 3 -Partition 2 | add-PartitionAccessPath c:\SomePath -passthru | set-Partition -NoDefaultDriveLetter:$True
I had a bunch of them to do so I used the following:
Function Config-Disk {
[cmdletbinding()]
Param(
[INT]$Disk,
[INT]$Partition = 2,
[String]$Label,
[String]$MountPoint
Get-Disk $Disk | Initialize-Disk -Partitionstyle GPT
Get-Disk $Disk | New-Partition -UseMaximumSize |
Format-Volume -FileSystem NTFS -NewFileSystemLabel $Label -Confirm:$False
Add-PartitionAccessPath -DiskNumber $Disk -PartitionNumber $Partition -AccessPath $MountPoint -Passthru |
set-Partition -NoDefaultDriveLetter:$True
MD "c:\SomeLocation1"
MD "c:\SomeLocation2"
Config-Disk -Disk 3 -Label "SomeLabel1" -MountPoint "c:\SomeLocation1"
Config-Disk -Disk 4 -Label "SomeLabel2" -MountPoint "c:\SomeLocation2"

Duplicate Outputs proposed in Billing Document unexpectedly after 3 months

We are facing a weird problem in some of our billing documents. After the billing document has been saved and the EDI output ZEDI issued, some days later (or even some months later), 2 or 3 duplicate outputs have been proposed (automatically ?) and the IDOCs also have gone out of the system. But the status of the duplicate outputs remain in "Yellow" status and their Processing Log does not contain the new IDOC #s but the original IDOC # that was sent first.
We are at a loss to determine root of issue, Users don't remember changing the billing documents at these times but even if they did, the "Multiple Issuing" checkbox is not selected in the Output Type "ZEDI" and hence, outputs should not have been proposed.
Has anyone faced such an issue before ?
I have tried to paste some logs below:
Output Screen:
              Output     Description Medium     PF     Part#     Language     Proc Date          Proc Time     Date/Tim
duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
duplicate ZEDI     EDI Invoice     EDI     BP     266     EN                    00:00:00     4
original    ZEDI     EDI Invoice     EDI     BP     266     EN     05/13/2010     00:56:37     4
When I do a "Determination Analysis" in Output Screen for this faulty billing doc, I get the following..
Z1EX     502     Output ignored (requirement 962 not fulfilled)
Z1PA     502     Output ignored (requirement 962 not fulfilled)
ZCRE     540     Output not found
ZED2     524     Access not made (initialized field)
ZEDI     541     Output found
ZLDO     540     Output not found
The NAST entries for these outputs are follows:
Object key     Message type     Message partner     Created on     Created at     Message manually     Processing date     Processing time     Response date     User name     Processing status     Output Device     Spool request name     Suffix 1     Suffix 2     Automatic     Recipient
92494146     ZEDI     266     5/13/2010     0:56:37          5/13/2010     0:56:37          BATCHADM     1                         X
92494146     ZEDI     266     9/9/2010     8:45:26     X          0:00:00          5ECND6     0     AdobePDF     84526     MPDF     20100909     X     5ECND6
92494146     ZEDI     266     9/9/2010     8:46:09     X          0:00:00          5ECND6     0     AdobePDF     84609     MPDF     20100909     X     5ECND6
92494146     ZEDI     266     9/9/2010     8:59:20     X          0:00:00          QZL49N     0     AdobePDF     85920     MPDF     20100909     X     QZL49N

Hi,
I am getting the same issue. Did you solve this issue? If yes, please share your solution.
Best Regards,
Mayank Malpani

Built in rule in Linux to prevent additional space after 90% of mount point

We have an RHEL instance on VMware which uses RAID configuration for storage on SAN device. There is an observation with regard to the virtual instance on which our Oracle database is hosted that one of the mount points on which backup is stored starts giving trouble after the spaces reaches 90% in the way that the Oracle backup fails. There is another virtual machine on which there is no problem even if the spaces crosses 90%. Is there something like a rule built in into the file system that could prevent an attempt to write something on it once it reaches 90%?
I hope I have been able to explain the problem that can a rule be built into the file system which prevents writing to it once it reaches 90%.
Requesting a reply to my query.
Regards

Disk space can be restricted by implementing disk quotas which alert a system administrator before a user consumes too much disk space or a partition becomes full. Disk quotas can be configured for individual users as well as user groups.

After Effects Alert when opening (Error: Mount Point list is empty)

I am so confused right now. I have searched everywhere for a solution to no avail. I have a brand new Mac Pro 2.7 Ghz 12-core intel Xeon e5 with 32 gigs of ram. I installed Reelsmart's Motion blur and when I tried to re-open After Effects I got an After Efects Alert that reads.
Last log message was: <140735179719440> <EAMountPoints> <0> Error: mount point list is empty
Generating crash log, which may take a few minutes.
Can anyone help please! I'm on a tight deadline and I'm grounded.
Thank you, thank you!!

What exact version of AE (down to the last decimal point)?

Mount point ownership changed to root after GI install

version:11.2.0.3
Platform : Oracle Enterprise Linus 5.6
I succesfully installed Grid infrastructure. RDBMS software is yet to be installed.
Following are the Software location variables for Grid Infrastructure.
ORACLE_BASE=/u01/grid
ORACLE_HOME=/u01/app/11.2.0.3/grid
After the succesful installation, I've noticed that /u01 mount point's ownership has been changed from oracle:oinstall to root:oinstall.
Is this normal ?

/u01 should be root:root.
/u01/app should be root:root.
I don't know why your top-level directory has oinstall as the group owner. That just seems wrong. I ran some tests and it allows grid to change and delete other people's directories located under /u01.
I recommend you change ownership of /u01 to root:root. Do not use the -R option because you don't want to mess up the sub-directories.

Having issue restarting database after switching mount point

We needed to change the mount point of the disk that has our mount points, so instead of going to /opt, it going to /opt/san/mdb4. I have created a control file to use to start up the database, but I'm still having issues. Here is part of the control file:
CREATE CONTROLFILE REUSE SET DATABASE "INVEST" RESETLOGS NOARCHIVELOG
MAXLOGFILES 64
MAXLOGMEMBERS 2
MAXDATAFILES 254
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 (
'/opt/san/mdb4/db02/oradata/INVEST/redo01a.log',
'/opt/san/mdb4/db03/oradata/INVEST/redo01b.log'
) SIZE 50M,
etc....
DATAFILE
'/opt/san/mdb4/db02/oradata/INVEST/XXX.dbf',
'/opt/san/mdb4/db03/oradata/INVEST/XXX01.dbf',
'/opt/san/mdb4/db07/oradata/INVEST/XXX02.dbf',
'/opt/san/mdb4/db07/oradata/INVEST/XXX03.dbf',
'/opt/san/mdb4/db03/oradata/INVEST/XXX04.dbf',
'/opt/san/mdb4/db03/oradata/INVEST/XXX05.dbf',
'/opt/san/mdb4/db03/oradata/INVEST/XXX06.dbf',
etc...
CHARACTER SET UTF8
All of the files are in the correct spot. I have also edited the init.ora file so that the directories are correct. This is the error that I get every time:
CREATE CONTROLFILE REUSE SET DATABASE "INVEST" RESETLOGS NOARCHIVELOG
ORA-01503: CREATE CONTROLFILE failed
ORA-00449: background process 'DBW0' unexpectedly terminated with error 7446
ORA-07446: sdnfy: bad value '' for parameter .
I am running Oracle 8.1.7 on Sun Solaris 8 (SunOS 5.8).
Does anyone have any idea what is going on? Let me know.

According to error message you have syntax error in your create statement. double check it.
ORA-07446: sdnfy: bad value 'string' for parameter string.
Cause: The directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.

Changing Oracle Mount Point After Installation Is Completed.

How easy is it to change an Oracle Mount Point once an SAP installation has been completed? Reason I am asking, is another Basis person believes it's easier to wipe the partition and reinstall.

Hello,
Yes this is OK (for SAP/Oracle) and easy for unix team too. You please shut down SAP and Oracle completely and Unix expert can change the file system. But be careful that the exact mount point 'name' should remain intact. For e.g. '/oracle/SID' is a mount point and if you want to change the file system or mount this particular 'directory' onto a different filesystem/partition then the 'mount point name' i.e. 'oracle/SID' should remain same - as required by oracle/sap to run.
Thanks

Automatic re-mount of networked volumes after reboot

Hello.
Does anyone know if its at all possible to automatically re-connect network volumes after a reboot? Or if there's an app out there to do just that?
I really don't want to have every network volume (I have LOTS) in the dock...

Yes this works, but I have been unable to find out how to do this without opening the root of the volumes after the reboot. I tried "Hide Item" in the Login Items control panel, but to no avail.
Anyone have any ideas?

ZFS 7320c and T4-2 server mount points for NFS

Hi All,
We have an Oracle ZFS 7320c and T4-2 servers. Apart from the on-board 1 GB Ethernet, we also have a 10 Gbe connectivity between the servers and the storage
configured as 10.0.0.0/16 network.
We have created a few NFS shares but unable to mount them automatically after reboot inside Oracle VM Server for SPARC guest domains.
The following document helped us in configuration:
Configure and Mount NFS shares from SUN ZFS Storage 7320 for SPARC SuperCluster [ID 1503867.1]
However, we can manually mount the file systems after reaching run level 3.
The NFS mount points are /orabackup and /stage and the entries in /etc/vfstab are as follows:
10.0.0.50:/export/orabackup - /orabackup nfs - yes rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,vers=3
10.0.0.50:/export/stage - /stage nfs - yes rw,bg,hard,nointr,rsize=131072,wsize=131072,proto=tcp,vers=3
On the ZFS storage, the following are the properties for shares:
zfsctrl1:shares> select nfs_prj1
zfsctrl1:shares nfs_prj1> show
Properties:
aclinherit = restricted
aclmode = discard
atime = true
checksum = fletcher4
compression = off
dedup = false
compressratio = 100
copies = 1
creation = Sun Jan 27 2013 11:17:17 GMT+0000 (UTC)
logbias = latency
mountpoint = /export
quota = 0
readonly = false
recordsize = 128K
reservation = 0
rstchown = true
secondarycache = all
nbmand = false
sharesmb = off
sharenfs = on
snapdir = hidden
vscan = false
sharedav = off
shareftp = off
sharesftp = off
sharetftp =
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1
default_group = other
default_permissions = 700
default_sparse = false
default_user = nobody
default_volblocksize = 8K
default_volsize = 0
exported = true
nodestroy = false
space_data = 43.2G
space_unused_res = 0
space_unused_res_shares = 0
space_snapshots = 0
space_available = 3.97T
space_total = 43.2G
origin =
Shares:
Filesystems:
NAME SIZE MOUNTPOINT
orabackup 31K /export/orabackup
stage 43.2G /export/stage
Children:
groups => View per-group usage and manage group
quotas
replication => Manage remote replication
snapshots => Manage snapshots
users => View per-user usage and manage user quotas
zfsctrl1:shares nfs_prj1> select orabackup
zfsctrl1:shares nfs_prj1/orabackup> show
Properties:
aclinherit = restricted (inherited)
aclmode = discard (inherited)
atime = true (inherited)
casesensitivity = mixed
checksum = fletcher4 (inherited)
compression = off (inherited)
dedup = false (inherited)
compressratio = 100
copies = 1 (inherited)
creation = Sun Jan 27 2013 11:17:46 GMT+0000 (UTC)
logbias = latency (inherited)
mountpoint = /export/orabackup (inherited)
normalization = none
quota = 200G
quota_snap = true
readonly = false (inherited)
recordsize = 128K (inherited)
reservation = 0
reservation_snap = true
rstchown = true (inherited)
secondarycache = all (inherited)
shadow = none
nbmand = false (inherited)
sharesmb = off (inherited)
sharenfs = sec=sys,rw,[email protected]/16:@10.0.0.218/16:@10.0.0.215/16:@10.0.0.212/16:@10.0.0.209/16:@10.0.0.206/16:@10.0.0.13/16:@10.0.0.200/16:@10.0.0.203/16
snapdir = hidden (inherited)
utf8only = true
vscan = false (inherited)
sharedav = off (inherited)
shareftp = off (inherited)
sharesftp = off (inherited)
sharetftp = (inherited)
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1/orabackup
exported = true (inherited)
nodestroy = false
space_data = 31K
space_unused_res = 0
space_snapshots = 0
space_available = 200G
space_total = 31K
root_group = other
root_permissions = 700
root_user = nobody
origin =
zfsctrl1:shares nfs_prj1> select stage
zfsctrl1:shares nfs_prj1/stage> show
Properties:
aclinherit = restricted (inherited)
aclmode = discard (inherited)
atime = true (inherited)
casesensitivity = mixed
checksum = fletcher4 (inherited)
compression = off (inherited)
dedup = false (inherited)
compressratio = 100
copies = 1 (inherited)
creation = Tue Feb 12 2013 11:28:27 GMT+0000 (UTC)
logbias = latency (inherited)
mountpoint = /export/stage (inherited)
normalization = none
quota = 100G
quota_snap = true
readonly = false (inherited)
recordsize = 128K (inherited)
reservation = 0
reservation_snap = true
rstchown = true (inherited)
secondarycache = all (inherited)
shadow = none
nbmand = false (inherited)
sharesmb = off (inherited)
sharenfs = sec=sys,rw,[email protected]/16:@10.0.0.218/16:@10.0.0.215/16:@10.0.0.212/16:@10.0.0.209/16:@10.0.0.206/16:@10.0.0.203/16:@10.0.0.200/16
snapdir = hidden (inherited)
utf8only = true
vscan = false (inherited)
sharedav = off (inherited)
shareftp = off (inherited)
sharesftp = off (inherited)
sharetftp = (inherited)
pool = oocep_pool
canonical_name = oocep_pool/local/nfs_prj1/stage
exported = true (inherited)
nodestroy = false
space_data = 43.2G
space_unused_res = 0
space_snapshots = 0
space_available = 56.8G
space_total = 43.2G
root_group = root
root_permissions = 755
root_user = root
origin =
Can anybody please help?
Regards.

try this:
svcadm enable nfs/clientcheers
bjoern

Force Mount Point for USB disk drive

I need to force my 2TB usb drive to mount at the same mount point every time I log on or after I reboot the machine it seems to change - /Volumes/data, /Volumes/Data 1, ...
Can someone offer a solution?

Just to make sure I'm understanding this correctly....the iTunes library files (iTunes Library.itl and iTunes Music Library.xml) are currently located in my "My Documents\My Music\iTunes" folder. So, first I should delete the .xml file, right?
Then, you say to change my preferences and redirect iTunes to the new location of my songs (on the external USB drive). So, I would change the current setting of "C:\Documents and Settings\Jim\My Documents\My Music\iTunes\iTunes Music" to now point to the location of the new drive "I:\mp3" ?
What happens to the .itl file left behind in the old location? ...and all the directories with all my album art....I dont' want to lose that stuff.
Sorry, but I'm just a bit confused...well, a lot confused about where these files will be located. Before, my iTunes was configured with the iTunes music folder locations to be: "C:\Documents and Settings\Jim\My Documents\My Music\iTunes\iTunes Music" and all my mp3s were stored on the external USB disk drive....no music was in the iTunes Music folder. This config also put the library files in the \My Music\iTunes folder.
With making the changes you suggest will the library files and all the music now be on the external drive? The reason I ask is that I read some other posts from people that had everything on the external drive and if they had issues with their system connecting to the external drive, then iTunes would create a new library on the C drive and not let the user know.
Thanks for your patience in trying to explain this to me.

Messaging Server and Calendar Server Mount points for SAN

Hi! Jay,
We are planning to configure "JES 05Q4" Messaging and Calendar Servers on 2 v490 Servers running Solaris 9.0, Sun Cluster, Sun Volume Manager and UFS. The Servers will be connected to the SAN (EMC Symmetrix) for storage.
I have the following questions:
1. What are the SAN mount points to be setup for Messaging Server?
I was planning to have the following on SAN:
- /opt/SUNWmsgsr
- /var/opt/SUNWmsgsr
- Sun Cluster (Global Devices)
Are there any other mount points that needs to be on SAN for Messaging to be configured on Sun Cluster?
2. What are the SAN mount points to be setup for Calendar Server?
I was planning to have the following on SAN:
- /opt/SUNWics5
- /var/opt/SUNWics5
- /etc/opt/SUNWics5
3. What are the SAN mount points to be setup for Web Server (v 6.0) for Delegated Admin 1.2?
- /opt/ES60 (Planned location for Web Server)
Delegated Admin will be installed under /opt/ES60/ida12
Directory server will be on its own cluster. Are there any other storage needs to be considered?
Also, Is there a good document that walks through step-by-step on how to install Messaging, Calendar and Web Server on 2 node Sun Cluster.
The installation document doesn't do a good job or atleast I am seeing a lot of gaps.
Thanks

Hi,
There are basically two choices..
a) Have local binaries in cluster nodes (e.g 2 nodes) ... which means there will be two sets of binaries, one on each node in your case.
Then when you configure the software ..you will have to point the data directory to a cluster filesystem which may not be neccasarily global. But this filsystem should be mountable on both nodes.
The advantage of this method is that ... during patching and similar system maintenance activities....the downtime is minimum...
The disadvantage is that you have to maintain two sets of binaries ..i.e patch twice.
The suggested filesystems can be e.g.
/opt for local binaries
/SJE/SUNWmsgr for data (used during configure option)
This will mean installing the binaries twice...
b) Having a single copy of binaries on clustered filesystem....
This was the norm in iMS5.2 era ...and Sun would recommend this...though I have seen type a) also for iMs 5.2
This means there should no configuration files in local fs. Everything related to iPlanet on clustered filesystem.
I have not come accross type b) post SUNONE i.e 6.x .....it seems 6.x has to keep some files on the local filesystem anyway..so b) is either not possible or needs some special configuration
so may be you should try a) ...
The Sequence would be ..
After the cluster framework is ready:
1) Insall the binaries on both side
2 ) Install agent on one side
3) switch the filesytem resource on any node
4) Configure the software with the clustered FS
5) Switch the filesystem resource on the other node and useconfig of first node.
Cheers--

Recover /var mount-point into new boot environment

I installed Solaris 10 u7 with zfs pool containing / mount-point (root)
One issue to mention is that - for no compulsory reason - I asked Solaris installer to place /var mount point into different file system (an option of the installer which I did not fully understood)
I used Live Upgrade to migrate Solaris 10 u7 to U8. First:
lucreate -c CBE - n NBE
I assume NBE boot environment was created in the zfs pool (rpool)
I did not take care of /var at this time.
I did luupgrade - to apply new Update 8 into NBE - the target boot environment.
Then did luactivate NBE and "init 6" to reboot.
At boot time Solaris does start NBE (Solaris 10 U8) - but cannot mount /var - hence forces console into
Maintenance Mode.
What is the strategy to use the /var file-system from CBE (old boot environment) ?
Can I mount file-system of old CBE /var ?
Or should I mount a spare file system as NBE /var and somehow copy it?
Please enlist a series of steps (commands), thanks.

I reinstalled Solaris 10 Update7 - this time with / (root) and /var on same dataset (file system).
This time lucreate and "luupgrade to Update 8" and luactivate ended OK
(no problems with mounting /var after "init 6" reboot)

Duplicate Mount Point "Documents 1" after improper reboot

Similar Messages

Maybe you are looking for