Lvm and gparted

a few months ago i installed arch linux on my computer. i use reiserfs as a filesystem and i have lvm on it (or is this backwards, i don't know ). i really don't know why i used lvm at installation, but at that time it seemed to me as a great tool to manage different "partitions" (logical volumes) on one partition. now i am thinking to cut a little space from my windows partition and give it to linux. So i have a few (well lots of ) questions.
My specs first:
# fdisk -l
Disk /dev/sda: 118.5 GB, 118526284800 bytes
255 heads, 63 sectors/track, 14410 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1912 15358108+ 7 HPFS/NTFS
/dev/sda2 * 1913 1925 104422+ 83 Linux
/dev/sda3 1926 14410 100285762+ f W95 Ext'd (LBA)
/dev/sda5 1926 4475 20482843+ 7 HPFS/NTFS
/dev/sda6 4476 4606 1052226 82 Linux swap / Solaris
/dev/sda7 4607 14410 78750598+ 8e Linux LVM
# di -h
Filesystem Mount Size Used Avail %Used fs Type
/dev/mapper/VolGro / 10.0G 4.6G 5.4G 46% reiserfs #VolGroup00-lvol0
/dev/sda2 /boot 101.9M 59.5M 42.4M 58% reiserfs
/dev/mapper/VolGro /home 65.1G 46.6G 18.5G 72% reiserfs #VolGroup00-lvol1
/dev/sda5 /mnt/win 19.5G 12.1G 7.5G 62% fuseblk
And questions:
1. can i resize partitions using gparted without damaging data on them? does this include partitions with lvm on them?
2. can i resize logical volumes on lvm without damaging data on them too? is snapshot used at doing this and how?
3. is there any benefit of using lvm if i can resize partitions without damaging data on them?
4. does changing logical volumes require a restart?
5. why does gparted show that on /dev/sda7 there is only 34 MB of used space?
6. is it ok to have two partitions marked as boot?
thank you for your answers.
Last edited by billy (2007-02-24 17:25:19)

Originally Posted by cmosentine
I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
Chris
With OES11 it's possible and quite easy to use the left free space on the system disk for NSS.
It also does not have the potential for havoc as was the case with OES2 (as with OES2 this was also possible, it just meant using EVMS on the system disk device, which could lead to issues booting after patching of updating due to needed missing kernel modules for EVMS within initrd).
Still, even with it being possible and supported to do so, if you can house the OS bits and data (be it on NSS and other filesystems) on different disk devices.. that would always be what I'd opt for. It makes certain maintenance/recovery and update tasks easier/more flexible/reliable as OS and data partitions are not within one and the same "container".
Cheers,
Willem

Similar Messages

  • LVM and NSS in OES11

    I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
    So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
    Chris

    Originally Posted by cmosentine
    I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
    So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
    Chris
    With OES11 it's possible and quite easy to use the left free space on the system disk for NSS.
    It also does not have the potential for havoc as was the case with OES2 (as with OES2 this was also possible, it just meant using EVMS on the system disk device, which could lead to issues booting after patching of updating due to needed missing kernel modules for EVMS within initrd).
    Still, even with it being possible and supported to do so, if you can house the OS bits and data (be it on NSS and other filesystems) on different disk devices.. that would always be what I'd opt for. It makes certain maintenance/recovery and update tasks easier/more flexible/reliable as OS and data partitions are not within one and the same "container".
    Cheers,
    Willem

  • [solved] Can't boot with LVM and usb external disk

    I successfully installed Archlinux on my first computer, using LVM on two internal Hard Drives.
    I'm trying to do exactly the same on my second computer, but I got a problem: the LVM volume is not found at boot, so that the root partition can't be mounted and the boot fails.
    The only difference is that, on my second computer, the second hard drive is connected through USB.
    Some hints: my second computer boots perfectly with LVM and Ubuntu. Archlinux needs to be configured adequately.
    I tried to add rootdelay=30 in menu.lst, but it changes nothing. Of course, in /etc/rc.conf I have USELVM="yes" and in /etc/mkinitcpio.conf I have HOOKS="base udev autodetect pata scsi sata keymap lvm2 filesystems"
    Thank you for helping me to keep Archlinux on my second computer!
    Last edited by Achille (2008-06-29 21:59:09)

    I finally solved my problem!
    In the file /etc/mkinitcpio.conf, I modified the MODULES loaded:
    MODULES="pata_acpi ata_generic ata_piix usbcore usb_storage uhci_hcd ehci_hcd sg scsi_mod sd_mod dm_mod"
    I also add in the file /lib/initcpio/hooks/lvm2 the line /bin/sleep 10
    /bin/sleep 10
    msg "Scanning logical volumes..."
    And finally, I ran the command:
    mkinitcpio -p kernel26

  • Can I install oracle VM server with lvm and md raid?

    Hello,
    I am trying to install oracle vm server 2.1.2 on a server with md raid and I would like to use lvm on it. It seems to me that the installer md raid support is not working and lvm support is missing.
    Can you help me?
    Thanks in advance for any reply.
    Mario Giammarco

    Hi,
    now i understand...
    hm - if the install does let you create a raid ( mdraid ) -> you can try to setup the system preconfigured by anaconda...
    the lines would be like following:
    part swap size 8000 asprimary --ondisk cciss/c0d0
    part swap size 8000 asprimary --ondisk cciss/c0d1
    part /boot fstype ext3 size 200 asprimary ondisk cciss/c0d0
    part / fstype ext3 size 14750 asprimary ondisk cciss/c0d0
    part /appl fstype ext3 size 30000 asprimary ondisk cciss/c0d1
    part raid.01 size 1000 grow --ondisk cciss/c0d0
    part raid.02 size 1000 grow --ondisk cciss/c0d1
    raid /disk/disk1 level 0 device=md0 --fstype ext3 raid.01 raid.02
    -> check out the your anaconda file: #/root/anaconda*
    -> -> modify the part lines and setup a anaconda installer...
    ( would also a better idea - if you like to install standarized systems )
    let me know - if you need assistance with anaconda...

  • Issue with LVM and 2 volume groups.

    I have 2 physical disks with one volume group on each of them. First contains root and /home. Second one contains /var and swap. After update I got "Timeout error" for /var and swap. I can boot in emergency systemd mode and can clearly see /var and swap partitions. I have lvm2 hook after udev and before fiesystems. I done latest changes to LVM long before and everything worked fine.
    Any advice? Thank you.
    Last edited by Gonzih (2013-05-03 13:33:15)

    Yep, I can see them and mount them (logical volumes). I booted with debug log level for systemd and log target to kmsg. But I can't find anything interesting in logs.
    here is dmesg output:
    [ 0.000000] Initializing cgroup subsys cpuset
    [ 0.000000] Initializing cgroup subsys cpu
    [ 0.000000] Linux version 3.8.10-1-ARCH (tobias@T-POWA-LX) (gcc version 4.8.0 20130411 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013
    [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/SSDVolGroup-root ro resume=/dev/mapper/MainVolGroup-swap systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
    [ 0.000000] e820: BIOS-provided physical RAM map:
    [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009e7ff] usable
    [ 0.000000] BIOS-e820: [mem 0x000000000009e800-0x000000000009ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] usable
    [ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000040200000-0x00000000aac0bfff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aac0c000-0x00000000aad8dfff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000aad8e000-0x00000000aad93fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aad94000-0x00000000aad94fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000aad95000-0x00000000aad95fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aad96000-0x00000000aadb7fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000aadb8000-0x00000000aadc5fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aadc6000-0x00000000aade7fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000aade8000-0x00000000aae21fff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aae22000-0x00000000aafe7fff] ACPI NVS
    [ 0.000000] BIOS-e820: [mem 0x00000000aafe8000-0x00000000aaffcfff] usable
    [ 0.000000] BIOS-e820: [mem 0x00000000aaffd000-0x00000000aaffffff] ACPI data
    [ 0.000000] BIOS-e820: [mem 0x00000000ab000000-0x00000000afffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000e3ffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed13fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed18000-0x00000000fed19fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ff980000-0x00000000ffbfffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x00000000ffd80000-0x00000000ffffffff] reserved
    [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000024f7fffff] usable
    [ 0.000000] NX (Execute Disable) protection: active
    [ 0.000000] SMBIOS 2.6 present.
    [ 0.000000] DMI: ASUSTeK Computer Inc. N55SL/N55SL, BIOS N55SL.201 11/10/2011
    [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
    [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
    [ 0.000000] No AGP bridge found
    [ 0.000000] e820: last_pfn = 0x24f800 max_arch_pfn = 0x400000000
    [ 0.000000] MTRR default type: uncachable
    [ 0.000000] MTRR fixed ranges enabled:
    [ 0.000000] 00000-9FFFF write-back
    [ 0.000000] A0000-BFFFF uncachable
    [ 0.000000] C0000-CFFFF write-protect
    [ 0.000000] D0000-E7FFF uncachable
    [ 0.000000] E8000-FFFFF write-protect
    [ 0.000000] MTRR variable ranges enabled:
    [ 0.000000] 0 base 000000000 mask F80000000 write-back
    [ 0.000000] 1 base 080000000 mask FE0000000 write-back
    [ 0.000000] 2 base 0A0000000 mask FF8000000 write-back
    [ 0.000000] 3 base 0A8000000 mask FFC000000 write-back
    [ 0.000000] 4 base 0AB000000 mask FFF000000 uncachable
    [ 0.000000] 5 base 100000000 mask F00000000 write-back
    [ 0.000000] 6 base 200000000 mask FC0000000 write-back
    [ 0.000000] 7 base 240000000 mask FF0000000 write-back
    [ 0.000000] 8 base 24F800000 mask FFF800000 uncachable
    [ 0.000000] 9 disabled
    [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    [ 0.000000] e820: update [mem 0xab000000-0xffffffff] usable ==> reserved
    [ 0.000000] e820: last_pfn = 0xaaffd max_arch_pfn = 0x400000000
    [ 0.000000] found SMP MP-table at [mem 0x000fcc80-0x000fcc8f] mapped at [ffff8800000fcc80]
    [ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
    [ 0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
    [ 0.000000] reserving inaccessible SNB gfx pages
    [ 0.000000] init_memory_mapping: [mem 0x00000000-0xaaffcfff]
    [ 0.000000] [mem 0x00000000-0xaadfffff] page 2M
    [ 0.000000] [mem 0xaae00000-0xaaffcfff] page 4k
    [ 0.000000] kernel direct mapping tables up to 0xaaffcfff @ [mem 0x1fffb000-0x1fffffff]
    [ 0.000000] init_memory_mapping: [mem 0x100000000-0x24f7fffff]
    [ 0.000000] [mem 0x100000000-0x24f7fffff] page 2M
    [ 0.000000] kernel direct mapping tables up to 0x24f7fffff @ [mem 0xaaff6000-0xaaffcfff]
    [ 0.000000] log_buf_len: 1048576
    [ 0.000000] early log buf free: 519132(99%)
    [ 0.000000] RAMDISK: [mem 0x378d0000-0x37c5ffff]
    [ 0.000000] ACPI: RSDP 00000000000f0430 00024 (v02 _ASUS_)
    [ 0.000000] ACPI: XSDT 00000000aaffee18 00074 (v01 _ASUS_ Notebook 06222004 MSFT 00010013)
    [ 0.000000] ACPI: FACP 00000000aaf9ad98 000F4 (v04 _ASUS_ Notebook 06222004 MSFT 00010013)
    [ 0.000000] ACPI Warning: 32/64 FACS address mismatch in FADT - two FACS tables! (20121018/tbfadt-394)
    [ 0.000000] ACPI BIOS Bug: Warning: 32/64X FACS address mismatch in FADT - 0xAAFE4E40/0x00000000AAFE4D40, using 32 (20121018/tbfadt-521)
    [ 0.000000] ACPI: DSDT 00000000aaf85018 14057 (v01 _ASUS_ Notebook 00000000 INTL 20091112)
    [ 0.000000] ACPI: FACS 00000000aafe4e40 00040
    [ 0.000000] ACPI: APIC 00000000aaffdf18 000CC (v02 _ASUS_ Notebook 06222004 MSFT 00010013)
    [ 0.000000] ACPI: DBGP 00000000aaffff18 00034 (v01 _ASUS_ Notebook 06222004 MSFT 00010013)
    [ 0.000000] ACPI: ECDT 00000000aafe4b18 000C1 (v01 _ASUS_ Notebook 06222004 AMI. 00000003)
    [ 0.000000] ACPI: SLIC 00000000aaf9be18 00176 (v01 _ASUS_ Notebook 06222004 ASUS 00000001)
    [ 0.000000] ACPI: HPET 00000000aafe5d18 00038 (v01 _ASUS_ Notebook 06222004 AMI. 00000003)
    [ 0.000000] ACPI: MCFG 00000000aafe5c98 0003C (v01 _ASUS_ Notebook 06222004 MSFT 00000097)
    [ 0.000000] ACPI: SSDT 00000000aaf84018 00955 (v01 PmRef Cpu0Ist 00003000 INTL 20091112)
    [ 0.000000] ACPI: SSDT 00000000aaf83018 00996 (v01 PmRef CpuPm 00003000 INTL 20091112)
    [ 0.000000] ACPI: ASF! 00000000aafe4a18 000A0 (v32 INTEL HCG 00000001 TFSM 000F4240)
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] No NUMA configuration found
    [ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000024f7fffff]
    [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x24f7fffff]
    [ 0.000000] NODE_DATA [mem 0x24f6fb000-0x24f6fffff]
    [ 0.000000] [ffffea0000000000-ffffea00093fffff] PMD -> [ffff880246e00000-ffff88024edfffff] on node 0
    [ 0.000000] Zone ranges:
    [ 0.000000] DMA [mem 0x00010000-0x00ffffff]
    [ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
    [ 0.000000] Normal [mem 0x100000000-0x24f7fffff]
    [ 0.000000] Movable zone start for each node
    [ 0.000000] Early memory node ranges
    [ 0.000000] node 0: [mem 0x00010000-0x0009dfff]
    [ 0.000000] node 0: [mem 0x00100000-0x1fffffff]
    [ 0.000000] node 0: [mem 0x20200000-0x3fffffff]
    [ 0.000000] node 0: [mem 0x40200000-0xaac0bfff]
    [ 0.000000] node 0: [mem 0xaad8e000-0xaad93fff]
    [ 0.000000] node 0: [mem 0xaad95000-0xaad95fff]
    [ 0.000000] node 0: [mem 0xaadb8000-0xaadc5fff]
    [ 0.000000] node 0: [mem 0xaade8000-0xaae21fff]
    [ 0.000000] node 0: [mem 0xaafe8000-0xaaffcfff]
    [ 0.000000] node 0: [mem 0x100000000-0x24f7fffff]
    [ 0.000000] On node 0 totalpages: 2072574
    [ 0.000000] DMA zone: 64 pages used for memmap
    [ 0.000000] DMA zone: 142 pages reserved
    [ 0.000000] DMA zone: 3776 pages, LIFO batch:0
    [ 0.000000] DMA32 zone: 10850 pages used for memmap
    [ 0.000000] DMA32 zone: 683534 pages, LIFO batch:31
    [ 0.000000] Normal zone: 21472 pages used for memmap
    [ 0.000000] Normal zone: 1352736 pages, LIFO batch:31
    [ 0.000000] ACPI: PM-Timer IO Port: 0x408
    [ 0.000000] ACPI: Local APIC address 0xfee00000
    [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x08] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x09] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0a] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0c] lapic_id[0x0b] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0d] lapic_id[0x0c] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0e] lapic_id[0x0d] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x0f] lapic_id[0x0e] disabled)
    [ 0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x0f] disabled)
    [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
    [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [ 0.000000] ACPI: IRQ0 used by override.
    [ 0.000000] ACPI: IRQ2 used by override.
    [ 0.000000] ACPI: IRQ9 used by override.
    [ 0.000000] Using ACPI (MADT) for SMP configuration information
    [ 0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
    [ 0.000000] smpboot: Allowing 16 CPUs, 8 hotplug CPUs
    [ 0.000000] nr_irqs_gsi: 40
    [ 0.000000] PM: Registered nosave memory: 000000000009e000 - 000000000009f000
    [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    [ 0.000000] PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    [ 0.000000] PM: Registered nosave memory: 0000000020000000 - 0000000020200000
    [ 0.000000] PM: Registered nosave memory: 0000000040000000 - 0000000040200000
    [ 0.000000] PM: Registered nosave memory: 00000000aac0c000 - 00000000aad8e000
    [ 0.000000] PM: Registered nosave memory: 00000000aad94000 - 00000000aad95000
    [ 0.000000] PM: Registered nosave memory: 00000000aad96000 - 00000000aadb8000
    [ 0.000000] PM: Registered nosave memory: 00000000aadc6000 - 00000000aade8000
    [ 0.000000] PM: Registered nosave memory: 00000000aae22000 - 00000000aafe8000
    [ 0.000000] PM: Registered nosave memory: 00000000aaffd000 - 00000000ab000000
    [ 0.000000] PM: Registered nosave memory: 00000000ab000000 - 00000000b0000000
    [ 0.000000] PM: Registered nosave memory: 00000000b0000000 - 00000000e0000000
    [ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000e4000000
    [ 0.000000] PM: Registered nosave memory: 00000000e4000000 - 00000000fec00000
    [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 00000000fec01000
    [ 0.000000] PM: Registered nosave memory: 00000000fec01000 - 00000000fed10000
    [ 0.000000] PM: Registered nosave memory: 00000000fed10000 - 00000000fed14000
    [ 0.000000] PM: Registered nosave memory: 00000000fed14000 - 00000000fed18000
    [ 0.000000] PM: Registered nosave memory: 00000000fed18000 - 00000000fed1a000
    [ 0.000000] PM: Registered nosave memory: 00000000fed1a000 - 00000000fed1c000
    [ 0.000000] PM: Registered nosave memory: 00000000fed1c000 - 00000000fed20000
    [ 0.000000] PM: Registered nosave memory: 00000000fed20000 - 00000000fee00000
    [ 0.000000] PM: Registered nosave memory: 00000000fee00000 - 00000000fee01000
    [ 0.000000] PM: Registered nosave memory: 00000000fee01000 - 00000000ff980000
    [ 0.000000] PM: Registered nosave memory: 00000000ff980000 - 00000000ffc00000
    [ 0.000000] PM: Registered nosave memory: 00000000ffc00000 - 00000000ffd80000
    [ 0.000000] PM: Registered nosave memory: 00000000ffd80000 - 0000000100000000
    [ 0.000000] e820: [mem 0xb0000000-0xdfffffff] available for PCI devices
    [ 0.000000] Booting paravirtualized kernel on bare hardware
    [ 0.000000] setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:16 nr_node_ids:1
    [ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88024f400000 s85184 r8192 d21312 u131072
    [ 0.000000] pcpu-alloc: s85184 r8192 d21312 u131072 alloc=1*2097152
    [ 0.000000] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
    [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2040046
    [ 0.000000] Policy zone: Normal
    [ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/SSDVolGroup-root ro resume=/dev/mapper/MainVolGroup-swap systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
    [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
    [ 0.000000] __ex_table already sorted, skipping sort
    [ 0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
    [ 0.000000] Checking aperture...
    [ 0.000000] No AGP bridge found
    [ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
    [ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
    [ 0.000000] Memory: 8074672k/9691136k available (4908k kernel code, 1400840k absent, 215624k reserved, 4024k data, 820k init)
    [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=1
    [ 0.000000] Preemptible hierarchical RCU implementation.
    [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
    [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP.
    [ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=16.
    [ 0.000000] NR_IRQS:4352 nr_irqs:808 16
    [ 0.000000] Extended CMOS year: 2000
    [ 0.000000] Console: colour dummy device 80x25
    [ 0.000000] console [tty0] enabled
    [ 0.000000] allocated 33554432 bytes of page_cgroup
    [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
    [ 0.000000] hpet clockevent registered
    [ 0.000000] tsc: Fast TSC calibration using PIT
    [ 0.003333] tsc: Detected 2194.984 MHz processor
    [ 0.000003] Calibrating delay loop (skipped), value calculated using timer frequency.. 4391.88 BogoMIPS (lpj=7316613)
    [ 0.000006] pid_max: default: 32768 minimum: 301
    [ 0.000039] Security Framework initialized
    [ 0.000045] AppArmor: AppArmor disabled by boot time parameter
    [ 0.000573] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
    [ 0.002327] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
    [ 0.003081] Mount-cache hash table entries: 256
    [ 0.003260] Initializing cgroup subsys cpuacct
    [ 0.003262] Initializing cgroup subsys memory
    [ 0.003269] Initializing cgroup subsys devices
    [ 0.003271] Initializing cgroup subsys freezer
    [ 0.003272] Initializing cgroup subsys net_cls
    [ 0.003274] Initializing cgroup subsys blkio
    [ 0.003298] CPU: Physical Processor ID: 0
    [ 0.003299] CPU: Processor Core ID: 0
    [ 0.003304] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
    ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
    [ 0.003307] mce: CPU supports 9 MCE banks
    [ 0.003321] CPU0: Thermal monitoring enabled (TM1)
    [ 0.003330] process: using mwait in idle threads
    [ 0.003333] Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0
    Last level dTLB entries: 4KB 512, 2MB 32, 4MB 32
    tlb_flushall_shift: 5
    [ 0.003497] Freeing SMP alternatives: 20k freed
    [ 0.004779] ACPI: Core revision 20121018
    [ 0.048855] ftrace: allocating 19313 entries in 76 pages
    [ 0.059156] Switched APIC routing to physical flat.
    [ 0.059575] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
    [ 0.092543] smpboot: CPU0: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz (fam: 06, model: 2a, stepping: 07)
    [ 0.092551] TSC deadline timer enabled
    [ 0.092554] Performance Events: PEBS fmt1+, 16-deep LBR, SandyBridge events, Intel PMU driver.
    [ 0.092560] perf_event_intel: PEBS disabled due to CPU errata, please upgrade microcode
    [ 0.092562] ... version: 3
    [ 0.092563] ... bit width: 48
    [ 0.092564] ... generic registers: 4
    [ 0.092565] ... value mask: 0000ffffffffffff
    [ 0.092567] ... max period: 000000007fffffff
    [ 0.092568] ... fixed-purpose events: 3
    [ 0.092569] ... event mask: 000000070000000f
    [ 0.145921] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
    [ 0.132666] smpboot: Booting Node 0, Processors #1 #2 #3 #4 #5 #6 #7
    [ 0.252559] Brought up 8 CPUs
    [ 0.252563] smpboot: Total of 8 processors activated (35133.06 BogoMIPS)
    [ 0.260397] devtmpfs: initialized
    [ 0.261702] PM: Registering ACPI NVS region [mem 0xaae22000-0xaafe7fff] (1859584 bytes)
    [ 0.262489] RTC time: 13:35:47, date: 05/03/13
    [ 0.262533] NET: Registered protocol family 16
    [ 0.262683] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
    [ 0.262685] ACPI: bus type pci registered
    [ 0.262752] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xe0000000-0xe3ffffff] (base 0xe0000000)
    [ 0.262754] PCI: MMCONFIG at [mem 0xe0000000-0xe3ffffff] reserved in E820
    [ 0.271626] PCI: Using configuration type 1 for base access
    [ 0.271915] mtrr: your CPUs had inconsistent variable MTRR settings
    [ 0.271916] mtrr: probably your BIOS does not setup all CPUs.
    [ 0.271917] mtrr: corrected configuration.
    [ 0.272339] bio: create slab <bio-0> at 0
    [ 0.272400] ACPI: Added _OSI(Module Device)
    [ 0.272402] ACPI: Added _OSI(Processor Device)
    [ 0.272403] ACPI: Added _OSI(3.0 _SCP Extensions)
    [ 0.272405] ACPI: Added _OSI(Processor Aggregator Device)
    [ 0.274772] ACPI: EC: EC description table is found, configuring boot EC
    [ 0.274777] ACPI: EC: Look up EC in DSDT
    [ 0.277260] ACPI: Executed 1 blocks of module-level executable AML code
    [ 0.280704] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
    [ 0.334137] ACPI: SSDT 00000000aadca798 0073F (v01 PmRef Cpu0Cst 00003001 INTL 20091112)
    [ 0.334721] ACPI: Dynamic OEM Table Load:
    [ 0.334724] ACPI: SSDT (null) 0073F (v01 PmRef Cpu0Cst 00003001 INTL 20091112)
    [ 0.335028] ACPI: SSDT 00000000aadcba98 00303 (v01 PmRef ApIst 00003000 INTL 20091112)
    [ 0.335636] ACPI: Dynamic OEM Table Load:
    [ 0.335639] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20091112)
    [ 0.335809] ACPI: SSDT 00000000aadc9d98 00119 (v01 PmRef ApCst 00003000 INTL 20091112)
    [ 0.336390] ACPI: Dynamic OEM Table Load:
    [ 0.336393] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20091112)
    [ 0.337542] ACPI: Interpreter enabled
    [ 0.337547] ACPI: (supports S0 S3 S4 S5)
    [ 0.337567] ACPI: Using IOAPIC for interrupt routing
    [ 0.343600] ACPI: EC: GPE = 0x1b, I/O: command/status = 0x66, data = 0x62
    [ 0.343756] ACPI: No dock devices found.
    [ 0.343760] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
    [ 0.343970] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
    [ 0.343973] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    [ 0.344693] PCI host bridge to bus 0000:00
    [ 0.344696] pci_bus 0000:00: root bus resource [bus 00-3e]
    [ 0.344698] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
    [ 0.344700] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
    [ 0.344702] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
    [ 0.344704] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
    [ 0.344706] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
    [ 0.344708] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
    [ 0.344709] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
    [ 0.344711] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
    [ 0.344713] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
    [ 0.344715] pci_bus 0000:00: root bus resource [mem 0xb0000000-0xfeafffff]
    [ 0.344717] pci_bus 0000:00: root bus resource [mem 0xfed40000-0xfed44fff]
    [ 0.344725] pci 0000:00:00.0: [8086:0104] type 00 class 0x060000
    [ 0.344763] pci 0000:00:01.0: [8086:0101] type 01 class 0x060400
    [ 0.344796] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
    [ 0.344816] pci 0000:00:02.0: [8086:0116] type 00 class 0x030000
    [ 0.344827] pci 0000:00:02.0: reg 10: [mem 0xdc400000-0xdc7fffff 64bit]
    [ 0.344834] pci 0000:00:02.0: reg 18: [mem 0xb0000000-0xbfffffff 64bit pref]
    [ 0.344839] pci 0000:00:02.0: reg 20: [io 0xe000-0xe03f]
    [ 0.344895] pci 0000:00:16.0: [8086:1c3a] type 00 class 0x078000
    [ 0.344920] pci 0000:00:16.0: reg 10: [mem 0xdf00b000-0xdf00b00f 64bit]
    [ 0.344999] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
    [ 0.345035] pci 0000:00:1a.0: [8086:1c2d] type 00 class 0x0c0320
    [ 0.345058] pci 0000:00:1a.0: reg 10: [mem 0xdf008000-0xdf0083ff]
    [ 0.345152] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
    [ 0.345180] pci 0000:00:1b.0: [8086:1c20] type 00 class 0x040300
    [ 0.345197] pci 0000:00:1b.0: reg 10: [mem 0xdf000000-0xdf003fff 64bit]
    [ 0.345268] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
    [ 0.345294] pci 0000:00:1c.0: [8086:1c10] type 01 class 0x060400
    [ 0.345376] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
    [ 0.345403] pci 0000:00:1c.1: [8086:1c12] type 01 class 0x060400
    [ 0.345486] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
    [ 0.345517] pci 0000:00:1c.3: [8086:1c16] type 01 class 0x060400
    [ 0.345598] pci 0000:00:1c.3: PME# supported from D0 D3hot D3cold
    [ 0.345627] pci 0000:00:1c.5: [8086:1c1a] type 01 class 0x060400
    [ 0.345709] pci 0000:00:1c.5: PME# supported from D0 D3hot D3cold
    [ 0.345744] pci 0000:00:1d.0: [8086:1c26] type 00 class 0x0c0320
    [ 0.345766] pci 0000:00:1d.0: reg 10: [mem 0xdf007000-0xdf0073ff]
    [ 0.345860] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
    [ 0.345889] pci 0000:00:1f.0: [8086:1c49] type 00 class 0x060100
    [ 0.346019] pci 0000:00:1f.2: [8086:1c03] type 00 class 0x010601
    [ 0.346039] pci 0000:00:1f.2: reg 10: [io 0xe0b0-0xe0b7]
    [ 0.346048] pci 0000:00:1f.2: reg 14: [io 0xe0a0-0xe0a3]
    [ 0.346056] pci 0000:00:1f.2: reg 18: [io 0xe090-0xe097]
    [ 0.346065] pci 0000:00:1f.2: reg 1c: [io 0xe080-0xe083]
    [ 0.346074] pci 0000:00:1f.2: reg 20: [io 0xe060-0xe07f]
    [ 0.346082] pci 0000:00:1f.2: reg 24: [mem 0xdf006000-0xdf0067ff]
    [ 0.346131] pci 0000:00:1f.2: PME# supported from D3hot
    [ 0.346151] pci 0000:00:1f.3: [8086:1c22] type 00 class 0x0c0500
    [ 0.346167] pci 0000:00:1f.3: reg 10: [mem 0xdf005000-0xdf0050ff 64bit]
    [ 0.346189] pci 0000:00:1f.3: reg 20: [io 0xe040-0xe05f]
    [ 0.346253] pci 0000:01:00.0: [10de:1247] type 00 class 0x030000
    [ 0.346266] pci 0000:01:00.0: reg 10: [mem 0xda000000-0xdbffffff]
    [ 0.346279] pci 0000:01:00.0: reg 14: [mem 0xc0000000-0xcfffffff 64bit pref]
    [ 0.346292] pci 0000:01:00.0: reg 1c: [mem 0xd0000000-0xd3ffffff 64bit pref]
    [ 0.346301] pci 0000:01:00.0: reg 24: [io 0xd000-0xd07f]
    [ 0.346310] pci 0000:01:00.0: reg 30: [mem 0xdc000000-0xdc07ffff pref]
    [ 0.353417] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.353425] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    [ 0.353432] pci 0000:00:01.0: bridge window [mem 0xda000000-0xdc0fffff]
    [ 0.353442] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xd3ffffff 64bit pref]
    [ 0.353540] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.353544] pci 0000:00:1c.0: bridge window [io 0xc000-0xcfff]
    [ 0.353549] pci 0000:00:1c.0: bridge window [mem 0xde600000-0xdeffffff]
    [ 0.353556] pci 0000:00:1c.0: bridge window [mem 0xd6200000-0xd6bfffff 64bit pref]
    [ 0.353763] pci 0000:03:00.0: [8086:008a] type 00 class 0x028000
    [ 0.353907] pci 0000:03:00.0: reg 10: [mem 0xddc00000-0xddc01fff 64bit]
    [ 0.354584] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
    [ 0.363542] pci 0000:00:1c.1: PCI bridge to [bus 03]
    [ 0.363546] pci 0000:00:1c.1: bridge window [io 0xb000-0xbfff]
    [ 0.363551] pci 0000:00:1c.1: bridge window [mem 0xddc00000-0xde5fffff]
    [ 0.363557] pci 0000:00:1c.1: bridge window [mem 0xd5700000-0xd60fffff 64bit pref]
    [ 0.363641] pci 0000:04:00.0: [1b21:1042] type 00 class 0x0c0330
    [ 0.363678] pci 0000:04:00.0: reg 10: [mem 0xdd200000-0xdd207fff 64bit]
    [ 0.363870] pci 0000:04:00.0: PME# supported from D3hot D3cold
    [ 0.373416] pci 0000:00:1c.3: PCI bridge to [bus 04]
    [ 0.373426] pci 0000:00:1c.3: bridge window [io 0xa000-0xafff]
    [ 0.373435] pci 0000:00:1c.3: bridge window [mem 0xdd200000-0xddbfffff]
    [ 0.373449] pci 0000:00:1c.3: bridge window [mem 0xd4c00000-0xd55fffff 64bit pref]
    [ 0.373564] pci 0000:05:00.0: [1969:1083] type 00 class 0x020000
    [ 0.373593] pci 0000:05:00.0: reg 10: [mem 0xdc800000-0xdc83ffff 64bit]
    [ 0.373608] pci 0000:05:00.0: reg 18: [io 0x9000-0x907f]
    [ 0.373738] pci 0000:05:00.0: PME# supported from D0 D1 D2 D3hot D3cold
    [ 0.383416] pci 0000:00:1c.5: PCI bridge to [bus 05]
    [ 0.383425] pci 0000:00:1c.5: bridge window [io 0x9000-0x9fff]
    [ 0.383434] pci 0000:00:1c.5: bridge window [mem 0xdc800000-0xdd1fffff]
    [ 0.383448] pci 0000:00:1c.5: bridge window [mem 0xd4100000-0xd4afffff 64bit pref]
    [ 0.383531] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEG0._PRT]
    [ 0.383599] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
    [ 0.383633] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
    [ 0.383666] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP04._PRT]
    [ 0.383698] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP06._PRT]
    [ 0.383884] pci0000:00: Requesting ACPI _OSC control (0x1d)
    [ 0.384170] pci0000:00: ACPI _OSC control (0x1d) granted
    [ 0.385076] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12)
    [ 0.385119] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 12)
    [ 0.385160] ACPI: PCI Interrupt Link [LNKC] (IRQs *3 4 5 6 7 10 12)
    [ 0.385199] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 12)
    [ 0.385240] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    [ 0.385282] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 12) *0, disabled.
    [ 0.385326] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 *5 6 7 10 12)
    [ 0.385366] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 12)
    [ 0.385442] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
    [ 0.385446] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=none,locks=none
    [ 0.385448] vgaarb: loaded
    [ 0.385449] vgaarb: bridge control possible 0000:01:00.0
    [ 0.385450] vgaarb: no bridge control possible 0000:00:02.0
    [ 0.385484] PCI: Using ACPI for IRQ routing
    [ 0.387021] PCI: pci_cache_line_size set to 64 bytes
    [ 0.387097] e820: reserve RAM buffer [mem 0x0009e800-0x0009ffff]
    [ 0.387099] e820: reserve RAM buffer [mem 0xaac0c000-0xabffffff]
    [ 0.387102] e820: reserve RAM buffer [mem 0xaad94000-0xabffffff]
    [ 0.387104] e820: reserve RAM buffer [mem 0xaad96000-0xabffffff]
    [ 0.387105] e820: reserve RAM buffer [mem 0xaadc6000-0xabffffff]
    [ 0.387107] e820: reserve RAM buffer [mem 0xaae22000-0xabffffff]
    [ 0.387109] e820: reserve RAM buffer [mem 0xaaffd000-0xabffffff]
    [ 0.387110] e820: reserve RAM buffer [mem 0x24f800000-0x24fffffff]
    [ 0.387195] NetLabel: Initializing
    [ 0.387197] NetLabel: domain hash size = 128
    [ 0.387198] NetLabel: protocols = UNLABELED CIPSOv4
    [ 0.387208] NetLabel: unlabeled traffic allowed by default
    [ 0.387231] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [ 0.387236] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
    [ 0.389244] Switching to clocksource hpet
    [ 0.393649] pnp: PnP ACPI init
    [ 0.393662] ACPI: bus type pnp registered
    [ 0.393721] pnp 00:00: [dma 4]
    [ 0.393744] pnp 00:00: Plug and Play ACPI device, IDs PNP0200 (active)
    [ 0.393766] pnp 00:01: Plug and Play ACPI device, IDs INT0800 (active)
    [ 0.393863] pnp 00:02: Plug and Play ACPI device, IDs PNP0103 (active)
    [ 0.393893] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
    [ 0.393936] system 00:04: [io 0x0680-0x069f] has been reserved
    [ 0.393939] system 00:04: [io 0x1000-0x100f] has been reserved
    [ 0.393941] system 00:04: [io 0xffff] has been reserved
    [ 0.393943] system 00:04: [io 0xffff] has been reserved
    [ 0.393945] system 00:04: [io 0x0400-0x0453] has been reserved
    [ 0.393947] system 00:04: [io 0x0458-0x047f] has been reserved
    [ 0.393949] system 00:04: [io 0x0500-0x057f] has been reserved
    [ 0.393951] system 00:04: [io 0x164e-0x164f] has been reserved
    [ 0.393954] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.393978] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
    [ 0.394018] system 00:06: [io 0x0454-0x0457] has been reserved
    [ 0.394021] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
    [ 0.394050] system 00:07: [io 0x0240-0x0259] has been reserved
    [ 0.394053] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.394103] pnp 00:08: Plug and Play ACPI device, IDs SYN0a17 SYN0a00 SYN0002 PNP0f13 (active)
    [ 0.394137] pnp 00:09: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
    [ 0.394358] system 00:0a: [mem 0xfed1c000-0xfed1ffff] has been reserved
    [ 0.394360] system 00:0a: [mem 0xfed10000-0xfed17fff] could not be reserved
    [ 0.394362] system 00:0a: [mem 0xfed18000-0xfed18fff] has been reserved
    [ 0.394364] system 00:0a: [mem 0xfed19000-0xfed19fff] has been reserved
    [ 0.394367] system 00:0a: [mem 0xe0000000-0xe3ffffff] has been reserved
    [ 0.394369] system 00:0a: [mem 0xfed20000-0xfed3ffff] has been reserved
    [ 0.394371] system 00:0a: [mem 0xfed90000-0xfed93fff] has been reserved
    [ 0.394372] system 00:0a: [mem 0xfed45000-0xfed8ffff] has been reserved
    [ 0.394375] system 00:0a: [mem 0xff000000-0xffffffff] could not be reserved
    [ 0.394377] system 00:0a: [mem 0xfee00000-0xfeefffff] could not be reserved
    [ 0.394380] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.394450] system 00:0b: [mem 0xd6c00000-0xd6c00fff] has been reserved
    [ 0.394453] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
    [ 0.394580] system 00:0c: [mem 0x20000000-0x201fffff] has been reserved
    [ 0.394582] system 00:0c: [mem 0x40000000-0x401fffff] has been reserved
    [ 0.394585] system 00:0c: Plug and Play ACPI device, IDs PNP0c01 (active)
    [ 0.394610] pnp: PnP ACPI: found 13 devices
    [ 0.394612] ACPI: ACPI bus type pnp unregistered
    [ 0.400997] pci 0000:00:01.0: PCI bridge to [bus 01]
    [ 0.401001] pci 0000:00:01.0: bridge window [io 0xd000-0xdfff]
    [ 0.401004] pci 0000:00:01.0: bridge window [mem 0xda000000-0xdc0fffff]
    [ 0.401007] pci 0000:00:01.0: bridge window [mem 0xc0000000-0xd3ffffff 64bit pref]
    [ 0.401011] pci 0000:00:1c.0: PCI bridge to [bus 02]
    [ 0.401014] pci 0000:00:1c.0: bridge window [io 0xc000-0xcfff]
    [ 0.401020] pci 0000:00:1c.0: bridge window [mem 0xde600000-0xdeffffff]
    [ 0.401024] pci 0000:00:1c.0: bridge window [mem 0xd6200000-0xd6bfffff 64bit pref]
    [ 0.401031] pci 0000:00:1c.1: PCI bridge to [bus 03]
    [ 0.401034] pci 0000:00:1c.1: bridge window [io 0xb000-0xbfff]
    [ 0.401040] pci 0000:00:1c.1: bridge window [mem 0xddc00000-0xde5fffff]
    [ 0.401044] pci 0000:00:1c.1: bridge window [mem 0xd5700000-0xd60fffff 64bit pref]
    [ 0.401051] pci 0000:00:1c.3: PCI bridge to [bus 04]
    [ 0.401054] pci 0000:00:1c.3: bridge window [io 0xa000-0xafff]
    [ 0.401059] pci 0000:00:1c.3: bridge window [mem 0xdd200000-0xddbfffff]
    [ 0.401064] pci 0000:00:1c.3: bridge window [mem 0xd4c00000-0xd55fffff 64bit pref]
    [ 0.401070] pci 0000:00:1c.5: PCI bridge to [bus 05]
    [ 0.401074] pci 0000:00:1c.5: bridge window [io 0x9000-0x9fff]
    [ 0.401079] pci 0000:00:1c.5: bridge window [mem 0xdc800000-0xdd1fffff]
    [ 0.401084] pci 0000:00:1c.5: bridge window [mem 0xd4100000-0xd4afffff 64bit pref]
    [ 0.401125] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
    [ 0.401127] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
    [ 0.401129] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
    [ 0.401131] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
    [ 0.401133] pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
    [ 0.401134] pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
    [ 0.401136] pci_bus 0000:00: resource 10 [mem 0x000dc000-0x000dffff]
    [ 0.401138] pci_bus 0000:00: resource 11 [mem 0x000e0000-0x000e3fff]
    [ 0.401140] pci_bus 0000:00: resource 12 [mem 0x000e4000-0x000e7fff]
    [ 0.401142] pci_bus 0000:00: resource 13 [mem 0xb0000000-0xfeafffff]
    [ 0.401143] pci_bus 0000:00: resource 14 [mem 0xfed40000-0xfed44fff]
    [ 0.401145] pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
    [ 0.401147] pci_bus 0000:01: resource 1 [mem 0xda000000-0xdc0fffff]
    [ 0.401149] pci_bus 0000:01: resource 2 [mem 0xc0000000-0xd3ffffff 64bit pref]
    [ 0.401151] pci_bus 0000:02: resource 0 [io 0xc000-0xcfff]
    [ 0.401152] pci_bus 0000:02: resource 1 [mem 0xde600000-0xdeffffff]
    [ 0.401154] pci_bus 0000:02: resource 2 [mem 0xd6200000-0xd6bfffff 64bit pref]
    [ 0.401156] pci_bus 0000:03: resource 0 [io 0xb000-0xbfff]
    [ 0.401158] pci_bus 0000:03: resource 1 [mem 0xddc00000-0xde5fffff]
    [ 0.401160] pci_bus 0000:03: resource 2 [mem 0xd5700000-0xd60fffff 64bit pref]
    [ 0.401162] pci_bus 0000:04: resource 0 [io 0xa000-0xafff]
    [ 0.401163] pci_bus 0000:04: resource 1 [mem 0xdd200000-0xddbfffff]
    [ 0.401165] pci_bus 0000:04: resource 2 [mem 0xd4c00000-0xd55fffff 64bit pref]
    [ 0.401167] pci_bus 0000:05: resource 0 [io 0x9000-0x9fff]
    [ 0.401169] pci_bus 0000:05: resource 1 [mem 0xdc800000-0xdd1fffff]
    [ 0.401170] pci_bus 0000:05: resource 2 [mem 0xd4100000-0xd4afffff 64bit pref]
    [ 0.401203] NET: Registered protocol family 2
    [ 0.401386] TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.401597] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
    [ 0.401732] TCP: Hash tables configured (established 65536 bind 65536)
    [ 0.401751] TCP: reno registered
    [ 0.401763] UDP hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.401796] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
    [ 0.401871] NET: Registered protocol family 1
    [ 0.401882] pci 0000:00:02.0: Boot video device
    [ 0.649137] PCI: CLS 64 bytes, default 64
    [ 0.649172] Unpacking initramfs...
    [ 0.717214] Freeing initrd memory: 3648k freed
    [ 0.717643] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
    [ 0.717647] software IO TLB [mem 0xa6c0c000-0xaac0c000] (64MB) mapped at [ffff8800a6c0c000-ffff8800aac0bfff]
    [ 0.718142] audit: initializing netlink socket (disabled)
    [ 0.718152] type=2000 audit(1367588147.679:1): initialized
    [ 0.730817] HugeTLB registered 2 MB page size, pre-allocated 0 pages
    [ 0.732352] VFS: Disk quotas dquot_6.5.2
    [ 0.732401] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
    [ 0.732571] msgmni has been set to 15778
    [ 0.732780] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
    [ 0.732809] io scheduler noop registered
    [ 0.732810] io scheduler deadline registered
    [ 0.732815] io scheduler cfq registered (default)
    [ 0.732906] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
    [ 0.733001] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
    [ 0.733106] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
    [ 0.733210] pcieport 0000:00:1c.3: irq 43 for MSI/MSI-X
    [ 0.733313] pcieport 0000:00:1c.5: irq 44 for MSI/MSI-X
    [ 0.733390] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
    [ 0.733392] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
    [ 0.733395] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
    [ 0.733413] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
    [ 0.733417] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
    [ 0.733434] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
    [ 0.733436] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
    [ 0.733440] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
    [ 0.733461] pcieport 0000:00:1c.3: Signaling PME through PCIe PME interrupt
    [ 0.733463] pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
    [ 0.733467] pcie_pme 0000:00:1c.3:pcie01: service driver pcie_pme loaded
    [ 0.733484] pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
    [ 0.733486] pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
    [ 0.733491] pcie_pme 0000:00:1c.5:pcie01: service driver pcie_pme loaded
    [ 0.733537] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
    [ 0.733538] vesafb: scrolling: redraw
    [ 0.733540] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
    [ 0.734311] vesafb: framebuffer at 0xb0000000, mapped to 0xffffc90004f00000, using 5120k, total 5120k
    [ 0.834874] Console: switching to colour frame buffer device 160x64
    [ 0.935388] fb0: VESA VGA frame buffer device
    [ 0.935400] intel_idle: MWAIT substates: 0x21120
    [ 0.935401] intel_idle: v0.4 model 0x2A
    [ 0.935403] intel_idle: lapic_timer_reliable_states 0xffffffff
    [ 0.935440] GHES: HEST is not enabled!
    [ 0.935483] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    [ 0.935911] Linux agpgart interface v0.103
    [ 0.935990] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
    [ 0.937667] i8042: Detected active multiplexing controller, rev 1.1
    [ 0.938451] serio: i8042 KBD port at 0x60,0x64 irq 1
    [ 0.938474] serio: i8042 AUX0 port at 0x60,0x64 irq 12
    [ 0.938494] serio: i8042 AUX1 port at 0x60,0x64 irq 12
    [ 0.938515] serio: i8042 AUX2 port at 0x60,0x64 irq 12
    [ 0.938532] serio: i8042 AUX3 port at 0x60,0x64 irq 12
    [ 0.938616] mousedev: PS/2 mouse device common for all mice
    [ 0.938686] rtc_cmos 00:05: RTC can wake from S4
    [ 0.938811] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
    [ 0.938838] rtc0: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
    [ 0.938991] cpuidle: using governor ladder
    [ 0.939190] cpuidle: using governor menu
    [ 0.939192] EFI Variables Facility v0.08 2004-May-17
    [ 0.939237] drop_monitor: Initializing network drop monitor service
    [ 0.939306] TCP: cubic registered
    [ 0.939395] NET: Registered protocol family 10
    [ 0.939535] NET: Registered protocol family 17
    [ 0.939543] Key type dns_resolver registered
    [ 0.939844] PM: Checking hibernation image partition /dev/mapper/MainVolGroup-swap
    [ 0.972538] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
    [ 1.084950] PM: Hibernation image not present or could not be loaded.
    [ 1.084974] registered taskstats version 1
    [ 1.085749] Magic number: 13:624:583
    [ 1.085763] pci_bus 0000:04: hash matches
    [ 1.085842] rtc_cmos 00:05: setting system clock to 2013-05-03 13:35:48 UTC (1367588148)
    [ 1.087384] Freeing unused kernel memory: 820k freed
    [ 1.087474] Write protecting the kernel read-only data: 8192k
    [ 1.091223] Freeing unused kernel memory: 1224k freed
    [ 1.092704] Freeing unused kernel memory: 440k freed
    [ 1.100348] systemd-udevd[79]: starting version 202
    [ 1.104141] device-mapper: uevent: version 1.0.3
    [ 1.104302] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: [email protected]
    [ 1.125733] ACPI: bus type usb registered
    [ 1.125784] usbcore: registered new interface driver usbfs
    [ 1.125818] usbcore: registered new interface driver hub
    [ 1.125883] usbcore: registered new device driver usb
    [ 1.126941] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    [ 1.127436] ehci-pci: EHCI PCI platform driver
    [ 1.127537] xhci_hcd 0000:04:00.0: xHCI Host Controller
    [ 1.127539] ehci-pci 0000:00:1a.0: setting latency timer to 64
    [ 1.127543] ehci-pci 0000:00:1a.0: EHCI Host Controller
    [ 1.127557] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
    [ 1.127567] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
    [ 1.127587] ehci-pci 0000:00:1a.0: debug port 2
    [ 1.127598] SCSI subsystem initialized
    [ 1.128985] ACPI: bus type scsi registered
    [ 1.129170] libata version 3.00 loaded.
    [ 1.131512] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
    [ 1.131535] ehci-pci 0000:00:1a.0: irq 16, io mem 0xdf008000
    [ 1.132114] xhci_hcd 0000:04:00.0: irq 45 for MSI/MSI-X
    [ 1.132121] xhci_hcd 0000:04:00.0: irq 46 for MSI/MSI-X
    [ 1.132127] xhci_hcd 0000:04:00.0: irq 47 for MSI/MSI-X
    [ 1.132133] xhci_hcd 0000:04:00.0: irq 48 for MSI/MSI-X
    [ 1.132138] xhci_hcd 0000:04:00.0: irq 49 for MSI/MSI-X
    [ 1.132143] xhci_hcd 0000:04:00.0: irq 50 for MSI/MSI-X
    [ 1.132149] xhci_hcd 0000:04:00.0: irq 51 for MSI/MSI-X
    [ 1.132154] xhci_hcd 0000:04:00.0: irq 52 for MSI/MSI-X
    [ 1.132484] xHCI xhci_add_endpoint called for root hub
    [ 1.132487] xHCI xhci_check_bandwidth called for root hub
    [ 1.132548] hub 2-0:1.0: USB hub found
    [ 1.132561] hub 2-0:1.0: 2 ports detected
    [ 1.132717] xhci_hcd 0000:04:00.0: xHCI Host Controller
    [ 1.132725] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 3
    [ 1.132884] xHCI xhci_add_endpoint called for root hub
    [ 1.132886] xHCI xhci_check_bandwidth called for root hub
    [ 1.132937] hub 3-0:1.0: USB hub found
    [ 1.132946] hub 3-0:1.0: 2 ports detected
    [ 1.138468] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
    [ 1.138852] hub 1-0:1.0: USB hub found
    [ 1.138856] hub 1-0:1.0: 2 ports detected
    [ 1.139004] ehci-pci 0000:00:1d.0: setting latency timer to 64
    [ 1.139008] ehci-pci 0000:00:1d.0: EHCI Host Controller
    [ 1.139013] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
    [ 1.139027] ehci-pci 0000:00:1d.0: debug port 2
    [ 1.142933] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
    [ 1.142950] ehci-pci 0000:00:1d.0: irq 23, io mem 0xdf007000
    [ 1.151785] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
    [ 1.152053] hub 4-0:1.0: USB hub found
    [ 1.152057] hub 4-0:1.0: 2 ports detected
    [ 1.152155] ahci 0000:00:1f.2: version 3.0
    [ 1.152226] ahci 0000:00:1f.2: irq 53 for MSI/MSI-X
    [ 1.165142] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x5 impl SATA mode
    [ 1.165152] ahci 0000:00:1f.2: flags: 64bit ncq sntf pm led clo pio slum part ems apst
    [ 1.165162] ahci 0000:00:1f.2: setting latency timer to 64
    [ 1.172449] scsi0 : ahci
    [ 1.172628] scsi1 : ahci
    [ 1.172789] scsi2 : ahci
    [ 1.172947] scsi3 : ahci
    [ 1.173104] scsi4 : ahci
    [ 1.173232] scsi5 : ahci
    [ 1.173279] ata1: SATA max UDMA/133 abar m2048@0xdf006000 port 0xdf006100 irq 53
    [ 1.173281] ata2: DUMMY
    [ 1.173284] ata3: SATA max UDMA/133 abar m2048@0xdf006000 port 0xdf006200 irq 53
    [ 1.173285] ata4: DUMMY
    [ 1.173287] ata5: DUMMY
    [ 1.173288] ata6: DUMMY
    [ 1.491471] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 1.491534] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [ 1.492344] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    [ 1.492383] ata3.00: ATA-9: OCZ-VERTEX4, 1.5, max UDMA/133
    [ 1.492386] ata3.00: 250069680 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 1.493193] ata3.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    [ 1.493231] ata3.00: configured for UDMA/133
    [ 1.493884] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    [ 1.493970] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    [ 1.494053] ata1.00: ACPI cmd ef/90:03:00:00:00:a0 (SET FEATURES) succeeded
    [ 1.494756] usb 2-2: new high-speed USB device number 2 using xhci_hcd
    [ 1.496558] ata1.00: ATA-8: WDC WD7500BPKT-80PK4T0, 01.01A01, max UDMA/133
    [ 1.496567] ata1.00: 1465149168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
    [ 1.499166] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
    [ 1.499312] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
    [ 1.499465] ata1.00: ACPI cmd ef/90:03:00:00:00:a0 (SET FEATURES) succeeded
    [ 1.501976] ata1.00: configured for UDMA/133
    [ 1.502207] scsi 0:0:0:0: Direct-Access ATA WDC WD7500BPKT-8 01.0 PQ: 0 ANSI: 5
    [ 1.502554] scsi 2:0:0:0: Direct-Access ATA OCZ-VERTEX4 1.5 PQ: 0 ANSI: 5
    [ 1.506105] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/698 GiB)
    [ 1.506109] sd 0:0:0:0: [sda] 4096-byte physical blocks
    [ 1.506148] sd 0:0:0:0: [sda] Write Protect is off
    [ 1.506151] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 1.506154] sd 2:0:0:0: [sdb] 250069680 512-byte logical blocks: (128 GB/119 GiB)
    [ 1.506169] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.506212] sd 2:0:0:0: [sdb] Write Protect is off
    [ 1.506216] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00
    [ 1.506243] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 1.506699] sdb: sdb1 sdb2
    [ 1.506982] sd 2:0:0:0: [sdb] Attached SCSI disk
    [ 1.515208] Initializing USB Mass Storage driver...
    [ 1.515403] scsi6 : usb-storage 2-2:1.0
    [ 1.515477] usbcore: registered new interface driver usb-storage
    [ 1.515479] USB Mass Storage support registered.
    [ 1.559813] sda: sda1 sda2 sda3 sda4
    [ 1.560554] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 1.568887] bio: create slab <bio-1> at 1
    [ 1.617994] usb 1-1: new high-speed USB device number 2 using ehci-pci
    [ 1.717847] tsc: Refined TSC clocksource calibration: 2195.013 MHz
    [ 1.717860] Switching to clocksource tsc
    [ 1.741822] hub 1-1:1.0: USB hub found
    [ 1.741901] hub 1-1:1.0: 6 ports detected
    [ 1.847695] usb 4-1: new high-speed USB device number 2 using ehci-pci
    [ 1.971554] hub 4-1:1.0: USB hub found
    [ 1.971646] hub 4-1:1.0: 6 ports detected
    [ 2.050951] usb 1-1.1: new full-speed USB device number 3 using ehci-pci
    [ 2.204028] usb 1-1.2: new high-speed USB device number 4 using ehci-pci
    [ 2.334884] PM: Starting manual resume from disk
    [ 2.334889] PM: Hibernation image partition 254:3 present
    [ 2.334890] PM: Looking for hibernation image.
    [ 2.335066] PM: Image not found (code -22)
    [ 2.335071] PM: Hibernation image not present or could not be loaded.
    [ 2.354107] EXT4-fs (dm-0): INFO: recovery required on readonly filesystem
    [ 2.354110] EXT4-fs (dm-0): write access will be enabled during recovery
    [ 2.359269] EXT4-fs (dm-0): recovery complete
    [ 2.360870] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    [ 2.433463] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset.
    [ 2.443949] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
    [ 2.447276] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
    [ 2.450612] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
    [ 2.453928] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
    [ 2.457242] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
    [ 2.460576] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
    [ 2.463921] systemd[1]: systemd 202 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
    [ 2.466588] systemd[1]: Set hostname to <laptop>.
    [ 2.468578] systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system.
    [ 2.468640] systemd[1]: Installed release agent.
    [ 2.470573] systemd[1]: Using notification socket @/org/freedesktop/systemd1/notify
    [ 2.470586] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
    [ 2.470700] systemd[1]: Successfully created private D-Bus server.
    [ 2.471882] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-fstab-generator as 176
    [ 2.471962] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-efi-boot-generator as 177
    [ 2.472047] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-system-update-generator as 178
    [ 2.472156] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-getty-generator as 179
    [ 2.472263] systemd[1]: Spawned /usr/lib/systemd/system-generators/systemd-cryptsetup-generator as 180
    [ 2.476365] systemd[1]: /usr/lib/systemd/system-generators/systemd-fstab-generator exited successfully.
    [ 2.476378] systemd[1]: /usr/lib/systemd/system-generators/systemd-efi-boot-generator exited successfully.
    [ 2.476385] systemd[1]: /usr/lib/systemd/system-generators/systemd-system-update-generator exited successfully.
    [ 2.476391] systemd[1]: /usr/lib/systemd/system-generators/systemd-getty-generator exited successfully.
    [ 2.476397] systemd[1]: /usr/lib/systemd/system-generators/systemd-cryptsetup-generator exited successfully.
    [ 2.476871] systemd[1]: Looking for unit files in (higher priority first):
    [ 2.476876] systemd[1]: /etc/systemd/system
    [ 2.476878] systemd[1]: /run/systemd/system
    [ 2.476880] systemd[1]: /run/systemd/generator
    [ 2.476882] systemd[1]: /usr/local/lib/systemd/system
    [ 2.476884] systemd[1]: /usr/lib/systemd/system
    [ 2.476887] systemd[1]: SysV init scripts and rcN.d links support disabled
    [ 2.493752] systemd[1]: Failed to load configuration for syslog.target: No such file or directory
    [ 2.495520] systemd[1]: Failed to load configuration for plymouth-quit.service: No such file or directory
    [ 2.496386] systemd[1]: Failed to load configuration for plymouth-quit-wait.service: No such file or directory
    [ 2.496999] systemd[1]: Failed to load configuration for plymouth-start.service: No such file or directory
    [ 2.504860] systemd[1]: Failed to load configuration for ypbind.service: No such file or directory
    [ 2.517488] systemd[1]: Failed to load configuration for syslog.service: No such file or directory
    [ 2.520082] scsi 6:0:0:0: Direct-Access 1.00 PQ: 0 ANSI: 4
    [ 2.520543] systemd[1]: Failed to load configuration for runlevel5.target: No such file or directory
    [ 2.520551] systemd[1]: Failed to load configuration for runlevel4.target: No such file or directory
    [ 2.520556] systemd[1]: Failed to load configuration for runlevel3.target: No such file or directory
    [ 2.520561] systemd[1]: Failed to load configuration for runlevel2.target: No such file or directory
    [ 2.520566] systemd[1]: Failed to load configuration for runlevel1.target: No such file or directory
    [ 2.520571] systemd[1]: Failed to load configuration for auditd.service: No such file or directory
    [ 2.521264] sd 6:0:0:0: [sdc] 30343168 512-byte logical blocks: (15.5 GB/14.4 GiB)
    [ 2.522318] sd 6:0:0:0: [sdc] Write Protect is off
    [ 2.522320] sd 6:0:0:0: [sdc] Mode Sense: 2f 00 00 00
    [ 2.523352] sd 6:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.523974] systemd[1]: -.mount changed dead -> mounted
    [ 2.524009] systemd[1]: Activating default unit: default.target
    [ 2.524016] systemd[1]: Trying to enqueue job graphical.target/start/isolate
    [ 2.524119] systemd[1]: Looking at job [email protected]/stop conflicted_by=yes
    [ 2.524122] systemd[1]: Looking at job [email protected]/start conflicted_by=no
    [ 2.524125] systemd[1]: Fixing conflicting jobs by deleting job [email protected]/start
    [ 2.524129] systemd[1]: Looking at job gdm.service/start conflicted_by=no
    [ 2.524132] systemd[1]: Looking at job gdm.service/stop conflicted_by=no
    [ 2.524134] systemd[1]: Fixing conflicting jobs by deleting job gdm.service/stop
    [ 2.524147] systemd[1]: Installed new job graphical.target/start as 1
    [ 2.524151] systemd[1]: Installed new job multi-user.target/start as 2
    [ 2.524155] systemd[1]: Installed new job basic.target/start as 3
    [ 2.524158] systemd[1]: Installed new job sysinit.target/start as 4
    [ 2.524162] systemd[1]: Installed new job local-fs.target/start as 5
    [ 2.524165] systemd[1]: Installed new job var-cache-fontconfig.automount/start as 6
    [ 2.524168] systemd[1]: Installed new job var.mount/start as 7
    [ 2.524171] systemd[1]: Installed new job systemd-fsck@dev-mapper-MainVolGroup\x2dvar.service/start as 8
    [ 2.524174] systemd[1]: Installed new job dev-mapper-MainVolGroup\x2dvar.device/start as 9
    [ 2.524183] systemd[1]: Installed new job mnt-hdd\x2dhome.automount/start as 12
    [ 2.524186] systemd[1]: Installed new job mnt-hdd\x2droot.automount/start as 13
    [ 2.524189] systemd[1]: Installed new job var.automount/start as 14
    [ 2.524192] systemd[1]: Installed new job boot.automount/start as 15
    [ 2.524195] systemd[1]: Installed new job home.automount/start as 16
    [ 2.524198] systemd[1]: Installed new job systemd-fsck-root.service/start as 17
    [ 2.524201] systemd[1]: Installed new job systemd-remount-fs.service/start as 18
    [ 2.524204] systemd[1]: Installed new job local-fs-pre.target/start as 19
    [ 2.524207] systemd[1]: Installed new job tmp.mount/start as 21
    [ 2.524210] systemd[1]: Installed new job swap.target/start as 22
    [ 2.524213] systemd[1]: Installed new job dev-mapper-MainVolGroup\x2dswap.swap/start as 23
    [ 2.524216] systemd[1]: Installed new job dev-mapper-MainVolGroup\x2dswap.device/start as 24
    [ 2.524222] systemd[1]: Installed new job debug-shell.service/start as 25
    [ 2.524225] systemd[1]: Installed new job systemd-tmpfiles-setup.service/start as 26
    [ 2.524228] systemd[1]: Installed new job systemd-journal-flush.service/start as 27
    [ 2.524231] systemd[1]: Installed new job systemd-journald.service/start as 28
    [ 2.524234] systemd[1]: Installed new job systemd-journald.socket/start as 29
    [ 2.524237] systemd[1]: Installed new job cryptsetup.target/start as 30
    [ 2.524240] systemd[1]: Installed new job systemd-vconsole-setup.service/start as 31
    [ 2.524243] systemd[1]: Installed new job systemd-static-nodes.service/start as 32
    [ 2.524245] systemd[1]: Installed new job systemd-modules-load.service/start as 33
    [ 2.524248] systemd[1]: Installed new job dev-mqueue.mount/start as 34
    [ 2.524251] systemd[1]: Installed new job systemd-ask-password-console.path/start as 35
    [ 2.524254] systemd[1]: Installed new job systemd-binfmt.service/start as 36
    [ 2.524257] systemd[1]: Installed new job sys-kernel-debug.mount/start as 37
    [ 2.524260] systemd[1]: Installed new job systemd-random-seed-load.service/start as 38
    [ 2.524263] systemd[1]: Installed new job systemd-udevd.service/start as 39
    [ 2.524266] systemd[1]: Installed new job systemd-udevd-control.socket/start as 40
    [ 2.524269] systemd[1]: Installed new job systemd-udevd-kernel.socket/start as 41
    [ 2.524272] systemd[1]: Installed new job dev-hugepages.mount/start as 42
    [ 2.524275] systemd[1]: Installed new job proc-sys-fs-binfmt_misc.automount/start as 43
    [ 2.524278] systemd[1]: Installed new job sys-kernel-config.mount/start as 44
    [ 2.524281] systemd[1]: Installed new job systemd-udev-trigger.service/start as 45
    [ 2.524283] systemd[1]: Installed new job systemd-sysctl.service/start as 46
    [ 2.524286] systemd[1]: Installed new job sys-fs-fuse-connections.mount/start as 47
    [ 2.524289] systemd[1]: Installed new job sockets.target/start as 50
    [ 2.524292] systemd[1]: Installed new job systemd-initctl.socket/start as 51
    [ 2.524295] systemd[1]: Installed new job systemd-shutdownd.socket/start as 52
    [ 2.524298] systemd[1]: Installed new job lvmetad.socket/start as 53
    [ 2.524301] systemd[1]: Installed new job dmeventd.socket/start as 54
    [ 2.524304] systemd[1]: Installed new job dbus.socket/start as 55
    [ 2.524307] systemd[1]: Installed new job timers.target/start as 56
    [ 2.524310] systemd[1]: Installed new job systemd-tmpfiles-clean.timer/start as 57
    [ 2.524313] systemd[1]: Installed new job paths.target/start as 58
    [ 2.524316] systemd[1]: Installed new job alsa-restore.service/start as 59
    [ 2.524319] systemd[1]: Installed new job alsa-state.service/start as 60
    [ 2.524322] systemd[1]: Installed new job NetworkManager.service/start as 61
    [ 2.524325] systemd[1]: Installed new job network.target/start as 62
    [ 2.524327] systemd[1]: Installed new job [email protected]/start as 63
    [ 2.524330] systemd[1]: Installed new job laptop-mode.service/start as 64
    [ 2.524333] systemd[1]: Installed new job ntpd.service/start as 65
    [ 2.524336] systemd[1]: Installed new job postfix.service/start as 66
    [ 2.524339] systemd[1]: Installed new job autofs.service/start as 67
    [ 2.524342] systemd[1]: Installed new job psd.service/start as 68
    [ 2.524345] systemd[1]: Installed new job cronie.service/start as 69
    [ 2.524347] systemd[1]: Installed new job hddtemp.service/start as 70
    [ 2.524350] systemd[1]: Installed new job remote-fs.target/start as 71
    [ 2.524353] systemd[1]: Installed new job sshd.service/start as 72
    [ 2.524356] systemd[1]: Installed new job sshdgenkeys.service/start as 73
    [ 2.524359] systemd[1]: Installed new job systemd-user-sessions.service/start as 74
    [ 2.524362] systemd[1]: Installed new job getty.target/start as 75
    [ 2.524364] systemd[1]: Installed new job gdm.service/start as 83
    [ 2.524367] systemd[1]: Installed new job systemd-logind.service/start as 78
    [ 2.524370] systemd[1]: Installed new job dbus.service/start as 79
    [ 2.524373] systemd[1]: Installed new job systemd-ask-password-wall.path/start as 80
    [ 2.524376] systemd[1]: Installed new job bumblebeed.service/start as 86
    [ 2.524381] systemd[1]: Enqueued job graphical.target/start as 1
    [ 2.524388] systemd[1]: Loaded units and determined initial transaction in 53.717ms.
    [ 2.524451] systemd[1]: Got SIGCHLD for process 175 (switch_root)
    [ 2.524487] systemd[1]: Child 175 died (code=exited, status=0/SUCCESS)
    [ 2.524506] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
    [ 2.524557] systemd[1]: systemd-ask-password-wall.path changed dead -> waiting
    [ 2.524562] systemd[1]: Job systemd-ask-password-wall.path/start finished, result=done
    [ 2.524570] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
    [ 2.524581] systemd[1]: Starting Login Prompts.
    [ 2.524584] systemd[1]: getty.target changed dead -> active
    [ 2.524587] systemd[1]: Job getty.target/start finished, result=done
    [ 2.525191] systemd[1]: Reached target Login Prompts.
    [ 2.525200] systemd[1]: Starting Remote File Systems.
    [ 2.525203] systemd[1]: remote-fs.target changed dead -> active
    [ 2.525207] systemd[1]: Job remote-fs.target/start finished, result=done
    [ 2.525847] systemd[1]: Reached target Remote File Systems.
    [ 2.525857] systemd[1]: Starting Device-mapper event daemon FIFOs.
    [ 2.525880] systemd[1]: dmeventd.socket changed dead -> listening
    [ 2.525884] systemd[1]: Job dmeventd.socket/start finished, result=done
    [ 2.526631] systemd[1]: Listening on Device-mapper event daemon FIFOs.
    [ 2.526640] systemd[1]: Starting LVM2 metadata daemon socket.
    [ 2.526658] systemd[1]: lvmetad.socket changed dead -> listening
    [ 2.526662] systemd[1]: Job lvmetad.socket/start finished, result=done
    [ 2.527368] systemd[1]: Listening on LVM2 metadata daemon socket.
    [ 2.527377] systemd[1]: Starting Delayed Shutdown Socket.
    [ 2.527392] systemd[1]: systemd-shutdownd.socket changed dead -> listening
    [ 2.527396] systemd[1]: Job systemd-shutdownd.socket/start finished, result=done
    [ 2.527773] sdc: sdc1
    [ 2.528062] systemd[1]: Listening on Delayed Shutdown Socket.
    [ 2.528071] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
    [ 2.528085] systemd[1]: systemd-initctl.socket changed dead -> listening
    [ 2.528089] systemd[1]: Job systemd-initctl.socket/start finished, result=done
    [ 2.528886] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
    [ 2.528913] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
    [ 2.528928] systemd[1]: Autofs kernel version 1.0
    [ 2.528999] systemd[1]: Autofs protocol version 5.2
    [ 2.529006] systemd[1]: proc-sys-fs-binfmt_misc.automount changed dead -> waiting
    [ 2.529010] systemd[1]: Job proc-sys-fs-binfmt_misc.automount/start finished, result=done
    [ 2.530088] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
    [ 2.530148] systemd[1]: Starting udev Kernel Socket.
    [ 2.530162] systemd[1]: systemd-udevd-kernel.socket changed dead -> listening
    [ 2.530166] systemd[1]: Job systemd-udevd-kernel.socket/start finished, result=done
    [ 2.530792] systemd[1]: Listening on udev Kernel Socket.
    [ 2.530842] systemd[1]: Starting udev Control Socket.
    [ 2.530861] systemd[1]: systemd-udevd-control.socket changed dead -> listening
    [ 2.530865] systemd[1]: Job systemd-udevd-control.socket/start finished, result=done
    [ 2.531232] sd 6:0:0:0: [sdc] Attached SCSI removable disk
    [ 2.531491] systemd[1]: Listening on udev Control Socket.
    [ 2.531505] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
    [ 2.531537] systemd[1]: systemd-ask-password-console.path changed dead -> waiting
    [ 2.531542] systemd[1]: Job systemd-ask-password-console.path/start finished, result=done
    [ 2.531548] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
    [ 2.531556] systemd[1]: Starting Paths.
    [ 2.531559] systemd[1]: paths.target changed dead -> active
    [ 2.531562] systemd[1]: Job paths.target/start finished, result=done
    [ 2.532064] systemd[1]: Reached target Paths.
    [ 2.532073] systemd[1]: Starting Encrypted Volumes.
    [ 2.532076] systemd[1]: cryptsetup.target changed dead -> active
    [ 2.532079] systemd[1]: Job cryptsetup.target/start finished, result=done
    [ 2.532698] systemd[1]: Reached target Encrypted Volumes.
    [ 2.532708] systemd[1]: Starting Journal Socket.
    [ 2.532744] systemd[1]: systemd-journald.socket changed dead -> listening
    [ 2.532748] systemd[1]: Job systemd-journald.socket/start finished, result=done
    [ 2.533319] systemd[1]: Listening on Journal Socket.
    [ 2.533332] systemd[1]: Starting Setup Virtual Console...
    [ 2.533931] systemd[1]: About to execute: /usr/lib/systemd/systemd-vconsole-setup
    [ 2.534187] systemd[1]: Forked /usr/lib/systemd/systemd-vconsole-setup as 184
    [ 2.547297] systemd[1]: systemd-vconsole-setup.service changed dead -> start
    [ 2.547302] systemd[184]: Executing: /usr/lib/systemd/systemd-vconsole-setup
    [ 2.547373] systemd[1]: Starting Create static device nodes in /dev...
    [ 2.548118] systemd[1]: About to execute: /usr/bin/systemd-tmpfiles --prefix=/dev --create
    [ 2.548361] systemd[1]: Forked /usr/bin/systemd-tmpfiles as 185
    [ 2.560348] systemd[185]: Executing: /usr/bin/systemd-tmpfiles --prefix=/dev --create
    [ 2.560365] systemd[1]: systemd-static-nodes.service changed dead -> start
    [ 2.562192] systemd[1]: Starting Load Kernel Modules...
    [ 2.562760] systemd[1]: About to execute: /usr/lib/systemd/systemd-modules-load
    [ 2.562937] systemd[1]: Forked /usr/lib/systemd/systemd-modules-load as 190
    [ 2.563964] systemd[190]: Executing: /usr/lib/systemd/systemd-modules-load
    [ 2.563973] systemd[1]: systemd-modules-load.service changed dead -> start
    [ 2.564002] systemd[1]: Mounting POSIX Message Queue File System...
    [ 2.564818] systemd[1]: About to execute: /bin/mount mqueue /dev/mqueue -t mqueue
    [ 2.565013] systemd[1]: Forked /bin/mount as 191
    [ 2.570344] systemd[1]: dev-mqueue.mount changed dead -> mounting
    [ 2.570404] systemd[191]: Executing: /bin/mount mqueue /dev/mqueue -t mqueue
    [ 2.571513] systemd[1]: Starting of systemd-binfmt.service requested but condition failed. Ignoring.
    [ 2.571519] systemd[1]: Job systemd-binfmt.service/start finished, result=done
    [ 2.571532] systemd[1]: Started Set Up Additional Binary Formats.
    [ 2.571556] systemd[1]: Mounting Debug File System...
    [ 2.572101] systemd[1]: About to execute: /bin/mount debugfs /sys/kernel/debug -t debugfs
    [ 2.572284] systemd[1]: Forked /bin/mount as 192
    [ 2.573859] systemd[1]: sys-kernel-debug.mount changed dead -> mounting
    [ 2.573900] systemd[1]: Mounting Huge Pages File System...
    [ 2.573939] systemd[192]: Ex

  • Need help with LVM and Virtual Machine Manager

    Hello,i want to know if there is any way to install LVM (Logical Volume Management) manually and separately on Linux operating system as when i initially installed RedHat Enterprise Linux 6,i mistakenly did not select the application LVM itself.
    Another issue i have not been able to fix is the Virtual Machine Manager.i have tried to connect but it keeps showing me the following error message on RedHat Enterprise Enterprise Linux 6.
    Error Message from Virtual Machine Manager :
    Unable to open a connection to the libvirt management daemon.
    Libvirt URI is: qemu:///system
    Verify that The 'libvirtd' daemon has been started
    any advices,please feel free to let me know.thank you.

    I want to know if there is any way to install LVM (Logical Volume Management) manually and separately on Linux operating system as when i initially installed RedHat Enterprise Linux 6,i mistakenly did not select the application LVM itself.You can install the tools like this:
    # yum install -y lvm2Although you can use the tools to construct new LVM devices and partitoins, you can't change your existing partitions into LVM.
    Another issue i have not been able to fix is the Virtual Machine Manager. I have tried to connect but it keeps showing me the following error message on RedHat Enterprise Enterprise Linux 6:
    Error Message from Virtual Machine Manager :
    Unable to open a connection to the libvirt management daemon.
    Libvirt URI is: qemu:///system
    Verify that The 'libvirtd' daemon has been startedOn your physical host, do this:
    # /sbin/chkconfig libvirtd on
    # /sbin/service libvirtd startThis will start the virtualization tools.

  • [SOLVED] mkinicpio's systemd hook, LUKS, LVM and resume

    I had a working LUKS/LVM/resume using the following HOOKS and kernel parameters:
    # /etc/mkinitcpio.conf
    HOOKS="base udev autodetect modconf block keymap encrypt lvm2 btrfs resume filesystems keyboard"
    # /boot/loader/entries/arch.conf
    options cryptodevice=PARTUUID=28230c39-5262-4778-b12a-b5eda11831d0:lvm resume=/dev/mapper/vol0-lv_swap root=/dev/mapper/vol0-lv_root rw
    Since systemd 217 is supposed to support hiberation, I am trying to setup a pure systemd initrd image. So I changed my mkinitcpio.conf and arch.conf files to the following:
    # /etc/mkinitcpio.conf
    HOOKS="systemd autodetect modconf block keymap sd-encrypt sd-lvm2 btrfs filesystems keyboard"
    # /boot/loader/entries/arch.conf
    options rd.luks.uuid=176a3eb9-90c3-49c7-a0b5-697860d21068 resume=UUID=b89c478e-a1ff-4332-a11b-ceebc3b08de8 root=UUID=e180cd3e-d4c4-4e0a-9426-0f7e460a7303 rw
    The change in boot entry is done as suggested in this topic, since using cryptodevice doesn't seem to work. I only changed the resume/root to UUID since this seems to be the right way to do things (UUID is not supposed to change, while labels may change).
    And the system boots, but resume doesn't work (tried to run "systemctl hibernate" from terminal, the system hibernates but never resumes). I removed the resume hook since it doesn't seem to be necessary with systemd hook. Even if I put it again it doesn't work (it tries to run the resume hook, I can see the logs during the boot, but nothing changes). I think this is a problem in the root entry or resume entry in my boot parameters (maybe both), probably I need to change for some other think but I didn't find anything searching in Google.
    Maybe someone with a Fedora setup may help? The suggestion to use rd.luks.uuid instead of cryptsetup seems to come from there.
    Last edited by m45t3r (2014-11-29 22:30:13)

    I know this may seem like I am reviving an old topic, but recently I bought a SSD and tried to replicate my setup, including supporting for TRIM. While it's easy to do it's not something trivial since it's not really well docummented.
    You will need three things:
    A filesystem that supports discard (I am using XFS).
    In /etc/lvm/lvm.conf, enable issue_discards option.
    Lastly, add rd.luks.options=discard in your kernel boot options
    To test if everything is working as it should, just do:
    # fstrim /
    And if everything is working it should return 0, or a error message in case of error.
    Hope this help someone.

  • LVM and eee

    I tried to install archlinux over a LVM in a eee. Using the default disc and a sd memory.
    Before the installation i created the partition and the logical volumes. according to  http://wiki.archlinux.org/index.php/LVM2
    In the mkinitcpio.conf 's modules part i put sdhci, mmc_block and in the hook's part  the full usb drivers, the lvm2 and the filesystem
    In the rc.conf i change the LVM option to YES
    but when is booting
    ERROR: failed to parse block device name for '/dev/mapper/vo1-voldatos' unknown
    ERROR: unable to create/detect root device '/dev/mapper/vol1-voldatos'
    Then a emergency shell appears.
    Grub configuration is ok. It has the root setting with the logical volume
    The system can see the devices correctly.
    What could be the problem?
    Last edited by lucianolorenti (2009-04-19 01:37:22)

    The problem is that the kernel tries to activate the LVM root partition before creates the device of the USB CardReader. So of Course when the booting process executes lvscan and lvchange -ay , it's impossible to find that devices
    There is a way to make lvm2 hook wait until all the storage devices were loaded?

  • Large ext4 vs. LVM and several ext3

    I am getting a new laptop with a 500GB hard-drive and am deciding how to partition it.  It will only have Arch on it so there is no need for many partitions.  Here is my current plan:
    "The usual"
    100MB /boot  (ext2)
    10GB /  (ext3)
    8GB swap
    With the rest, I could go for a single ext4 or LVM with several ext3.  A single ext3 would take forever for fsck so is not really an option.  I'm thinking the single ext4 would just be easier and I am a lazy person...   
    Any opinions on those two options?   (and only those two. I do not want to know about other FS types).

    Yes, a single ext4 would be /home.  I guess the decision points are:
    1) is ext4 stable enough (probably yes...)
    2) would I even need other partitions (probably no - I use qemu to test other distros etc).
    So I suppose ext4 is the best idea.  I was just checking other opinions...
    foutrelis wrote:Which laptop are you getting by the way?
    It is being bought through work so I am basically stuck with Dell (the other options are not any better...):
    Dell Studio XPS 13
    Intel Core2Duo P9600  (2.66GHz/ 1066 FSB/ 6MB Cache)
    6GB (1x4GB/1x2GB) 1066MHz DDR3 SDRAM
    500GB 7200RPM SATA Hard Drive
    NVIDIA® GeForce® 210M – 512MB
    Should be good enough to check emails.   

  • LVM and Linux

    I have medium sized 9i warehouse (750GB). I have read Bert Scalzo's article on OTN about "Linux Maximus Part 2: The RAW Facts on File Systems". He suggests that using LVM with Linux over hardware RAID provides better performance. I have a Dell server with a 14 disk array attached. Can I set LVM up on such a configuration?
    Thank you,
    Michael

    Excerpts prior thread,
    "Prior to starting the migrated VM you will have to update "grub.conf" and "device.map". I also find it useful to clear out the "blkid.tab" cache. Rebuilding "initrd" is also recommended."
    P2V
    "If the legacy system uses LVM for block devices then "ssh | tar" method will migrate to simple filesystem. There is no need for LVM on a VM."

  • LVM and EBS R 12

    hi
    is there any issue arise if we use LVM on DB tier as partion and apps tier on IBM peoduction server and RHEL5.3 ?
    DB 10.2.0.2.0
    APPS EBS R12 RUP 6.
    rgrds

    Hi You;
    I found one note, its not recomended, please check below
    http://download.oracle.com/docs/cd/B28359_01/server.111/b31107.pdf
    Its mention there:
    *Raw logical volumes (LVM)—LVMs are supported in less complicated configurations where an LVM is mapped to a LUN, or an LVM uses disks or raw
    partitions. LVM configurations are not recommended by Oracle because they create a duplication of functionality. Oracle also does not recommended using
    LVMs for mirroring because ASM already provides mirroring.*
    But there are some note too:
    HOWTO Understand And Use The Logical Volume Manager (LVM) On Linux [ID 858497.1]
    Setting up ASM on linux wiht LVM [ID 292348.1]
    I belive its best way to confirm it wiht oracle support
    Regard
    Helios

  • Installation with LVM and gpg-encrypted key, what to tell Grub

    Hi,
    after years of using Gentoo Linux I grew tired of the compilation effort, so I decided to give Arch Linux a shot. I like the idea of a basic system which I can fit to my needs instead of a bloated distribution.
    I want to encrypt my disk and did this with the following tutorials:
    Official Arch Linux Install Guide
    DM Crypt with LUKS
    Basic Cryptsetup
    Gentoo DM-Crypt with LUKS
    So far, the installation worked well, but I'm stuck with this problem:
    I have a gpg encrypted key stored on a SD-Card.
    My mkinitcpio.conf has the hook line:
    HOOKS="base udev autodetect pata scsi sata mmc usbinput fsck keymap encrypt lvm2 filesystems
    /etc/default/grub contains:
    GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda6:vg root=/dev-mapper/vg-root ro cryptkey=/dev/mmcblk0p1:jfs:/Key.gpg"
    However, if I am booting, there are the following outputs:
    No key available with this passphrase.
    Invalid keyfile. Reverting to passphrase.
    A password is required to access the vg volume:
    Enter passphrase for /dev/sda6:
    So, obviously, he isn't able to gpg-decrypt the key, or am I missing something?
    I do really need some help at this point.

    On my gentoo installation, I had to tell cryptsetup to use the decrypted key as password for the new key. In fact
    gpg -q -d <GPG-Keyfile> | cryptsetup luksOpen /dev/<encryptedPartition> <cryptContainer>
    did exactly what I wanted.
    I wanted to have my system highly secured, so a password-protected keyfile on an extern medium was the best choice.
    Edit: There has been another tutorial: System encryption with gpg encrypted keys, but it's out of date.
    Last edited by iarumas (2012-12-05 22:50:34)

  • [SOLVED] system not booting with LVM root and systemd

    hi everyone ,
    I've update my arch installation and performed the upgrade to systemd , and after that the system is not booting , it brings me to a recovery shell .
    the root FS is on LVM , and everything under /dev/mapper is missing .
    journalctl -xb -p err show me this error :
    -- Logs begin at Tue 2013-05-28 21:14:18 CEST, end at Tue 2013-07-23 19:29:38 CEST. --
    Jul 23 19:29:35 elminster systemd[1]: Timed out waiting for device dev-mapper-VolGroup00\x2dhome.device.
    -- Subject: Unit dev-mapper-VolGroup00\x2dhome.device has failed
    -- Defined-By: systemd
    -- Unit dev-mapper-VolGroup00\x2dhome.device has failed.
    -- The result is timeout.
    Jul 23 19:29:35 elminster systemd[1]: Dependency failed for /home.
    -- Subject: Unit home.mount has failed
    -- Defined-By: systemd
    -- Unit home.mount has failed.
    -- The result is dependency.
    Jul 23 19:29:35 elminster systemd[1]: Dependency failed for Local File Systems.
    -- Subject: Unit local-fs.target has failed
    -- Defined-By: systemd
    -- Unit local-fs.target has failed.
    -- The result is dependency.
    Jul 23 19:29:35 elminster systemd[1]: Dependency failed for /home/andrea/DropBox.
    -- Subject: Unit home-andrea-DropBox.mount has failed
    -- Defined-By: systemd
    -- Unit home-andrea-DropBox.mount has failed.
    -- The result is dependency.
    Jul 23 19:29:35 elminster systemd[1]: Dependency failed for File System Check on /dev/mapper/VolGroup00-home.
    -- Subject: Unit systemd-fsck@dev-mapper-VolGroup00\x2dhome.service has failed
    -- Defined-By: systemd
    -- Unit systemd-fsck@dev-mapper-VolGroup00\x2dhome.service has failed.
    -- The result is dependency.
    Jul 23 19:29:35 elminster systemd[298]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
    -- Subject: Process /bin/plymouth could not be executed
    -- Defined-By: systemd
    -- The process /bin/plymouth could not be executed and failed.
    -- The error number returned while executing this process is 2.
    here the relevant section of the /etc/fstab
    /dev/mapper/VolGroup00-arch_i686_root / ext4 defaults,noatime,nodiratime 0 1
    /dev/mapper/VolGroup00-home /home ext4 defaults,noatime,nodiratime 0 2
    /dev/sda1 /boot ext4 defaults 0 1
    /dev/mapper/VolGroup00-Store /media/store ext4 defaults,noatime,nodiratime 0 2
    /dev/mapper/VolGroup00-migration /media/migration ext4 defaults,noatime,nodiratime,noauto 0 2
    /dev/mapper/VolGroup00-DropBox /home/andrea/DropBox ext4 rw,noatime,nodiratime 0 0
    /dev/mapper/VolGroup00-virtualbox--machines /media/store/virtualbox ext3 rw 0 0
    /dev/mapper/VolGroup00-backup /media/backup ext3 rw,relatime,data=ordered 0 0
    lvm services are enabled on systemd , but under /dev/mapper i find only  /dev/mapper/control , all the other files are missing  (list from another install)
    ls -l /dev/mapper/*
    crw------- 1 root root 10, 236 Jul 23 20:19 /dev/mapper/control
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-arch_i686_root -> ../dm-3
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-debian_root -> ../dm-6
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-DropBox -> ../dm-2
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-home -> ../dm-0
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-Store -> ../dm-1
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-ubuntu1204 -> ../dm-5
    lrwxrwxrwx 1 root root 7 Jul 23 20:19 /dev/mapper/VolGroup00-virtualbox--machines -> ../dm-4
    tried also vgchange -ay from recover shell but still no luck
    any clue ?
    Last edited by andreagrax (2013-07-26 19:46:12)

    andreagrax wrote:lvm services are enabled on systemd
    Which?
    tried also vgchange -ay from recover shell but still no luck
    Did you do vgscan first? What error did you get or did the command just return empty?
    Is the lvm2 hook in mkinitcpio.conf? Have you tried regenerating your initramfs?

  • [SOLVED] Grub2 and LVM -- "Couldn't find physical volume `pv1'"

    Hello Folks
    I'm trying to upgrade from grub-legacy to grub2, following the instructions at https://wiki.archlinux.org/index.php/GRUB2
    I've installed grub-bios, and run this without problem:
    # modprobe dm-mod
    # grub-install --recheck /dev/sda
    But this command
    # grub-mkconfig -o /boot/grub/grub.cfg
    gives this:
    Generating grub.cfg ...
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
    /usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
    done
    So now I'm reluctant to try to reboot the system because it seems likely to be broken.  Should I ignore the warnings, or fix something?
    I'm using LVM2 as you can see.  /boot is on a separate non-LVM partition (/dev/sdc1).  root is on LVM.  This is all on a recently-updated 64-bit Arch installation using systemd.
    Here's a load of information -- I hope it's relevant.
    # fdisk -lu
    Disk /dev/sdb: 250.1 GB, 250059350016 bytes, 488397168 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: 0xea22bb30
    Device Boot Start End Blocks Id System
    /dev/sdb1 63 488392064 244196001 83 Linux
    Disk /dev/sda: 250.0 GB, 250000000000 bytes, 488281250 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: 0x00000080
    Device Boot Start End Blocks Id System
    /dev/sda1 2048 488281249 244139601 8e Linux LVM
    Disk /dev/sdc: 500.1 GB, 500107862016 bytes, 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/sdc1 * 63 481949 240943+ 83 Linux
    /dev/sdc2 481950 12482504 6000277+ 82 Linux swap / Solaris
    /dev/sdc3 12482505 976773167 482145331+ 8e Linux LVM
    Disk /dev/mapper/vg1-root: 64.4 GB, 64424509440 bytes, 125829120 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 /dev/mapper/vg1-home: 583.0 GB, 583008256000 bytes, 1138688000 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
    # pvdisplay
    --- Physical volume ---
    PV Name /dev/sdc3
    VG Name vg1
    PV Size 459.81 GiB / not usable 1.05 MiB
    Allocatable yes (but full)
    PE Size 4.00 MiB
    Total PE 117711
    Free PE 0
    Allocated PE 117711
    PV UUID zaLJiO-1LCH-TGi6-hwBr-OyNs-Sjlm-HggrMo
    --- Physical volume ---
    PV Name /dev/sda1
    VG Name vg1
    PV Size 232.83 GiB / not usable 1.58 MiB
    Allocatable yes
    PE Size 4.00 MiB
    Total PE 59604
    Free PE 22955
    Allocated PE 36649
    PV UUID P05c2d-1d2i-bf0M-u6BX-EEq0-fvZW-VkTLhY
    # lvdisplay
    --- Logical volume ---
    LV Path /dev/vg1/root
    LV Name root
    VG Name vg1
    LV UUID Z68H3p-VvbC-ZNau-7Ds7-GptS-Hpl0-VZNjo4
    LV Write Access read/write
    LV Creation host, time ,
    LV Status available
    # open 1
    LV Size 60.00 GiB
    Current LE 15360
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:0
    --- Logical volume ---
    LV Path /dev/vg1/home
    LV Name home
    VG Name vg1
    LV UUID uUfmS9-C4CK-Vw3V-cmwD-hEC1-VcwD-90yAyO
    LV Write Access read/write
    LV Creation host, time ,
    LV Status available
    # open 1
    LV Size 542.97 GiB
    Current LE 139000
    Segments 2
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:1
    Last edited by Chris Dennis (2013-04-03 19:04:58)

    Chris Dennis wrote:
    Oh well, I took a punt on the word 'Warning' in the message, and rebooted anyway.
    It worked!
    I've just completed a series of experiments involving LVM and GRUB2. The short story is that such warnings are innocuous and arise from extending a volume group.
    Now in some detail, here's what happens (all of which was performed in VirtualBox with the current Arch rolling release just to make it easy to add and remove disk devices):
    a). pvcreate /dev/sde1 /dev/sdf1
    * Use partitions of type 8e, spanning the whole drive, for BOTH devices comprising the physical
    volume to prove that partitioning is irrelevant to the matter.
    b). vgcreate vg_x /dev/sde1
    * Start with just one device in the volume group.
    c). lvcreate --extents 100%VG --name boot vg_x
    d). mkfs.ext4 /dev/vg_x/boot && mount /dev/vg_x/boot /mnt/other
    e). grub2-install --boot-directory=/mnt/other /dev/sde
    Installation finished. No error reported.
    All is well...but now let's extend the vg_x volume group with the pre-allocated device, /dev/sdf1:
    f). vgextend vg_x /dev/sdf1
    g). grub2-install --boot-directory=/mnt/other /dev/sde
    /usr/sbin/grub2-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core
    /usr/sbin/grub2-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core
    Installation finished. No error reported.
    ...and boom goes the dynamite. As Chris Dennis stated, GRUB2 installs fine and the system is bootable in spite of the warning. The grub-2.00 source where the warning arises is in ./grub-core/disk/diskfilter.c and has this comment:
    /* TRANSLATORS: This message kicks in during the detection of
    which modules needs to be included in core image. This happens
    in the case of degraded RAID and means that autodetection may
    fail to include some of modules. It's an installation time
    message, not runtime message. */
    I haven't tried to hack the GRUB code but, based upon my experimentation and the ease of replicating the problem, my guess is that somehow a volume group that extended in manner shown above is mishandled by GRUB. It's arguably a bug, IMHO, since a volume group, even when extended, is still a valid entity.

  • How I tried fix my partitions and restore a Dell Diagnostic Partition.

    UPDATED: 2 September 2012
    UPDATE: Now that I reflect back on the incidence, I realize that the Dell Utility partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partitions after fixing the partition table. But as I have already written this long post, lets just keep it here for future reference of anyone else stumbling across a similar problem. Read on to know about my experience.
    RECOMMENDATION: I do not recommend trying out all the steps below as they did not completely solve the problem for me. If you need the Diagnostic Utility, download the update package from Dell's support website for your model. This package can be used to create a boot-able USB drive and/or CD/DVD. These work fine and are pretty fast also.
    Something strange happened to me and I am now reporting my experience in trying to solve it (somewhat unsuccessfully!!)
    First of all, my setup is: Dell Studio 1555 laptop. I dual boot Windows 7 and Archlinux. So here's how it went:
    After using the partitioning tool Gparted under Archlinux to resize a partition, I found a problem had occurred. The Partition was NTFS formatted and all of my data files were stored on it. The partition worked fine under Archlinux as I was able to access my files fine under it. But in Windows, although the partition was listed under Windows explorer, it wanted to format it!! When I tried to access the partition it gave an error that it was not formatted (
    The drive is not formatted, do you want to format it now?
    ). Of course, that was not right and Gparted had messed something up. I fixed that using Testdisk under Archlinux (See the Details). So now the partition problem under windows was fixed. But now another problem cropped up under Archlinux. When I booted into Archlinux and started Gparted to confirm everything was fine I saw something strange in Gparted. The whole space on my hard disk was marked as "unallocated" under Gparted. Windows and Archlinux could "see" the partitions. By this I mean that I was able to boot fine under both my OSes. And I could access all my files under all my partitions. But somehow Gparted was not able to "see" them. Gparted was reporting my whole disk to be marked as unallocated. After that I researched a lot and lots of stuff happened experimenting to fix the problem. I used a lot of utilities. But actually only one fixed the problem-fixparts from the gptfdisk package. But it seemed like a lot of work trying to get the problem fixed (See the Details).
    Now we get to the point in discussion. I was able to get my partitions back under Gparted. But I lost the Dell Diagnostics Utility partition's ability to boot up. [Actually, now that I reflect back on the incidence, I realize that the Dell Utility partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partition after fixing the partition table. But more on this later.] It gave an error that the partition was not found.
    So, in short: After all this restoring partitions' visibility under Gparted, I realized that the Dell Utility partition on my Studio 1555 was not booting up. To explain this, it means that when I press F-12 when starting the laptop and select Diagnostics from the menu to run the Diagnostic Utility and after running the Pre-boot System Assesment tests when I consented to boot the Diagnostic Utility partition, it gave me the error that the partition was not found. When I tried to run the "Dell 32 Bit Diagnostics (Graphical User Interface version)" update package under Windows, it resulted in a similar error: Partition not found.
    For some background on what makes the Dell Utility partition so special, please read this thread and the third post on this thread.
    WARNING: You and only you are responsible for your data. Please make a backup before performing any of the partitioning steps below.
    NOTE: Please read the entire post before actually performing the steps.
    So, to try and fix this I did the following:
    Boot into Windows 7.
    Open Disk Management under the Computer Management console (To open the Computer Management console, right click on Computer in the Start menu and select Manage).
    Reformat the Dell Diagnostic Utility partition as FAT(not FAT32). This is the first partition on the drive (marked as Healthy (OEM Partition) under the Status column). [This step may not be required, however I had done it. See Notes below.]
    UPDATE: After reading around a bit I found that these steps to format the partition might not actually be necessary. Simply changing the type of the partition (as detailed below) might also work. However as I had done that, lets just keep these steps over here.
    Reboot into a Linux distribution Live CD (I had Ubuntu 10.10). Or, If you dual boot with a Linux distribution that does not complain about the now inconsistent fstab entry, you can also boot into that distribution directly. I had to boot into Live CD to fix my /etc/fstab.
    UPDATE: After considering all the aspects from start to end I have come to a conclusion regarding the efficacy of this method on dual boot machines with Windows and Linux installed. I doubt anyone with a dual boot Windows/Linux setup would be able to boot into the Dell Diagnostic Utility even with the Utility Partition restored. This is detailed below.
    (As noted above my Archlinux install did not boot up after I had reformatted  my Dell Diagnostic Utility partition. This is because I was mounting the Dell Utility partition at boot using fstab inside Archlinux. And I was using the UUID to mount the partition. After reformatting the partition its UUID changed. So, it wouldn't mount. And because of how my fstab was setup Archlinux won't boot. So, I had to boot into a live environment to fix this. This step applied only to me. YRMV.) Fix the fstab entry.
    (This step also applied to me.) Boot into the repaired Linux Distribution.
    And open a Terminal.
    In the open terminal run fdisk on your drive, e.g.,
    fdisk /dev/sda
    This is how it looks:
    [abhishek@Nitaichand ~]$ sudo fdisk /dev/sda
    Password:
    Command (m for help):
    To change the partition type give the appropriate command, i.e.,
    Command (m for help): t
    Specify the partition, i.e.,
    Partition number (1-10): 1
    Type L to see available codes:
    Hex code (type L to list codes):L
    0 Empty 24 NEC DOS 81 Minix / old Lin bf Solaris
    1 FAT12 27 Hidden NTFS Win 82 Linux swap / So c1 DRDOS/sec (FAT-
    2 XENIX root 39 Plan 9 83 Linux c4 DRDOS/sec (FAT-
    3 XENIX usr 3c PartitionMagic 84 OS/2 hidden C: c6 DRDOS/sec (FAT-
    4 FAT16 <32M 40 Venix 80286 85 Linux extended c7 Syrinx
    5 Extended 41 PPC PReP Boot 86 NTFS volume set da Non-FS data
    6 FAT16 42 SFS 87 NTFS volume set db CP/M / CTOS / .
    7 HPFS/NTFS/exFAT 4d QNX4.x 88 Linux plaintext de Dell Utility
    8 AIX 4e QNX4.x 2nd part 8e Linux LVM df BootIt
    9 AIX bootable 4f QNX4.x 3rd part 93 Amoeba e1 DOS access
    a OS/2 Boot Manag 50 OnTrack DM 94 Amoeba BBT e3 DOS R/O
    b W95 FAT32 51 OnTrack DM6 Aux 9f BSD/OS e4 SpeedStor
    c W95 FAT32 (LBA) 52 CP/M a0 IBM Thinkpad hi eb BeOS fs
    e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a5 FreeBSD ee GPT
    f W95 Ext'd (LBA) 54 OnTrackDM6 a6 OpenBSD ef EFI (FAT-12/16/
    10 OPUS 55 EZ-Drive a7 NeXTSTEP f0 Linux/PA-RISC b
    11 Hidden FAT12 56 Golden Bow a8 Darwin UFS f1 SpeedStor
    12 Compaq diagnost 5c Priam Edisk a9 NetBSD f4 SpeedStor
    14 Hidden FAT16 <3 61 SpeedStor ab Darwin boot f2 DOS secondary
    16 Hidden FAT16 63 GNU HURD or Sys af HFS / HFS+ fb VMware VMFS
    17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fc VMware VMKCORE
    18 AST SmartSleep 65 Novell Netware b8 BSDI swap fd Linux raid auto
    1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid fe LANstep
    1c Hidden W95 FAT3 75 PC/IX be Solaris boot ff BBT
    1e Hidden W95 FAT1 80 Old Minix
    Type the desired code, i.e.,
    Hex code (type L to list codes): de
    Write the partition table with:
    Command (m for help): w
    The partition table has been altered!
    Calling ioctl() to re-read partition table.
    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
    The kernel still uses the old table. The new table will be used at
    the next reboot or after you run partprobe(8) or kpartx(8)
    Syncing disks.
    [abhishek@Nitaichand ~]$
    Download the required Diagnostics Update Package from the Drivers Download page for your model. Got mine from here.
    Run the downloaded package under the OS you it downloaded for. That is, run the .exe on Windows. Or, if you downloaded the .bin file for Linux then first make it executable:
    chmod u+x CL1367A0.bin
    And now run it under a Linux distribution with an older version of python installed (I think <2.7). I say this because the .bin package didn't run on an updated Archlinux for me, probably because it has the latest python. I ran it from the Ubuntu 10.10 Live CD and it ran fine under that.
    On Windows, If you are not automatically prompted with an option to update your Utility Partition then you need to browse to the location where the package was extracted (for me it was C:\dell\drivers\R239866).
    Now you need to manually run the extracted file (for me it was DDDP.exe). Most probably you'll need to right-click it and run it as an Administrator. And if all went well, it will extract/update the diagnostic utilities to/on the Dell Utility Partition.
    I believe the above steps should be sufficient for someone who's lucky and who's update package is smart enough. However these steps were not sufficient for me. My "Partition not found" error was gone because I had changed the partition type. And so the update package was able to recognize the partition and extract the necessary files to it. But I was still not able to boot the utility partition. After the Pre-boot System Assessment although I no longer got the "Partition not found" error, but I was just dropped onto the GRUB boot menu prompt.
    [UPDATE: As stated above, I realize that the recovery partition had lost its ability to boot long before I had messed up my partition table. But I realized it only when I was testing all my partition after fixing the partition table. Please refer to this forum thread for further Details. I  do not think that it is possible longer to boot from the Dell Utility Parttion on my setup which has GRUB installed to the MBR. But the rest of the post documents my attempts to slove the problem without the knowledge from the forum post.]
    Anyways, it was a pain to again and again set up/update the partition and test it after waiting half an hour or so for the Pre-boot System Assessment to complete. But I was determined to solve the problem at-least partially, until next time. So I created a GRUB entry to boot the Utility partition. Assuming the partition is the first partition on the drive (which is the case here), the grub entry is simply:
    title Dell Utility
    rootnoverify (hd0,0)
    chainloader +1
    I tried downloading an older update package. I updated my Partition with it. And tested. Still, I was unsuccessful. I researched a little bit and found this link. Out of frustration,I decided to use brute force this time . So, the below are the steps which let me have at-least a glimpse of The Dell Diagnostic Utility booting up from the partition:
    Backup your partition table using the sfdisk command (not fdisk).
    Follow the instructions in the link I gave above (i.e., http://community.spiceworks.com/how_to/show/1123) and build your Utility Partition from scratch.
    Now after that when you try to boot into the OS you'll be presented with an blue bar on top. This is because the mkup batch file from the Dell Diagnostic/Drivers CD/DVD wiped your partition table and rewrote it with only one partition on it- the Dell utility partition.
    Boot into a Live environment and restore your partition table from the backup created earlier using sfdisk.
    Now boot with a Windows disc to repair your Windows boot problem. This applied to me but may not apply to you.
    Again boot into a live environment and restore GRUB to MBR.
    After a reboot press F-12 to get to the BIOS boot menu and select Diagnostics.
    Let the Pre-boot Assessment run and after its complete it will ask you to press any key to boot the Dell Utility partition. Do that.
    You'll notice your still dropped into GRUB instead of getting the Diagnostics GUI.
    Now when on GRUB prompt don't boot any other OS.
    Press any key (other than <Enter>, that is ) to stop the timer if you have one set.
    Now look carefully at the boot menu.
    Remember I told you that I had created a GRUB menu entry to boot the Dell Utility partition. Select that. And if you are lucky you might just be able boot the partition. This worked for me (finally!).
    After this initial run I was unable to run the Diagnostics GUI from the GRUB menu entry again. I haven't tried to re-run the Pre-boot Assessment and wait to see, if I'm able to boot it from there. But now, I'm satisfied that at-least the file there are in a running condition.
    Also, the update package can be used to create boot-able USB drives or boot-able CD/DVDs which can run the Diagnostics just fine. They are almost as fast as the partition (especially the USB which seems even faster). They are recommend, instead of going into this trouble to recreate the partition. That is unless you are a purist/perfectionist .
    Notes:
    At first, I panicked and tried a lot of steps that are not exactly documented above for the sake of convenience to others who might refer.
    I have thus rewritten the post in a manner to make it very general in nature as it did not become very fruitful for myself.  If you attempt to use this guide, use common sense where necessary .
    Of course, if you are trying to build a Utility partition on a bare hard drive or you're feeling adventurous, you can always follow this link .
    Last edited by bhadotia (2012-10-08 19:03:18)

    bhadotia wrote:Anyway's the file downloaded from dell to update the partition for Studio 1555 is corrupted (checksums don't match). My partition still doesn't boot. I'm working to fix this and will update my post when I'm done.
    The file seems to create the CD/DVD/Image and USB just fine. So I used this only to create a CD image which I then wrote on a blank CD which seems to work fine. Also, I played around a bit and had some partial success in booting the partition. I've updated my original opening post with the new findings.
    Whew!! what a waste of time! Never want to do all of this again .
    Last edited by bhadotia (2012-03-03 00:05:22)

Maybe you are looking for

  • Predictive Analysis 2.0 - 'BW' connect feature ?

    Hello folks, In the latest Predictive Analysis, do we have 'BW' data connect feature ? BW offline connection or connection via Lumira is fine. Looking forward to hearing any response. My customer'd like to know this. Thanks a lot. JH Yang.

  • Suppressing Page Headers

    Post Author: Stingray CA Forum: General Hi,I'm working on my first report using Crystal Reports XI R2.I've grouped my report by task.  For each task I have included details of the various task issues.  The group heading appears on its own page togeth

  • Calendar Drag and Drop not working

    Hi All, I am trying drag and drop feature in calendar. I added Calendar Drop Attribute and associated a listener from my backing bean. Upon Drag and drop activity listener is not fired. Below is the xml fragment <af:calendarDropTarget dropListener="#

  • Changing file type association through java

    hello all, here i had a problem like , we know when we try to open .csv file by default it wll open in excel , because the csv file type was associated with excel this we can see in mycomputer->tools->folder options->file types and here we even have

  • IPhoto '11- super drive failed.  It won't burn to disc.

    iPhoto '11 won't burn to disc...says super drive failed.  It goes through preparing to burn and then, immediately shows "finished" and spits out the disc.  I had just finished burning another successfully.  I talked with apple and we repaired permiss