Volume manage rootdg create problem

Hi, all
I used dd copy a disk with Veritas Volume Manager(VxVM) software packag on it to a new disk, after that, I use new disk to boot system (sparc-10), get messages like that :
Aug 27 05:38:00 vxvm:vxconfigd: enable failed: Error in disk group configuration copies
Aug 27 05:38:00 vxvm:vxconfigd: Disk group has no valid configuration copies; transactions are disabled.
Aug 27 05:38:00 vxvm:vxconfigd: Rootdg cannot be imported during boot
so, I want to recreate rootdg for the new disk with command: vxdg init rootdg c0t3d0s2=c0t3d0s2, but get error messages: private region contents is invalid, can't create rootdg, can anybody tell me how to fix this problem? thanks a lot!
weilin

Hi Joan,
You can set the Default Value for the history version of idClient to :P7_CLIENTID with a Default Type of PL/SQL Expression. This should ensure that it is always populated.
Regards
Andy

Similar Messages

  • Hal/Dbus/gnome-volume-manager mount permission problem

    Hello,
    I have hal/dbus/gnome-volume-manager installed (of course I use gnome as DE).
    I need help in configuring the permissions for automatically mounted disk/partitions.
    When I connect an external USB HDD having 1 NTFS and 1 partition, these partitions are auto-mounted and the desktop icons appear for the both.
    As a normal user I am able to read/write FAT partition (I think, not because I have configured anything properly, but because FAT does not support permissions on filesystem), but I am not even able to read (browse) NTFS filesystem (ERORR: You do not have permission...).
    Yes, I have NTFS filesystm support enabled, because I am able to access that same NTFS partition as root.

    Well, Thanks for the reply but I had not put any static entry in fstab for this external USB HDD.
    Anyway, I figured out something (havn't tested it yet)
    When an external USB HDD is attached ... depending storage.policy and volume.policy rules in /usr/share/hal .. the hal daemon (hald) calls fstab-sync with appropriate parameters.
    fstab-sync, then, generates /etc/fstab enteries automatically (with comment=managed keyword).
    I have added a user policy so that umask and gid value is set correctly. I'll test is as soon as I'll get time.
    In the meanwhile if anybody have any other suggestions, please post it here.

  • Solaris Volume Manager - mount problems

    hi.
    first i set up a raid on a StorEdge 5100 :
    metainit d4 -r c2t1d0s0 c2t2d0s0 .............. (13 devices) -i 64k
    works fine now i want to create a fs on d4:
    newfs /dev/md/rdsk/d4
    works fine.
    i insert this line in vfstab:
    /dev/md/dsk/d4 /dev/md/rdsk/d4 /d4 ufs 1 yes -
    now after a reboot the system hangs in maintanance mode and want a fsck . after a fsck and control+d
    the system coming up. after a next reboot The same Problem... !!
    without any problems i run two mirror disksets / and /var on d0 and d3 and the swap on d1.
    is it a problem with the size of 101GB on the raid5 (A5100)
    yes i know i can run veritas volume manager on the A5100 (a license is on the machine) but i was not able to install the vm bacause the vm cant find the A5100 and the license. So please help me .

    Duplicate slicing: prtvtoc /dev/rdsk/c1t0d0s7|fmthard -s - /dev/rdsk/c1t1d0s7
    Lather, rinse, repeat for each file system:
    metainit the bootable side of the mirror: metainit -f d71 1 1 c1t0d0s7.
    metainit the other side: metainit d72 1 1 c1t1d0s7.
    Attach one side of the mirror: metainit d70 -m d71
    When done: lockfs -fa;init 6
    Lather, rinse, repeat for each file system:
    After reboot attach the other side of the mirror: metattach d70 d72
    bash-3.00# metastat -p
    d70 -m d71 d72 1
    d71 1 1 c1t0d0s7
    d72 1 1 c1t1d0s7
    d50 -m d51 d52 1
    d51 1 1 c1t0d0s5
    d52 1 1 c1t1d0s5
    d10 -m d11 d12 1
    d11 1 1 c1t0d0s1
    d12 1 1 c1t1d0s1
    d0 -m d1 d2 1
    d1 1 1 c1t0d0s0
    d2 1 1 c1t1d0s0
    d60 -m d61 d62 1
    d61 1 1 c1t0d0s6
    d62 1 1 c1t1d0s6
    bash-3.00# cat /etc/vfstab
    #device         device          mount           FS      fsck    mount   mount
    #to mount       to fsck         point           type    pass    at boot options
    fd      -       /dev/fd fd      -       no      -
    /proc   -       /proc   proc    -       no      -
    /dev/md/dsk/d10 -       -       swap    -       no      -
    /dev/md/dsk/d0  /dev/md/rdsk/d0 /       ufs     1       no      -
    /dev/md/dsk/d70 /dev/md/rdsk/d70        /usr    ufs     1       no      -
    /dev/md/dsk/d50 /dev/md/rdsk/d50        /var    ufs     1       no      -
    /dev/md/dsk/d60 /dev/md/rdsk/d60        /opt    ufs     2       yes     -
    /devices        -       /devices        devfs   -       no      -
    ctfs    -       /system/contract        ctfs    -       no      -
    objfs   -       /system/object  objfs   -       no      -
    swap    -       /tmp    tmpfs   -       yes     -

  • Dbus/hal/gnome-volume-manager problem

    I've got hal and dbus running but it doesnt even seem that gnome-volume-manager is started. I added it to my gnome session but that didnt seem to do the trick. I'm trying to be able to just plug in my usb key and ipod and have them automount. It works if I restart hal or run gnome-volume-manager from the command line but then work work again unless I restart that stuff again. Here is a cut from my fstab:
    /dev/sda1 /mnt/usb auto user,noauto 0 0
    /dev/sda2 /mnt/ipod auto user,noauto 0 0

    Hi lhoerste,
    I had this problem with automount as well. The way I fixed it was adding
    dbus hal to daemons line in /etc/rc.conf. You probably did this already.
    Next, when you are in the gnome desktop, stick in a cd. Nothing happens right?
    Now go to preferences=>removable drives and media (I think this is what it is called. I'm not sitting infront of my computer at the moment). Then make sure that the checkboxes pertaining to "mount automatically" are checked.
    Close window.
    Now your cd should automount and appear on the desktop. Eject the cd by right clicking on the icon and choosing eject.
    Now, restart and ***make sure you save settings*** before leaving.
    Get back into the gnome desktop and plug your cd back in. It should automount now.
    This is how I got automount to work for me.

  • C Program APIs or "ioctls" to access volume information created using Solaris Volume Manager

    Hi,
    Does "SUNWlvm" provide any C language program APIs or "ioctls" to know
    about volumes created using "Sun Volume Manager" like volume
    components, size, type and rest. I did not find any API manual page.
    Thanks,
    Jai

    Hi,
    Does "SUNWlvm" provide any C language program APIs or "ioctls" to know
    about volumes created using "Sun Volume Manager" like volume
    components, size, type and rest. I did not find any API manual page.
    Thanks,
    Jai

  • Unable to Initialize Volume Manager from a Configuration File

    I'd like to reattach a D1000 to a rebuilt system. The array contains a raid 5 partition that was built with Solaris Volume Manager (Solaris 9). Since it is the same system all controller/target/slice ids have not changed. I was able to restore the Volume Manager configuration files (/etc/lvm) from a tape backup and followed the instructions provided in the Solaris Volume Manager Administration Guide: How to Initialize Solaris Volume Manager from a Configuration File <http://docs.sun.com/db/doc/816-4519/6manoju60?a=view>.
    All of the state database replicas for this partition are contained on the disks within the array so I began by creating new database replicas on a local disk.
    I then copied the /etc/md.cf file to /etc/md.tab
    # more /etc/lvm/md.tab
    # metadevice configuration file
    # do not hand edit
    d0 -r c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t8d0s0 c1t9d0s0 c2t10d0s0 c2t11d0s0 c2t12d0s0 c2t8d0s0 c2t9d0s0 -k -i 32b -h hsp000
    hsp000 c1t13d0s0 c2t13d0s0
    I then tested the syntax of the md.tab file (this output is actually from my secomd attempt).
    # /sbin/metainit -n -a
    d0: RAID is setup
    metainit: <hostname>: /etc/lvm/md.tab line 4: hsp000: hotspare pool is already setup
    Not seeing any problems I then attempted to recreate the d0 volume, but it fails with the error below:
    # /sbin/metainit -a
    metainit: <hostname>: /etc/lvm/md.tab line 3: d0: devices were not RAIDed previously or are specified in the wrong order
    metainit: <hostname>: /etc/lvm/md.tab line 4: hsp000: hotspare pool is already setup
    Any suggestions on how to reinitialize this volume would be appreciated.
    Thanks, Doug

    You have UserPrincipalName column heading in the csv file so this should be your cmdlet.
    import-csv C:\temp\sharedMailboxCreationTest.csv | ForEach-Object {New-Mailbox -shared  -Name $_.Name  -Alias $_.Alias  -OrganizationalUnit $_.OrganizationalUnit -UserPrincipalName $_.UserPrincipalName -Database $_.Database}
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Solaris Volume Manager packages installation fails

    During the OS installation phase while jumpstarting, the output is as follows for Solaris Volume Manager (see below).
    To begin with, why are SUNWmdr and SUNWmdu packages trying to install? They are not mentioned in my Profile file, neither are they included in CORE OS. Is this a bug and has anyone found a fix to it?
    /tmp/install2gaGwn/checkinstall4gaGwn: /tmp/sh68390: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdr> failed.
    No changes were made to the system.
    /tmp/installHBaqyn/checkinstallJBaqyn: /tmp/sh68530: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdu> failed.
    No changes were made to the system.
    3751 blocks
    Thanks in advance,
    David
    p.s. This is happening while installing Sol9 sparc 04/2004 version (CORE) on Blade100, V480 and V240 machines.

    <table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>grestep wrote on Fri, 24 September 2004 14:34</b></td></tr><tr><td class="quote">
    Unfortunately, this is a bug in the Sun jumpstart process.
    You will have to install the same packages in a postinstall phase.
    This bug has been there for years.
    It is fixed in the latest Solaris 9 cdroms dated 09/04.
    I know of no other fix except the latest cdroms.
    It is also fixed in Solaris 10.
    Solaris 8 even the most recent cdroms have the bug.
    This bug only appears in a jumpstart. It works fine in a cdrom install. I haven't investigated why the jumpstart from a jumpstart server fails, but installing the package in a postinstall phase works.
    I recommend that you download the latest Solaris 9 cdroms if it is Solaris 9 that is having the problem. For Solaris 8, postinstall phase is your only option.
    I don't remember this bug in Solaris 7.
    </td></tr></table>
    Any idea how to fix this ? Ive jumped a lot of machines using this jumpstart server using JET, always using the SDS product from JET, it always worked well, until I tried to jump this v210 recently acquired and firmware updated.
    I got those errors and have no clue how to fix this .. :
    SDS: Installing sds....
    SDS: Installing SUNWmdr from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
    Copyright 2000 Sun Microsystems, Inc. All rights reserved.
    /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdr/inst all/checkinstall: /t
    mp/sh39790: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdr> failed.
    No changes were made to the system.
    SDS: SUNWmdr installation complete
    SDS: Installing SUNWmdu from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
    Copyright 2000 Sun Microsystems, Inc. All rights reserved.
    /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdu/inst all/checkinstall: /t
    mp/sh40210: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdu> failed.
    No changes were made to the system.
    SDS: SUNWmdu installation complete
    SDS: Installing SUNWmdx from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
    Copyright 2000 Sun Microsystems, Inc. All rights reserved.
    /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdx/inst all/checkinstall: /t
    mp/sh40640: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdx> failed.
    No changes were made to the system.
    SDS: SUNWmdx installation complete
    SDS: Installing SUNWmdnr from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
    Copyright 2000 Sun Microsystems, Inc. All rights reserved.
    /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdnr/ins tall/checkinstall: /
    tmp/sh41060: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdnr> failed.
    No changes were made to the system.
    SDS: SUNWmdnr installation complete
    SDS: Installing SUNWmdnu from: /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc
    Copyright 2000 Sun Microsystems, Inc. All rights reserved.
    /a/var/opt/sun/jet/js_media/pkg/sds/4.2.1/sparc/SUNWmdnu/ins tall/checkinstall: /
    tmp/sh41460: cannot create
    pkgadd: ERROR: checkinstall script did not complete successfully
    Installation of <SUNWmdnu> failed.
    No changes were made to the system.
    SDS: SUNWmdnu installation complete
    SDS: Apply patch 108693-25
    Using : SunOS Release 5.8 Version Generic_117350-16 64-bit
    All other packages installed without problem
    Any insights ?

  • WebStart Flash and Veritas Volume Manager

    I would like to use WebStart Flash for backup of the system
    disk. The goal is to be able to recover the system disk rapidly.
    It works perfectly for systems without Veritas Volume
    Manager on the system disk.
    However, if Veritas Volume Manager is installed and used
    for mirroring the root disk, the system is not able to boot using
    WebStart Flash. This is probably because the "private region"
    of the disk is not included in the flash archive.
    Does anybody have a solution for this, or does any of
    you successfully combine WebStart Flash and Veritas
    Volume Manager?
    I use Jumpstart and the install_type is configured to
    flash_install.
    The question was also asked in the newsgroup
    comp.unix.solaris.
    Rgds,
    Henrik

    For many reasons, today you cannot save the VxVM
    private region information as an implicit part of a
    flash archive. The procedure would likely be to
    unencapsulate the root drive, create the flash archive,
    then re-encapsulate the root drive. This is an ugly
    procedure and may cause more pain than it is worth.
    When a root disk is encapsulated, an entry is put
    into the /etc/system file which says to use the VxVM
    or SVM logical volume for the rootdev rather than
    the actual device from which the system was originally
    booted. When you create a flash archive, this modification
    to the /etc/system is carried along. But, when you install
    it on a new system which doesn't have VxVM properly
    installed already (a chicken-and-the-egg problem)
    then the change of the rootdev to the logical volume
    will fail. The result is an unbootable system (without
    using 'boot -a' and pointing to a different /etc/system
    file like /dev/null).
    The current recommended process is to use a prototype
    system which does not have an encapsulated root
    to create the flash archive.
    VxVM also uses the ELM license manager which will
    tie the VxVM runtime license to the hostid. This makes
    moving flash archives with VxVM to other machines
    impractical or difficult.
    The long term solution would be to add logical volume
    management support to the JumpStart infrastructure.
    I'm not counting on this anytime soon :-(
    -- richard

  • Solaris upgrade with Veritas Volume Manager

    I have to upgrade Solaris from 7 to 8 on a server which has Veritas Volume Manager. OK, I already found the necessary information to make this upgrade, but I have not found any answers on my problem.
    It is quite possible that after VVM was installed, some of the filesystems like /, /opt, /usr or /var were increased or that additional filesystems were added on the rootdisk. This will prevent the upgrade_start to run correctly. One way to overcome this problem is to boot the machine in single-user mode, create all the root filesystems as standard ufs filesystems on a free disk with the same size as the VVM filesystems and then use ufsdump to copy all data over. When that is done, install a bootblock on the new disk and boot the machine from this disk. Then, start the Solaris upgrade. The problem with this is that when there is no free disk available, then I clearly have a problem.
    Does anyone have experience with this or has a better plan ?
    Should I completely de-install VVM or is it enough to convert all rootfilesystems to ufs filesystems ?
    Please reply to me individually at [email protected]
    Thanks,
    Bruno

    There are more things that you need to do.
    Read veritas install guide -- it has a pretty good section of what needs to be done.
    http://www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software/VERITAS_Volume_Manager/

  • Volume Manager arrangement

    I have an E250 with Veritas Volume Manager 3.0.2 installed. Since E250 can have only internal 6 disks and I've mirrored first two disks (encapsulated), that leaves me 4 18G disks to do a RAID 5 for Oracle databases. However, I also want to use Vxvm's RAID 5 logging. I've tried to ceate a RAID 5 with some space left on each of the 4 disks and then attempted to mirror RAID 5 logs across the remaining space on the 4 disks. But Vxvm did not let me. I suppose the RAID 5 log plex should be on seperate disks? On the other hand, to maximize space I don't want to do RAID 5 with only 3 disks and use the 4th one as the RAID 5 log.
    Does anybody have any suggestions on how to do RAID 5 with logging for 4 disks while maximizing the available disk space?
    thanks!

    Or you could do this:
    Once you have created the disk group and added the disks you want (the 4 disks available)
    vxassist -g <dg name> maxsize layout=raid5,log
    Then run:
    vxassist -g <dg name> make <volname> <volsize> layout=raid5,log <disk1> <disk2> <disk3> <disk4>
    This way of course you'll have to have the 4 disks on a separate dg.
    imho, it's not a very good idea to keep data volumes in the rootdg (but I'm sure you already know that)...

  • Volume manager or zfs

    I have veritas volume manager in a couple of systems.
    Zfs is it similar ?
    I read the documentation, and, the pool disk creation, file systems depend of the pool of disk. Its like veritas.
    What is the big difference ?

    Refer to the first link which I provided. What I
    meant is that those admins who use fsck on occasion
    will realise that the zfs filesystems do not have
    such a utility or requires one (as yet).Correct. It's not needed.
    Yes it does resilver data - provided you are using
    redundant disks - the zfs data integrity model is
    based on checksumming - the checksums assists zfs to
    recognise data is bad, but in order ot this to
    resilver data - it must check the other copy - zfs
    will allow you to create unmirrored filesystems -
    this means - that if you did not use the replication
    features using mirroring or raidz - you are SOL. Of course. This is no different from any other volume manager. I was just confused by your original quote that it would "resilver corrupted data
    by means of the built-in checksumming." It may use checksumming for verification, but it must resilver from redundant storage, not the checksum. If no redundant storage exists, then your data is gone, just like any other storage system.
    I'm not nervous about the lack of fsck - If I have to
    use this filesystem on my company's data - and
    something terrible happens - the questions management
    will ask: Why did you use zfs? Were you aware of
    potential issues? Has this been tested in a
    development environment?
    I'm not working in a fictious environment but one
    that contains terabytes of data. It is my
    responsibility to find tested and proven
    technologies, leverage them in order to achieve a
    stable environment. New technologies are always
    tested as proof of concept then tested further in
    development. A business case is then written which
    justifies the use of that technology. I'm not
    nervous.Yes, as expected. Even besides design issues, the age of ZFS is still young compared to other similar technology. There are still known bugs and limitations with ZFS. Those would be my primary concern before using it in production.
    I just didn't know what you were referring to with the "if you're willing to overlook this" sentence. I was assuming that something about the lack of fsck was a problem that had to be overlooked. That's why I was asking for clarification.
    There's no fsck by design, and resilvering data works similarly to other volume managers (except that it does so only after verification, not blindly). So I'm not sure what I'm supposed to overlook.
    Darren

  • How do I use copyprofile, image manager and create a wim file to Sysprep a reference Windows 8 computer.

    Im trying to deploy a reference machine (configured) to other machines (exact or close image) with different hardware.
    I have successfully used sysprep in out of the box, generalise, shutdown mode although i havent tried to deploy this to another device.  Unfortunately it doesnt copy the profile to default.
    I understand that I have to create an answer file using image manager based on that image, save it to a usb drive and attach this in the sysprep command line when sysprepping it.
    My problem is I dont know how to easily capture an image of windows 8 into a wim file so that i can add this into image manager to create a answer file.  Im also not sure what I have to do in image manager, is it a simple matter of creating and saving
    the answer file or do i have to configure it to copy the profile specifically (theres only one account anyhow).
    I also want to know if i have to attach the drivers or are all the standard drivers put into the sysprep image as standard.  I would like the machine to be an exactly replica, same as doing a clone (but with the drivers for the new machine installed
    so it will boot) same as doing a clone and then repair? If thats possible.
    Any specific instructions on this would be helpful.  I have read the microsft links but they are somewhat confusing.

    I know this is a very late response but I thought I'd post for others who search.
    The easiest way to create the .wim file is via WinPE, this guy's two YouTube videos explain the entire process in detail - 
    Windows 8 ADK Part 1: Capture an OS image - https://www.youtube.com/watch?v=XJ8zKX_8E9w
    Windows 8 ADK Part 2: Windows Image Deployment - https://www.youtube.com/watch?v=HHIvoqSw_FI
    Here's a quick rundown from my notes:
    WINPE
    Create WinPE via imaging tools command prompt
    copype amd64 c:\winpe
    makewinpemedia /iso "c:\winpe" "c:\winpe\winpe64.iso"
    UNATTEND
    Open Windows System Image Manager
    Configure unattend.xml
    Save unattend.xml to sysprep folder
    Create script and save it to sysprep folder to launch sysprep with unattend
    @echo off
    cd C:\Windows\System32\sysprep
    Sysprep /oob /generalize /unattend:C:\Windows\System32\sysprep\unattend.xml
    SYSPREP
    C:\Windows\System32\Sysprep
    Run as administrator
    OOBE/Generalize
    Shutdown
    CONFIGURATION of WINPE
    Set IP - netsh int ip set address "Local Area Connection" static 192.168.1.2 255.255.255.0 192.168.1.1
    Set DNS - netsh int ip set dns name = "Local Area Connection" source = static addr = 192.168.1.4 validate = no
    Map Network Name - net use z:
    \\WindowsADK\reflex\images password /USER:domain.local\username
    DISKPART
    diskpart
    list disk
    select disk zero
    list partition
    select partition 2 (OS partition #)
    Assign letter=S (assigns drive letter to partition)
    Exit
    DISM
    dism /capture-image /imagefile:z:\image.wim /capturedir:s:\ /name:"Windows 8.1 Custom"
    Verify image is saved in the image share (z:)
    http://www.microsoftfanboys.com

  • How do you change volume permissions with Solaris Volume Manager?

    (Previously posted in "Talk to the Sysop" - no replies)
    I'm trying to set up Solaris 9 to run Oracle on raw partitions. I have my design nailed down and I have built all the raw partitions I need as soft partitions on top of RAID 1 volumes. All this is built using Solaris Volume Manager (SVM).
    However, all the partitions are still owned by root. Before I can create my Oracle database, I need to change the owner of the Oracle partitions to oracle:oinstall. The only reference I found telling me how to do this was in a Sun Blueprint and it essentially said "You can't change volume permissions directly or permanently using SVM and chown will only remain effective until the next reboot. To make the changes permanent, you must modify /etc/minor_perm". Unfortunately, I can't find an example of how to do this anywhere and the online man pages are not particularly helpful (at least not to me).
    I'd appreciate a quick pointer, either to a good online resource or, even better, a simple example. For background, the volumes Oracle needs to own are:
    /dev/md/rdsk/d101-109
    /dev/md/rdsk/d201-203
    /dev/md/rdsk/d301-303
    /dev/md/rdsk/d401-403
    /dev/md/rdsk/d501-505
    I provide this information because I'd like to assign some, but not all, of the devices under /dev/md/rdsk to the oracle user and I was hoping some smart person out there could illustrate an approach using simle regular expressions, at which I'm horribly poor.
    Thanks in advance,
    Adrian

    Ron, I feel your pain.  I just came from an HTC also and a lot of stuff with this iPhone is bugging the crap out of me.  Who makes a phone where you can't adjust the ringer and alert volumes independently?  Instead, I have to adjust the alert volume when it is active.  C'mon guys.  Get with the program.  You won a bunch of Android users over with the 4S, but you're going to chase us all back when we're done with our contract.  Frustrating.  

  • Can't use built in volume manager in PCMan File Manager

    Trying to use the built in volume manager in PCMan FM causes 2 error messages to appear.  They are unreadable (the title bar says "Unable t" that's it).  An error like the one that follows appears in the the console (or whatever Eterm is) for each:
    (pcmanfm:3084): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 57: '-' is not a valid character following a '<' character; it may not begin an element name
    After those a third message box appears and says: "Directory doesn't exist".  That box is not accompanied by any error text on the console.
    I assume the first to say something like "Unable to mount" but I don't know WHY.
    The problem does NOT occur if I mount it as root (using sudo) and access it that way.  This however then requires any further access to be made as root if anything useful is to be done with the drive (copying files, writing to it, etc.)
    I'm running Fluxbox as my WM, if that matters.
    Thanks in advance!

    Hmm...the wiki refers to files I don't have.  /etc/hal/fdi/policy and /etc/hal/fdi/information are both empty directories (even when viewed as root).  Any thoughts?
    I feel like an idiot now.  I should have guessed i needed to put those files in.
    Last edited by guitarMan666 (2009-04-22 03:22:36)

  • [SOLVED] gnome-volume-manager is lazy

    Until some update that I missed all was fine. I boot, my volumes are mounted, I can see them in ROX (my main file management program).
    I insert a CD/DVD/whatever, its mounted and its all in /media/.:D
    But now it just does nothing, until I start Nautilus, then everything gets mounted.
    I close Nautilus, and it doesnt mount anything again.
    gnome-volume-manager process is up and running after login before running nautilus and after closing it too.
    How can I make it behave nicely without the nuisance that Nautilus is?
    Oh and Im running Openbox as the window manager in Gnome, Nautilus desktop handling disabled.
    Last edited by Hohoho (2008-05-28 20:21:12)

    i had the same problem.
    i looked in the changelog and it appears that from now on the automount function is disabled upstream because that function is to be handled by the nautilus ( http://ftp.gnome.org/pub/GNOME/sources/ … .3.changes ). For me it is a problem because i use openbox and thunar, so you just have to recompile the package with the option: "--enable-automount" .
    info from:
    ~/Desktop/gnome-volume-manager-2.22.3  $  ./configure --help
    then start it ( after recompiling with abs, for example ), but look that the path changed, now in my autostart file for openbox i have:
    /usr/lib/gnome-volume-manager/gnome-volume-manager --sm-disable --daemon=yes &
    hope it helps you, because this annoyed me for a long time and this is the only easy way to mount my partitions easily
    Last edited by Diaz (2008-05-28 20:04:56)

Maybe you are looking for