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)

Similar Messages

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/

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

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

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)

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

Systemd-remount-fs.service fails [SOLVED]

After a fresh install on a brandnew laptop, my root partition is being mounted read only, and I see that systemd-remount-fs.service fails:
[root@anton ~]# systemctl status systemd-remount-fs.service
systemd-remount-fs.service - Remount Root and Kernel File Systems
Loaded: loaded (/usr/lib/systemd/system/systemd-remount-fs.service; static)
Active: failed (Result: exit-code) since Sat, 2012-12-01 21:00:05 MST; 18min ago
Docs: man:systemd-remount-fs.service(8)
Process: 186 ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/systemd-remount-fs.service
Dec 01 21:00:05 anton systemd-remount-fs[186]: mount: / not mounted or bad option
Dec 01 21:00:05 anton systemd-remount-fs[186]: In some cases useful info is found in syslog - try
Dec 01 21:00:05 anton systemd-remount-fs[186]: dmesg | tail or so
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I have no idea why this is happening, or what to do to try and fix it - any help/advice would be greatly appreciated. Following is the information I think is necessary for assistance:
Note that I have /usr on a separate partition, which I suspect is possibly involved in the issue somehow.
Here's my fstab:
[root@anton ~]# cat /etc/fstab
# /dev/sda5
#UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 / ext4 defaults,rw,noatime,discard,data=writeback 0 1
# /dev/sda6
UUID=f4ab3551-c4f8-4e77-97bb-cc754c81af24 /usr ext4 defaults,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
Here's the relevant output from mount (note that my root (sda5) partition is not being mount with the options I specified in fstab):
[root@anton ~]# mount | grep sda
/dev/sda5 on / type ext4 (ro,relatime,data=ordered)
/dev/sda6 on /usr type ext4 (rw,noatime,discard,data=writeback)
/dev/sda7 on /var type ext4 (rw,noatime,discard,data=ordered)
/dev/sda8 on /home type ext4 (rw,relatime,discard,data=ordered)
Relavant snippet from /boot/grub/grub.cfg:
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a09ff37e-ce60-4173-b95a-4b71a53c01d3' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 a09ff37e-ce60-4173-b95a-4b71a53c01d3
else
search --no-floppy --fs-uuid --set=root a09ff37e-ce60-4173-b95a-4b71a53c01d3
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=UUID=a09ff37e-ce60-4173-b95a-4b71a53c01d3 ro init=/usr/lib/systemd/systemd
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
Finally, here's my mkinitcpio.cfg:
[root@anton ~]# cat /etc/mkinitcpio.conf
MODULES=""
BINARIES=""
FILES=""
HOOKS="base udev autodetect sata filesystems usbinput usr fsck shutdown"
Last edited by corey_s (2012-12-02 08:57:35)

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)

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

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.

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.

[SOLVED]systemd-tmpfiles-setup.service fails

Hi,
I have installed arch on an old laptop (dell inspiron 6000). I haven't used arch linux for last 2 years. It seems system management style has changed drastically.
Anyways, systemctl status systemd-tmpfiles-setup.service returns this;
● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sal 2015-06-09 11:00:18 EEST; 38min ago
Docs: man:tmpfiles.d(5)
man:systemd-tmpfiles(8)
Process: 228 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE)
Main PID: 228 (code=exited, status=1/FAILURE)
Haz 09 11:00:18 yasar-laptop systemd[1]: Starting Create Volatile Files and Directories...
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service: main process exited, code=exited, status=1/FAILURE
Haz 09 11:00:18 yasar-laptop systemd[1]: Failed to start Create Volatile Files and Directories.
Haz 09 11:00:18 yasar-laptop systemd[1]: Unit systemd-tmpfiles-setup.service entered failed state.
Haz 09 11:00:18 yasar-laptop systemd[1]: systemd-tmpfiles-setup.service failed.
Is this something that I should be concerned? I don't really know what this service supposed to do?
If I should be concerned, how to troubleshoot it? Keep in mind that this is a fresh arch install.
Last edited by yasar11732 (2015-06-09 16:31:04)

Thanks,
I have add acl option to fstab file, it works now. If anyone else has this problem, here is how my fstab file looks now;
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
UUID=936297ec-2bc3-45ef-bdb0-0a4ce7239204 / ext4 rw,relatime,data=ordered 0 1
UUID=d1fd9d31-99b5-45ba-97f4-a4c20b96e48b /var reiserfs rw,relatime,acl 0 2
UUID=6a9b3e39-8ea2-446f-9a71-79faab7cdafe /home xfs rw,relatime,attr2,inode64,noquota 0 2
# UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4
UUID=eb0b40d3-43ac-4f1f-8b29-97cd16a534d4 none swap defaults 0 0

/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?

Mounting local filesystem - FAIL (yet the fs still mounts...) [SOLVED]

After modifying my time/date setup (setting the hardware clock to UTC, and using a custom timezone file) I started to get a [FAIL] message during boot (after the system had resynched to drive times to the system time), and shutdown.
@ boot time
Mounting local filesystem
Ext3-fs: barriers not enabled
kjournal starting. Commit interval 5 seconds
Ext3-fs (sda4): using internal journal
Ext3-fs (sda4): mounted filesystem with ordered data mode
[FAIL]
@ shutdown
Unmounting Filesystem [FAIL]
Nothing seems to be negatively affected, and the boot and shutdown processes continue without even pausing, and sda4 (my /home directory) certainly seems to by mounted (since I'm using it now).
I've run fsck at boot a couple times, but the drives keep coming back clean. I've tried using my old timezone setup, but the fail message persists. I've successfully unmounted and mounted sda4 as Root, trying to generate an error message of some kind, but all I get is a successfully unmounted, or mounted, drive. I've unmounted sda4 priod to shutdown as well, but the message persists.
The only place in the logs the [FAIL] message shows up is in /var/log/boot:
Mounting local filesystem [BUSY] [FAIL]
I'm at a loss. I would like to fix this, if only to be sure that it's not a symptom of a larger problem. At the very least, I'd like to know what is causing it.
Last edited by uxrs75 (2011-08-02 06:40:31)

You interpret correctly, Logicien. BIOS is set to UTC; HARDWARECLOCK="UTC". Time and date are a-ok.
I ran mkinitcpio -p kernel26, but the message persists. I also tried using the live cd, and mounting each of the drives in turn. All of them mounted successfully, with no error messages. To verify that it is sda4, I commented the sda4 line out in fstab, and rebooted the machine. I got:
Mounting Local Filesystems [FAIL]
but none of the Ext3-fs stuff, and the boot process continued successfully. I'm wondering if it's something else.
I'll try adding quiet to the kernel boot line later this evening and see what that brings about.
rc.conf
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="PST"
KEYMAP="uk"
CONSOLEFONT="ter-116n.psf.gz"
#CONSOLEMAP="8859-1"
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="darkstar"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
DAEMONS=(hwclock syslog-ng dbus !network !netfs crond alsa mpd)
fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
#none /proc/bus/usb usbfs auto,busgid=101,busmode=0775,devgid=101,devmode=0664 0 0
/dev/sr0 /media/sr0 auto ro,users,noauto,unhide 0 0
/dev/sr1 /media/sr1 auto ro,users,noauto,unhide 0 0
#/dev/sda1 /boot ext2 defaults 0 1
#/dev/sda2 swap swap defaults 0 0
#/dev/sda3 / ext3 defaults 0 1
#/dev/sda4 /home ext3 defaults 0 1
UUID=597bd99a-173b-4b23-947d-b8a50859bcdd /boot ext2 defaults 0 1
UUID=a51a3b55-7c5c-45bb-96eb-79cfd1a77f54 swap swap defaults 0 0
UUID=c6ecf0fe-d2c4-4743-b639-1550295b65c6 / ext3 defaults 0 1
UUID=ff7030b8-890a-4673-bd1c-f502ca5efb2b /home ext3 defaults 0 1
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdb1 /media/sdb1 auto noauto,owner,users 0 0
/dev/sdc1 /media/sdc1 auto noauto,owner,users 0 0
/dev/sdd1 /media/sdd1 auto noauto,owner,users 0 0
/dev/sde1 /media/sde1 auto noauto,owner,users 0 0
/dev/sdf1 /media/sdf1 auto noauto,owner,users 0 0
fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sda1 * 1 208844 104422 83 Linux
/dev/sda2 208845 738989 265072+ 82 Linux swap / Solaris
/dev/sda3 738990 103153364 51207187+ 83 Linux
/dev/sda4 103153365 976768064 436807350 83 Linux
dumpe2fs -h /dev/sda1
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 597bd99a-173b-4b23-947d-b8a50859bcdd
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype sparse_super
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: not clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 26208
Block count: 104420
Reserved block count: 5221
Free blocks: 84721
Free inodes: 26177
First block: 1
Block size: 1024
Fragment size: 1024
Reserved GDT blocks: 256
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 2016
Inode blocks per group: 252
Filesystem created: Fri Apr 30 20:35:47 2010
Last mount time: Thu Aug 19 05:44:48 2010
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:23:24 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:24 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Default directory hash: half_md4
Directory Hash Seed: f5f22ff8-0cb1-4c30-a172-ead082f0ad8a
dumpe2fs -h /dev/sda3
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: c6ecf0fe-d2c4-4743-b639-1550295b65c6
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 3203072
Block count: 12801796
Reserved block count: 640089
Free blocks: 10487133
Free inodes: 3000642
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 1020
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:35:51 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 07:22:14 2011
Mount count: 8
Maximum mount count: 23
Last checked: Mon Aug 1 07:22:14 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:22:14 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 262152
Default directory hash: half_md4
Directory Hash Seed: 08e3f2db-7bb4-41fc-9364-9a9f637951ff
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0007df4e
Journal start: 1
dumpe2fs -h /dev/sda4
dumpe2fs 1.41.14 (22-Dec-2010)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: ff7030b8-890a-4673-bd1c-f502ca5efb2b
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 27303936
Block count: 109201837
Reserved block count: 5460091
Free blocks: 80860937
Free inodes: 27074933
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 997
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Filesystem created: Fri Apr 30 20:36:07 2010
Last mount time: Mon Aug 1 13:58:14 2011
Last write time: Mon Aug 1 13:58:14 2011
Mount count: 8
Maximum mount count: 25
Last checked: Mon Aug 1 07:23:25 2011
Check interval: 15552000 (6 months)
Next check after: Sat Jan 28 07:23:25 2012
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: e8dbb219-f7fe-4878-96b6-9137361ce1e2
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 128M
Journal length: 32768
Journal sequence: 0x0011b560
Journal start: 1
Last edited by uxrs75 (2011-08-02 06:19:11)

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.

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

Similar Messages

Maybe you are looking for