[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.

Similar Messages

  • Do I need to run fsck manually on Clustered disks?

    I am just wondering if fsck is run automatically on Clustered monitored disks, once the resource is brought on line after a crash?
    Or if not what steps should be taken to make this happen automatically?

    what do you mean by clustered disks? What file system is it running ufs? A fsck checks the file system not the hard disks so it is always good to check it no matter where it resides, however some NAS will have thier own file system checking commands so its important to establish where the disks are and what fs is on them.

  • I can´t run fsck /dev/sda6 is mounted

    How I can enter on unique user mode to umount my partition and run fsck. A day before I had it  this problem with my archive system, my archlinux was working ok but after shutdown my computer and turn on again I had it this problem. Please I need help with this problem, i´m going insane with this.

    Inxsible wrote:
    learn to use the edit functionality instead of posting consecutively.
    Read the forum rules and abide by them.
    joelvilabringuez wrote:is my home partition but anyway it doesn´t work mate
    This is the most useless comment. What doesn't work? Were there any errors? Please don't post half assed answers.
    In addition, I think posting the exact commands you used would be helpful.

  • 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

  • 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)

  • Inconsistent Run times for the Calcscript

    Hello Guys,
    I am getting inconsistent run times when I am executing the same Calcscript on EAS DEV server again and again. Please let me know your thoughts.
    Thanks

    There are a number of factors that can affect this
    First. If the first time you had just loaded the database and ran the calc times would vary from when the calculation is against a fully calculated database
    Second, Each time you run the calc, you could be creating fragmentation whould would lenghten the calculation
    Third, depending on what is going on, you might have cached some blocks from a previous run wich would speed up calculations. To try to get consistant results there are a few things you could do
    1. reload the data prior to every test
    2. or restructure the Database to remove fragmentation
    3. Stop and restart the database between runs to clear the cache

  • Cannot mount or run fsck on filesystem

    Yesterday, our helpdesk crew had to shutdown our systems due to overheating in our lab. After bringing up one of our servers, one of its filesystems could not be found. Below is what I see from the /var/adm/messages:
    Apr 10 12:41:54 unode2 genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinf
    o@0
    Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
    4,1 (glm3):
    Apr 10 12:41:55 unode2 SCSI bus DATA IN phase parity error
    Apr 10 12:41:55 unode2 glm: [ID 663555 kern.warning] WARNING: ID[SUNWpd.glm.pari
    ty_check.6010]
    Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
    4,1 (glm3):
    Apr 10 12:41:55 unode2 Target 0 reducing sync. transfer rate
    Apr 10 12:41:55 unode2 glm: [ID 923092 kern.warning] WARNING: ID[SUNWpd.glm.sync
    widebackoff.6014]
    Apr 10 12:41:55 unode2 scsi: [ID 107833 kern.warning] WARNING: /pci@6,4000/scsi@
    4,1/sd@0,0 (sd45):
    Apr 10 12:41:55 unode2 SCSI transport failed: reason 'tran_err': retrying comma
    nd
    Apr 10 12:41:56 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : PCI IO 2.0 (Rev Id
    = c1) Found
    Apr 10 12:41:56 unode2 pcipsy: [ID 370704 kern.info] PCI-device: network@1,1, hm
    e0
    Apr 10 12:41:56 unode2 genunix: [ID 936769 kern.info] hme0 is /pci@1f,4000/netwo
    rk@1,1
    Apr 10 12:42:01 unode2 genunix: [ID 454863 kern.info] dump on /dev/md/dsk/d2 siz
    e 5724 MB
    Apr 10 12:42:01 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : Internal Transceiv
    er Selected.
    Apr 10 12:42:01 unode2 hme: [ID 517527 kern.info] SUNW,hme0 : 100 Mbps Full-Du
    plex Link Up
    Apr 10 12:42:07 unode2 scsi: [ID 243001 kern.warning] WARNING: /pci@6,4000/SUNW,
    qlc@3/fp@0,0 (fcp0):
    Apr 10 12:42:07 unode2 Failed to create nodes for pwwn=216000c0ff884ad2; error=
    5
    Apr 10 12:42:08 unode2 scsi: [ID 243001 kern.warning] WARNING: /pci@6,4000/SUNW,
    qlc@3/fp@0,0 (fcp0):
    Apr 10 12:42:08 unode2 Failed to create nodes for pwwn=256000c0ffc84ad2; error=
    5
    Apr 10 13:00:35 unode2 pseudo: [ID 129642 kern.info] pseudo-device: tod0
    Apr 10 13:00:35 unode2 pseudo: [ID 129642 kern.info] pseudo-device: tod0
    Apr 10 13:00:35 unode2 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
    Apr 10 13:00:35 unode2 genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0
    Apr 10 13:00:36 unode2 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Apr 10 13:00:36 unode2 pseudo: [ID 129642 kern.info] pseudo-device: pm0
    Apr 10 13:00:36 unode2 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Apr 10 13:00:36 unode2 genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0
    Apr 10 13:00:38 unode2 There are no devices (controllers) in the system; nvutil
    terminated.
    Apr 10 13:00:38 unode2 Array Monitor initiated
    Apr 10 13:00:38 unode2 RDAC daemons initiated
    Apr 10 13:00:39 unode2 /usr/lib/osa/bin/arraymon: [ID 712306 user.error] No RAID
    devices found to check.
    Apr 10 13:00:39 unode2 rdriver: [ID 400281 kern.notice] ID[RAIDarray.rdaemon.100
    1] RDAC Resolution Daemon locked in memory
    Apr 10 13:00:39 unode2 rdriver: [ID 400281 kern.notice] ID[RAIDarray.rdaemon.100
    1] RDAC Resolution Daemon locked in memory
    I cannot run fsck or mount back to what it suppose to be. Looking at previous reports, this is how the file structure use to look:
    /dev/dsk/c68t216000C0FF884AD2d0s0 62493372 2142901 59725538 4% /disk6
    /dev/vx/dsk/rootdg/vol02 7559245 1602962 5880691 22% /disk1
    /dev/md/dsk/d3 4032504 734383 3257796 19% /opt
    /dev/vx/dsk/rootdg/vol01 7559245 3388798 4094855 46% /disk0
    /dev/vx/dsk/rootdg/vol03 33263336 22259082 10671622 68% /disk2
    /dev/md/dsk/d5 6552557 1813979 4673053 28% /export/home
    How can I resolve this issue?

    As it turns out, someone had turned off the storage array during the shutdown on sunday and no one ever powered back up. So when the server connected to the storage device was booted up, it could not see the file system. But even when I turned on the storage array, the server still could not mount to the filesystem residing there. The server had to be rebooted to re-sync with the storage array.
    Our database users can now access the filesystem. Thank you all for your help.

  • 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

  • /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)

  • Need to run fsck on UCS Central VM -- how?

    We had a storage disruption event recently that appears to have flipped the root volume on our UCS Central VM to read-only. After rebooting the VM, I get an error message about needing to run a manual fsck due to filesystem errors on /dev/VolGroup00/LogVol00 (see attached screenshot), and I get dropped into a shell prompting for the root password. I can't seem to find any root credentials in the UCS documentation. Is there a procedure for repairing the filesystem and repairing the VM?

    Brad,
    You'll need to open a TAC case.  We don't provide root/shell access to the VM externally.
    Regards,
    Robert

  • Oracle ASM can't see /dev/mapper devices

    I am running RHEL 5, Oracle 11G. I have Clusterware working properly but can't get my devices in the /dev/mapper directory to be seen when I install the ASM. Any help would be appreciated.
    thanks,

    Are you using ASMLib to present your raw devices to ASM?
    Have you set your ASM discovery disk string to point to the raw device during ASM installation?

  • 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)

  • How to run fsck.vfat for USB-stick during cRIO-9030 boot?

    Hi all,
    we have a cRIO-9030 with a USB-stick. Sometimes after power loss the USB-stick filesystem (FAT32) gets corrupted and has to be checked/fixed. How can I configure cRIO LinuxRT to do that?
    I've checked /etc/fstab, but it looks that the USB-stick is mounted somewhere else. I run mount - here is the line:
    /dev/sdc1 on /media/sdc1 type vfat (ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,quiet,errors=remount-ro)
    It would be nice if I can run fsck.vfat /dev/sdc1 every boot or when an error is detected.
    Thanks in advance,
    Nikolai

    Hi NickViz,
    My name is Ed form National Instruments Technical Support, I have researched into the topic and found that it is possible to use the 'System Exec.vi' to complete the command during the initialization of your RT application.
    You simply need to input your commands as a string just as you would to command prompt/terminal (depending on OS), you can also execute commands via SSH however this is one way communication between the RT application and the command shell.
    I have included some links below to articles which describe the methodology as well as give some further explanation into the NI Linux Real-Time OS.
    http://digital.ni.com/public.nsf/allkb/AFCAC25164CDBD4C86257C6A00545CD5?OpenDocument
    http://digital.ni.com/public.nsf/allkb/9822A3A39B1D0CBB86257C55006B962A
    http://www.ni.com/white-paper/14626/en/
    I hope this is helpful and you achieve what it is you need, do note you will need to enable SSH scripting as described in the article on using PuTTY for your Real Time device.
    Kind Regards,
    Ed

  • Boot stuck at waiting for dev-mapper

    When I boot, my system gets stuck at:
    A start job is running for dev-mapper-tank1.device (33min 36s / no limit)
    Does anyone know how to abort the process so I can finish booting my system and disable the job? I tried adding systemd.unit=rescue.target to my kernel flags but the job seems to start before I get a shell.
    Thanks!

    APIC: http://en.wikipedia.org/wiki/Advanced_P … Controller
    ACPI: http://en.wikipedia.org/wiki/Advanced_C … _Interface
    add 'nomodeset' to your kernel options.

  • How to solve that error in primavera p6 version 8.4 installation???????upgarding Data Base((missing permissions: DBMS_REPUTIL. Run the manual script first -- manual_script_before_upgrade.sql)

    please advice how to solve that problem (in steps):
    after completing p6 installation and during upgrading the old Data Base from p6 v8.3 to P6 v8.4 I'm facing that error
    ((missing permissions: DBMS_REPUTIL. Run the manual script first --> manual_script_before_upgrade.sql)

    for more help this image is much helpful
    1. Open cmd prompt >> Type sqlplus / as sysdba; >> connect sys/oracle@XE as sysdba;
    2. Type @ <path>\manual_script_before_install.sql
    thanks for      Pablo Oyarzo - Oracle    for his help as the above answer related to him

Maybe you are looking for