LVM on LUKS on LVM
Does anyone know if, on a system with LVM on LUKS on LVM, a logical volume created inside a LUKS container can be added to the same volume group that the LUKS container is in? Even if this is possible, is it this just a bad idea from a security perspective? Should the outer LVM and inner LVM each have their own physical devices, volume groups, and logical volumes?
sda
└─sda1
└─Storage 254:0 0 XG 0 lvm
├─Storage-lrootvol 254:1 0 XG 0 lvm /
└─luks 254:0 0 XG 0 crypt
├─Storage-lvarvol 254:2 0 XG 0 lvm /var
├─Storage-lhomevol 254:3 0 XG 0 lvm /home
├─Storage-ltmpvol 254:4 0 XG 0 lvm /tmp
└─Storage-lswapvol 254:5 0 XG 0 lvm swap
Yes, that's what I was thinking, except that it's all on sda2 because sda1 is my EFI System partion.
Why don't you just encrypt the root partition as well? Any reason why that wouldn't work for you?
This is on a laptop, so I was trying to avoid the performance/battery life penalty of encrypting the root partition.
Similar Messages
-
[solved] luks on lvm encryption keymap issue
hi,
i just installed arch on a new notebook of mine.
i used a luks encrypted lvm installation, which works (guided by the wiki)
but i am encoutering an issue with the keymap while decrypting at boot.
i've installed using "de-latin1-nodeadkeys" as keymap, and my actual passwort has some special characters.
at boot, i'v entered the passwort but it doesn't work.
so i rebootet with the live image and checked, with the german keymap again, which worked.
i checked for mispelling btw .
for testing purposes i set a password like "///" and it seems that the keymap at boot is an english one.
https://bugs.archlinux.org/task/36689 i found this bug, but it says closed so i'm thinking i went wrong somewhere.
any help is appreciated
here is my mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf encrypt lvm2 block filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
and my grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if loadfont unicode ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-e084640b-9864-4667-84a4-9f5fb0a43483' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 802f1bee-db08-4896-87df-97c3883f58be
else
search --no-floppy --fs-uuid --set=root 802f1bee-db08-4896-87df-97c3883f58be
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=/dev/mapper/main-root rw cryptdevice=/dev/sda2:main quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-e084640b-9864-4667-84a4-9f5fb0a43483' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 802f1bee-db08-4896-87df-97c3883f58be
else
search --no-floppy --fs-uuid --set=root 802f1bee-db08-4896-87df-97c3883f58be
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=/dev/mapper/main-root rw cryptdevice=/dev/sda2:main quiet
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/60_memtest86+ ###
### END /etc/grub.d/60_memtest86+ ###
and my default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=/dev/sda2:main quiet"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
vconsole.conf
KEYMAP="de-latin1-nodeadkeys"
Last edited by ziv667 (2013-11-27 12:18:03)ziv667 wrote:HOOKS="base udev autodetect modconf encrypt lvm2 block filesystems keyboard fsck"
Where's the keymap hook?
HOOKS="base udev autodetect modconf keymap encrypt lvm2 block filesystems keyboard fsck" -
System encryption :: Luks on lvm or Lvm on Luks?
Hello,
I was reading up about lvm and luks and decided I want to encrypt my system. Until now I have been using truecrypt to encrypt a data partition which get mounted during boot. I recently bought myself a netbook and since then I've been pondering how to make the most use of HD space and keeping it secure should it get stolen.
I have 3 Harddrives in my tower. One of the HDs is my backup drive. The other two are for OSs. What I would like to do is
1) Create an encrypted volume group on HD 1 (has about 650 Gb).
2) Create 2 LVs for /root /home on HD1
3) Rsync /root and /home to the LVs HD2 -> HD1
4) HD2 secure erase
5) create VG on HD2 and add it to VG on HD1
*** My Question ***
While reading up on lvm and luks I came upon this article and I'm not quite sure which one is better suited for my situation. I don't know how easy it is to grow/add to an encrypted vg or lg.
There are two ways of setting up an encrypted disk using LVM:
1. Create the LVM and encrypt every volume separately
2. Set up LVM on top of an encrypted partition
source :: http://www.pindarsign.de/webblog/?p=767
Update : Using badblocks on /dev/sda4 didn't work as intended. It completely wiped /dev/sda. One way of going Windows free.
Luckily enough windows 7 was still able to boot without a partition table (scratches head), so I was able to copy some saved games and the downloads folder.
Last edited by whitethorn (2011-09-19 15:12:12)Dieter@be wrote:
AFAIK you cannot resize luks/dm_crypt devices, so you lose a lot of the flexibility if you put luks on top. of lvm.
personally i do full disk encryption with luks/dm_crypt, then lvm on top of that.
btw the arch installer supports both scenarios out of the box.
Sounds like what I'm doing right now. I encrypted my first HD then added lvm on top of that. It took a little while to get a seperate boot working and chroot to get all the files setup how I want. At the moment I'm randomizing a 2 Tb harddrive 10 hours 85%. Once it finishes encrypt the drive and add lvm on top. I'm not quite sure if I can grow my /home with the space from the 2nd drive and how to decrypt it during boot -
Best way to securely backup LVM on LUKS encrypted system
I'm upgrading harddisks and would like to backup my system to external storage and restore it on the new disk
This is the high level plan:
1. use ecryptfs to create an encrypted directory on a mounted external stroage device
2. mount ecryptfs directory
3. use rsync to make a backup into the ecryptfs directory
4. swap harddisks
5. use an arch live usb to encrypt and partition new disk (LVM on LUKS)
6. mount external storage and mount encrypted ecryptfs on the storage
7. restore system with rsync
Is this the way to do it?
After reading a little on ecryptfs, it seems like the passphrase and keys I create work only for the current kernel using ecryptfs (adds to the kernel key ring). So my understanding is that if I try to decrypt and mount the ecryptfs using a live arch usb, I won't be able to.
Any clarification of the process would be of great help! Thank youclfarron4 wrote:Any particular reason you're planning to use eCryptfs for the backup and LUKS for the actual system when you could use LUKS for both?
No particular reason for ecryptfs. I believe my two options are ecryptfs and encfs as described in the disk encryption comparison table: https://wiki.archlinux.org/index.php/Di … ison_table
clfarron4 wrote:
trillian wrote:After reading a little on ecryptfs, it seems like the passphrase and keys I create work only for the current kernel using ecryptfs (adds to the kernel key ring). So my understanding is that if I try to decrypt and mount the ecryptfs using a live arch usb, I won't be able to.
I'm not sure whether this is how it works. Could you show us the documentation which led you to this conclusion please?
I'm also not very familiar with keyrings and how the kernel manages it, or whether it's possible to do what I want with ecryptfs.
http://manpages.ubuntu.com/manpages/uto … ase.1.html -
2 question concerning LVM over LUKS
I succesfully configured LVM over LUKS, but have 2 parts that are not 100% clear to me
My setup is now
/dev/vda1 /boot
/dev/vda2 LVM2 with volumegroup name lvm holding three logical volumes: lvm-root, lvm-home, lvm-swap
The following I am wondering if someone would like to clarify to me
1. For booting I added cryptdevice to my kernel with the following parameter settings
kernel /vmlinuz-linux cryptdevice=/dev/vda2:encrypted root=/dev/mapper/lvm-root ro
It doesn't seems to matter what name I use in the red part of cryptdevice.
So why do I need to put a name in this red part ?? Does it matter at all what name I use here ??
2. I did not fill in anyhting in /etc/crypttab and all seems to be working without issues.
I could have entered something like "encrypted /dev/vda2 none luks" in it....
What good would it do me to enter anything in crypttab ?? When would I really need this to be filled in ??
Hoping someone would mind to explains this to me .... thxI just started playing with encryption so take what I say with a block of salt.
The name you give is what will show up in /dev/mapper, ie /dev/mapper/encrypted in this case. Since you're using lvm I think you could change the name every boot if you wanted. OTOH, if you formatted the partition directly, you could use the /dev/mapper/encrypted in fstab for example.
On the subject of crypttab I can't help you, except to say that in my experiments with encryption I've never touched it. -
LVM on LUKS split across drives
I'm installing LVM on LUKS, as follows:
/dev/sda1: boot
/dev/sda2: first LUKS device
/dev/sdb1: second LUKS device
/dev/sda2 and /dev/sdb1 are in a volume group, which is then split into logical volumes.
/dev/sda2 and /dev/sdb1 have the same password.
How can I only be prompted once for this password at boot?Strike0 has told me in the past that this is actually supported. Just use the LVM2 hook twice, once before and once after the encrypt hook. There is also the cryptsetup-multi package, but it is partially broken. In these forums somewhere there are instructions from falconindy on using the hook (maybe the install) file from the multi package in the current cryptsetup package. but you are going to have to seach for that yourself.
-
[Solved] Enlarge logical Volume (LVM on Luks)
I moved my whole system to a new SSD which is bigger than the old one, now I need to enlarge the root partition.
sda3 is my LUKS encrypted partition.
lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74,5G 0 disk
├─sda1 8:1 0 2M 0 part
├─sda2 8:2 0 200M 0 part /boot
└─sda3 8:3 0 29,6G 0 part
└─MyStorage 254:0 0 29,6G 0 crypt
├─MyStorage-swapvol 254:1 0 1G 0 lvm [SWAP]
└─MyStorage-rootvol 254:2 0 28,6G 0 lvm /
How can I resize sda3, MyStorage and Mystorage-rootvol without loosing data?
I found a post in the ubuntu-Wiki, but didn't quite understand Step 3.
Thanks in advance
Last edited by hasdf (2014-11-23 17:17:38)frostschutz wrote:Is there free space on the disk to make that partition larger?
If I got you right, there is free space after the partition:
Modell: ATA INTEL SSDSA2M080 (scsi)
Festplatte /dev/sda: 156301488s
Sektorgröße (logisch/physisch): 512B/512B
Partitionstabelle: gpt
Disk-Flags:
Nummer Anfang Ende Größe Dateisystem Name Flags
34s 2047s 2014s Freier Platz
1 2048s 6143s 4096s
2 6144s 415743s 409600s ext2
3 415744s 62533262s 62117519s
62533263s 156301454s 93768192s Freier Platz
Thank you for your help! I'll try it and post the result here.
EDIT: I coudn't enlarge the partition like frostschulz said. And since I had to delete the partition in question, I just deleted everything and reinstalled archlinux with a full system backup.
Last edited by hasdf (2014-11-23 17:15:07) -
[SOLVED] [LVM over LUKS] TRIM forwarding doesn't work
Recently I encrypted my SSD using LUKS and created three LVM volumes on top of it. Then I added "allow-discards" to the list of kernel parameters, here is the respective entry from grub.cfg:
linux /vmlinuz-linux root=/dev/mapper/vgarch-root ro cryptdevice=/dev/sda2:vgarch:allow-discards cryptkey=/dev/disk/by-uuid/02F2-CDB8:vfat:/lukskey quiet logo.nologo loglevel=3 console=tty1 splash=silent,theme:arch-elegant elevator=noop transparent_hugepage=never radeon.modeset=1
And an excerpt from fstab:
/dev/mapper/vgarch-root / ext4 defaults,auto,noatime,discard 0 1
UUID=e8ba294e-9621-422d-8f40-d9ffbc715484 /boot ext2 defaults 0 2
/dev/mapper/vgarch-var /var ext4 defaults,auto,noatime,discard 0 2
/dev/mapper/vgarch-home /home ext4 defaults,auto,noatime,discard 0 2
When the system is booting up, "encrypt" hook prints the appropriate message ("Enabling TRIM/discard support."), so everything seems to work fine. But when I check for TRIM support using the following method, the last command doesn't print zeroes as expected.
[root@archhost /]# dd if=/dev/urandom of=tempfile count=100 bs=512k oflag=direct
100+0 records in
100+0 records out
52428800 bytes (52 MB) copied, 5.66872 s, 9.2 MB/s
[root@archhost /]# hdparm --fibmap tempfile
tempfile:
filesystem blocksize 4096, begins at LBA 0; assuming 512 byte sectors.
byte_offset begin_LBA end_LBA sectors
0 13969408 13970431 1024
524288 13986816 13987839 1024
1048576 14026752 14127103 100352
[root@archhost /]# hdparm --read-sector 13969408 /dev/sda
/dev/sda:
reading sector 13969408: succeeded
bc43 41aa 82eb 4200 438a 6151 cbbd 0842
4014 cfa4 17e7 b2ca 7c92 ec35 9fe3 0089
206c beba c33d 5876 89e7 0d9c 1fc7 b122
801e bdb9 82af 8885 add9 7b17 7aa4 4c69
d4c1 da55 2029 bd05 d0f0 cd22 a944 b27b
ffa7 9c29 ad4a 9292 7f3a 9e4d 9040 f135
f507 3d8b c142 6ac2 da83 167a c40e 1be4
2c58 f7b6 fb50 2ce7 c7d2 6f70 ce45 be87
bfe4 2755 4795 10ee e1e1 1362 d078 a8ac
0754 8663 6881 12e4 fe8c c1c1 795f 7617
0423 1abf eade 31d1 4bfc e7a0 5fbc 36cd
af25 febe 374a bef1 eb3b 2b73 df5c a5fe
9dc3 d5e9 e31c 97ec 35ca 4002 4beb 0917
2d72 d0e3 f0ab 8d75 0fcf ce97 500f e869
875b 7866 1528 7148 99d0 6369 3369 a639
cb39 f552 a277 62c3 1ba8 bdb3 4127 a6ca
5cdd d934 5f5b a434 a20e 980c 7bfd 6f40
7029 d9aa 294f 321e 4eab 8130 adf3 140a
5352 328b 6713 25ac c37a d33a 2be9 3699
459c fc7a 1b10 7e99 8b74 cc60 e5b9 3a85
edbb 7baf 2205 34a4 c10e 6d79 1e44 239f
dad3 ee10 b76f 76fa 569c 3b73 81e0 0848
db89 4efd c520 163e af72 b83b ff3b a924
d2f1 120d 75df f7ae 3922 1b2a ee39 5efd
3ade 6a0e f24e f14d 7444 d7b6 3c3a 5ab6
2345 420d e9a4 1811 807e 9c29 5da3 f9a0
f7cb ba53 b3f1 69c4 b76d fa9d 6a0a 0184
a69c fe16 42d9 71a9 85b9 1b01 8870 40b1
585a c191 a101 39b4 2203 b662 2a17 50fc
93ac 3a2d 2b27 22f4 ff60 f7d1 fd59 feda
1477 c56f 816a 0199 34b7 ba4c 4950 6af8
b7bf c409 d48a e701 2894 1be1 3ac9 d4b1
[root@archhost /]# rm tempfile
[root@archhost /]# sync
[root@archhost /]# hdparm --read-sector 13969408 /dev/sda
/dev/sda:
reading sector 13969408: succeeded
bc43 41aa 82eb 4200 438a 6151 cbbd 0842
4014 cfa4 17e7 b2ca 7c92 ec35 9fe3 0089
206c beba c33d 5876 89e7 0d9c 1fc7 b122
801e bdb9 82af 8885 add9 7b17 7aa4 4c69
d4c1 da55 2029 bd05 d0f0 cd22 a944 b27b
ffa7 9c29 ad4a 9292 7f3a 9e4d 9040 f135
f507 3d8b c142 6ac2 da83 167a c40e 1be4
2c58 f7b6 fb50 2ce7 c7d2 6f70 ce45 be87
bfe4 2755 4795 10ee e1e1 1362 d078 a8ac
0754 8663 6881 12e4 fe8c c1c1 795f 7617
0423 1abf eade 31d1 4bfc e7a0 5fbc 36cd
af25 febe 374a bef1 eb3b 2b73 df5c a5fe
9dc3 d5e9 e31c 97ec 35ca 4002 4beb 0917
2d72 d0e3 f0ab 8d75 0fcf ce97 500f e869
875b 7866 1528 7148 99d0 6369 3369 a639
cb39 f552 a277 62c3 1ba8 bdb3 4127 a6ca
5cdd d934 5f5b a434 a20e 980c 7bfd 6f40
7029 d9aa 294f 321e 4eab 8130 adf3 140a
5352 328b 6713 25ac c37a d33a 2be9 3699
459c fc7a 1b10 7e99 8b74 cc60 e5b9 3a85
edbb 7baf 2205 34a4 c10e 6d79 1e44 239f
dad3 ee10 b76f 76fa 569c 3b73 81e0 0848
db89 4efd c520 163e af72 b83b ff3b a924
d2f1 120d 75df f7ae 3922 1b2a ee39 5efd
3ade 6a0e f24e f14d 7444 d7b6 3c3a 5ab6
2345 420d e9a4 1811 807e 9c29 5da3 f9a0
f7cb ba53 b3f1 69c4 b76d fa9d 6a0a 0184
a69c fe16 42d9 71a9 85b9 1b01 8870 40b1
585a c191 a101 39b4 2203 b662 2a17 50fc
93ac 3a2d 2b27 22f4 ff60 f7d1 fd59 feda
1477 c56f 816a 0199 34b7 ba4c 4950 6af8
b7bf c409 d48a e701 2894 1be1 3ac9 d4b1
Is it possible at all to enable TRIM support in this case? And if yes, what did I miss?
Last edited by Atragor (2012-07-01 19:19:14)Good, my guess then would be that your trim is working already and you should be able to invoke it also with fstrim manually to get a positive confirmation in bash.
The reason you don't see the zeros in your check should be that the hdparm reports back the wrong starting sector of the file due to offsets. See here for a thorough explanation by the developer and here another summary. -
[Luks] SWAP hibernation in LVM using LUKS (resolved)
Hi,
I use Luks for encrypt my root, home and swap.
At the boot, the message is
ERROR can't find /dev/mapper/cr-swap wainting 10 seconds..
And after I can enter the passphrase.
Here's the config.
$ lsblk
sdb 8:16 0 149,1G 0 disk
├─sdb1 8:17 0 94,1M 0 part /boot
└─sdb2 8:18 0 149G 0 part
└─root 254:0 0 149G 0 crypt
├─cr-root 254:1 0 15G 0 lvm /
├─cr-home 254:2 0 100G 0 lvm /home
└─cr-swap 254:3 0 3G 0 lvm
I also add
vim /etc/crypttab
cr-swap /dev/mapper/cr-swap dev/urandom swap,cipher=aes-cbc-essiv:sha256
How can I use /dev/mapper/rc-swap to SWAP in order to suspend-to-disk support ?
Thanks in adance.
Last edited by NeanderMarcl (2013-10-06 19:38:31)-- Logs begin at ven. 2013-10-04 19:47:19 CEST, end at dim. 2013-10-06 20:58:49 CEST. --
oct. 06 20:46:25 stan systemd-journal[177]: Runtime journal is using 544.0K (max 150.6M, leaving 226.0M of free 1.4G, current limit 150.6M).
oct. 06 20:46:25 stan systemd-journal[177]: Runtime journal is using 548.0K (max 150.6M, leaving 226.0M of free 1.4G, current limit 150.6M).
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys cpuset
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys cpu
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys cpuacct
oct. 06 20:46:25 stan kernel: Linux version 3.11.3-1-ARCH (nobody@var-lib-archbuild-extra-x86_64-thomas) (gcc version 4.8.1 20130725 (prerelease) (GCC) ) #1 SMP PREEMPT Wed Oct 2 01:38:48 CEST 2013
oct. 06 20:46:25 stan kernel: Command line: root=/dev/mapper/cr-root cryptdevice=/dev/sdb2:root initrd=/initramfs-linux.img BOOT_IMAGE=/vmlinuz-linux
oct. 06 20:46:25 stan kernel: e820: BIOS-provided physical RAM map:
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000000e6000-0x00000000000fffff] reserved
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000bffaffff] usable
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000bffb0000-0x00000000bffbffff] ACPI data
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000bffc0000-0x00000000bffeffff] ACPI NVS
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000bfff0000-0x00000000bfffffff] reserved
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed003ff] reserved
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
oct. 06 20:46:25 stan kernel: BIOS-e820: [mem 0x00000000ff380000-0x00000000ffffffff] reserved
oct. 06 20:46:25 stan kernel: NX (Execute Disable) protection: active
oct. 06 20:46:25 stan kernel: SMBIOS 2.4 present.
oct. 06 20:46:25 stan kernel: DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./G31M-GS. , BIOS P1.80 05/20/2011
oct. 06 20:46:25 stan kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
oct. 06 20:46:25 stan kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
oct. 06 20:46:25 stan kernel: No AGP bridge found
oct. 06 20:46:25 stan kernel: e820: last_pfn = 0xbffb0 max_arch_pfn = 0x400000000
oct. 06 20:46:25 stan kernel: MTRR default type: uncachable
oct. 06 20:46:25 stan kernel: MTRR fixed ranges enabled:
oct. 06 20:46:25 stan kernel: 00000-9FFFF write-back
oct. 06 20:46:25 stan kernel: A0000-BFFFF uncachable
oct. 06 20:46:25 stan kernel: C0000-CFFFF write-protect
oct. 06 20:46:25 stan kernel: D0000-DFFFF uncachable
oct. 06 20:46:25 stan kernel: E0000-EFFFF write-through
oct. 06 20:46:25 stan kernel: F0000-FFFFF write-protect
oct. 06 20:46:25 stan kernel: MTRR variable ranges enabled:
oct. 06 20:46:25 stan kernel: 0 base 000000000 mask F80000000 write-back
oct. 06 20:46:25 stan kernel: 1 base 080000000 mask FC0000000 write-back
oct. 06 20:46:25 stan kernel: 2 disabled
oct. 06 20:46:25 stan kernel: 3 disabled
oct. 06 20:46:25 stan kernel: 4 disabled
oct. 06 20:46:25 stan kernel: 5 disabled
oct. 06 20:46:25 stan kernel: 6 disabled
oct. 06 20:46:25 stan kernel: 7 disabled
oct. 06 20:46:25 stan kernel: x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
oct. 06 20:46:25 stan kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [ffff8800000ff780]
oct. 06 20:46:25 stan kernel: Scanning 1 areas for low memory corruption
oct. 06 20:46:25 stan kernel: Base memory trampoline at [ffff880000099000] 99000 size 24576
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0x00000000-0x000fffff]
oct. 06 20:46:25 stan kernel: [mem 0x00000000-0x000fffff] page 4k
oct. 06 20:46:25 stan kernel: BRK [0x01b2d000, 0x01b2dfff] PGTABLE
oct. 06 20:46:25 stan kernel: BRK [0x01b2e000, 0x01b2efff] PGTABLE
oct. 06 20:46:25 stan kernel: BRK [0x01b2f000, 0x01b2ffff] PGTABLE
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0xbfc00000-0xbfdfffff]
oct. 06 20:46:25 stan kernel: [mem 0xbfc00000-0xbfdfffff] page 2M
oct. 06 20:46:25 stan kernel: BRK [0x01b30000, 0x01b30fff] PGTABLE
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0xbc000000-0xbfbfffff]
oct. 06 20:46:25 stan kernel: [mem 0xbc000000-0xbfbfffff] page 2M
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0x80000000-0xbbffffff]
oct. 06 20:46:25 stan kernel: [mem 0x80000000-0xbbffffff] page 2M
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0x00100000-0x7fffffff]
oct. 06 20:46:25 stan kernel: [mem 0x00100000-0x001fffff] page 4k
oct. 06 20:46:25 stan kernel: [mem 0x00200000-0x7fffffff] page 2M
oct. 06 20:46:25 stan kernel: init_memory_mapping: [mem 0xbfe00000-0xbffaffff]
oct. 06 20:46:25 stan kernel: [mem 0xbfe00000-0xbffaffff] page 4k
oct. 06 20:46:25 stan kernel: BRK [0x01b31000, 0x01b31fff] PGTABLE
oct. 06 20:46:25 stan kernel: RAMDISK: [mem 0x7fb1a000-0x7fffefff]
oct. 06 20:46:25 stan kernel: ACPI: RSDP 00000000000fa010 00014 (v00 ACPIAM)
oct. 06 20:46:25 stan kernel: ACPI: RSDT 00000000bffb0000 00040 (v01 052011 RSDT1536 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: FACP 00000000bffb0200 00084 (v01 A M I OEMFACP 12000601 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: DSDT 00000000bffb0440 05641 (v01 AS166 AS166172 00000172 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: FACS 00000000bffc0000 00040
oct. 06 20:46:25 stan kernel: ACPI: APIC 00000000bffb0390 0006C (v01 052011 APIC1536 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: MCFG 00000000bffb0400 0003C (v01 052011 OEMMCFG 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: OEMB 00000000bffc0040 00071 (v01 052011 OEMB1536 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: AAFT 00000000bffb5a90 00027 (v01 052011 OEMAAFT 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: GSCI 00000000bffc00c0 02024 (v01 052011 GMCHSCI 20110520 MSFT 00000097)
oct. 06 20:46:25 stan kernel: ACPI: SSDT 00000000bffc2a10 00A7C (v01 DpgPmm CpuPm 00000012 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: Local APIC address 0xfee00000
oct. 06 20:46:25 stan kernel: No NUMA configuration found
oct. 06 20:46:25 stan kernel: Faking a node at [mem 0x0000000000000000-0x00000000bffaffff]
oct. 06 20:46:25 stan kernel: Initmem setup node 0 [mem 0x00000000-0xbffaffff]
oct. 06 20:46:25 stan kernel: NODE_DATA [mem 0xbffab000-0xbffaffff]
oct. 06 20:46:25 stan kernel: [ffffea0000000000-ffffea0002ffffff] PMD -> [ffff8800bc400000-ffff8800bf3fffff] on node 0
oct. 06 20:46:25 stan kernel: Zone ranges:
oct. 06 20:46:25 stan kernel: DMA [mem 0x00001000-0x00ffffff]
oct. 06 20:46:25 stan kernel: DMA32 [mem 0x01000000-0xffffffff]
oct. 06 20:46:25 stan kernel: Normal empty
oct. 06 20:46:25 stan kernel: Movable zone start for each node
oct. 06 20:46:25 stan kernel: Early memory node ranges
oct. 06 20:46:25 stan kernel: node 0: [mem 0x00001000-0x0009efff]
oct. 06 20:46:25 stan kernel: node 0: [mem 0x00100000-0xbffaffff]
oct. 06 20:46:25 stan kernel: On node 0 totalpages: 786254
oct. 06 20:46:25 stan kernel: DMA zone: 64 pages used for memmap
oct. 06 20:46:25 stan kernel: DMA zone: 21 pages reserved
oct. 06 20:46:25 stan kernel: DMA zone: 3998 pages, LIFO batch:0
oct. 06 20:46:25 stan kernel: DMA32 zone: 12223 pages used for memmap
oct. 06 20:46:25 stan kernel: DMA32 zone: 782256 pages, LIFO batch:31
oct. 06 20:46:25 stan kernel: ACPI: PM-Timer IO Port: 0x808
oct. 06 20:46:25 stan kernel: ACPI: Local APIC address 0xfee00000
oct. 06 20:46:25 stan kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
oct. 06 20:46:25 stan kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
oct. 06 20:46:25 stan kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
oct. 06 20:46:25 stan kernel: ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
oct. 06 20:46:25 stan kernel: ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
oct. 06 20:46:25 stan kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
oct. 06 20:46:25 stan kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
oct. 06 20:46:25 stan kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
oct. 06 20:46:25 stan kernel: ACPI: IRQ0 used by override.
oct. 06 20:46:25 stan kernel: ACPI: IRQ2 used by override.
oct. 06 20:46:25 stan kernel: ACPI: IRQ9 used by override.
oct. 06 20:46:25 stan kernel: Using ACPI (MADT) for SMP configuration information
oct. 06 20:46:25 stan kernel: smpboot: Allowing 4 CPUs, 2 hotplug CPUs
oct. 06 20:46:25 stan kernel: nr_irqs_gsi: 40
oct. 06 20:46:25 stan kernel: PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
oct. 06 20:46:25 stan kernel: PM: Registered nosave memory: [mem 0x000a0000-0x000e5fff]
oct. 06 20:46:25 stan kernel: PM: Registered nosave memory: [mem 0x000e6000-0x000fffff]
oct. 06 20:46:25 stan kernel: e820: [mem 0xc0000000-0xfecfffff] available for PCI devices
oct. 06 20:46:25 stan kernel: Booting paravirtualized kernel on bare hardware
oct. 06 20:46:25 stan kernel: setup_percpu: NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1
oct. 06 20:46:25 stan kernel: PERCPU: Embedded 29 pages/cpu @ffff8800bfa00000 s86528 r8192 d24064 u524288
oct. 06 20:46:25 stan kernel: pcpu-alloc: s86528 r8192 d24064 u524288 alloc=1*2097152
oct. 06 20:46:25 stan kernel: pcpu-alloc: [0] 0 1 2 3
oct. 06 20:46:25 stan kernel: Built 1 zonelists in Node order, mobility grouping on. Total pages: 773946
oct. 06 20:46:25 stan kernel: Policy zone: DMA32
oct. 06 20:46:25 stan kernel: Kernel command line: root=/dev/mapper/cr-root cryptdevice=/dev/sdb2:root initrd=/initramfs-linux.img BOOT_IMAGE=/vmlinuz-linux
oct. 06 20:46:25 stan kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
oct. 06 20:46:25 stan kernel: Checking aperture...
oct. 06 20:46:25 stan kernel: No AGP bridge found
oct. 06 20:46:25 stan kernel: Calgary: detecting Calgary via BIOS EBDA area
oct. 06 20:46:25 stan kernel: Calgary: Unable to locate Rio Grande table in EBDA - bailing!
oct. 06 20:46:25 stan kernel: Memory: 3078568K/3145016K available (5046K kernel code, 795K rwdata, 1696K rodata, 1140K init, 1284K bss, 66448K reserved)
oct. 06 20:46:25 stan kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
oct. 06 20:46:25 stan kernel: Preemptible hierarchical RCU implementation.
oct. 06 20:46:25 stan kernel: RCU dyntick-idle grace-period acceleration is enabled.
oct. 06 20:46:25 stan kernel: Dump stacks of tasks blocking RCU-preempt GP.
oct. 06 20:46:25 stan kernel: RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
oct. 06 20:46:25 stan kernel: NR_IRQS:4352 nr_irqs:712 16
oct. 06 20:46:25 stan kernel: Console: colour VGA+ 80x25
oct. 06 20:46:25 stan kernel: console [tty0] enabled
oct. 06 20:46:25 stan kernel: allocated 12582912 bytes of page_cgroup
oct. 06 20:46:25 stan kernel: please try 'cgroup_disable=memory' option if you don't want memory cgroups
oct. 06 20:46:25 stan kernel: tsc: Fast TSC calibration using PIT
oct. 06 20:46:25 stan kernel: tsc: Detected 2193.912 MHz processor
oct. 06 20:46:25 stan kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 4389.65 BogoMIPS (lpj=7313040)
oct. 06 20:46:25 stan kernel: pid_max: default: 32768 minimum: 301
oct. 06 20:46:25 stan kernel: Security Framework initialized
oct. 06 20:46:25 stan kernel: AppArmor: AppArmor disabled by boot time parameter
oct. 06 20:46:25 stan kernel: Yama: becoming mindful.
oct. 06 20:46:25 stan kernel: Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
oct. 06 20:46:25 stan kernel: Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes)
oct. 06 20:46:25 stan kernel: Mount-cache hash table entries: 256
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys memory
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys devices
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys freezer
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys net_cls
oct. 06 20:46:25 stan kernel: Initializing cgroup subsys blkio
oct. 06 20:46:25 stan kernel: CPU: Physical Processor ID: 0
oct. 06 20:46:25 stan kernel: CPU: Processor Core ID: 0
oct. 06 20:46:25 stan kernel: mce: CPU supports 6 MCE banks
oct. 06 20:46:25 stan kernel: CPU0: Thermal monitoring enabled (TM2)
oct. 06 20:46:25 stan kernel: Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
tlb_flushall_shift: -1
oct. 06 20:46:25 stan kernel: Freeing SMP alternatives memory: 20K (ffffffff819e5000 - ffffffff819ea000)
oct. 06 20:46:25 stan kernel: ACPI: Core revision 20130517
oct. 06 20:46:25 stan kernel: ACPI: All ACPI Tables successfully acquired
oct. 06 20:46:25 stan kernel: ftrace: allocating 20089 entries in 79 pages
oct. 06 20:46:25 stan kernel: ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
oct. 06 20:46:25 stan kernel: smpboot: CPU0: Intel(R) Pentium(R) Dual CPU E2200 @ 2.20GHz (fam: 06, model: 0f, stepping: 0d)
oct. 06 20:46:25 stan kernel: Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
oct. 06 20:46:25 stan kernel: perf_event_intel: PEBS disabled due to CPU errata
oct. 06 20:46:25 stan kernel: ... version: 2
oct. 06 20:46:25 stan kernel: ... bit width: 40
oct. 06 20:46:25 stan kernel: ... generic registers: 2
oct. 06 20:46:25 stan kernel: ... value mask: 000000ffffffffff
oct. 06 20:46:25 stan kernel: ... max period: 000000007fffffff
oct. 06 20:46:25 stan kernel: ... fixed-purpose events: 3
oct. 06 20:46:25 stan kernel: ... event mask: 0000000700000003
oct. 06 20:46:25 stan kernel: NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
oct. 06 20:46:25 stan kernel: smpboot: Booting Node 0, Processors #1
oct. 06 20:46:25 stan kernel: Brought up 2 CPUs
oct. 06 20:46:25 stan kernel: smpboot: Total of 2 processors activated (8779.30 BogoMIPS)
oct. 06 20:46:25 stan kernel: devtmpfs: initialized
oct. 06 20:46:25 stan kernel: PM: Registering ACPI NVS region [mem 0xbffc0000-0xbffeffff] (196608 bytes)
oct. 06 20:46:25 stan kernel: RTC time: 18:46:18, date: 10/06/13
oct. 06 20:46:25 stan kernel: NET: Registered protocol family 16
oct. 06 20:46:25 stan kernel: ACPI: bus type PCI registered
oct. 06 20:46:25 stan kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
oct. 06 20:46:25 stan kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
oct. 06 20:46:25 stan kernel: PCI: not using MMCONFIG
oct. 06 20:46:25 stan kernel: PCI: Using configuration type 1 for base access
oct. 06 20:46:25 stan kernel: bio: create slab <bio-0> at 0
oct. 06 20:46:25 stan kernel: ACPI: Added _OSI(Module Device)
oct. 06 20:46:25 stan kernel: ACPI: Added _OSI(Processor Device)
oct. 06 20:46:25 stan kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
oct. 06 20:46:25 stan kernel: ACPI: Added _OSI(Processor Aggregator Device)
oct. 06 20:46:25 stan kernel: ACPI: EC: Look up EC in DSDT
oct. 06 20:46:25 stan kernel: ACPI: Executed 1 blocks of module-level executable AML code
oct. 06 20:46:25 stan kernel: ACPI: SSDT 00000000bffc20f0 00235 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: Dynamic OEM Table Load:
oct. 06 20:46:25 stan kernel: ACPI: SSDT (null) 00235 (v01 DpgPmm P001Ist 00000011 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: SSDT 00000000bffc2580 00235 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: Dynamic OEM Table Load:
oct. 06 20:46:25 stan kernel: ACPI: SSDT (null) 00235 (v01 DpgPmm P002Ist 00000012 INTL 20051117)
oct. 06 20:46:25 stan kernel: ACPI: Interpreter enabled
oct. 06 20:46:25 stan kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
oct. 06 20:46:25 stan kernel: ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20130517/hwxface-571)
oct. 06 20:46:25 stan kernel: ACPI: (supports S0 S1 S4 S5)
oct. 06 20:46:25 stan kernel: ACPI: Using IOAPIC for interrupt routing
oct. 06 20:46:25 stan kernel: PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
oct. 06 20:46:25 stan kernel: PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
oct. 06 20:46:25 stan kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
oct. 06 20:46:25 stan kernel: ACPI: No dock devices found.
oct. 06 20:46:25 stan kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
oct. 06 20:46:25 stan kernel: acpi PNP0A08:00: Requesting ACPI _OSC control (0x1d)
oct. 06 20:46:25 stan kernel: acpi PNP0A08:00: ACPI _OSC control (0x1c) granted
oct. 06 20:46:25 stan kernel: PCI host bridge to bus 0000:00
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [bus 00-ff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000dffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [mem 0xc0000000-0xdfffffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: root bus resource [mem 0xf0000000-0xffffffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:00.0: [8086:29c0] type 00 class 0x060000
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: [8086:29c1] type 01 class 0x060400
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
oct. 06 20:46:25 stan kernel: pci 0000:00:1b.0: reg 0x10: [mem 0xf9ffc000-0xf9ffffff 64bit]
oct. 06 20:46:25 stan kernel: pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:1b.0: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.0: reg 0x20: [io 0xc480-0xc49f]
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.0: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.1: reg 0x20: [io 0xc800-0xc81f]
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.1: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.2: reg 0x20: [io 0xc880-0xc89f]
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.2: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.3: reg 0x20: [io 0xcc00-0xcc1f]
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.3: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.7: reg 0x10: [mem 0xf9ffbc00-0xf9ffbfff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:1d.7: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: [8086:244e] type 01 class 0x060401
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: System wakeup disabled by ACPI
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: [8086:27b8] type 00 class 0x060100
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: Force enabled HPET at 0xfed00000
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: address space collision: [io 0x0800-0x087f] conflicts with ACPI CPU throttle [??? 0x00000810-0x00000815 flags 0x80000000]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: quirk: [io 0x0480-0x04bf] claimed by ICH6 GPIO
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 1 PIO at 0280 (mask 00ff)
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: ICH7 LPC Generic IO decode 2 PIO at 0300 (mask 003f)
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: [8086:27df] type 00 class 0x01018a
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: reg 0x10: [io 0x0000-0x0007]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: reg 0x14: [io 0x0000-0x0003]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: reg 0x18: [io 0x08f0-0x08f7]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: reg 0x1c: [io 0x08f8-0x08fb]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.1: reg 0x20: [io 0xffa0-0xffaf]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: [8086:27c0] type 00 class 0x01018f
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: reg 0x10: [io 0xc400-0xc407]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: reg 0x14: [io 0xc080-0xc083]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: reg 0x18: [io 0xc000-0xc007]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: reg 0x1c: [io 0xbc00-0xbc03]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: reg 0x20: [io 0xb880-0xb88f]
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.2: PME# supported from D3hot
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.3: reg 0x20: [io 0x0400-0x041f]
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: [10de:06e0] type 00 class 0x030000
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: reg 0x10: [mem 0xfd000000-0xfdffffff]
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: reg 0x1c: [mem 0xfa000000-0xfbffffff 64bit]
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: reg 0x24: [io 0xec00-0xec7f]
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: reg 0x30: [mem 0xfebe0000-0xfebfffff pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: PCI bridge to [bus 04]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [mem 0xfa000000-0xfebfffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [mem 0xcff00000-0xcfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: [10ec:8168] type 00 class 0x020000
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: reg 0x10: [io 0xd800-0xd8ff]
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: reg 0x18: [mem 0xcfeff000-0xcfefffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: reg 0x20: [mem 0xcfef8000-0xcfefbfff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: supports D1 D2
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [mem 0xcfe00000-0xcfefffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: PCI bridge to [bus 03] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000dffff] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [mem 0xc0000000-0xdfffffff] (subtractive decode)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: bridge window [mem 0xf0000000-0xffffffff] (subtractive decode)
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15)
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
oct. 06 20:46:25 stan kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs *3 4 5 6 7 10 11 12 14 15)
oct. 06 20:46:25 stan kernel: ACPI: Enabled 2 GPEs in block 00 to 1F
oct. 06 20:46:25 stan kernel: ACPI: \_SB_.PCI0: notify handler is installed
oct. 06 20:46:25 stan kernel: Found 1 acpi root devices
oct. 06 20:46:25 stan kernel: vgaarb: device added: PCI:0000:04:00.0,decodes=io+mem,owns=io+mem,locks=none
oct. 06 20:46:25 stan kernel: vgaarb: loaded
oct. 06 20:46:25 stan kernel: vgaarb: bridge control possible 0000:04:00.0
oct. 06 20:46:25 stan kernel: PCI: Using ACPI for IRQ routing
oct. 06 20:46:25 stan kernel: PCI: pci_cache_line_size set to 64 bytes
oct. 06 20:46:25 stan kernel: e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
oct. 06 20:46:25 stan kernel: e820: reserve RAM buffer [mem 0xbffb0000-0xbfffffff]
oct. 06 20:46:25 stan kernel: NetLabel: Initializing
oct. 06 20:46:25 stan kernel: NetLabel: domain hash size = 128
oct. 06 20:46:25 stan kernel: NetLabel: protocols = UNLABELED CIPSOv4
oct. 06 20:46:25 stan kernel: NetLabel: unlabeled traffic allowed by default
oct. 06 20:46:25 stan kernel: hpet clockevent registered
oct. 06 20:46:25 stan kernel: HPET: 3 timers in total, 0 timers will be used for per-cpu timer
oct. 06 20:46:25 stan kernel: hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
oct. 06 20:46:25 stan kernel: hpet0: 3 comparators, 64-bit 14.318180 MHz counter
oct. 06 20:46:25 stan kernel: Switched to clocksource hpet
oct. 06 20:46:25 stan kernel: pnp: PnP ACPI init
oct. 06 20:46:25 stan kernel: ACPI: bus type PNP registered
oct. 06 20:46:25 stan kernel: system 00:00: [mem 0xfed14000-0xfed19fff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
oct. 06 20:46:25 stan kernel: pnp 00:01: [dma 4]
oct. 06 20:46:25 stan kernel: pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
oct. 06 20:46:25 stan kernel: pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
oct. 06 20:46:25 stan kernel: pnp 00:03: Plug and Play ACPI device, IDs PNP0800 (active)
oct. 06 20:46:25 stan kernel: pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
oct. 06 20:46:25 stan kernel: pnp 00:05: [dma 3]
oct. 06 20:46:25 stan kernel: pnp 00:05: Plug and Play ACPI device, IDs PNP0401 (active)
oct. 06 20:46:25 stan kernel: system 00:06: [io 0x04d0-0x04d1] has been reserved
oct. 06 20:46:25 stan kernel: system 00:06: [io 0x0800-0x087f] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:06: [io 0x0480-0x04bf] has been reserved
oct. 06 20:46:25 stan kernel: system 00:06: [io 0x0900-0x090f] has been reserved
oct. 06 20:46:25 stan kernel: system 00:06: [mem 0xfed1c000-0xfed1ffff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:06: [mem 0xfed20000-0xfed8ffff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
oct. 06 20:46:25 stan kernel: pnp 00:07: Plug and Play ACPI device, IDs INT0800 (active)
oct. 06 20:46:25 stan kernel: system 00:08: [mem 0xffc00000-0xfff7ffff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
oct. 06 20:46:25 stan kernel: system 00:09: [mem 0xfec00000-0xfec00fff] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:09: [mem 0xfee00000-0xfee00fff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
oct. 06 20:46:25 stan kernel: pnp 00:0a: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
oct. 06 20:46:25 stan kernel: pnp 00:0b: [dma 0 disabled]
oct. 06 20:46:25 stan kernel: pnp 00:0b: Plug and Play ACPI device, IDs PNP0501 (active)
oct. 06 20:46:25 stan kernel: system 00:0c: [io 0x0280-0x028f] has been reserved
oct. 06 20:46:25 stan kernel: system 00:0c: [io 0x0290-0x029f] has been reserved
oct. 06 20:46:25 stan kernel: system 00:0c: Plug and Play ACPI device, IDs PNP0c02 (active)
oct. 06 20:46:25 stan kernel: system 00:0d: [mem 0xe0000000-0xefffffff] has been reserved
oct. 06 20:46:25 stan kernel: system 00:0d: Plug and Play ACPI device, IDs PNP0c02 (active)
oct. 06 20:46:25 stan kernel: system 00:0e: [mem 0x00000000-0x0009ffff] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:0e: [mem 0x000c0000-0x000cffff] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:0e: [mem 0x000e0000-0x000fffff] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:0e: [mem 0x00100000-0xbfffffff] could not be reserved
oct. 06 20:46:25 stan kernel: system 00:0e: Plug and Play ACPI device, IDs PNP0c01 (active)
oct. 06 20:46:25 stan kernel: pnp: PnP ACPI: found 15 devices
oct. 06 20:46:25 stan kernel: ACPI: bus type PNP unregistered
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff] to [bus 02] add_size 400000
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff] to [bus 01] add_size 400000
oct. 06 20:46:25 stan kernel: pci 0000:00:1f.0: BAR 13: [io 0x0800-0x087f] has bogus alignment
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 400000
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: res[14]=[mem 0x00100000-0x000fffff] get_res_add_size add_size 400000
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: BAR 14: assigned [mem 0xc0000000-0xc03fffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: BAR 14: assigned [mem 0xc0400000-0xc07fffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: BAR 13: assigned [io 0x1000-0x1fff]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: PCI bridge to [bus 04]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [io 0xe000-0xefff]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [mem 0xfa000000-0xfebfffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: PCI bridge to [bus 02]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [io 0x1000-0x1fff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [mem 0xc0000000-0xc03fffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: bridge window [mem 0xcff00000-0xcfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: PCI bridge to [bus 01]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [io 0xd000-0xdfff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [mem 0xc0400000-0xc07fffff]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.1: bridge window [mem 0xcfe00000-0xcfefffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: PCI bridge to [bus 03]
oct. 06 20:46:25 stan kernel: pci 0000:00:1c.0: enabling device (0106 -> 0107)
oct. 06 20:46:25 stan kernel: pci 0000:00:1e.0: setting latency timer to 64
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000dffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 8 [mem 0xc0000000-0xdfffffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:00: resource 9 [mem 0xf0000000-0xffffffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:04: resource 0 [io 0xe000-0xefff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:04: resource 1 [mem 0xfa000000-0xfebfffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:04: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci_bus 0000:02: resource 0 [io 0x1000-0x1fff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:02: resource 1 [mem 0xc0000000-0xc03fffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:02: resource 2 [mem 0xcff00000-0xcfffffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci_bus 0000:01: resource 0 [io 0xd000-0xdfff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:01: resource 1 [mem 0xc0400000-0xc07fffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:01: resource 2 [mem 0xcfe00000-0xcfefffff 64bit pref]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 4 [io 0x0000-0x0cf7]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 5 [io 0x0d00-0xffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 6 [mem 0x000a0000-0x000bffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 7 [mem 0x000d0000-0x000dffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 8 [mem 0xc0000000-0xdfffffff]
oct. 06 20:46:25 stan kernel: pci_bus 0000:03: resource 9 [mem 0xf0000000-0xffffffff]
oct. 06 20:46:25 stan kernel: NET: Registered protocol family 2
oct. 06 20:46:25 stan kernel: TCP established hash table entries: 32768 (order: 7, 524288 bytes)
oct. 06 20:46:25 stan kernel: TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
oct. 06 20:46:25 stan kernel: TCP: Hash tables configured (established 32768 bind 32768)
oct. 06 20:46:25 stan kernel: TCP: reno registered
oct. 06 20:46:25 stan kernel: UDP hash table entries: 2048 (order: 4, 65536 bytes)
oct. 06 20:46:25 stan kernel: UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes)
oct. 06 20:46:25 stan kernel: NET: Registered protocol family 1
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: Boot video device
oct. 06 20:46:25 stan kernel: PCI: CLS 32 bytes, default 64
oct. 06 20:46:25 stan kernel: Unpacking initramfs...
oct. 06 20:46:25 stan kernel: Freeing initrd memory: 5012K (ffff88007fb1a000 - ffff88007ffff000)
oct. 06 20:46:25 stan kernel: Scanning for low memory corruption every 60 seconds
oct. 06 20:46:25 stan kernel: audit: initializing netlink socket (disabled)
oct. 06 20:46:25 stan kernel: type=2000 audit(1381085178.279:1): initialized
oct. 06 20:46:25 stan kernel: HugeTLB registered 2 MB page size, pre-allocated 0 pages
oct. 06 20:46:25 stan kernel: zbud: loaded
oct. 06 20:46:25 stan kernel: VFS: Disk quotas dquot_6.5.2
oct. 06 20:46:25 stan kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
oct. 06 20:46:25 stan kernel: msgmni has been set to 6022
oct. 06 20:46:25 stan kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
oct. 06 20:46:25 stan kernel: io scheduler noop registered
oct. 06 20:46:25 stan kernel: io scheduler deadline registered
oct. 06 20:46:25 stan kernel: io scheduler cfq registered (default)
oct. 06 20:46:25 stan kernel: pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
oct. 06 20:46:25 stan kernel: pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
oct. 06 20:46:25 stan kernel: pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
oct. 06 20:46:25 stan kernel: pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
oct. 06 20:46:25 stan kernel: pci 0000:04:00.0: Signaling PME through PCIe PME interrupt
oct. 06 20:46:25 stan kernel: pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
oct. 06 20:46:25 stan kernel: pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
oct. 06 20:46:25 stan kernel: pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
oct. 06 20:46:25 stan kernel: pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
oct. 06 20:46:25 stan kernel: pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
oct. 06 20:46:25 stan kernel: pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
oct. 06 20:46:25 stan kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
oct. 06 20:46:25 stan kernel: pciehp: PCI Express Hot Plug Controller Driver version: 0.4
oct. 06 20:46:25 stan kernel: intel_idle: does not run on family 6 model 15
oct. 06 20:46:25 stan kernel: GHES: HEST is not enabled!
oct. 06 20:46:25 stan kernel: Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
oct. 06 20:46:25 stan kernel: 00:0b: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
oct. 06 20:46:25 stan kernel: Linux agpgart interface v0.103
oct. 06 20:46:25 stan kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
oct. 06 20:46:25 stan kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
oct. 06 20:46:25 stan kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
oct. 06 20:46:25 stan kernel: mousedev: PS/2 mouse device common for all mice
oct. 06 20:46:25 stan kernel: rtc_cmos 00:02: RTC can wake from S4
oct. 06 20:46:25 stan kernel: rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
oct. 06 20:46:25 stan kernel: rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
oct. 06 20:46:25 stan kernel: cpuidle: using governor ladder
oct. 06 20:46:25 stan kernel: cpuidle: using governor menu
oct. 06 20:46:25 stan kernel: drop_monitor: Initializing network drop monitor service
oct. 06 20:46:25 stan kernel: TCP: cubic registered
oct. 06 20:46:25 stan kernel: NET: Registered protocol family 10
oct. 06 20:46:25 stan kernel: NET: Registered protocol family 17
oct. 06 20:46:25 stan kernel: Key type dns_resolver registered
oct. 06 20:46:25 stan kernel: PM: Hibernation image not present or could not be loaded.
oct. 06 20:46:25 stan kernel: registered taskstats version 1
oct. 06 20:46:25 stan kernel: Magic number: 1:620:796
oct. 06 20:46:25 stan kernel: rtc_cmos 00:02: setting system clock to 2013-10-06 18:46:18 UTC (1381085178)
oct. 06 20:46:25 stan kernel: Freeing unused kernel memory: 1140K (ffffffff818c8000 - ffffffff819e5000)
oct. 06 20:46:25 stan kernel: Write protecting the kernel read-only data: 8192k
oct. 06 20:46:25 stan kernel: Freeing unused kernel memory: 1088K (ffff8800014f0000 - ffff880001600000)
oct. 06 20:46:25 stan kernel: Freeing unused kernel memory: 352K (ffff8800017a8000 - ffff880001800000)
oct. 06 20:46:25 stan systemd-udevd[46]: starting version 208
oct. 06 20:46:25 stan kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
oct. 06 20:46:25 stan kernel: SCSI subsystem initialized
oct. 06 20:46:25 stan kernel: ACPI: bus type USB registered
oct. 06 20:46:25 stan kernel: usbcore: registered new interface driver usbfs
oct. 06 20:46:25 stan kernel: usbcore: registered new interface driver hub
oct. 06 20:46:25 stan kernel: ACPI: bus type ATA registered
oct. 06 20:46:25 stan kernel: usbcore: registered new device driver usb
oct. 06 20:46:25 stan kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
oct. 06 20:46:25 stan kernel: ehci-pci: EHCI PCI platform driver
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: setting latency timer to 64
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: EHCI Host Controller
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: debug port 1
oct. 06 20:46:25 stan kernel: libata version 3.00 loaded.
oct. 06 20:46:25 stan kernel: uhci_hcd: USB Universal Host Controller Interface driver
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: cache line size of 32 is not supported
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: irq 23, io mem 0xf9ffbc00
oct. 06 20:46:25 stan kernel: ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
oct. 06 20:46:25 stan kernel: hub 1-0:1.0: USB hub found
oct. 06 20:46:25 stan kernel: hub 1-0:1.0: 8 ports detected
oct. 06 20:46:25 stan kernel: ata_piix 0000:00:1f.1: version 2.13
oct. 06 20:46:25 stan kernel: ata_piix 0000:00:1f.1: setting latency timer to 64
oct. 06 20:46:25 stan kernel: scsi0 : ata_piix
oct. 06 20:46:25 stan kernel: scsi1 : ata_piix
oct. 06 20:46:25 stan kernel: ata1: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xffa0 irq 14
oct. 06 20:46:25 stan kernel: ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xffa8 irq 15
oct. 06 20:46:25 stan kernel: ata_piix 0000:00:1f.2: MAP [
oct. 06 20:46:25 stan kernel: P0 P2 P1 P3 ]
oct. 06 20:46:25 stan kernel: ata_piix 0000:00:1f.2: setting latency timer to 64
oct. 06 20:46:25 stan kernel: scsi2 : ata_piix
oct. 06 20:46:25 stan kernel: scsi3 : ata_piix
oct. 06 20:46:25 stan kernel: ata3: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xb880 irq 19
oct. 06 20:46:25 stan kernel: ata4: SATA max UDMA/133 cmd 0xc000 ctl 0xbc00 bmdma 0xb888 irq 19
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.0: setting latency timer to 64
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.0: UHCI Host Controller
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000c480
oct. 06 20:46:25 stan kernel: hub 2-0:1.0: USB hub found
oct. 06 20:46:25 stan kernel: hub 2-0:1.0: 2 ports detected
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.1: setting latency timer to 64
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.1: UHCI Host Controller
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000c800
oct. 06 20:46:25 stan kernel: hub 3-0:1.0: USB hub found
oct. 06 20:46:25 stan kernel: hub 3-0:1.0: 2 ports detected
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.2: setting latency timer to 64
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.2: UHCI Host Controller
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000c880
oct. 06 20:46:25 stan kernel: hub 4-0:1.0: USB hub found
oct. 06 20:46:25 stan kernel: hub 4-0:1.0: 2 ports detected
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.3: setting latency timer to 64
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.3: UHCI Host Controller
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
oct. 06 20:46:25 stan kernel: uhci_hcd 0000:00:1d.3: irq 16, io base 0x0000cc00
oct. 06 20:46:25 stan kernel: hub 5-0:1.0: USB hub found
oct. 06 20:46:25 stan kernel: hub 5-0:1.0: 2 ports detected
oct. 06 20:46:25 stan kernel: ata3.01: NODEV after polling detection
oct. 06 20:46:25 stan kernel: ata3.00: ATAPI: ATAPI DVD A DH16A6S, YA16, max UDMA/100
oct. 06 20:46:25 stan kernel: ata4.00: ATA-8: Hitachi HDP725016GLA380, GMBOA52A, max UDMA/133
oct. 06 20:46:25 stan kernel: ata4.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
oct. 06 20:46:25 stan kernel: ata3.00: configured for UDMA/100
oct. 06 20:46:25 stan kernel: ata4.00: configured for UDMA/133
oct. 06 20:46:25 stan kernel: ata1.01: ATA-6: ST3120022A, 3.06, max UDMA/100
oct. 06 20:46:25 stan kernel: ata1.01: 234441648 sectors, multi 0: LBA48
oct. 06 20:46:25 stan kernel: ata1.01: limited to UDMA/33 due to 40-wire cable
oct. 06 20:46:25 stan kernel: ata1.01: configured for UDMA/33
oct. 06 20:46:25 stan kernel: scsi 0:0:1:0: Direct-Access ATA ST3120022A 3.06 PQ: 0 ANSI: 5
oct. 06 20:46:25 stan kernel: sd 0:0:1:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB)
oct. 06 20:46:25 stan kernel: sd 0:0:1:0: [sda] Write Protect is off
oct. 06 20:46:25 stan kernel: sd 0:0:1:0: [sda] Mode Sense: 00 3a 00 00
oct. 06 20:46:25 stan kernel: sd 0:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
oct. 06 20:46:25 stan kernel: scsi 2:0:0:0: CD-ROM ATAPI DVD A DH16A6S YA16 PQ: 0 ANSI: 5
oct. 06 20:46:25 stan kernel: scsi 3:0:0:0: Direct-Access ATA Hitachi HDP72501 GMBO PQ: 0 ANSI: 5
oct. 06 20:46:25 stan kernel: sd 3:0:0:0: [sdb] 312581808 512-byte logical blocks: (160 GB/149 GiB)
oct. 06 20:46:25 stan kernel: sd 3:0:0:0: [sdb] Write Protect is off
oct. 06 20:46:25 stan kernel: sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
oct. 06 20:46:25 stan kernel: sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
oct. 06 20:46:25 stan kernel: sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
oct. 06 20:46:25 stan kernel: cdrom: Uniform CD-ROM driver Revision: 3.20
oct. 06 20:46:25 stan kernel: sr 2:0:0:0: Attached scsi CD-ROM sr0
oct. 06 20:46:25 stan kernel: sdb: sdb1 sdb2
oct. 06 20:46:25 stan kernel: sd 3:0:0:0: [sdb] Attached SCSI disk
oct. 06 20:46:25 stan kernel: sda: sda1
oct. 06 20:46:25 stan kernel: sd 0:0:1:0: [sda] Attached SCSI disk
oct. 06 20:46:25 stan kernel: device-mapper: uevent: version 1.0.3
oct. 06 20:46:25 stan kernel: device-mapper: ioctl: 4.25.0-ioctl (2013-06-26) initialised: [email protected]
oct. 06 20:46:25 stan kernel: usb 2-2: new low-speed USB device number 2 using uhci_hcd
oct. 06 20:46:25 stan kernel: hidraw: raw HID events driver (C) Jiri Kosina
oct. 06 20:46:25 stan kernel: usbcore: registered new interface driver usbhid
oct. 06 20:46:25 stan kernel: usbhid: USB HID core driver
oct. 06 20:46:25 stan kernel: input: USB Optical Mouse USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input1
oct. 06 20:46:25 stan kernel: a4tech 0003:09DA:0006.0001: input,hidraw0: USB HID v1.10 Mouse [USB Optical Mouse USB Optical Mouse] on usb-0000:00:1d.0-2/input0
oct. 06 20:46:25 stan kernel: tsc: Refined TSC clocksource calibration: 2193.925 MHz
oct. 06 20:46:25 stan kernel: Switched to clocksource tsc
oct. 06 20:46:25 stan kernel: sha256_ssse3: Using SSSE3 optimized SHA-256 implementation
oct. 06 20:46:25 stan kernel: bio: create slab <bio-1> at 1
oct. 06 20:46:25 stan kernel: bio: create slab <bio-1> at 1
oct. 06 20:46:25 stan kernel: EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
oct. 06 20:46:25 stan systemd[1]: systemd 208 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
oct. 06 20:46:25 stan systemd[1]: Set hostname to <stan>.
oct. 06 20:46:25 stan systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
oct. 06 20:46:25 stan systemd[1]: Started Forward Password Requests to Wall Directory Watch.
oct. 06 20:46:25 stan systemd[1]: Expecting device sys-subsystem-net-devices-enp1s0.device...
oct. 06 20:46:25 stan systemd[1]: Starting Remote File Systems.
oct. 06 20:46:25 stan systemd[1]: Reached target Remote File Systems.
oct. 06 20:46:25 stan systemd[1]: Starting Delayed Shutdown Socket.
oct. 06 20:46:25 stan systemd[1]: Listening on Delayed Shutdown Socket.
oct. 06 20:46:25 stan systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
oct. 06 20:46:25 stan systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
oct. 06 20:46:25 stan systemd[1]: Starting Device-mapper event daemon FIFOs.
oct. 06 20:46:25 stan systemd[1]: Listening on Device-mapper event daemon FIFOs.
oct. 06 20:46:25 stan systemd[1]: Starting LVM2 metadata daemon socket.
oct. 06 20:46:25 stan systemd[1]: Listening on LVM2 metadata daemon socket.
oct. 06 20:46:25 stan systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
oct. 06 20:46:25 stan systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
oct. 06 20:46:25 stan systemd[1]: Starting Paths.
oct. 06 20:46:25 stan systemd[1]: Reached target Paths.
oct. 06 20:46:25 stan systemd[1]: Starting Journal Socket.
oct. 06 20:46:25 stan systemd[1]: Listening on Journal Socket.
oct. 06 20:46:25 stan systemd[1]: Mounting POSIX Message Queue File System...
oct. 06 20:46:25 stan systemd[1]: Starting Setup Virtual Console...
oct. 06 20:46:25 stan systemd[1]: Starting Journal Service...
oct. 06 20:46:25 stan systemd[1]: Started Journal Service.
oct. 06 20:46:25 stan systemd-journal[177]: Journal started
oct. 06 20:46:25 stan systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
oct. 06 20:46:25 stan systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
oct. 06 20:46:25 stan systemd[1]: Starting Apply Kernel Variables...
oct. 06 20:46:25 stan systemd[1]: Mounting Huge Pages File System...
oct. 06 20:46:25 stan systemd[1]: Starting udev Kernel Socket.
oct. 06 20:46:25 stan systemd[1]: Listening on udev Kernel Socket.
oct. 06 20:46:25 stan systemd[1]: Starting udev Control Socket.
oct. 06 20:46:25 stan systemd[1]: Listening on udev Control Socket.
oct. 06 20:46:25 stan systemd[1]: Starting udev Coldplug all Devices...
oct. 06 20:46:25 stan systemd[1]: Mounting Debug File System...
oct. 06 20:46:25 stan systemd[1]: Started Load Kernel Modules.
oct. 06 20:46:25 stan systemd[1]: Mounted FUSE Control File System.
oct. 06 20:46:25 stan systemd[1]: Starting Create list of required static device nodes for the current kernel...
oct. 06 20:46:25 stan systemd[1]: Starting Encrypted Volumes.
oct. 06 20:46:25 stan systemd[1]: Reached target Encrypted Volumes.
oct. 06 20:46:25 stan systemd[1]: Mounting Configuration File System...
oct. 06 20:46:25 stan systemd[1]: Started Set Up Additional Binary Formats.
oct. 06 20:46:25 stan systemd[1]: Expecting device dev-disk-by\x2duuid-895cfe76\x2d97d7\x2d4e2d\x2d8433\x2d267fe59df5a5.device...
oct. 06 20:46:25 stan systemd[1]: Mounting Temporary Directory...
oct. 06 20:46:25 stan systemd[1]: Starting File System Check on Root Device...
oct. 06 20:46:25 stan systemd[1]: Expecting device dev-disk-by\x2duuid-ad0bf6d6\x2d6faf\x2d448a\x2d88fd\x2d8589f635e86b.device...
oct. 06 20:46:25 stan systemd[1]: Starting Root Slice.
oct. 06 20:46:25 stan systemd[1]: Created slice Root Slice.
oct. 06 20:46:25 stan systemd[1]: Starting User and Session Slice.
oct. 06 20:46:25 stan systemd[1]: Created slice User and Session Slice.
oct. 06 20:46:25 stan systemd[1]: Starting System Slice.
oct. 06 20:46:25 stan systemd[1]: Created slice System Slice.
oct. 06 20:46:25 stan systemd[1]: Starting system-dhcpcd.slice.
oct. 06 20:46:25 stan systemd[1]: Created slice system-dhcpcd.slice.
oct. 06 20:46:25 stan systemd[1]: Starting system-getty.slice.
oct. 06 20:46:25 stan systemd[1]: Created slice system-getty.slice.
oct. 06 20:46:25 stan systemd[1]: Starting Slices.
oct. 06 20:46:25 stan systemd[1]: Reached target Slices.
oct. 06 20:46:25 stan systemd[1]: Expecting device dev-disk-by\x2duuid-64f23708\x2de717\x2d4399\x2da654\x2dc785dffab70b.device...
oct. 06 20:46:25 stan systemd[1]: Mounted POSIX Message Queue File System.
oct. 06 20:46:25 stan systemd[1]: Started Apply Kernel Variables.
oct. 06 20:46:25 stan systemd[1]: Mounted Huge Pages File System.
oct. 06 20:46:25 stan systemd[1]: Mounted Debug File System.
oct. 06 20:46:25 stan systemd[1]: Mounted Configuration File System.
oct. 06 20:46:25 stan systemd[1]: Mounted Temporary Directory.
oct. 06 20:46:26 stan systemd[1]: Started udev Coldplug all Devices.
oct. 06 20:46:26 stan systemd[1]: Started Create list of required static device nodes for the current kernel.
oct. 06 20:46:26 stan systemd[1]: Starting Create static device nodes in /dev...
oct. 06 20:46:26 stan systemd-fsck[193]: [74B blob data]
oct. 06 20:46:26 stan systemd[1]: Started Setup Virtual Console.
oct. 06 20:46:26 stan systemd[1]: Started File System Check on Root Device.
oct. 06 20:46:26 stan systemd[1]: Starting Remount Root and Kernel File Systems...
oct. 06 20:46:26 stan systemd[1]: Started Create static device nodes in /dev.
oct. 06 20:46:26 stan systemd[1]: Starting udev Kernel Device Manager...
oct. 06 20:46:26 stan systemd[1]: Started udev Kernel Device Manager.
oct. 06 20:46:26 stan systemd-udevd[205]: starting version 208
oct. 06 20:46:26 stan systemd[1]: Started Remount Root and Kernel File Systems.
oct. 06 20:46:26 stan systemd[1]: Starting Load/Save Random Seed...
oct. 06 20:46:26 stan systemd[1]: Starting Local File Systems (Pre).
oct. 06 20:46:26 stan systemd[1]: Reached target Local File Systems (Pre).
oct. 06 20:46:26 stan kernel: EXT4-fs (dm-1): re-mounted. Opts: data=ordered
oct. 06 20:46:26 stan systemd[1]: Started Load/Save Random Seed.
oct. 06 20:46:26 stan kernel: input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
oct. 06 20:46:26 stan kernel: ACPI: Power Button [PWRB]
oct. 06 20:46:26 stan kernel: input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
oct. 06 20:46:26 stan kernel: ACPI: Power Button [PWRF]
oct. 06 20:46:26 stan kernel: snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
oct. 06 20:46:26 stan kernel: parport_pc 00:05: reported by Plug and Play ACPI
oct. 06 20:46:26 stan kernel: parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
oct. 06 20:46:26 stan kernel: ACPI: Requesting acpi_cpufreq
oct. 06 20:46:27 stan kernel: intel_rng: FWH not detected
oct. 06 20:46:27 stan kernel: input: HDA Intel Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
oct. 06 20:46:27 stan kernel: input: HDA Intel Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
oct. 06 20:46:27 stan kernel: input: HDA Intel Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
oct. 06 20:46:27 stan kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
oct. 06 20:46:27 stan kernel: ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \PMRG 1 (20130517/utaddress-251)
oct. 06 20:46:27 stan kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
oct. 06 20:46:27 stan kernel: ACPI Warning: 0x0000000000000480-0x00000000000004af SystemIO conflicts with Region \GPR2 1 (20130517/utaddress-251)
oct. 06 20:46:27 stan kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
oct. 06 20:46:27 stan kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
oct. 06 20:46:27 stan kernel: i801_smbus 0000:00:1f.3: SMBus using PCI Interrupt
oct. 06 20:46:27 stan kernel: leds_ss4200: no LED devices found
oct. 06 20:46:27 stan kernel: microcode: CPU0 sig=0x6fd, pf=0x1, revision=0xa3
oct. 06 20:46:27 stan kernel: input: PC Speaker as /devices/platform/pcspkr/input/input7
oct. 06 20:46:27 stan kernel: ppdev: user-space parallel port driver
oct. 06 20:46:27 stan systemd[1]: Starting Sound Card.
oct. 06 20:46:27 stan systemd[1]: Reached target Sound Card.
oct. 06 20:46:27 stan kernel: iTCO_vendor_support: vendor-support=0
oct. 06 20:46:27 stan kernel: iTCO_wdt: Intel TCO WatchDog Timer Driver v1.10
oct. 06 20:46:27 stan kernel: iTCO_wdt: Found a ICH7 or ICH7R TCO device (Version=2, TCOBASE=0x0860)
oct. 06 20:46:27 stan kernel: iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
oct. 06 20:46:27 stan kernel: microcode: CPU1 sig=0x6fd, pf=0x1, revision=0xa3
oct. 06 20:46:27 stan kernel: microcode: Microcode Update Driver: v2.00 <[email protected]>, Peter Oruba
oct. 06 20:46:27 stan kernel: coretemp coretemp.0: Using relative temperature scale!
oct. 06 20:46:27 stan kernel: coretemp coretemp.0: Using relative temperature scale!
oct. 06 20:46:27 stan kernel: [drm] Initialized drm 1.1.0 20060810
oct. 06 20:46:27 stan kernel: wmi: Mapper loaded
oct. 06 20:46:27 stan kernel: nouveau [ DEVICE][0000:04:00.0] BOOT0 : 0x298000a2
oct. 06 20:46:27 stan kernel: nouveau [ DEVICE][0000:04:00.0] Chipset: G98 (NV98)
oct. 06 20:46:27 stan kernel: nouveau [ DEVICE][0000:04:00.0] Family : NV50
oct. 06 20:46:27 stan kernel: nouveau [ VBIOS][0000:04:00.0] checking PRAMIN for image...
oct. 06 20:46:27 stan kernel: nouveau [ VBIOS][0000:04:00.0] ... appears to be valid
oct. 06 20:46:27 stan kernel: nouveau [ VBIOS][0000:04:00.0] using image from PRAMIN
oct. 06 20:46:27 stan kernel: nouveau [ VBIOS][0000:04:00.0] BIT signature found
oct. 06 20:46:27 stan kernel: nouveau [ VBIOS][0000:04:00.0] version 62.98.29.00.35
oct. 06 20:46:27 stan kernel: nouveau [ PFB][0000:04:00.0] RAM type: DDR2
oct. 06 20:46:27 stan kernel: nouveau [ PFB][0000:04:00.0] RAM size: 256 MiB
oct. 06 20:46:27 stan kernel: nouveau [ PFB][0000:04:00.0] ZCOMP: 960 tags
oct. 06 20:46:27 stan kernel: nouveau [ PTHERM][0000:04:00.0] FAN control: none / external
oct. 06 20:46:27 stan kernel: nouveau [ PTHERM][0000:04:00.0] fan management: disabled
oct. 06 20:46:27 stan kernel: nouveau [ PTHERM][0000:04:00.0] internal sensor: yes
oct. 06 20:46:27 stan kernel: [TTM] Zone kernel: Available graphics memory: 1543090 kiB
oct. 06 20:46:27 stan kernel: [TTM] Initializing pool allocator
oct. 06 20:46:27 stan kernel: [TTM] Initializing DMA pool allocator
oct. 06 20:46:27 stan kernel: nouveau [ DRM] VRAM: 256 MiB
oct. 06 20:46:27 stan kernel: nouveau [ DRM] GART: 1048576 MiB
oct. 06 20:46:27 stan kernel: nouveau [ DRM] TMDS table version 2.0
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB version 4.0
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB outp 00: 04000310 00000028
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB outp 01: 01011302 00000030
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB outp 02: 02011300 00000028
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB outp 03: 02022322 00020010
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB conn 00: 00000000
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB conn 01: 00001130
oct. 06 20:46:27 stan kernel: nouveau [ DRM] DCB conn 02: 00002261
oct. 06 20:46:27 stan kernel: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
oct. 06 20:46:27 stan kernel: [drm] No driver support for vblank timestamp query.
oct. 06 20:46:27 stan kernel: nouveau [ DRM] 1 available performance level(s)
oct. 06 20:46:27 stan kernel: nouveau [ DRM] 3: core 540MHz shader 1300MHz memory 510MHz fanspeed 100%
oct. 06 20:46:27 stan kernel: nouveau [ DRM] c: core 540MHz shader 1300MHz memory 499MHz
oct. 06 20:46:27 stan kernel: nouveau [ DRM] MM: using M2MF for buffer copies
oct. 06 20:46:27 stan kernel: gpio_ich: GPIO from 206 to 255 on gpio_ich
oct. 06 20:46:27 stan kernel: nouveau [ DRM] allocated 1360x768 fb: 0x60000, bo ffff8800bb3fb400
oct. 06 20:46:27 stan kernel: fbcon: nouveaufb (fb0) is primary device
oct. 06 20:46:28 stan kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
oct. 06 20:46:28 stan kernel: r8169 0000:01:00.0: irq 44 for MSI/MSI-X
oct. 06 20:46:28 stan kernel: r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xffffc90011d26000, XID 081000c0 IRQ 44
oct. 06 20:46:28 stan kernel: r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
oct. 06 20:46:28 stan kernel: Console: switching to colour frame buffer device 170x48
oct. 06 20:46:28 stan kernel: nouveau 0000:04:00.0: fb0: nouveaufb frame buffer device
oct. 06 20:46:28 stan kernel: nouveau 0000:04:00.0: registered panic notifier
oct. 06 20:46:28 stan kernel: [drm] Initialized nouveau 1.1.1 20120801 for 0000:04:00.0 on minor 0
oct. 06 20:46:28 stan systemd[1]: Starting LVM2 metadata daemon...
oct. 06 20:46:28 stan systemd[1]: Started LVM2 metadata daemon.
oct. 06 20:46:28 stan systemd[1]: Found device /dev/disk/by-uuid/895cfe76-97d7-4e2d-8433-267fe59df5a5.
oct. 06 20:46:28 stan systemd[1]: Activating swap /dev/disk/by-uuid/895cfe76-97d7-4e2d-8433-267fe59df5a5...
oct. 06 20:46:28 stan swapon[238]: [137B blob data]
oct. 06 20:46:28 stan systemd[1]: Found device Motherboard (one of many).
oct. 06 20:46:28 stan systemd-udevd[211]: renamed network interface eth0 to enp1s0
oct. 06 20:46:28 stan systemd[1]: Found device Hitachi_HDP725016GLA380.
oct. 06 20:46:28 stan systemd[1]: Starting File System Check on /dev/disk/by-uuid/64f23708-e717-4399-a654-c785dffab70b...
oct. 06 20:46:28 stan systemd[1]: Activated swap /dev/disk/by-uuid/895cfe76-97d7-4e2d-8433-267fe59df5a5.
oct. 06 20:46:28 stan systemd[1]: Starting Swap.
oct. 06 20:46:28 stan systemd[1]: Reached target Swap.
oct. 06 20:46:28 stan kernel: Adding 3145724k swap on /dev/mapper/cr-swap. Priority:-1 extents:1 across:3145724k FS
oct. 06 20:46:28 stan systemd-fsck[241]: [38B blob data]
oct. 06 20:46:29 stan systemd[1]: Found device /dev/disk/by-uuid/ad0bf6d6-6faf-448a-88fd-8589f635e86b.
oct. 06 20:46:29 stan systemd[1]: Starting File System Check on /dev/disk/by-uuid/ad0bf6d6-6faf-448a-88fd-8589f635e86b...
oct. 06 20:46:29 stan systemd-fsck[245]: [48B blob data]
oct. 06 20:46:29 stan systemd-fsck[241]: [57B blob data]
oct. 06 20:46:29 stan systemd[1]: Started File System Check on /dev/disk/by-uuid/64f23708-e717-4399-a654-c785dffab70b.
oct. 06 20:46:29 stan systemd[1]: Mounting /boot...
oct. 06 20:46:30 stan systemd[1]: Mounted /boot.
oct. 06 20:46:30 stan kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: data=ordered
oct. 06 20:46:30 stan systemd-fsck[245]: /dev/mapper/cr-home: Lors de l'effacement de l'i-noeud orphelin 1572908 (uid=1000, gid=100, mode=0100755, taille=1079)
oct. 06 20:46:30 stan systemd-fsck[245]: [75B blob data]
oct. 06 20:46:31 stan systemd[1]: Started File System Check on /dev/disk/by-uuid/ad0bf6d6-6faf-448a-88fd-8589f635e86b.
oct. 06 20:46:31 stan systemd[1]: Mounting /home...
oct. 06 20:46:31 stan systemd[1]: Mounted /home.
oct. 06 20:46:31 stan systemd[1]: Starting Local File Systems.
oct. 06 20:46:31 stan systemd[1]: Reached target Local File Systems.
oct. 06 20:46:31 stan systemd[1]: Starting Recreate Volatile Files and Directories...
oct. 06 20:46:31 stan kernel: EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: data=ordered
oct. 06 20:46:31 stan systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
oct. 06 20:46:31 stan systemd[1]: Started Recreate Volatile Files and Directories.
oct. 06 20:46:31 stan systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
oct. 06 20:46:31 stan systemd[1]: Started Update UTMP about System Reboot/Shutdown.
oct. 06 20:46:31 stan systemd[1]: Starting System Initialization.
oct. 06 20:46:31 stan systemd[1]: Reached target System Initialization.
oct. 06 20:46:31 stan systemd[1]: Starting ACPID Listen Socket.
oct. 06 20:46:31 stan systemd[1]: Listening on ACPID Listen Socket.
oct. 06 20:46:31 stan systemd[1]: Starting D-Bus System Message Bus Socket.
oct. 06 20:46:31 stan systemd[1]: Listening on D-Bus System Message Bus Socket.
oct. 06 20:46:31 stan systemd[1]: Starting Sockets.
oct. 06 20:46:31 stan systemd[1]: Reached target Sockets.
oct. 06 20:46:31 stan systemd[1]: Starting Daily Cleanup of Temporary Directories.
oct. 06 20:46:31 stan systemd[1]: Started Daily Cleanup of Temporary Directories.
oct. 06 20:46:31 stan systemd[1]: Starting Timers.
oct. 06 20:46:31 stan systemd[1]: Reached target Timers.
oct. 06 20:46:31 stan systemd[1]: Started Manage Sound Card State (restore and store).
oct. 06 20:46:31 stan systemd[1]: Starting Restore Sound Card State...
oct. 06 20:46:31 stan systemd[1]: Starting Basic System.
oct. 06 20:46:31 stan systemd[1]: Reached target Basic System.
oct. 06 20:46:31 stan systemd[1]: Starting dhcpcd on enp1s0...
oct. 06 20:46:31 stan systemd[1]: Started SSH Key Generation.
oct. 06 20:46:31 stan systemd[1]: Starting Login Service...
oct. 06 20:46:31 stan systemd[1]: Starting ACPI event daemon...
oct. 06 20:46:31 stan systemd[1]: Started ACPI event daemon.
oct. 06 20:46:31 stan systemd[1]: Starting D-Bus System Message Bus...
oct. 06 20:46:31 stan systemd[1]: Started D-Bus System Message Bus.
oct. 06 20:46:31 stan systemd[1]: Started Restore Sound Card State.
oct. 06 20:46:32 stan systemd-journal[177]: Permanent journal is using 324.2M (max 1.4G, leaving 2.1G of free 11.9G, current limit 1.4G).
oct. 06 20:46:31 stan acpid[272]: starting up with netlink and the input layer
oct. 06 20:46:31 stan acpid[272]: 1 rule loaded
oct. 06 20:46:31 stan acpid[272]: waiting for events: event logging is off
oct. 06 20:46:31 stan dhcpcd[269]: version 6.0.5 starting
oct. 06 20:46:33 stan dhcpcd[269]: enp1s0: waiting for carrier
oct. 06 20:46:33 stan dhcpcd[269]: enp1s0: carrier acquired
oct. 06 20:46:33 stan dhcpcd[269]: enp1s0: soliciting an IPv6 router
oct. 06 20:46:33 stan dhcpcd[269]: enp1s0: rebinding lease of 192.168.0.12
oct. 06 20:46:31 stan systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
oct. 06 20:46:31 stan systemd[1]: Starting Permit User Sessions...
oct. 06 20:46:31 stan systemd[1]: Started Permit User Sessions.
oct. 06 20:46:31 stan systemd[1]: -
How to setup grub2 with arch linux and xen, lvm on luks
OK, so I tried downloading this package from AUR: https://aur.archlinux.org/packages/xen-git/ , but that has patching problems as noted in the comments. It looks like the packagebuild sets up all the xen stuff for you, but I can't seem to get the package to install because of the error's while patching. If anyone can point me in the right direction on what all the extra files in the PKGBUILD are for or how to debug problems with PKGBUILDs not working because of patches.
So next I just tried to compile the latest xen from git://xenbits.xen.org/xen.git (with ./configure, make, make install) and that seemed to go fine, but I'm a bit confused:
1. Do I have to do any additional configuration for xen when working with arch linux? On ubuntu I could just compile the source, update grub, and make sure to start the x services at runtime.
2. How do I set up grub to load xen with this setup? Right now this is my /boot/grub/grub.cfg:
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda3:vgStorage"
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
~
I've tried throwing in a line like: XEN_HYPERVISOR_CMDLINE="cryptdevice=/dev/sda3:vgStorage", but nothing new shows up on the grub boot menu.
First time trying to set up a non-ubuntu system, please help!As for XEN.... well you could always try QEMU/KVM or LXC.
As for the LVM2-on-LUKS/dm-crypt
My /etc/mkinitcpio.conf looks like this...
MODULES="aesni_intel ata_generic ata_piix nls_cp437 ext4 intel_agp i915 dm-snapshot"
BINARIES=""
FILES=""
HOOKS="base udev autodetect block keymap encrypt lvm2 filesystems keyboard fsck shutdown"
/etc/defaults/grub
GRUB_CMDLINE_LINUX="cryptdevice=/dev/sda2:root:allow-discards"
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
The running grub config looks like this
/boot/grub/grub.cfg
9 insmod part_gpt
10 insmod part_msdos
53 if loadfont unicode ; then
54 set gfxmode=auto
55 load_video
56 insmod gfxterm
57 set locale_dir=$prefix/locale
58 set lang=en_US
59 insmod gettext
60 fi
61 terminal_input console
62 terminal_output gfxterm
63 set timeout=3
84 menuentry 'Backup, Arch Linux grsec kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-grsec kernel-true-12341234-8080-8080-8080-332200882255' {
85 load_video
86 set gfxpayload=keep
87 insmod gzio
88 insmod part_msdos
89 insmod ext2
90 set root='hd1,msdos2'
91 if [ x$feature_platform_search_hint = xy ]; then
92 search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos2 --hint-efi=hd1,msdos2 --hint-baremetal=ahci1,msdos2 BBAAEEAA-FFCC-CCFF-FFCC-AABBCCEEBBAA
93 else
94 search --no-floppy --fs-uuid --set=root BBAAEEAA-FFCC-CCFF-FFCC-AABBCCEEBBAA
95 fi
96 echo 'Loading Linux grsec kernel ...'
97 linux /vmlinuz-linux-grsec root=/dev/mapper/VolGroup00-lvroot rw cryptdevice=/dev/sda2:root:allow-discards quiet
98 echo 'Loading initial ramdisk ...'
99 initrd /initramfs-linux-grsec.img
100 }
Things to note:
Numerical UUID is the UUID of the ROOT partition.
Alphabetical UUIS is the BOOT partition
hd1,msdos2 AND ahci1,msdos2 are how the Grub Bootloader numbers the drives not Linux.
I have my BOOT partition on a USB stick, and it is the Second partition.
So, that would make it, Device 2 and Partition 2
Device numbering starts at 0
Partition numbering starts at 1
Oh, and note that you don't need ":allow-discards" ... at all but certainly if you don't have an SSD. Also note that I included the line numbers so it is very clear that I didn't post the whole thing, but instead what I thought was relevant. Finally, I am loading modules that I don't even need, but what the hell... if it ain't broke, don't fix it
Last edited by hunterthomson (2013-12-04 08:31:45) -
Mounting an LVM on Luks Partition [SOLVED]
Hello Arch Linux Community:
This likely sounds like a very stupid question, but I have honestly hit a wall and need some advice. To make a long story short I was messing around in some configuration files and forgot to undo a change that I made before rebooting, which has rendered my system mostly inoperable. (I mistakenly changed the address for Bash in /etc/shells, so I can't log in as either my user or root). Now ordinarily this would be a very simple fix, but for whatever reason it is proving to be far more difficult that I anticipated. My root partition is stored as Logical Volume on a Physical Volume on /dev/sda3 and the entire Volume Group (containing my root, home, swap and var partitions) is locked up with Luks.
I booted my computer to an Arch live CD and attempted to mount the root filesystem, though wasn't exactly sure how to go about doing it (I tried several methods). First I tried just opening the root logical volume and mounting that.
# cryptsetup luksOpen /dev/sda3 rootvol
# mount /dev/mapper/rootvol /mnt
This resulted in the system alerting me that the device I was trying to mount was an LVM2 member and that the system could not do it. So next I tried opening the entire Volume Group.
# cryptsetup luksOpen /dev/sda3 VolGroup00
# mount /dev/mapper/VolGroup00 /mnt
Which, as I expected did not work. However, when I tried to mount the root volume again (having opened the entire Volume Group)
# mount /dev/mapper/VolGroup00-rootvol /mnt
and
# mount /dev/VolGroup00/rootvol /mnt
the system alerted me that the device I was trying to mount did not exist, which is odd considering that running
# lvdisplay /dev/VolGroup00
showed all of my logical volumes to exist at the locations /dev/VolGroup00/foo.
I could really use some guidance here. I know that I'm probably missing something very stupid and obvious, but I cannot for the life of me see it. Thank you for your time.
Douglas Bahr Rumbaugh, Jr.
Last edited by douglasr (2013-06-23 23:14:56)After the luksOpen I believe you need
vgchange -a y -
Libvirt: Unable to define LVM storage pool
Hello,
I'm trying to define an LVM storage pool for my virtual machines using KVM/libvirt. The configuration looks like this:
<pool type="logical">
<name>vol0</name>
<source>
<device path="/dev/md0"/>
</source>
<target>
<path>/dev/vol0</path>
</target>
</pool>
The problem is, that this LVM group is already active (other vms running using volumes inside this group) and 'virsh pool-start vol0' wants me to disable it. Is there any way to start the pool without "deactivate" the volume group?
virsh pool-start vol0
error: internal error '/sbin/vgchange -an vol0' exited with non-zero status 5 and signal 0: Can't deactivate volume group "vol0" with 14 open logical volume(s)
Further, I'm a bit curious that libvirt might recreate the volume group and therefore deletes all the content during the building process.
Would appreciate any advice
Regards,
Jonasmaahes wrote:
did so now, only now I'm getting a slightly different error: could not find udevd no such file or directory. I checked both grub.cfg's and my mkinitcpio.conf and there's no listing for udevd ....which I've never heard of, so I assumed it was a typo?
For clarification: udev is in the mkinitcpio.
I'm not sure whether I yet have a good intuition for how you have your machine set up, but I suspect you need to include a cryptdevice flag to the kernel in your grub config. The file isn't found because the kernel doesn't know your root directory needs decrypting first.
My setup is an LVM over LUKS over LVM sandwich. To boot into my system, the grub.cfg contains the line:
linux /vmlinuz-linux root=/dev/mapper/cryptvg-root cryptdevice=/dev/mapper/vg-crypt:root rootfstype=ext4 pcie_aspm=force acpi_osi=Linux acpi_backlight=vendor i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 ro
Now, most of those flags don't have anything to do with your problem, but note the cryptdevice. It tells the kernel it's dealing with an encrypted filesystem sitting in a logical volume called crypt on a volume group called vg. The bit after the colon tells the kernel to associate this encrypted filesystem with /dev/mapper/root.
As for how to fix your system, I'm afraid I still feel a bit fuzzy about how your LVM and encrypted layers relate to each other, whether you have LVM over LUKS, or LUKS over LVM, or something else. Was there a particular how-to that you followed? -
[SOLVED] Newbie asks how to suggest edits to LVM Luks Wiki page...
I'm a newb to Arch. I've been using Fedora for about four years, so Arch is a fun challenge. And I wish to contribute to the clarity of the Wiki page. Having set up LUKS with LVM for Fedora twice, and now Arch, one or two points might benefit the following wiki pages.
First, The instructions for kernel parameters on Kernel parameter configuration of the bootloader refers to the kernel parameter as:
cryptdevice=<device>:<dmname>
<device>
The path to the raw encrypted device. Usage of Persistent block device naming is advisable.
<dmname>
The name given to the device after decryption, will be available as /dev/mapper/<dmname>. (<dmname> MUST NOT be set to a name already used for LVM partitions!)
While higher up the page LVM on LUKS:
cryptsetup luksOpen /dev/sda3 lvmpool (alternate)
For setting up LVM ontop the encryption layer the device file for the decrypted volume group would be anything like /dev/mapper/lvmpool instead of /dev/sda3. LVM will then give additional names to all logical volumes created, e.g. /dev/mapper/lvmpool-root and /dev/mapper/lvmpool-swap.
The alternate reflects the LVM setup which seems to be a best practice in Fedora. My working setup is
cryptdevice=/dev/sda3:<LVMvolumeGroup>
. And when mounting the LUKS partitions I found it necessary to activate the volume group name with
#vgchange -ay <volumeGroup>
In that scenario the configuration install was:
# cryptsetup luksFormat -y --cipher aes-xts-plain --key-size 512 /dev/sda3
# cryptsetup luksOpen /dev/sda3 cryptVG
# pvcreate /dev/mapper/crypt
# vgcreate cryptVG /dev/mapper/crypt
# lvcreate -n root -L 20.0G cryptVG
# lvcreate -n swap -L 6.0G cryptVG
# lvcreate -n data -l 100%FREE cryptVG
/** For Arch you're applying the file-systems now, but in Fedora, the Anaconda installer takes care of it.**/
# cryptsetup luksClose crypt
For me, as a newbie setting up the two L's I found it easier to understand LVM as logical volumes in a volume group. Not sure how much this matters in theory, but in practice as a newbie setting up the two L's, I found it easier to understand LVM as logical volumes in a single volume group. Mainly because the Anaconda installer was automatically setting up the volume group name, and when I used the above setup, my custom name was reflected in Anaconda's GUI.
Second, The omnious Bang'd warning not to use 'a name already used for LVM partitions' seemed to conflict with the GRUB page instructions, until I noticed the GRUB page didn't include LVM. Given the popularity of LUKS and LVM solutions, it seems some hyperlinking notes would be appropriate. Yes?
And maybe third... I was working on a GRUB config issue and couldn't find any reference in the GRUB wiki page to explain to me the difference between GRUB_CMDLINE_LINUX and GRUB_CMDLINE_LINUX_DEFAULT (or more importantly, something to explain putting commands into one, the other or both). The GRUB wiki instructs to put the encryption parameter on the former, and dm-luks instructs to put it ... well, it doesn't state where to put the encryption parameters, and simply refers to Kernel parameters page.
Last edited by xtian (2013-09-17 22:00:44)As stated by WonderWoofy, you are more than welcome on the wiki! Just register and edit the article, but I'd like to add that you (like everyone else) are very warmly invited to always explain each of your edits exhaustively using the Edit Summary at the bottom of the Editor page; if the explanation is so long that doesn't fit in the summary, open a discussion in the talk page and link to that discussion from the summary itself. Last thing, don't do big edits all at once, but prefer splitting your work in a series of little edits: this will help everybody understand what you've done, since the resulting diffs will be much clearer.
Edit: typo
Last edited by kynikos (2013-09-01 04:56:26) -
Pacman induces kernel panic (intermittent)
Hello Archers,
I've got a fresh Arch install. I'm working my way through syncing packages I want from pacman. Two times now, a call to "pacman -S" has resulted in a kernel panic requiring a hard reboot.
I've booted into my Arch CD - it was still sitting in the drive anyway - and recovered the kernel and pacman logs.
$ tail -22 kernel.log
Jan 22 09:43:42 localhost kernel: [ 82.840043] NET: Unregistered protocol family 10
Jan 22 09:44:09 localhost kernel: [ 110.618188] NET: Registered protocol family 10
Jan 22 09:44:09 localhost kernel: [ 110.618491] PERCPU: allocation failed, size=252 align=4, failed to allocate new chunk
Jan 22 09:44:09 localhost kernel: [ 110.618494] Pid: 751, comm: modprobe Not tainted 3.2.1-1-ARCH #1
Jan 22 09:44:09 localhost kernel: [ 110.618496] Call Trace:
Jan 22 09:44:09 localhost kernel: [ 110.618502] [<c0473180>] ? printk+0x1d/0x1f
Jan 22 09:44:09 localhost kernel: [ 110.618506] [<c01f335b>] pcpu_alloc+0x7ab/0x810
Jan 22 09:44:09 localhost kernel: [ 110.618517] [<f830fe1b>] ? __addrconf_sysctl_register+0xab/0xf0 [ipv6]
Jan 22 09:44:09 localhost kernel: [ 110.618521] [<c03d9b4e>] ? neigh_parms_alloc+0x6e/0x100
Jan 22 09:44:09 localhost kernel: [ 110.618524] [<c047afc2>] ? _raw_write_unlock_bh+0x22/0x30
Jan 22 09:44:09 localhost kernel: [ 110.618526] [<c01f33cf>] __alloc_percpu+0xf/0x20
Jan 22 09:44:09 localhost kernel: [ 110.618529] [<c0428ee8>] snmp_mib_init+0x18/0x30
Jan 22 09:44:09 localhost kernel: [ 110.618539] [<f83111a1>] ipv6_add_dev+0x121/0x440 [ipv6]
Jan 22 09:44:09 localhost kernel: [ 110.618548] [<f80c52da>] addrconf_init+0x4b/0x1a1 [ipv6]
Jan 22 09:44:09 localhost kernel: [ 110.618551] [<c03ca5ad>] ? register_pernet_subsys+0x2d/0x40
Jan 22 09:44:09 localhost kernel: [ 110.618559] [<f80c5179>] inet6_init+0x179/0x280 [ipv6]
Jan 22 09:44:09 localhost kernel: [ 110.618562] [<c0101125>] do_one_initcall+0x35/0x170
Jan 22 09:44:09 localhost kernel: [ 110.618568] [<f80c5000>] ? 0xf80c4fff
Jan 22 09:44:09 localhost kernel: [ 110.618570] [<c0182acd>] sys_init_module+0x91d/0x1af0
Jan 22 09:44:09 localhost kernel: [ 110.618576] [<c047be1f>] sysenter_do_call+0x12/0x28
Jan 22 09:44:10 localhost kernel: [ 111.030054] NET: Unregistered protocol family 10
Jan 22 09:44:54 localhost kernel: [ 155ai.417609] EXT2-fs (sda10): warning: mounting unchecked fs, running e2fsck is recommended
$ tail -5 pacman.log
[2012-01-22 09:43] synchronizing package lists
[2012-01-22 09:43] starting full system upgrade
[2012-01-22 09:44] Running 'pacman -S cpio'
[2012-01-22 09:44] installed cpio (2.11-2)
[2012-01-22 10:17] Running 'pacman -S gvim'
$ lspci -nnmvk
Pastebin
$ lsmod
Module Size Used by
ext2 54892 1
snd_hda_codec_hdmi 21777 4
snd_hda_codec_realtek 149985 1
nouveau 680909 0
snd_usb_audio 75510 0
snd_usbmidi_lib 15644 1 snd_usb_audio
video 9716 1 nouveau
snd_rawmidi 15014 1 snd_usbmidi_lib
mxm_wmi 1101 1 nouveau
drm_kms_helper 22653 1 nouveau
ttm 45781 1 nouveau
drm 151588 3 ttm,drm_kms_helper,nouveau
agpgart 22255 2 drm,ttm
i2c_algo_bit 4487 1 nouveau
arc4 1086 2
snd_hda_intel 20050 0
snd_hda_codec 75987 3 snd_hda_intel,snd_hda_codec_realtek,snd_hda_codec_hdmi
snd_pcm 60595 4 snd_hda_codec,snd_hda_intel,snd_usb_audio,snd_hda_codec_hdmi
snd_page_alloc 5869 2 snd_pcm,snd_hda_intel
snd_hwdep 4942 2 snd_hda_codec,snd_usb_audio
firewire_ohci 27475 0
uvcvideo 57039 0
videodev 71421 1 uvcvideo
ath9k 77023 0
snd_seq_device 4284 1 snd_rawmidi
snd_timer 15438 1 snd_pcm
usb_storage 35343 0
media 8641 2 videodev,uvcvideo
snd 44501 11 snd_timer,snd_seq_device,snd_hwdep,snd_pcm,snd_hda_codec,snd_hda_intel,snd_rawmidi,snd_usbmidi_lib,snd_usb_audio,snd_hda_codec_realtek,snd_hda_codec_hdmi
firewire_core 43511 1 firewire_ohci
i2c_piix4 7084 0
ath9k_common 1604 1 ath9k
uas 6440 0
wmi 7263 1 mxm_wmi
i2c_core 16816 6 i2c_piix4,videodev,i2c_algo_bit,drm,drm_kms_helper,nouveau
usblp 9335 0
floppy 48805 0
serio_raw 3357 0
processor 23026 0
pcspkr 1375 0
k10temp 2139 0
crc_itu_t 1095 1 firewire_core
ath9k_hw 333834 2 ath9k_common,ath9k
button 3614 1 nouveau
evdev 7278 0
joydev 7439 0
r8169 41700 0
soundcore 5018 1 snd
ath 11990 3 ath9k_hw,ath9k_common,ath9k
mac80211 203700 1 ath9k
cfg80211 147716 3 mac80211,ath,ath9k
rfkill 12470 1 cfg80211
mii 3407 1 r8169
sp5100_tco 3760 0
aes_generic 25702 16
xts 1929 8
gf128mul 5950 1 xts
hid_logitech 14192 0
ff_memless 3895 1 hid_logitech
dm_crypt 13591 1
dm_mod 60337 17 dm_crypt
usbhid 31263 1 hid_logitech
hid 66367 2 usbhid,hid_logitech
sr_mod 13244 0
cdrom 31437 1 sr_mod
sd_mod 26211 7
pata_jmicron 1644 2
ohci_hcd 19119 0
pata_atiixp 2984 0
ahci 17529 2
pata_acpi 2388 0
libahci 16783 1 ahci
libata 146606 5 libahci,pata_acpi,ahci,pata_atiixp,pata_jmicron
ehci_hcd 36010 0
xhci_hcd 69730 0
scsi_mod 112826 5 libata,sd_mod,sr_mod,uas,usb_storage
usbcore 122501 11 xhci_hcd,ehci_hcd,ohci_hcd,usbhid,usblp,uas,usb_storage,uvcvideo,snd_usbmidi_lib,snd_usb_audio
usb_common 622 1 usbcore
ext4 377865 2
crc16 1091 1 ext4
jbd2 60273 1 ext4
mbcache 4281 2 ext4,ext2
$ grep "^MODULES\|^HOOKS\|^DAEMONS" /etc/{rc,mkinitcpio}.conf
/mnt/etc/rc.conf:MODULES=()
/mnt/etc/rc.conf:DAEMONS=(hwclock syslog-ng dbus iptables network netfs crond sshd)
/mnt/etc/mkinitcpio.conf:MODULES="ext4"
/mnt/etc/mkinitcpio.conf:HOOKS="base udev autodetect pata scsi sata keymap lvm2 encrypt lvm2 resume filesystems usbinput"
It seems to happen when pacman tries to use the network. The kernel log also seems to suggest a network problem.
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 6c:f0:49:ee:a7:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global eth0
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
link/ether 94:0c:6d:c9:63:26 brd ff:ff:ff:ff:ff:ff
$ ip route
default via 192.168.1.1 dev eth0 metric 202
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 202
I haven't had any kernel panics when using any other network programs, just pacman. I can ping google by name and I can scp to my laptop running on the WLAN.
I tried googling, using the wiki, and searching the forums, but all kernel-panic related problem seem to happen at boot time, not in the process of using pacman.
Some other things about my system that may or may not affect things: it's an LVM over LUKS over LVM, the lowest LVM sits across several hard-drives, and it's got an AMD64 processor but I installed off an i686 iso.
Does anyone have any ideas?I just generated another kernel panic while trying to sync fuse, openssh and sshfs from pacman.
I now notice something not captured by either the kernel log or the pacman log. Before the call trace begins, I also get this message:
:: Retrieving packages from extra...
[ 8340.507133] Kernel panic - not syncing: cannot create neighbour cache statistics
Still looking for ideas here. It's really weird that pacman can work properly for a while and then all of a sudden causes a kernel panic. -
I scanned an old image using my Epson NX515 printer, used GIMP to make some minor repairs on the image and printed it out. I noticed there were a number of evenly spaced thin blue lines across the image, approximately six of them. I opened & printed the image on my PC using PAINT.NET. No lines appeared. I sent the image to my daughter. She printed it and found no lines. I printed the image using Seahorse on my Mac and the lines still appeared. I used basically the same print settings on Mac and PC.
maahes wrote:
did so now, only now I'm getting a slightly different error: could not find udevd no such file or directory. I checked both grub.cfg's and my mkinitcpio.conf and there's no listing for udevd ....which I've never heard of, so I assumed it was a typo?
For clarification: udev is in the mkinitcpio.
I'm not sure whether I yet have a good intuition for how you have your machine set up, but I suspect you need to include a cryptdevice flag to the kernel in your grub config. The file isn't found because the kernel doesn't know your root directory needs decrypting first.
My setup is an LVM over LUKS over LVM sandwich. To boot into my system, the grub.cfg contains the line:
linux /vmlinuz-linux root=/dev/mapper/cryptvg-root cryptdevice=/dev/mapper/vg-crypt:root rootfstype=ext4 pcie_aspm=force acpi_osi=Linux acpi_backlight=vendor i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 ro
Now, most of those flags don't have anything to do with your problem, but note the cryptdevice. It tells the kernel it's dealing with an encrypted filesystem sitting in a logical volume called crypt on a volume group called vg. The bit after the colon tells the kernel to associate this encrypted filesystem with /dev/mapper/root.
As for how to fix your system, I'm afraid I still feel a bit fuzzy about how your LVM and encrypted layers relate to each other, whether you have LVM over LUKS, or LUKS over LVM, or something else. Was there a particular how-to that you followed?
Maybe you are looking for
-
Creating a role for t.code FBL1N
Hi All, Creating a role (PFCG), I've to assign the t.code FBL1N only. In this role and for the t.code FBL1N, I've to exclude a certain Vendor Account Group. Could anyone help me? Thanks
-
It used to be if you did a search for "monsters" and selected a web page from the results list, the term "monsters" would be highlighted at the top of the page. You could then click on "monsters" and you would jump to the place on the web page where
-
Is the iphone 4S bought in US compatible to use in Singapore
Hi, I have this URGENT question as i would like to purchase the lastest Iphone 4S but i do not know whether it is compatible to use in Singapore.Thank You for your help. Regards, Leong
-
Unable to upload photos to MobileMe
Hi all, I've enabled the 'adding of photos via email or iphone' setting in my web gallery, yet when I take a photo and use the 'send to MobileMe' option on my iphone, I get 'Your MobileMe gallery has no shared albums'. But it does. Anyone have any id
-
Can you make the "Apply CSS Class" part of the editor bigger?
Hi there... Just wondering - is it possible to make the "Apply CSS Class" editor window larger... It's TINY. (about 200px Square) As a result I can't see many of the classes... Cheers, Dave