PRVF-4172 : Check of OCR device "/dev/ocr_disk1" for sharedness failed

Hi,
I am upgrading RAC 11.1.0.7 version to 11gRAC3 and facing above mention error when running
runcluvfy.sh stage -pre crsinst -upgrade -n DEV1,DEV2 -src_crshome /u01/app/oracle/product/crs/11.1 -dest_crshome /u05/app/oracle/product/grid/11.2 -dest_version 11.2.0.3.0 -fixup -fixupdir /tmp -verbose
May I request to the community to help here as Oracle support does not have enough matiral for info.
I tried to skip the error and then my upgraderoot.sh fails.
Please help.
Regards

This looks mutch like this :
Re: PRVF-4172 when upgrading 10.2.0.5 to 11.2.0.2 with OCR,Vote on raw devices
But in that case user could skip errors.
What kind of error upgraderoot.sh does give?
There is big changes between 11.1 and 11.2 versions for example SCAN IP's/listeners. it might be easier to do clean installation of 11.2.0.3 and move data between old and new databases for example with expdp/impdp.

Similar Messages

  • Lucreate fails w/msg  cannot check device name d41 for device path abbre

    I'm using Live Upgrade to install Solaris 10 8/07 on a V490 currently running Solaris 9 4/04. Sol9 is using SVM to mirror two internal drives with file systems for /, /var and swap. I used format and formatted two new slices for / and /var. LU has been removed and the liveupgrade20 script used to install LU from the Solaris 10 CD. I believe the next step is to lucreate the BE, but the lucreate is failing:
    root@animal # lucreate -A 'dualboot' -m /:/dev/md/dsk/d40:ufs,mirror -m /:/dev/dsk/c1t0d0s4,d41:attach -m /var:/dev/md/dsk/d50:ufs,mirror -m /var:/dev/dsk/c1t0d0s5,d51:attach -m /var:/dev/dsk/c1t1d0s5,d52:attach -n sol10
    Discovering physical storage devices
    Discovering logical storage devices
    Cross referencing storage devices with boot environment configurations
    Determining types of file systems supported
    Validating file system requests
    ERROR: cannot check device name <d41> for device path abbreviation
    ERROR: cannot determine if device name <d41> is abbreviated device path
    ERROR: cannot create new boot environment using file systems as configured
    ERROR: please review all file system configuration options
    ERROR: cannot create new boot environment using options providedIt's probably something simple as this is the time I'm doing an upgrade on my own.
    Thanks for any ideas,
    Glen

    I received help elsewhere.
    To summarize using the full metadevice names worked:
    lucreate -A 'dualboot' -m /:/dev/md/dsk/d40:ufs,mirror -m /:/dev/dsk/c1t0d0s4,/dev/md/dsk/d41:attach -m /:/dev/dsk/c1t1d0s4,/dev/md/dsk/d42:attach -m /var:/dev/md/dsk/d50:ufs,mirror -m /var:/dev/dsk/c1t0d0s5,/dev/md/dsk/d51:attach -m /var:/dev/dsk/c1t1d0s5,/dev/md/dsk/d52:attach -n sol10
    (Note: Using the short names (d41, d42 etc) worked with Solaris 10 6/06, but fails with 8/07.)
    sysglen

  • [SOLVED] - Arch Boot Error: Unable to find Root Device /dev/sdb1

    I had Arch running perfectly using /dev/sdb1 (versus Disk Label or UUID) and decided to do a update.  After the Update I can't boot
    to a running system, and I get this error message:
    ERROR: Unable to find root device /dev/sdb1 
    You are being dropped into a recovery shell.
    Is there an easy way to convert to UUID or Disk Label since the latest Upgrade doesn't allow me to continue to use /dev/sdb1 ??
    I'd prefer not to have to rebuild both USB Flash Drives to get functional systems.
    Any Help is greatly appreciated.
    Suggestions?
    Larry
    Last edited by lkraemer (2012-02-21 15:14:02)

    Check your grub and read https://wiki.archlinux.org/index.php/UUID#By-uuid
    Edit:
    https://bbs.archlinux.org/viewtopic.php … 0#p1059160
    https://bbs.archlinux.org/viewtopic.php?pid=1059338
    https://bbs.archlinux.org/viewtopic.php?id=135288
    Last edited by karol (2012-02-21 01:07:21)

  • Can't start CRS -- giving error about OCR device but ....?? Please help.

    I am running CentOS 4.5 64-bit with kernel 2.6.9-55.EL on 2 AMD64 single CPU machines. Installed Oracle Clusterware 10.2.0.1 on both of these (pushing from node1). Then created RAC database using ASM. Everything worked fine & CRS/RAC were up (on both) for sometime. Then I stopped the resources & CRS/RAC. But, after sometime I can't start CRS on any of these! Getting error message (in /tmp/crsctl.pid):
    OCR initialization failed accessing OCR device: PROC-26: Error while accessing the physical storage.
    But I can see the FireWire drive/RAW partitions using "fdisk -l" and the permission/ownership are correct on the OCR/Voting Disk RAW partitions.
    I also don't see any socket opened under /var/tmp/.oracle!
    The is no other message in any other error/log file.
    What is this & how to solve?
    Thanks.

    Hi,
    Pls refer to the following solution:
    1. Please check the rights and owners of the ocr devices
    2. Check if the ocrconfig_loc is pointing to the correct ocr in /var/opt/oracle/ocr.loc.
    The ocrconfig_loc parameter specifies the location of the Oracle Cluster
    Registry (OCR) used by the CSS daemon. The path up to the cdata directory is the Oracle home directory where the CSS daemon is running.
    3. Reconfiguring Oracle Cluster Synchronization Services
    a. $/u01/app/oracle/product/10G/bin/localconfig delete
    Unexpected parameter: css
    $
    b - I killed init.cssd process
    $ps -ef |grep css
    root 1559 1 0.1 09:34:53 ?? 0:07.52 /sbin/init.d/init.cssd startcheck
    root 16390 16070 0.0 12:33:53 pts/1 0:00.01 grep css
    $kill -9 1559
    $ps -ef |grep css
    root 16407 16070 0.0 12:34:15 pts/1 0:00.01 grep css
    c - Set up ORACLE_HOME
    $export ORACLE_HOME=/u01/app/oracle/product/10G
    $/u01/app/oracle/product/10G/bin/localconfig delete
    Enter the following command to reconfigure the CSS daemon to run from this Oracle home:
    # $ORACLE_HOME/bin/localconfig reset $ORACLE_HOME
    The script stops the Oracle CSS daemon, reconfigures it in the new Oracle home, and then restarts it. When the system boots, the CSS daemon starts automatically from the new Oracle home.
    Terry liu

  • [SOLVED] Initramfs trim: "device '/dev/sda3' not fount" still boots.

    SOLUTION I should have never removed UUIDs from my fstab, instead I should have ADDED them to my bootloader config.  Putting UUIDs back in fstab and adding the UUID for my root partition to syslinux.cnf solved this.
    I've been pruning my initramfs following falconindy's blog post which I learned about from success stories in the systemd startup times thread.
    I ended up with this mkinitcpio.conf
    MODULES="ahci sd_mod ext4"
    BINARIES="fsck fsck.ext4"
    HOOKS="base consolefont"
    COMPRESSION="lzop"
    I've also tried without the compression method specified.  I've added in a couple modules which I admittedly don't know much about, but I found them in the lsmod list after appending the "break=postmount" to a working initramfs.  These included uhci_hcd and ehci_hcd.
    In every case I get the same error message on boot:
    device '/dev/sda3' not found. Skipping fsck
    Unable to find root device '/dev/sda3'
    and I am dropped to a recovery shell.  There is a message that says (paraphrasing) "type exit to attempt to continue".  I type exit and hit enter and I get a message:
    Trying to continue (This will likely fail)
    But it does not fail - it works perfectly and the system boots successfully.
    So in short - everything works, but there is some early boot test that "thinks" it won't work and leads to me having to exit from a recovery shell.
    I realized my fstab still had UUIDs, so I changed those to /dev/sdaX and rebuilt the initramfs, but this had no effect.
    The best I can guess (and it is a wild guess) is that the only remaining difference between the working initramfs and this problematic stripped down version is the absence of udev.  I did look at a diff of the lsinitcpio of a working version and the failing trimmed down version.  I've removed any items that went both ways in the diff output (eg ">some/file ... <some/file") and this is what remains:
    7c6
    < ./hooks/udev
    16,18d14
    < ./usr/bin/fsck.ext3
    20,21c16,17
    < ./usr/bin/udevadm
    < ./usr/bin/udevd
    130a127,128
    > ./usr/lib/libpthread-2.16.so
    > ./usr/lib/libpthread.so.0
    137,151d134
    < ./usr/lib/udev
    < ./usr/lib/udev/scsi_id
    < ./usr/lib/udev/ata_id
    < ./usr/lib/udev/rules.d
    < ./usr/lib/udev/rules.d/80-drivers.rules
    < ./usr/lib/udev/rules.d/60-persistent-storage.rules
    < ./usr/lib/udev/rules.d/50-udev-default.rules
    < ./usr/lib/libpthread-2.16.so
    < ./usr/lib/libpthread.so.0
    < ./usr/lib/libattr.so.1.1.0
    < ./usr/lib/libattr.so.1
    < ./usr/lib/librt-2.16.so
    < ./usr/lib/librt.so.1
    < ./usr/lib/libacl.so.1.1.0
    < ./usr/lib/libacl.so.1
    254a238,246
    > ./usr/lib/modules/3.5.3-2-ck/kernel/hwa-hc.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/isp116x-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/isp1362-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/isp1760.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/ohci-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/oxu210hp-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/r8a66597-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/sl811-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/u132-hcd.ko
    255a248,250
    > ./usr/lib/modules/3.5.3-2-ck/kernel/whci-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/xhci-hcd.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/ftdi-elan.ko
    256a252,256
    > ./usr/lib/modules/3.5.3-2-ck/kernel/wusb-wa.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/wusbcore.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/umc.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/uwb.ko
    > ./usr/lib/modules/3.5.3-2-ck/kernel/whci.ko
    274,275d273
    < ./etc/udev
    < ./etc/udev/udev.conf
    The ck-modules lead me to try this with a "vanilla" arch kernel which I also have installed.  With the default arch kernel I am left in a recovery shell but exiting does not lead to a successful boot.  I don't know what this really means, but perhaps something unique to the ck-kernel setup allows a recovery from this problem.
    Any suggestions for further troubleshooting or exploration?
    edit I put udev back in the hooks array, rebuilt the image, and now it works fine.  So udev is the relevant peice of the puzzle.  I thought the idea of using the modules, though, was so that udev wouldn't be needed.  I must have missed a needed module, though I cant figure what it would be.
    edit2 I've used "break=postmount" on both the working image with udev, and with the failing image without udev and I do an "lsmod" in the shell.  I get the exact same list of modules.  So all the correct modules are all loaded properly.  But the absence of udev seems to cause a problem.
    Last edited by Trilby (2012-09-01 15:10:14)

    Thanks.  I solved the issue.  I found this thread: https://bbs.archlinux.org/viewtopic.php?pid=901651
    Basically I just copied all of the modules listed in lsmod to the MODULES section of the mkinitcpio.conf on the HD, removed autodetect from the hooks, and ran mkinitcpio -p linux-mac.  I'm not sure what all of that was actually mandatory, I didn't check, but I know it worked.  I think the main thing was the pata_macio module.
    Turns out persistent block device naming wasn't my issue at all.  I reverted back to using /dev/sdaX names.

  • [SOLVED] ERROR: Can't find root device /dev/disk/by-uuid/...

    Yesterday I upgraded my Lenovo X100e
    # pacman -Syu
    and rebooted.  Upon reboot, I received the error
    ERROR: Cannot find root device '/dev/disk/by-uuid/[...]'
    just after kernel decompression. I got dropped into the recovery shell
    and could not boot.
    The problem persisted despite using different root device names (e.g. /dev/sda3, the actual root device).  After reading the instructions at https://wiki.archlinux.org/index.php/Chroot I used a core installation image (on a usb stick) to boot the machine, then chrooted into my installation.  I ran mkinitcpio and found that the udev hook was missing, i.e. not in /lib/initcpio/hooks.  Nor was there a file called 'udev' in /lib/initcpio/install.
    I copied these files from a friend's installation and then re-ran mkinitcpio:
    # mkinitcpio -p linux
    I was able to reboot successfully after that.
    The weird thing: I don't know how the udev hook script was deleted from /lib/initcpio/hooks.
    If someone else runs into this problem: try to run mkinitcpio (e.g. by using the chroot), and check for this problem.  I think the problem was that the root device could not be found because the udev hook had not run, and therefore /dev was unpopulated.

    Betwen udev-181-2 and udev-181-5, the hooks have moved from /lib/initcpio to /usr/lib/initcpio. But mkinitcpio -L should still list them.
    I have a similar problem since the last update. The kernel doesn't seem to load my raid driver anymore. Upon boot it throws some cryptic udev messages at me and then crashes. Haven't found out what that is about yet.

  • Systemd device dev-disk-by\{stuff} appeared twice with sysfs diff path

    $ dmesg -l err
    [ 6.330201] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache2
    [ 6.332384] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache1
    [ 6.334041] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache1
    [ 6.730564] systemd[1]: Device dev-disk-by\x2dlabel-raid0.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache2 and /sys/devices/virtual/block/bcache3
    [ 6.732213] systemd[1]: Device dev-disk-by\x2duuid-d527fcab\x2d1897\x2d46a1\x2d8324\x2d18de507f4993.device appeared twice with different sysfs paths /sys/devices/virtual/block/bcache0 and /sys/devices/virtual/block/bcache3
    [ 6.997304] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
    [ 6.999960] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf3
    [ 7.003235] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
    [ 7.005881] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf1
    [ 7.194594] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
    [ 7.197369] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde1
    [ 7.207859] systemd[1]: Device dev-disk-by\x2dlabel-raid1.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
    [ 7.210477] systemd[1]: Device dev-disk-by\x2duuid-99fd7889\x2dde7a\x2d4b30\x2d9745\x2d8ccb2b1ee75d.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc2 and /sys/devices/pci0000:00/0000:00:01.1/0000:04:00.0/ata7/host6/target6:0:0/6:0:0:0/block/sde/sde3
    [ 7.240459] systemd[1]: Device dev-disk-by\x2dlabel-aroot.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
    [ 7.243114] systemd[1]: Device dev-disk-by\x2duuid-3873d8ba\x2d9472\x2d4d92\x2dab0d\x2de94574bd0eae.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1c.7/0000:0c:00.0/ata17/host16/target16:0:0/16:0:0:0/block/sdf/sdf4 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb2
    [ 8.062829] systemd[1]: Device dev-disk-by\x2dlabel-jabod.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
    [ 8.065328] systemd[1]: Device dev-disk-by\x2duuid-0d19cfc3\x2d7588\x2d4c19\x2db85e\x2dbf3a3db2d4a0.device appeared twice with different sysfs paths /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdc/sdc3 and /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb/sdb4
    I've been getting this since I upgraded systemd last week. I tried fixing some of these by removing partitions with the same label that I wasn't using, which worked. The reason I have so many partitions with the same label is due to btrfs. Each partition that makes up a volume in btrfs has the same label. Apparently systemd doesn't like this.
    Everything on my system seems to be working fine, however I would like to stop these errors since they are annoying/scary, but without having to reduce all my volumes to single.
    Last edited by nstgc (2015-04-26 15:53:20)

    I'm running with a wired-only set up. I'll have to wait for the weekend to look into the wireless angle, however I doubt that is the cause for me.
    Following dront78's example below is the output of "# hwinfo --partitions"
    75: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: bdUI.SE1wIdpsiiC
    Parent ID: 3OOL.7ppt9e3ai+9
    SysFS ID: /class/block/sda/sda1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sda1
    Device Files: /dev/sda1, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part1, /dev/disk/by-id/wwn-0x6829766019904589826x-part1, /dev/disk/by-partuuid/77f1354c-3b20-454d-ba60-9dbab9bc8640, /dev/disk/by-uuid/ff387510-d0ad-498f-8d1b-576b26ed103e
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #74 (Disk)
    76: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: 2pkM.SE1wIdpsiiC
    Parent ID: 3OOL.7ppt9e3ai+9
    SysFS ID: /class/block/sda/sda2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sda2
    Device Files: /dev/sda2, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part2, /dev/disk/by-id/wwn-0x6829766019904589826x-part2, /dev/disk/by-partuuid/44596381-4cfe-4a2d-8e7b-f6427cc089d0
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #74 (Disk)
    77: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: W__Q.SE1wIdpsiiC
    Parent ID: 3OOL.7ppt9e3ai+9
    SysFS ID: /class/block/sda/sda3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sda3
    Device Files: /dev/sda3, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part3, /dev/disk/by-id/wwn-0x6829766019904589826x-part3, /dev/disk/by-partuuid/c9b404ec-f407-4081-a69c-9b10360d4cf7
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #74 (Disk)
    78: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: z9FV.SE1wIdpsiiC
    Parent ID: 3OOL.7ppt9e3ai+9
    SysFS ID: /class/block/sda/sda4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sda4
    Device Files: /dev/sda4, /dev/disk/by-id/ata-KINGSTON_SH103S3240G_50026B7234025EC8-part4, /dev/disk/by-id/wwn-0x6829766019904589826x-part4, /dev/disk/by-partuuid/69c0972d-51ed-429c-acea-6e1afd7ebb1f
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #74 (Disk)
    80: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: h4pj.SE1wIdpsiiC
    Parent ID: WZeP.bTSLTpVNGx8
    SysFS ID: /class/block/sdb/sdb1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdb1
    Device Files: /dev/sdb1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part1, /dev/disk/by-id/wwn-0x17950130428369588225x-part1, /dev/disk/by-uuid/2c0f1039-2d4b-4f75-8fa4-529d19cd18fc
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #79 (Disk)
    81: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: 8G3o.SE1wIdpsiiC
    Parent ID: WZeP.bTSLTpVNGx8
    SysFS ID: /class/block/sdb/sdb2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdb2
    Device Files: /dev/sdb2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part2, /dev/disk/by-id/wwn-0x17950130428369588225x-part2, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #79 (Disk)
    82: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: bRJs.SE1wIdpsiiC
    Parent ID: WZeP.bTSLTpVNGx8
    SysFS ID: /class/block/sdb/sdb3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdb3
    Device Files: /dev/sdb3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part3, /dev/disk/by-id/wwn-0x17950130428369588225x-part3, /dev/disk/by-label/old-raid1, /dev/disk/by-uuid/dfa989d8-edac-4c7e-b6fc-45237e6a0ebc
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #79 (Disk)
    83: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: 2dZw.SE1wIdpsiiC
    Parent ID: WZeP.bTSLTpVNGx8
    SysFS ID: /class/block/sdb/sdb4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdb4
    Device Files: /dev/sdb4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33388736-part4, /dev/disk/by-id/wwn-0x17950130428369588225x-part4, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #79 (Disk)
    85: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: mX79.SE1wIdpsiiC
    Parent ID: _kuT.rgQvtxWxfg6
    SysFS ID: /class/block/sdc/sdc1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdc1
    Device Files: /dev/sdc1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part1, /dev/disk/by-id/wwn-0x4611505914592251905x-part1, /dev/disk/by-uuid/80780835-de4b-462c-b7f0-2b389d3e2c2f
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #84 (Disk)
    86: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: DjND.SE1wIdpsiiC
    Parent ID: _kuT.rgQvtxWxfg6
    SysFS ID: /class/block/sdc/sdc2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdc2
    Device Files: /dev/sdc2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part2, /dev/disk/by-id/wwn-0x4611505914592251905x-part2, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #84 (Disk)
    87: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: gudH.SE1wIdpsiiC
    Parent ID: _kuT.rgQvtxWxfg6
    SysFS ID: /class/block/sdc/sdc3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdc3
    Device Files: /dev/sdc3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part3, /dev/disk/by-id/wwn-0x4611505914592251905x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #84 (Disk)
    88: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: 74uL.SE1wIdpsiiC
    Parent ID: _kuT.rgQvtxWxfg6
    SysFS ID: /class/block/sdc/sdc4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdc4
    Device Files: /dev/sdc4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WMAW31235179-part4, /dev/disk/by-id/wwn-0x4611505914592251905x-part4, /dev/disk/by-label/old-aroot, /dev/disk/by-uuid/b396dd50-e3f1-4b74-8cac-7d8d79a75386
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #84 (Disk)
    90: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: r_Ra.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd1
    Device Files: /dev/sdd1, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part1, /dev/disk/by-id/wwn-0x14865109125905272832x-part1, /dev/disk/by-partlabel/Microsoft\x20reserved\x20partition, /dev/disk/by-partuuid/f3e9ce24-988d-40ef-bd5c-6313c808bef2
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    91: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: IAie.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd2
    Device Files: /dev/sdd2, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part2, /dev/disk/by-id/wwn-0x14865109125905272832x-part2, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/f3344931-99c3-11e4-8601-806e6f6e6963, /dev/disk/by-uuid/30F403F0F403B75E
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    92: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: lLyi.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd3
    Device Files: /dev/sdd3, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part3, /dev/disk/by-id/wwn-0x14865109125905272832x-part3, /dev/disk/by-partlabel/EFI\x20system\x20partition, /dev/disk/by-partuuid/ffbaa0cc-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/0DE5-0CB0
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    93: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: CXCn.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd4
    Device Files: /dev/sdd4, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part4, /dev/disk/by-id/wwn-0x14865109125905272832x-part4, /dev/disk/by-partlabel/Basic\x20data\x20partition, /dev/disk/by-partuuid/ffbaa0b6-99c7-11e4-8625-806e6f6e6963, /dev/disk/by-uuid/FE2648382647EFE7
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    94: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: fiSr.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd5
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd5
    Device Files: /dev/sdd5, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part5, /dev/disk/by-id/wwn-0x14865109125905272832x-part5, /dev/disk/by-label/flbck, /dev/disk/by-partuuid/bd84f197-066e-4b9e-bf9b-b0b3a4090cde, /dev/disk/by-uuid/832bcc8d-836e-4b4e-8d9c-0a19f5bcf7dd
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    95: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: 6uiv.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd6
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd6
    Device Files: /dev/sdd6, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part6, /dev/disk/by-id/wwn-0x14865109125905272832x-part6, /dev/disk/by-partuuid/8f77bc79-ba57-462e-8beb-d09db5c77490
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    96: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: oKuO.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd7
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd7
    Device Files: /dev/sdd7, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part7, /dev/disk/by-id/wwn-0x14865109125905272832x-part7, /dev/disk/by-partuuid/7ca3eb27-d198-4915-9c71-e96fa7a34d8b, /dev/disk/by-uuid/fd43f1bd-9f52-41b7-badc-4ab7881473ee
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    97: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: GW8T.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd8
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd8
    Device Files: /dev/sdd8, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part8, /dev/disk/by-id/wwn-0x14865109125905272832x-part8, /dev/disk/by-partuuid/550f9e19-c0ec-4474-9e98-84c727854158
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    98: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: cPdt.SE1wIdpsiiC
    Parent ID: Rw8Y.lfY9_MpZuK1
    SysFS ID: /class/block/sdd/sdd10
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdd10
    Device Files: /dev/sdd10, /dev/disk/by-id/ata-ST4000NM0053-1C1170_Z1Z6NSNF-part10, /dev/disk/by-id/wwn-0x14865109125905272832x-part10, /dev/disk/by-label/bckup, /dev/disk/by-partuuid/de7eaa1e-66b0-4058-ad71-d0f8ea470b2f, /dev/disk/by-uuid/723d7788-8514-4777-8e07-e0faa48c9a83
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #89 (Disk)
    100: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: wRm+.SE1wIdpsiiC
    Parent ID: u5Pc.jfv0tLKpnVA
    SysFS ID: /class/block/sde/sde1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sde1
    Device Files: /dev/sde1, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part1, /dev/disk/by-id/wwn-0x9832618751734861824x-part1, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #99 (Disk)
    101: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: Nd04.SE1wIdpsiiC
    Parent ID: u5Pc.jfv0tLKpnVA
    SysFS ID: /class/block/sde/sde2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sde2
    Device Files: /dev/sde2, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part2, /dev/disk/by-id/wwn-0x9832618751734861824x-part2, /dev/disk/by-uuid/aa19d2cf-e59d-4277-a5e6-d0078ede6d3b
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #99 (Disk)
    102: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: qoG8.SE1wIdpsiiC
    Parent ID: u5Pc.jfv0tLKpnVA
    SysFS ID: /class/block/sde/sde3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sde3
    Device Files: /dev/sde3, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part3, /dev/disk/by-id/wwn-0x9832618751734861824x-part3, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #99 (Disk)
    103: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: H_WC.SE1wIdpsiiC
    Parent ID: u5Pc.jfv0tLKpnVA
    SysFS ID: /class/block/sde/sde4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sde4
    Device Files: /dev/sde4, /dev/disk/by-id/ata-ST2000NM0053-1C1175_Z1X48TVG-part4, /dev/disk/by-id/wwn-0x9832618751734861824x-part4
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #99 (Disk)
    105: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: +u4R.SE1wIdpsiiC
    Parent ID: LHfg.eZsVjjzwg10
    SysFS ID: /class/block/sdf/sdf1
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdf1
    Device Files: /dev/sdf1, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part1, /dev/disk/by-id/wwn-0x8355873293896667137x-part1, /dev/disk/by-label/raid1, /dev/disk/by-uuid/99fd7889-de7a-4b30-9745-8ccb2b1ee75d
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #104 (Disk)
    106: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: S4LV.SE1wIdpsiiC
    Parent ID: LHfg.eZsVjjzwg10
    SysFS ID: /class/block/sdf/sdf2
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdf2
    Device Files: /dev/sdf2, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part2, /dev/disk/by-id/wwn-0x8355873293896667137x-part2, /dev/disk/by-uuid/96fa47c5-061d-4849-8582-7186cc1695d2
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #104 (Disk)
    107: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: vFbZ.SE1wIdpsiiC
    Parent ID: LHfg.eZsVjjzwg10
    SysFS ID: /class/block/sdf/sdf3
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdf3
    Device Files: /dev/sdf3, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part3, /dev/disk/by-id/wwn-0x8355873293896667137x-part3, /dev/disk/by-label/jabod, /dev/disk/by-uuid/0d19cfc3-7588-4c19-b85e-bf3a3db2d4a0
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #104 (Disk)
    108: None 00.0: 11300 Partition
    [Created at block.414]
    Unique ID: NRrd.SE1wIdpsiiC
    Parent ID: LHfg.eZsVjjzwg10
    SysFS ID: /class/block/sdf/sdf4
    Hardware Class: partition
    Model: "Partition"
    Device File: /dev/sdf4
    Device Files: /dev/sdf4, /dev/disk/by-id/ata-WDC_WD1003FBYX-01Y7B1_WD-WCAW33509457-part4, /dev/disk/by-id/wwn-0x8355873293896667137x-part4, /dev/disk/by-label/aroot, /dev/disk/by-uuid/3873d8ba-9472-4d92-ab0d-e94574bd0eae
    Config Status: cfg=new, avail=yes, need=no, active=unknown
    Attached to: #104 (Disk)
    i don't have time to look at this in detail this morning, but I will this afternoon.
    Thank you for all the replies. Have any of you found this to actually be damaging?
    [edit] In an effort to not be completely lazy, and because I was curious, I did check a bit into netctl. Running "$ netctl list" returned exactly nothing. I have no profiles.
    [edit2]
    I just ran "$ dmesg -l err" on my laptop and I'm not getting any errors.
    Last edited by nstgc (2015-04-27 15:09:46)

  • I've done everything I know in order to get my calendar in iCloud synchronized with my macBook, my IPad and my iPhone, but get no success. I've checked if all devices are set to the same account. Can you help me?

    I've done everything I know in order to get my calendar in iCloud synchronized with my macBook, my IPad and my iPhone, but get no success. I've checked if all devices are set to the same account. Can you help me?

    The only thing I can see strange is that when I login my iCloud account through my principal email address, when I check my preferences is marked an @me.com address that is old and I don't use it anymore, but I can't erase it or even change it.

  • HT4847 I am unable to delete the last backup from icloud, i checked my all device setting but it still say "cannot delete icloud this time because it is in use,"Please tell me what should i do.

    I am unable to delete the last backup from icloud, i checked my all device setting but it still say "cannot delete icloud this time because it is in use,"Please tell me what should i do                             

    It still didn't work...
    Within this commonfiles\apple folder, there is only one folder, labeled "Internet Services." Within this folder, there are 6 folders, labeled:
    APLZOD.resources
    BookmarkDAV_client.resources
    CoreDAV.resources
    iCloud.resources
    iCloudServices.resources
    ShellStreams.resources
    Within all but CoreDAV and BookmarkDAV_client, there are multiple different folders, all labeled starting with a two letter (acronym I believe, for different languages) then .lproj (for example, a folder is labeled "ar.lproj".
    In each of the folders of APLZOD.resources, there is a file labeled "APLZODlocalized.dll."
    In all of the folders containing the multiple .lproj folders, there are likewise "name"localized.dll files contained.
    In the BookmarkDAV_client and Core DAV folders, they each contain only one file, "Info.plist"
    I attempted to delete all of these files, and still, the FileAssassin could not delete them. I unlocked one of them for instance, and I tried to delete the file myself (thru windows explorer and just clicking delete), and I still had the same issue of coming eventually to the window requesting me to "try again" to have permission.
    What can I do?? I'd like to avoid Unlocker, but if it really is a reliable and SAFE program, and someone knows a SAFE place to download it from, I'd appreciate it very much so!!
    thanks!!

  • Apple TV worked until today. Message says unsupported signal check your output device.  I have checked hdmi cable with another device and it's fine. Put on a different tv and same message.  Went out yesterday and bought a new Apple TV and same problem.

    Apple TV worked until today. Message says unsupported signal check your output device.  I have checked hdmi cable with another device and it's fine. Put on a different tv and same message.  Went out yesterday and bought a new Apple TV and same problem.

    Which TV do you have.
    You may wish to try the following:
    Press and hold the menu and the up button simultaneously on the remote for six seconds, the Apple TV should then begin to cycle through the various resolutions available to it at 20 second intervals.. If you see a picture appear up on your screen, use the remote to scroll down to the OK option and select it.

  • [SOLVED] ERROR: Unable to find root device '/dev/sda3'

    Earlier I updated the kernel to my arch system and found this error while trying to boot. I hate to post this because there are so many topics like it, but I've been looking for hours for a solution to this problem and can't find one.
    Here is the output:
    Booting 'Arch Linux'
    root (hd0,1)
    Filesystem type is ext2fs, partition type 0x83
    kernet /vmlinuz-linux root=/dev/sda3 ro
    [Linux-bzImage, setup=0x4200, size=0x2ff2d0]
    initrd /initrd @ 0xfd17000, 0x2c878c bytes]
    Probing EDD (edd=off to disable)... ok
    Decompressing Linux... Parsing ELF... done.
    Booting the kernel.
    :: Starting udevd...
    done.
    Waiting 10 seconds for device /dev/sda3 ...
    ERROR: device '/dev/sda3' not found. skipping fsck.
    ERROR: Unable to find root device '/dev/sda3'.
    You are being dropped to a recovery shell
    type 'exit' to try and continue booting
    sh: can't access tty; job control turned off
    My partition layout is like this:
    swap: /dev/sda1
    boot: /dev/sda2
    root: /dev/sda3
    extended: /dev/sda4
    home: /dev/sda5
    I have two hard drives, but i'm sure /dev/sda is the one with my OS.
    Here are some things I've tried:
    This was at the very bottom of the pacman wiki
    # mkdir /mnt/arch
    # mount /dev/sdaX /mnt/arch (your root partition)
    # cd /mnt/arch
    # mount -t proc proc proc/
    # mount -t sysfs sys sys/
    # mount -o bind /dev dev/
    # mount /dev/sdaX boot/ (your /boot partition) #This step is not needed if you do not have a separate boot partition
    # chroot .
    # pacman -Syu udev mkinitcpio
    # mkinitcpio -p linux
    I've also tried performing the above, downgrading the kernel, updating my mirrorlist, reinstalling the kernel, and rebooting as mentioned here.
    I've alsa tried a few other things that I've read, but can no longer remember.
    Any help would be greatly appreciated! Thanks.
    Last edited by colton7909 (2012-05-25 02:09:36)

    Thank colton
    Same problem here, but on a mac book (not mine eyh )
    So, for those how have the problem (or need a live usb for mac or uefi systems),
    1) with a 32bits system
    - download gparted live cd
    - use it for the step 3
    2) with a 64bits system:
    - you need the gparted live cd too: mount it and copy the EFI directory somewhere; then umount it;
    - download a 64bits system (system rescue cd, as colton said is enough, follow the instructions for installation on their website first);
    - mount you live usb, install the 64bits system;
    - copy EFI system on the key
    - edit the grub.cfg in EFI/boot/ , add the following before the other entries:
    menuentry "System Rescue" {
    set gfxpayload=keep
    linux /syslinux/altker64 nomodeset efi
    initrd /syslinux/initram.igz
    3) repairing...
    - boot the broken computer with the live usb
    - mount the partition on which your system is (e.g. /dev/sda1 on /mnt)
    - chroot it, init the system as needed (mount /dev, /proc, etc. the easier way is using init scripts)
    % chroot /mnt /bin/bash
    % /etc/rc.sysinit
    % mkinitcpio -p linux

  • Adobe FLME Error Message "Please check if video devices are connected properly and are not used by any other application."

    Hello, I'm trying to use my MAC Book Pro with Adobe FMLE. Once I select either my internal or external camera and microphone, in the live encoder I get this error message. "Please check if video devices are connected properly and are not used by any other application." The Facetime HD camera works in Photo Booth. Can someone assist me in what to do please, Thanks in advance!

    Hi all ,
    We found the solution for this issue .
    We have installed the crypto library in global executable directory and any way it will replicate those binaries to individual application servers.
    But the parameters are still looking for global executable directory for loading crypto library during time.
    So all application servers are trying to load crypto library files from global "exe" instead of local directory, which was clustered .Sometimes during  heavy network load it may cause some delays to load the libraries to individual application servers and in turn is causing the license key issues.
    Note 982056 - The license key library has not been initialized yet..
    SAP Recommend option for all SSF parameters should be instance profile parameters not in default parameters..This was mentioned in below note:
    Note 662340 - SSF Encryption Using the SAPCryptolib --- .
    But in our Environment SSF and SEC parameter were set in DEFAULT profile instead Instance profile.
    Recommendations:
    o     ssf/ssfapi_lib  = <Path and file name of SAPCRYPTOLIB>
    o     sec/libsapsecu  = <Path and file name of SAPCRYPTOLIB>
    This was mentioned in the below SAP HELP.
    http://help.sap.com/saphelp_nw04/helpdata/en/3d/bf463c6796e61ce10000000a114084/frameset.htm.

  • Couldn't open mixer device /dev/audioctl

    I have just installed Solaris10 x86 OS on my Toshiba Satellite Laptop, everything seesm to work fine but I have no audio. The volume control icon on the panel says > no audio device and when I click on it I get an error dialog saying> Couldn't open mixer device /dev/audioctl
    I have downloaded the Solaris Audio Drivers 1.0, audio810 and audiovia823x from the Sun website and installed them but no use, I also installed the audio drivers from the http://www.tools.de/solaris/audio/ website > audio1371, audioemu, audioi810, audiovia8233 but nothing.
    Could anyone please advise me how I can get the audio working.
    Thanks,
    Suraj

    HI thankx,
    I tried your solution but>
    devfsadm: driver failed to attach: audio810
    Warning: Driver (audio810) successfully added to system but failed to attach

  • Opening device /dev/sg3 failed - access denied to /dev/sg* device file

    Opening device /dev/sg3 failed - access denied to /dev/sg* device file (OB scsi device driver)
    Got this message when running an automated RMAN job.
    To my knowledge the only thing that has changed since being able to run RMAN jobs with OSB and not being able to run them is that the permissions on /usr/tmp were changed from drwxr-xr-x, not drwxrwxrwx.
    Transcript below:
    2010/01/27.04:03:20 ______________________________________________________________________
    2010/01/27.04:03:20
    2010/01/27.04:03:20 Transcript for job oracle/6142.1 running on backup01
    2010/01/27.04:03:20
    2010/01/27.04:03:20 (amh) qdv__automount_in_mh tape1 at 2010/01/27.04:03:20, flags 0x100
    2010/01/27.04:03:20 (amh) mount volume options list contains:
    2010/01/27.04:03:20 (amh) vtype 3, vid (null), vs_create 0, family PAS-RMAN, retain (null), size 0, scratch 0
    2010/01/27.04:03:21 (amh) don't preserve previous mh automount state
    2010/01/27.04:03:21 (amh) loaded volume has no barcode
    2010/01/27.04:03:22 (amh) beginning pass 1
    2010/01/27.04:03:22 (mmr) volset containing oid 20859 (vid PASWLY-000215, tag 000086L3) is closed
    2010/01/27.04:03:22 (amh) 1 oid 20859 doesn't meet mount requirements - volume set is closed to further update (OB device mgr)
    2010/01/27.04:03:22 (mmr) need next volume after oid 20543 (vid PAS-RMAN-018887, tag 000048L3) for append; its oid 20604
    2010/01/27.04:03:22 (amh) 2 oid 20543 doesn't meet mount requirements - the next volume of this set is needed (OB device mgr)
    2010/01/27.04:03:22 (mmr) oid 20949 (vid PAS-RMAN-018935, tag 000021L3) passes criteria
    2010/01/27.04:03:22 (amh) 3 loading
    2010/01/27.04:04:04 (mt) qdv__read_label() succeeded; read 65536 bytes
    2010/01/27.04:04:05 (atv) automount worked
    2010/01/27.04:04:05 (amh) 3 automount worked - returning
    2010/01/27.04:04:05 (amh) end of automount at 2010/01/27.04:04:05 (0x0)
    2010/01/27.04:04:05 Info: volume in tape1 is usable for this operation.
    2010/01/27.04:04:05 (pvfw) at BOT
    2010/01/27.04:04:05 (pvfw) previous state is invalid
    2010/01/27.04:04:05 (alv) backup image label is valid, file 1, section 1
    2010/01/27.04:04:05 (pvfw) invalidating tape position in mount db
    2010/01/27.04:04:05 (ial) invalidate backup image label (was valid)
    2010/01/27.04:05:17 (pvfw) space to EOD
    2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [0] = filemark
    2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [1] = filemark
    2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [2] = data
    2010/01/27.04:05:26 (pvfw) inspect_recs BSR: rtypes [3] = filemark
    2010/01/27.04:05:26 (pvfw) inspect_recs FSF
    2010/01/27.04:05:26 (pvfw) inspect_recs ready to mount
    2010/01/27.04:05:26 (pvfw) mounting at inspect_rec's request in rw_mode 2
    2010/01/27.04:05:28 (pvfw) mounted ok
    2010/01/27.04:05:28 (pvfw) at OB EOD, returning (2)
    2010/01/27.04:05:28 (pvfw) pos_vol_cleanup not returning pstate
    2010/01/27.04:05:28 (dmap) tape1 success
    04:05:28 OBTR: obtar version 10.2.0.3.0 (linuxamd64) -- Wed Sep 24 11:12:44 PDT 2008
    Copyright (c) 1992, 2007, Oracle. All rights reserved.
    04:05:28 OBTR: obtar -c -Xjob:oracle/6142.1 -Xob:10.2 -Xstat -X shm:/usr/tmp/obsbt_10985_0_126458300010985a -Xbga:oracle/6142.1 -y /usr/tmp/[email protected] -J -F5 -f tape1 -Xrescookie:0x99ECC895 -H backup01 -zR
    04:05:28 OBTR: running as root/root
    04:05:28 OBTR: record storage set to internal memory
    04:05:28 ATAL: reserved drive tape1, cookie 0x99ECC895
    04:05:28 OBTR: obsd=1, is_job=1, is_priv=0, os=15
    04:05:28 OBTR: rights established for user oracle, class admin
    04:05:28 SUUI: user info oracle/oinstall, ??/??
    04:05:28 STTY: background terminal I/O or is a tty
    04:05:28 MAIN: interactive
    04:05:28 SET: volume has no expiration time
    04:05:28 CNPC: data host reports this butype_info:
    04:05:28 CNPC: tar (attr 0x2C78: B_DIRECT, R_DIRECT, B_INCR, R_INCR, B_FH_DIR)
    04:05:28 CNPC: DIRECT = y
    04:05:28 CNPC: HISTORY = y
    04:05:28 CNPC: LEVEL = 0
    04:05:29 DOLM: nop (for tape1 (raw device "/dev/sg3"))
    04:05:29 DOLM: ok
    04:05:30 RLE: connecting to volume/archive database host
    04:05:30 RLE: device tape1 (raw device "/dev/sg3")
    04:05:30 RLE: mount_info is valid
    04:05:30 A_O: tape device is local
    04:05:30 A_O: Devname: HP,Ultrium 3-SCSI,G63Z
    04:05:30 Info version: 11
    04:05:30 WS version: 10.2
    04:05:30 Driver version: 10.2
    04:05:30 Max DMA: 2097152
    04:05:30 Blocksize in use: 65536
    04:05:30 Query frequency: 134217728
    04:05:30 Rewind on close: false
    04:05:30 Can compress: true
    04:05:30 Compression enabled: true
    04:05:30 8200 media: false
    04:05:30 Error threshold: 8%
    04:05:30 Remaining tape: 403359744
    04:05:30 A_GB: ar_block at 0x2B544951A000, size=2097152
    04:05:30 A_GB: ar_block_enc at 0x2B544971E000, size=2097152
    04:05:30 ADMS: reset library tape selection state
    04:05:30 ADMS: reset complete
    04:05:30 VLBR: not at bot: 0x9
    04:05:30 VLBR: tag on label just read: "000021L3"
    04:05:30 VLBR: master tag now "000021L3"
    04:05:30 RLE: set kb remaining to 403359744
    04:05:30 RLE: noticed nil label
    04:05:30 ARVI: resetting volume id from nil to PAS-RMAN-018935
    04:05:30 PF: here's the label at the current position:
    Volume label:
    Volume tag: 000021L3
    Intro time: Tue Jun 02 17:00:51 2009
    Volume UUID: d0e25812-ed54-102c-a34d-001143fd735c
    Volume ID: PAS-RMAN-018935
    Volume sequence: 1
    Volume set owner: root
    Volume set created: Tue Jan 26 23:32:25 2010
    Media family: PAS-RMAN
    Volume set expires: never; content manages reuse
    Original UUID: d0e25812-ed54-102c-a34d-001143fd735c
    Archive label:
    File number: 5
    File section: 1
    Owner: root
    Client host: merge01
    Backup level: 0
    S/w compression: no
    Archive created: Wed Jan 27 00:08:56 2010
    Marker: End of data
    04:05:30 PF: at desired location
    04:05:30 RCVW: volume "PAS-RMAN-018935" / vuuid d0e25812-ed54-102c-a34d-001143fd735c reserved for writing
    04:05:30 CREA: tape position after open_archive() is 0001A1800000
    04:05:30 GLMT: returning "000021L3", code = 0x0
    04:05:30 IMF: inherited media family PAS-RMAN is content-managed
    04:05:30 CREA: setting history tag to "000021L3" from volume label
    04:05:30 RLE: overwrite invalid/blank/marker section
    04:05:30 VLBW: on entry, l->tag = "", master tag = "000021L3", bot = 0
    04:05:30 VLBW: setting voltag from "" to "000021L3"
    04:05:30 VLBW: volume is content-managed
    04:05:30 RLE: write volume PAS-RMAN-018935, file 5, section 1, vltime 1264566745, vowner root, voltag 000021L3
    04:05:30 VSLW: set last write time for volume oid 20949
    04:05:31 ULVI: set mh db volume id "PAS-RMAN-018935" (retid "000021L3"), volume oid 20949, code 0
    04:05:31 ULTG: set mh db tag "000021L3" (retid "PAS-RMAN-018935"), volume oid 20949, code 0
    04:05:31 RLE: set kb remaining to "invalid or unknown"
    Volume label:
    Volume tag: 000021L3
    Intro time: Tue Jun 02 17:00:51 2009
    Volume UUID: d0e25812-ed54-102c-a34d-001143fd735c
    Volume ID: PAS-RMAN-018935
    Volume sequence: 1
    Volume set owner: root
    Volume set created: Tue Jan 26 23:32:25 2010
    Media family: PAS-RMAN
    Volume set expires: never; content manages reuse
    Original UUID: d0e25812-ed54-102c-a34d-001143fd735c
    Archive label:
    File number: 5
    File section: 1
    Owner: root
    Client host: backup01
    Backup level: 0
    S/w compression: no
    Archive created: Wed Jan 27 04:05:28 2010
    Archive owner UUID: 9d92d00e-0368-102b-89f6-001143fd735c
    Owner class UUID: edde6dc8-f857-102a-a357-001143fd735c
    Backup piece name: 8sl4ft06_1_1
    Backup db name: emrep
    Backup db id: 3844670930
    Backup copy number: not applicable
    Backup content: archivelog
    04:05:31 RCVW: volume "PAS-RMAN-018935" / vuuid d0e25812-ed54-102c-a34d-001143fd735c reserved for writing
    04:05:31 ADMS: reset library tape selection state
    04:05:31 ADMS: reset complete
    04:05:31 SNP: using NDMP protocol version 4
    04:05:36 FLDB: drive buffer flush to medium took 0:05 (min:sec)
    04:05:36 BNPC: volume position "0001A181" added to s_vol_start_pos
    04:05:36 BNPC: initial volume label "PAS-RMAN-018935" added to s_vids, s_last_section 1
    04:05:36 BNPC: initial volume tag "000021L3" added to s_vtags, s_last_section 1
    04:05:36 BNPC: environment variable DATA_BLOCK_SIZE = 64
    04:05:36 BNPC: environment variable DATA_ARCH_UUID = f3ccd49e-ed7a-102c-be2b-001143fd735c
    04:05:36 MGS: ms.record_size 65536, ms.record_num 0x0, ms.bytes_moved 0x0
    04:05:36 SMWB: setting mover window for possible checkpoint during backup
    04:05:36 MLIS: mover listen ok for local connection
    04:05:36 APNI: a preferred network interface does not apply to this connection
    04:05:36 DPNI: a local NDMP data connection is in use
    04:05:36 BNPC: directing data service to connect to mover
    04:05:42 BNPC: issuing NDMP_DATA_START_BACKUP
    04:05:47 BNPC: started OSB NDMP backup of backup01 to tape1
    04:16:51 MNPO: data service halted with reason=successful
    04:16:51 SNPD: Data Service reported bytes processed 0x6DF20000
    Opening device /dev/sg3 failed - access denied to /dev/sg* device file (OB scsi device driver)

    Permissions problem on the drive for the user running the job.

  • ERROR: Device '/dev/sda3' not found.

    This is my first time compiling a custom kernel. I am trying to compile zen kernel 3.12.3. Whenever I try to boot it up, it says this:
                    ERROR: device '/dev/sda3' not found. Skipping fsck
                    ERROR: Unable to find root device '/dev/sda3'
    Then it drops me to a recovery shell. When I look at the contents of '/dev' none of my partitions are found on sda. '/dev/sda' is listed but nothing else. Has anybody else had this problem? /i have read various fixes but none of them have helped.
    Sorry this is my first post.
    Thanks in advance.

    Well, the whole point of the initramfs is to have it load the necessary modules to mount the rootfs.  So if mkinitpcio complains that there are no modules to put in there, that is pretty problematic.
    I think you should take a look at the PKGBUILD for the official Arch kernel.  It includes a few lines that allow you to use menuconfig or nconfig or whatever, prior to that actual 'make'.  I think that any time you install things to your system, you should probably be leveraging the package manager in order to properly track the files.  This is particularly true when you are an Arch user and the creation of packages is so damn easy.

Maybe you are looking for

  • Wait ms Timer Multiple returning inaccurate timer value

    We are using the Wait Until Next ms Multiple Timer value to set the interval that data is recorded to a file. Because of Windows 2000 time indeterminancy, the Wait Until Next ms Multiple Timer value is written to file, along with the data point, and

  • Displaying current and previous 5 Year data in a bar graph

    Hi , My requirement goes like this ..... I have to show revenue (measure) data based on current year (period dimension) selection (from a dashboard prompt) and previous 5 year data's as well . i.e. if user selects 2013 , the bar graph will display 6

  • Location of State code in SAP B1

    Hi where is the location of state code in SAP B1 so that i can fill the correct codes of the state coz iwant to import BP and error while importing i get is wrong state code.

  • Default Employee vendor Cost Center

    hi, Can you please let me know HOw I CAN GET THE DEFAULT VENDOR COST CENTER (F-02). I was Tryed Substitutions But it is not working. Regards, Nageswar

  • Napster-to-go and "Download Erro

    The download errors I am talking about happen between the Napster site and my PC, not between my PC and my Micro. When I first started using Napster about 0 months ago, I used to get 'download errors' in about /2 the songs I would download, at which