Failed mount /dev/mapper/oradata

Hello experts!
After reboot OS failed mount /dev/mapper/oradata
OS: SUSE 10 sp4 ppc64
SAN: DS5300
My steps how i add the LUN:
1) rescan-scsi-bus.sh
2) vi /etc/multipath.conf
defaults
user_friendly_names no
multipaths {
multipath {
wwid 3600a0b80006e6a66000040a95066a18b
alias oradata
3) fdisk /dev/dm-2
4) echo 'add' > /sys/block/dm-2/uevent
5) /sbin/mkfs.reiserfs /dev/dm-2
6) mkdir /oradata
7) vi /etc/fstab
/dev/mapper/oradata /oradata reiserfs acl,user_xattr 1 2
8) mount a
C01-OraDB-02:~ # multipath -ll
oradata (3600a0b80006e6a66000040a95066a18b) dm-2 IBM,1818 FAStT
[size=100G][features=0][hwhandler=0]
\_ round-robin 0 [prio=0][enabled]
\_ 2:0:1:0 sdf 8:80 [failed][faulty]
\_ round-robin 0 [prio=1][active]
\_ 2:0:0:0 sde 8:64 [active][ready]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:1:0 sdd 8:48 [failed][faulty]
\_ round-robin 0 [prio=1][enabled]
\_ 1:0:0:0 sdc 8:32 [active][ready]
In logs /var/log/messages
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0
end_request: I/O error, dev sdf, sector 0
end_request: I/O error, dev sdd, sector 0

ostapv,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Similar Messages

  • Systemd: mounting /dev/mapper/... fails

    Since some recent update one of my LUKS-encrypted volumes is not being mounted correctly.
    I used to have this .mount file as the volume actually is a multi-device btrfs volume:
    [Unit]
    Description=/mnt/archive
    Wants=cryptsetup.target
    After=cryptsetup.target
    [Mount]
    What=/dev/mapper/archive1
    Where=/mnt/archive
    Type=btrfs
    Options=defaults,noatime,nodiratime
    The error I get when I try to manually start this service is:
    systemd[1]: Expecting device dev-mapper-archive1.device...
    thor systemd[1]: Job dev-mapper-archive1.device/start timed out.
    thor systemd[1]: Timed out waiting for device dev-mapper-archive1.device.
    thor systemd[1]: Dependency failed for /mnt/archive.
    thor systemd[1]: Job mnt-archive.mount/start failed with result 'dependency'.
    thor systemd[1]: Job dev-mapper-archive1.device/start failed with result 'timeout'.
    I double-checked /dev/mapper and there definitely is the device node in question, which I can manually mount without any problem.
    Any idea why my .mount file stopped working or why systemd doesn't find the existing /dev/mapper/archive1?

    Thanks for the quick response, WonderWoofy ( by the way, great username! )!
    When I removed or modified the the mount options in the bootloader kernel command line, there was no change to the status of the fs after boot-up. I had changed it at one point from 'ro', to 'rw'; but doing so had no affect on the output of the mount command.
    However, I did finally identify the cause:  turns out if I specify 'data=writeback', in fstab for the root partition, then systemd-remount-fs.service fails, as per my OP - leaving me with a 'ro'-mounted root filesystem. Simply removing that, or changing it to 'data=ordered', solved the issue: when I rebooted, the root partition was mounted as per my fstab config.
    So, my fstab now looks like this:
    # /dev/sda5
    UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 rw,noatime,discard 0 1
    # /dev/sda6
    UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,ro,noatime,discard,data=writeback 0 0
    # /dev/sda7
    UUID=c8d2776b-faaa-4a9d-ad49-4b09489faaaa /var ext4 defaults,rw,noatime,discard 0 2
    # /dev/sda8
    UUID=3dff3fa5-3291-4227-907a-258f12e1b3cf /home ext4 defaults,rw,relatime,discard 0 2
    ... and all is now well.
    I'll mark this as solved, but I'll also ask:  why does specifying 'data=writeback' on my root partition cause the systemd-remount-fs.service to fail? Any experts out there know?
    Last edited by corey_s (2012-12-02 06:46:32)

  • Is it possible to mount a physical disk (/dev/mapper/ disk) on one of my Oracle VM server

    I have a physical disk that I can see from multipath -ll  that shows up as such
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    That particular is visible in the OVMM Gui as a physical disk that I can present to one of my VMs but currently its not presented to any of them.
    I have about 50 physical LUNs that my Oracle VM server can see.  I believe I can see all of them from a fdisk -l, but "dm-115" (which is from the multipath above) doesnt show up.
    This disk has 3 usable partitions on it, plus a Swap.
    I want to mount the 3rd partition temporarily on the OVM server itself and I receive
    # mount /dev/mapper/3600c0ff00012f4878be35c5401000000p3 /mnt
    mount: you must specify the filesystem type
    If I present the disk to a VM and then try to mount the /dev/xvdx3 partition -it of course works.  (x3 - represents the 3rd partition on what ever letter position the disk shows up as)
    Is this possible?

    Its more of the correct syntax. Like I can not seem to figure out how to translate the /dev/mapper path above into what fdisk -l shows. Perhaps if I knew how fdisk and multipath can be cross referenced I could mount the partition.
    I had already tried what you suggested. Here is the output if I present the disk to a VM and then mount the 3rd partition.
    # fdisk -l
    Disk /dev/xvdh: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/xvdh1   *           1          13      104391   83  Linux
    /dev/xvdh2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/xvdh3            2103       27783   206282632+  83  Linux
    /dev/xvdh4           27784       30394    20972857+   5  Extended
    /dev/xvdh5           27784       30394    20972826   83  Linux
    # mount /dev/xvdh3 /mnt  <-- no error
    # df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/xvda3            197G  112G   75G  60% /
    /dev/xvda5             20G 1011M   18G   6% /var
    /dev/xvda1             99M   32M   63M  34% /boot
    tmpfs                 2.0G     0  2.0G   0% /dev/shm
    /dev/xvdh3            191G   58G  124G  32% /mnt  <-- mounted just fine
    Its ext3 partition
    # df -T
    /dev/xvdh3
    ext3   199822096  60465024 129042944  32% /mnt
    Now if I go to my vm.cfg file, I can see the disk that is presented.
    My disk line contains
    disk = [...'phy:/dev/mapper/3600c0ff00012f4878be35c5401000000,xvdh,w', ...]
    Multipath shows that disk and says "dm-115" but that does not translate on fdisk
    # multipath -ll
    3600c0ff00012f4878be35c5401000000 dm-115 HP,P2000G3 FC/iSCSI
    size=410G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | `- 7:0:0:49  sdcs 70:0   active ready running
    `-+- policy='round-robin 0' prio=10 status=enabled
      `- 10:0:0:49 sdcr 69:240 active ready running
    I have around 50 disks on this server, but the ones of the same size from fdisk -l from the server shows me many.
    # fdisk -l
    Disk /dev/sdp: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
       Device Boot      Start         End      Blocks   Id  System
    /dev/sdp1   *           1          13      104391   83  Linux
    /dev/sdp2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdp3            2103       27783   206282632+  83  Linux
    /dev/sdp4           27784       30394    20972857+   5  Extended
    /dev/sdp5           27784       30394    20972826   83  Linux
    Disk /dev/sdab: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdab1   *           1          13      104391   83  Linux
    /dev/sdab2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdab3            1319       27783   212580112+  83  Linux
    /dev/sdab4           27784       30394    20972857+   5  Extended
    /dev/sdab5           27784       30394    20972826   83  Linux
    Disk /dev/sdac: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdac1   *           1          13      104391   83  Linux
    /dev/sdac2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdac3            2103       27783   206282632+  83  Linux
    /dev/sdac4           27784       30394    20972857+   5  Extended
    /dev/sdac5           27784       30394    20972826   83  Linux
    Disk /dev/sdad: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdad1   *           1          13      104391   83  Linux
    /dev/sdad2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/sdad3            1319       27783   212580112+  83  Linux
    /dev/sdad4           27784       30394    20972857+   5  Extended
    /dev/sdad5           27784       30394    20972826   83  Linux
    Disk /dev/sdae: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdae1   *           1          13      104391   83  Linux
    /dev/sdae2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdae3            2103       27783   206282632+  83  Linux
    /dev/sdae4           27784       30394    20972857+   5  Extended
    /dev/sdae5           27784       30394    20972826   83  Linux
    Disk /dev/sdaf: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdaf1   *           1          13      104391   83  Linux
    /dev/sdaf2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdaf3            2103       27783   206282632+  83  Linux
    /dev/sdaf4           27784       30394    20972857+   5  Extended
    /dev/sdaf5           27784       30394    20972826   83  Linux
    Disk /dev/sdag: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
        Device Boot      Start         End      Blocks   Id  System
    /dev/sdag1   *           1          13      104391   83  Linux
    /dev/sdag2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/sdag3            2103       27783   206282632+  83  Linux
    /dev/sdag4           27784       30394    20972857+   5  Extended
    /dev/sdag5           27784       30394    20972826   83  Linux
    Disk /dev/dm-13: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-13p1   *           1          13      104391   83  Linux
    /dev/dm-13p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-13p3            2103       27783   206282632+  83  Linux
    /dev/dm-13p4           27784       30394    20972857+   5  Extended
    /dev/dm-13p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-25: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-25p1   *           1          13      104391   83  Linux
    /dev/dm-25p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-25p3            1319       27783   212580112+  83  Linux
    /dev/dm-25p4           27784       30394    20972857+   5  Extended
    /dev/dm-25p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-26: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-26p1   *           1          13      104391   83  Linux
    /dev/dm-26p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-26p3            2103       27783   206282632+  83  Linux
    /dev/dm-26p4           27784       30394    20972857+   5  Extended
    /dev/dm-26p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-27: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-27p1   *           1          13      104391   83  Linux
    /dev/dm-27p2              14        1318    10482412+  82  Linux swap / Solaris
    /dev/dm-27p3            1319       27783   212580112+  83  Linux
    /dev/dm-27p4           27784       30394    20972857+   5  Extended
    /dev/dm-27p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-28: 439.9 GB, 439956406272 bytes
    255 heads, 63 sectors/track, 53488 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-28p1   *           1          13      104391   83  Linux
    /dev/dm-28p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-28p3            2103       27783   206282632+  83  Linux
    /dev/dm-28p4           27784       30394    20972857+   5  Extended
    /dev/dm-28p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-29: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-29p1   *           1          13      104391   83  Linux
    /dev/dm-29p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-29p3            2103       27783   206282632+  83  Linux
    /dev/dm-29p4           27784       30394    20972857+   5  Extended
    /dev/dm-29p5           27784       30394    20972826   83  Linux
    Disk /dev/dm-30: 439.9 GB, 439999987712 bytes
    255 heads, 63 sectors/track, 53493 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
          Device Boot      Start         End      Blocks   Id  System
    /dev/dm-30p1   *           1          13      104391   83  Linux
    /dev/dm-30p2              14        2102    16779892+  82  Linux swap / Solaris
    /dev/dm-30p3            2103       27783   206282632+  83  Linux
    /dev/dm-30p4           27784       30394    20972857+   5  Extended
    /dev/dm-30p5           27784       30394    20972826   83  Linux
    How to translate the /dev/mapper address into the correct fdisk, I think I can then mount it.
    If I try the same command as before with the -t option it gives me this error.
    # mount -t ext3 /dev/mapper/3600c0ff00012f48791975b5401000000p3 /mnt
    mount: special device /dev/mapper/3600c0ff00012f48791975b5401000000p3 does not exist
    I know I am close here, and feel it should be possible, I am just missing something.
    Thanks for any help

  • Auto Partion fails error = /dev/sda is mounted

    I booted from the cd,  ran /arch/setup then began going through the setup program
    at the point it is going to auto partition my harddrive it fails with /dev/sda is mounted or busy.
    I checked /mnt and its not showing anything mounted.
    32M for boot
    512M for swap
    7500 for / and home

    Correct me if I'm wrong...I'm stuck at work on a *cough* winbloze machine. 
    rw=read/write
    auto=mount when it boots up
    user=users can mount/unmount
    sync=write data to the drive immediatly when saved.  async writes the data whenever it gets good and ready.
    0 0 means the drive will never be force checked.
    Or at least one of the 0's does.  can't remember for the life of me what the other means.

  • Mounting /dev/hda1 on home/ftp/c failed on NI-8196 PXI controller.

    Hi folks,
    I am having some problems in recognising a PXI controller ( NI-8196
    )  and a field point unit on my host MAX. I know both of them are
    on the same subnet. I have Labview RT running on the PXI controller. I
    don't know which version though.
    The problem is while setting up the IP configuration for the PXI
    controller in the MAX. It doesnt take the IP from either the DHCP
    server or when I use static IP's. I have already checked the Switch
    settings on the controller. All of them are OFF. The BIOS option for
    the IP reset has been disabled too, still the controller boots up with
    0.0.0.0 
    While booting up it gives me the error:  "  mounting
    /dev/hda1 on home/ftp/c failed:  Invalid Arguement. Booting in
    safe mode. "
    With the field point unit, the MAX doesnt recognise it on the network. it doesn't show up under the REMOTE SYSTEMS panel.
    My MAX version is 4.0, Labview version on the host is 8.0
    Any help will be greatly appreciated.
    Thank you,
    Sandeep

    For the PXI chassis, I would start by trying a reformat. RT Disk Utilities in MAX>> Create format and boot disks.
    For the fieldpoint Try using this document. http://zone.ni.com/devzone/conceptd.nsf/webmain/49e7983a1c47a3af86256a3a005b4a3e?OpenDocument

  • Adding a USB HDD to a VM via OVM - /dev/mapper Error

    Hey all,
    we're trying to hook up a USB HDD to a virtualized database server for a one time backup.
    So after connecting it to the OVS, i formatted it to ext3, mounted it and voila. When i edit the database VM via OVM i can add a Physical Disk.
    I am getting an error though:
    Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:disk:setup_error:Command: ['xm', 'block-attach', '0004fb000006000056a65a591c902757', 'phy:/dev/mapper/35000000000000001', 'xvdd', 'w'] failed (1): stderr: Error: Device 51760 (vbd) could not be connected. /dev/mapper/35000000000000001 does not exist.stdout: Usage: xm block-attach [BackDomain]
    ...and he is right. There is no /dev/mapper/35000000000000001
    But where does it get that information from?!
    Any ideas?

    OVM will only make use of volumes that are accessible through /dev/mapper. USB volumes are, as you already know, not available in /dev/mapper and thus can't be mapped to virtiual machines as volumes.
    This is a limitation, but I think Oracle decided for this, because a USB drive really doesn't make a good choice for a virtual drive, as is introduces a lot of latency and other potential I/O issues, you don't want to have in a virtualized environment.
    It would be better to map the backup drive in thge guest itself using other protocols like NFS.
    Cheers,
    budy

  • LVM /dev/mapper is empty, + systemd boot hangs

    Hi!
    1st problem:
    I have 2 vgs with 1 lv each -- called Sys/Linux and Sys2/Var. Booting the kernel with root=/dev/mapper/Sys-Linux works, but after mounting the root fs, /dev/mapper is empty:
    $ ls /dev/mapper
    control
    2nd problem:
    I changed UUID= to /dev/dm-1 for /var for testing purposes, but systemd will timeout on mounting /var. Note: after entering the emergency console, I can just type mount /var and it will mount.
    The system is was quite old and I changed to systemd-only right now, because I upgraded the filesystem package (that removes /bin, /sbin, /usr/sbin and required me to remove outdated packages). ((Yes, I'm late )).
    I hope anyone has some pointers; please tell me, which config files you need to see if any, to help out.
    Thanks,
    Andy
    Last edited by Black Sliver (2013-08-12 20:14:40)

    [2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
    [2013-08-12 19:33] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux.img
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Starting build: 3.10.5-1-ARCH
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [base]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [udev]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [block]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: bfa
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [lvm2]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> ERROR: file not found: `/usr/sbin/dmsetup'
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [resume]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] -> Running build hook: [shutdown]
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Generating module dependencies
    [2013-08-12 19:33] [ALPM-SCRIPTLET] ==> Creating lzma initcpio image: /boot/initramfs-linux-fallback.img
    [2013-08-12 19:34] [ALPM-SCRIPTLET] ==> WARNING: errors were encountered during the build. The image may not be complete.
    Note that initial mounting of root=/dev/mapper/Sys-Linux works. Can this be the problem anyway? I rebuilt the initrd, I'll try to boot it tomorrow.
    [2013-08-12 19:42] [PACMAN] Running 'pacman -R initscripts sysvinit' # NOTE: this was required for the filesystem upgrade to work (/sbin)
    [2013-08-12 19:42] [ALPM] warning: /etc/rc.conf saved as /etc/rc.conf.pacsave
    [2013-08-12 19:42] [ALPM] warning: /etc/inittab saved as /etc/inittab.pacsave
    Theese are not required with systemd ?
    Everything else is just upgrade/install/remove or uninteresting. Or do you want to see everything?
    Last edited by Black Sliver (2013-08-12 22:48:32)

  • OVM 3.1.1 Repository Being Mapped with Diffferent /dev/mapper/ address

    Hello,
    I'm running OVM 3.1 on a Dell T420 server with onboard storage. The RAID 5 virtual disk that was housing my repository was inadvertently deleted. I was able to recreate a new VD and the server can now see the original ocsf2 partition that the repository lived on. However, it obtained a new /dev/mapper/ address and OVM manager will not mount the repository. Is there a way to rename the /dev/mapper address to the old address that OVM manager is looking for? Thanks!

    No, the ID in /dev/mapper is generated from the SCSI-83-page and that one is created on the storage and it cannot be changed. You can find some howto on the net, that deals with such an issue where, but it's not for the faint-hearted. A lot of information are in this post, which deals with howto get an existing storage repo up on a remote site, but some of the concepts also apply to your situation:
    https://oraclenz.wordpress.com/2013/06/13/oracle-vm-3-1-disaster-recovery-ha/
    That one helped me as well…
    https://community.oracle.com/thread/3596198
    Cheers,
    budy

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

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

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

  • Mount: /dev/sda2 already mounted or /u01 busy

    Installed new OELinux4.7 with disk partitions but unable to to mount these
    [oracle@localhost sbin]$ ./fdisk -l (give no results)
    [root@localhost /]# mount /dev/sda3 /u01
    mount: /dev/sda3 already mounted or /u01 busy
    [root@localhost /]# cd /sbin
    *[root@localhost sbin]# ./fdisk -l*
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 19 152586 83 Linux
    /dev/sda2 20 2630 20972857+ 8e Linux LVM
    /dev/sda3 2631 5241 20972857+ 8e Linux LVM
    /dev/sda4 5242 60801 446285700 5 Extended
    /dev/sda5 5242 7852 20972826 8e Linux LVM
    /dev/sda6 7853 10463 20972826 8e Linux LVM
    /dev/sda7 10464 13074 20972826 8e Linux LVM
    *[root@localhost sbin]# df -h*
    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol01
    20G 3.5G 16G 19% /
    /dev/sda1 145M 15M 123M 11% /boot
    none 3.0G 0 3.0G 0% /dev/shm
    /dev/mapper/VolGroup00-LogVol02
    20G 78M 19G 1% /home
    [root@localhost /]# mount /dev/sda2 /u01
    mount: /dev/sda2 already mounted or /u01 busy
    [root@localhost /]#

    On a system without LVM, a filesystem is created inside a partition. fdisk is used to list partitions on disks. Because the filesystems are inside the partitions, you can use the name of parition to mount it.
    On a system with LVM, a filesystem is created inside a logical volume, not in a partition. The partitions (fdisk -l) are used as physical volumes (pvdisplay), which are added to a volume group (vgdisplay), in which a logical volume can be created (lvdisplay). In the logical volume a filesystem is created. Because of this, only the logical volumes can be used to mount the filesystem.
    LVM adds an abstraction layer between filesystems and partitions. This is extremely handy because it's easy to add a disk (which is made physical volume) to a volume group which makes space available, which can be added to any logical volume in the volume group. When that's done, the filesystem in the logical volume can be enlarged with resize2fs, even online. Without LVM, it's not possible or very hard at best to do that.

  • /dev/shm not mounted /dev busy

    Recently I was trying out a boot disk I had made, and basically, I switched it off several times due to it booting the completely wrong kernel.
    Now, I'm getting to the stage "Checking File systems" and then comes up [Failed]. I then get a message saying Reboot required, and that it will reboot in 15 seconds, just a few seconds before it reboots I get "/dev/shm not mounted, /dev busy" or something similar.
    I've booted up my sysresccd, ran "fsck.ext4 -fcv /dev/sda2" to force a check and scan for any bad blocks, it came up clean, then I rebooted and got the same error, so I copied the kernel and system.map over to /boot to make sure there's no corruption and reinstalled initscripts and util-linux-ng, rebooted, same error.
    Tried different kernels, I've checked fstab and menu.lst, no problems there, so I still don't get why I still get the same problem.
    Anybody know of any fix other than reinstalling arch?
    EDIT: Editing /etc/rc.sysinit and commenting out the fsck part made it work, finding out why fsck failed now.
    Last edited by compgenius999 (2010-03-03 19:21:35)

    anybody?

  • After boot can't mount SDS file systems on 3300 mount: cannot mount /dev/md

    Hi
    I have a SUNW,Netra-440 with two SE 3300 SCSI each with two controllers. The server was working fine but after a boot, it can not see the metadevices stored in the 3300.
    I have tried restarting the SE3300 and a boot -r from ok prompt but I still can see those disks or partitions.
    Metaset Import
    metaset: log01: setname "appvol": no such set
    mount all SVM filesystems for group appvol
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d101
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d102
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d103
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d104
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d105
    mount: No such device
    mount: cannot mount /dev/md/appvol/dsk/d106
    metaset: log01: setname "dbvol": no such set
    mount all SVM filesystems for group dbvol
    mount: No such device
    mount: cannot mount /dev/md/dbvol/dsk/d107
    mount: No such device
    mount: cannot mount /dev/md/dbvol/dsk/d108
    i can see the devices in /dev/md/appvol but i can't mount them.
    Any ideas what this could be? using metaset shows nothing, metastat -s dbvol hangs.
    Am I missing some patch or am I missing something here? is the SE3300 damaged? or is it a problem with SDS (solstice). I have solaris 9.
    The system was working fine until we had to boot and power off to perform power tests in the rack.
    thanks
    Ryck
    this is the output of prtdiag
    root@log01 >prtdiag
    System Configuration: Sun Microsystems sun4u Netra 440
    System clock frequency: 177 MHZ
    Memory size: 8GB
    ==================================== CPUs ====================================
    E$ CPU CPU Temperature
    CPU Freq Size Implementation Mask Die Amb. Status Location
    0 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    1 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    2 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    3 1593 MHz 1MB SUNW,UltraSPARC-IIIi 3.4 - - online -
    ================================= IO Devices =================================
    Bus Freq Slot + Name +
    Type MHz Status Path Model
    pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1c,600000/scsi@1
    pci 66 PCI5 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1c,600000/scsi@1,1
    pci 66 MB pci108e,abba (network) SUNW,pci-ce
    okay /pci@1c,600000/network@2
    pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1d,700000/scsi@1
    pci 66 PCI4 scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1d,700000/scsi@1,1
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@0
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@1
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@2
    pci 66 PCI2 pci100b,35 (network) SUNW,pci-x-qge
    okay /pci@1d,700000/pci@2/network@3
    pci 33 MB isa/su (serial)
    okay /pci@1e,600000/isa@7/serial@0,3f8
    pci 33 MB isa/su (serial)
    okay /pci@1e,600000/isa@7/serial@0,2e8
    pci 33 MB isa/rmc-comm-rmc_comm (seria+
    okay /pci@1e,600000/isa@7/rmc-comm@0,3e8
    pci 33 PCI0 SUNW,XVR-100 (display) SUNW,375-3290
    okay /pci@1e,600000/SUNW,XVR-100
    pci 33 MB pciclass,0c0310 (usb)
    okay /pci@1e,600000/usb@a
    pci 33 MB pciclass,0c0310 (usb)
    okay /pci@1e,600000/usb@b
    pci 33 MB pci10b9,5229 (ide)
    okay /pci@1e,600000/ide@d
    pci 66 MB pci108e,abba (network) SUNW,pci-ce
    okay /pci@1f,700000/network@1
    pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1f,700000/scsi@2
    pci 66 MB scsi-pci1000,30 (scsi-2) LSI,1030
    okay /pci@1f,700000/scsi@2,1
    ============================ Memory Configuration ============================
    Segment Table:
    Base Address Size Interleave Factor Contains
    0x0 2GB 4 BankIDs 0,1,2,3
    0x1000000000 2GB 4 BankIDs 16,17,18,19
    0x2000000000 2GB 4 BankIDs 32,33,34,35
    0x3000000000 2GB 4 BankIDs 48,49,50,51
    Bank Table:
    Physical Location
    ID ControllerID GroupID Size Interleave Way
    0 0 0 512MB 0,1,2,3
    1 0 1 512MB
    2 0 1 512MB
    3 0 0 512MB
    16 1 0 512MB 0,1,2,3
    17 1 1 512MB
    18 1 1 512MB
    19 1 0 512MB
    32 2 0 512MB 0,1,2,3
    33 2 1 512MB
    34 2 1 512MB
    35 2 0 512MB
    48 3 0 512MB 0,1,2,3
    49 3 1 512MB
    50 3 1 512MB
    51 3 0 512MB
    Memory Module Groups:
    ControllerID GroupID Labels Status
    0 0 C0/P0/B0/D0
    0 0 C0/P0/B0/D1
    0 1 C0/P0/B1/D0
    0 1 C0/P0/B1/D1
    1 0 C1/P0/B0/D0
    1 0 C1/P0/B0/D1
    1 1 C1/P0/B1/D0
    1 1 C1/P0/B1/D1
    2 0 C2/P0/B0/D0
    2 0 C2/P0/B0/D1
    2 1 C2/P0/B1/D0
    2 1 C2/P0/B1/D1
    3 0 C3/P0/B0/D0
    3 0 C3/P0/B0/D1
    3 1 C3/P0/B1/D0
    3 1 C3/P0/B1/D1
    root@log01 >

    Hi,
    thanks for your answer.
    Yes format displays the physical devices, but metadb -i only shows the internal disks of the netra 440, not the ones in the 3320. metadb -s dbvol -i doesnt show anything.
    metaset which is supposed to show me the metadevices, says the program is not registered.
    cat /etc/lvm/md.tab has the configuration but since the scsi can be seen, the devices aren't mounted.
    Any suggestions?
    Cheers
    Oscar
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootdisk
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> bootmirr
    /pci@1f,700000/scsi@2/sd@1,0
    2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare1
    /pci@1f,700000/scsi@2/sd@2,0
    3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848> spare2
    /pci@1f,700000/scsi@2/sd@3,0
    4. c2t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> appvol
    /pci@1c,600000/scsi@1/sd@8,0
    5. c2t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol01
    /pci@1c,600000/scsi@1/sd@9,0
    6. c2t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol02
    /pci@1c,600000/scsi@1/sd@a,0
    7. c2t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol03
    /pci@1c,600000/scsi@1/sd@b,0
    8. c2t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol04
    /pci@1c,600000/scsi@1/sd@c,0
    9. c2t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol05
    /pci@1c,600000/scsi@1/sd@d,0
    10. c3t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> dbvol06
    /pci@1c,600000/scsi@1,1/sd@8,0
    11. c3t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1
    /pci@1c,600000/scsi@1,1/sd@9,0
    12. c3t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2
    /pci@1c,600000/scsi@1,1/sd@a,0
    13. c3t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3
    /pci@1c,600000/scsi@1,1/sd@b,0
    14. c3t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotAPP
    /pci@1c,600000/scsi@1,1/sd@c,0
    15. c3t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDB
    /pci@1c,600000/scsi@1,1/sd@d,0
    16. c4t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> APPVOLm
    /pci@1d,700000/scsi@1/sd@8,0
    17. c4t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@9,0
    18. c4t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@a,0
    19. c4t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@b,0
    20. c4t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@c,0
    21. c4t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1/sd@d,0
    22. c5t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> d6Mirr
    /pci@1d,700000/scsi@1,1/sd@8,0
    23. c5t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free1M
    /pci@1d,700000/scsi@1,1/sd@9,0
    24. c5t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free2M
    /pci@1d,700000/scsi@1,1/sd@a,0
    25. c5t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> free3M
    /pci@1d,700000/scsi@1,1/sd@b,0
    26. c5t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1d,700000/scsi@1,1/sd@c,0
    27. c5t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> hotDBm
    /pci@1d,700000/scsi@1,1/sd@d,0
    root@log01 >metadb -i
    flags first blk block count
    a m p luo 16 8192 /dev/dsk/c1t0d0s7
    a p luo 8208 8192 /dev/dsk/c1t0d0s7
    a p luo 16400 8192 /dev/dsk/c1t0d0s7
    a p luo 16 8192 /dev/dsk/c1t1d0s7
    a p luo 8208 8192 /dev/dsk/c1t1d0s7
    a p luo 16400 8192 /dev/dsk/c1t1d0s7
    r - replica does not have device relocation information
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    root@log01 >
    root@log01 >metadb -i
    flags first blk block count
    a m p luo 16 8192 /dev/dsk/c1t0d0s7
    a p luo 8208 8192 /dev/dsk/c1t0d0s7
    a p luo 16400 8192 /dev/dsk/c1t0d0s7
    a p luo 16 8192 /dev/dsk/c1t1d0s7
    a p luo 8208 8192 /dev/dsk/c1t1d0s7
    a p luo 16400 8192 /dev/dsk/c1t1d0s7
    r - replica does not have device relocation information
    o - replica active prior to last mddb configuration change
    u - replica is up to date
    l - locator for this replica was read successfully
    c - replica's location was in /etc/lvm/mddb.cf
    p - replica's location was patched in kernel
    m - replica is master, this is replica selected as input
    W - replica has device write errors
    a - replica is active, commits are occurring to this replica
    M - replica had problem with master blocks
    D - replica had problem with data blocks
    F - replica had format problems
    S - replica is too small to hold current data base
    R - replica had device read errors
    root@log01 >metadb -s appvol -i
    metadb: log01: setname "appvol": no such set
    root@log01 >metaset
    metaset: log01: metad client create: RPC: Program not registered
    root@log01 >cat /etc/lvm/md.tab
    # Copyright 2002 Sun Microsystems, Inc. All rights reserved.
    # Use is subject to license terms.
    # ident "@(#)md.tab 2.4 02/01/29 SMI"
    # md.tab
    # metainit utility input file.
    dbvol/d57 1 1 c2t12d0s0
    dbvol/d58 1 1 c4t12d0s0
    dbvol/d4 -m dbvol/d57 dbvol/d58 1
    dbvol/d55 1 1 c2t11d0s0
    dbvol/d56 1 1 c4t11d0s0
    dbvol/d3 -m dbvol/d55 dbvol/d56 1
    dbvol/d61 1 1 c3t8d0s0
    dbvol/d62 1 1 c5t8d0s0
    dbvol/d6 -m dbvol/d61 dbvol/d62 1
    dbvol/d59 1 1 c2t13d0s0
    dbvol/d60 1 1 c4t13d0s0
    dbvol/d5 -m dbvol/d59 dbvol/d60 1
    dbvol/d53 1 1 c2t10d0s0
    dbvol/d54 1 1 c4t10d0s0
    dbvol/d2 -m dbvol/d53 dbvol/d54 1
    ###dbvol/d51 1 1 c2t9d0s0
    dbvol/d52 1 1 c4t9d0s0
    #dbvol/d1 -m dbvol/d51 dbvol/d52 1
    dbvol/d1 -m dbvol/d52 1
    # SOFT Partitions
    dbvol/d129 -p dbvol/d5 -o 19933376 -b 526336
    dbvol/d128 -p dbvol/d5 -o 19407008 -b 526336
    dbvol/d127 -p dbvol/d5 -o 18880640 -b 526336
    dbvol/d126 -p dbvol/d5 -o 10489952 -b 8390656
    dbvol/d125 -p dbvol/d5 -o 2099264 -b 8390656
    dbvol/d123 -p dbvol/d4 -o 4724864 -b 133120
    dbvol/d122 -p dbvol/d4 -o 4460640 -b 264192
    dbvol/d121 -p dbvol/d4 -o 4196416 -b 264192
    dbvol/d120 -p dbvol/d4 -o 32 -b 4196352
    dbvol/d119 -p dbvol/d3 -o 30972032 -b 526336
    dbvol/d118 -p dbvol/d3 -o 10489952 -b 20482048
    dbvol/d117 -p dbvol/d3 -o 4196416 -b 6293504
    dbvol/d116 -p dbvol/d3 -o 32 -b 4196352
    dbvol/d115 -p dbvol/d2 -o 8925408 -b 526336
    dbvol/d114 -p dbvol/d2 -o 8399040 -b 526336
    dbvol/d113 -p dbvol/d2 -o 7872672 -b 526336
    dbvol/d112 -p dbvol/d2 -o 7346304 -b 526336
    dbvol/d111 -p dbvol/d2 -o 5247072 -b 2099200
    dbvol/d110 -p dbvol/d2 -o 1050688 -b 4196352
    dbvol/d109 -p dbvol/d2 -o 32 -b 1050624
    dbvol/d108 -p dbvol/d1 -o 33554496 -b 1572864
    dbvol/d107 -p dbvol/d1 -o 32 -b 33554432
    dbvol/d124 -p dbvol/d5 -o 32 -b 2099200
    dbvol/d138 -p dbvol/d4 -o 38416608 -b 133120
    dbvol/d137 -p dbvol/d3 -o 31498400 -b 264192
    dbvol/d136 -p dbvol/d4 -o 21637312 -b 16779264
    dbvol/d135 -p dbvol/d4 -o 4858016 -b 16779264
    dbvol/d134 -p dbvol/d6 -o 69212288 -b 23070720
    dbvol/d133 -p dbvol/d6 -o 46141536 -b 23070720
    dbvol/d132 -p dbvol/d6 -o 23070784 -b 23070720
    dbvol/d131 -p dbvol/d6 -o 32 -b 23070720
    dbvol/d130 -p dbvol/d5 -o 20459744 -b 526336
    root@log01 >metadb -s dbvol -i
    metadb: log01: setname "dbvol": no such set
    root@log01 >\

  • Background Jobs are failing in DEV server after SP upgrade

    Hi Everyone,
    Below jobs are being failed in dev server after SP upgrade with error variant does not exist.
    SWWERRE, SWWDHEX, SWWCOND,  SWWCLEAR,SWFSLSDLEX, NON SAP USER UPLOAD
    System Details:
    SAP Version: ECC 6.0
    Database: SQL 2005
    OS: Windows 2003, SR2, 64 - bit.
    Kernel Patch: 221
    SAP_BASIS:19
    SAP_ABA :19
    SAP_APPL : 16
    SAP_AP :17
    SAP_HR : 51
    SAP_BW : 21
    PI_BASIS 2006_1_700 : patch 009
    ST_PI: ST_PI 2005_1_700 : 006
    FINBASIS : 16
    LOSFE: 16
    Can any one have idea on above mentioned jobs.
    Thanks & Regards,
    Vinod

    > Below jobs are being failed in dev server after SP upgrade with error variant does not exist.
    > SWWERRE, SWWDHEX, SWWCOND,  SWWCLEAR,SWFSLSDLEX,
    Those are workflow related jobs.
    > NON SAP USER UPLOAD
    This is a job name and not the program name.
    Markus

  • /etc/crypttab doesn't create /dev/mapper/swap

    I'm not lucky with encryption these days: keyfile on USB stick doesn't work ( http://bbs.archlinux.org/viewtopic.php?id=52507 ), so revert to the passphrase thing.
    I had swap encryption working using the old rc.local way etc. now there's a new way... "SWAP" keyword inside /etc/crypttab and no rc.local changes, wonderful right? Wrong. It doesn't work, if you put (example)
    swap /dev/sda3 SWAP -c aes-xts-plain -h whirlpool -s 512
    inside /etc/crypttab and reboot, it doesn't create any /dev/mapper/swap device (so it can't swapon).
    Where's the issue?
    Last edited by ekerazha (2008-08-20 13:22:35)

    dw wrote:
    hi ekerazha.
    i am playing around with system encryption a bit lately and i am experiencing exactly the same. my question. were you able to solve this?
    No... maybe reverting to the "old" way (no SWAP keyword etc.)
    Last edited by ekerazha (2008-08-23 16:36:41)

  • [SOLVED] mount: /dev/sda3 is already mounted or /mnt busy

    Hello all, I've spent several hours researching this to no avail.  I'm trying to mount my partitions, first with my root partition (/dev/sda3) mounted at /mnt.  It seems no matter what partition I try to mount it gives me the same error: mount: /dev/sda3 is already mounted or /mnt busy.  I've tried the fuser command and killed all process associated with this device but new processes seem to pop up making it busy once more.
    Hopefully somebody has some knowledge of what could be causing this one.
    Thanks, and I hope to resurrect an Arch workstation once more!
    -Aaron
    Last edited by guitarxperience (2012-10-09 14:52:21)

    guitarxperience wrote:
    ewaller wrote:
    guitarxperience wrote:
    I'd love to post that but can you tell me how to post it when I'm running the install on another computer. ...I just don't know if there's a way to route the output to a URL or something after-all it is connected to the internet. But there is no browser as far as I know.
    Why, yes! 
    community/wgetpaste 2.20-1 [installed]
    A script that automates pasting to a number of pastebin services
    ewaller@odin:~ 1004 %ls -l | wgetpaste
    Your paste can be seen here: https://gist.github.com/3842491
    ewaller@odin:~ 1005 %
    Looks like a groovy tool.. Can you tell me how to get it on my installation setup?  Don't seem to have apt-get available or anything like that to install things.
    Oh yeah this is Arch so I would use pacman.  The community database along with core and extra does not exist... when i run pacman.

Maybe you are looking for

  • Importing Vb Dll in Oracle Forms 6i

    If any one have idea importing vb dll in oracle forms 6i. If any one have idea to Use ORA_FFI package or any other way.

  • Photoshop CS3 delete issues

    I am having issues in photoshop. I can select a background of a photo but when I hit delete or cut nothing happens. I reset the preferences but still no luck. This has been going on for months and I need to get it fixed. Had the same problem today in

  • HT201210 I get an error message to reinstall itunes what do I do

    I get an error message to reinstall itunes what I do to get it reinstalled?

  • Detecting the type of Internet Connection

    Hi.. I am trying ... build an application that detects the kind of internet connection (Dial-up, T1, DSL etc) that you are using and then disconnects it. This application, must then send a response to a server-side program containing information abou

  • Error when activating Order Data Type ORDR

    Hi all We were activating all the ODM components acc to note 1178483 and got the following error when trying to activate Order Data Type ORDR: Parameter CONFSTAT in access path TSTP of order data type ORDR unknown (/SCMB/ODM_ORDTYPE043) Do any of you