S2disk mkinitcpio.conf question

Hi there,
I wasted some hours today to get hibernation working properly.
My setup is an unencrypted /boot partition and an encrypted lvm volume group which contains swap and root partitions.
Using uswsusp (because of the s2both feature) I followed this ("poorly written") guide: https://wiki.archlinux.org/index.php/S2 … e_intramfs
Putting the uresume hook before filesystems as mentions in the article, it always complaint it couldn't read the snapshot file.
Then I tried to put the uresume - hook _after_ (on the right side of) the filesystems hook in /etc/mkinitcpio.conf and it worked.
The snapshot file comes with the root filesystem which you have to mount first, so thats logical anyway.
My question here is: Am I doing the right thing here? If yes, why is this part of the article completely wrong? Not very helpful ...
greetings
rd

My configuration is the same as yours, and my hooks look like this:
HOOKS="base udev autodetect pata lvm2 uresume filesystems"
More generally - It's a wiki, which means it can be wrong. Correct it, and enjoy the warm glow that contributing creates.

Similar Messages

Installing Arch w/ LVM: how to mount and when to edit mkinitcpio.conf?

Hi,
about half way down this script (link at bottom) the guy has
genfstab /mnt >> /etc/mnt/fstab
should it be
genfstab /mnt >> /mnt/etc/fstab
because I keep getting "file or directory not found" with /etc/mnt/ but the reverse worked.
I don't know jack about linux so I figured I better check in with you all first before I continue.
Thanks!
http://blog.portnumber53.com/2012/10/30 … installer/
Last edited by hbc2 (2014-07-28 03:36:11)

Yes, both the Beginners guide and the Installation guide excellent. I studied them (and others) for about two weeks before even downloading the install iso. Also, I’ve read the Arch Way and it’s for me.
The script that I dug up wasn't just random. It turned up in a google search when I was looking for more info on setting up LVM partitions. The first half of that script turned out to be nearly identical to the notes that I had made from reading those guides as well as the LVM guide.
The Beginners and LVM guides are great (!) I learned a lot and I appreciate their attempt to be linear step by step. I also understand the LVM can’t be placed “inside” the Beginners guide since not everyone will want LVM.
However I ran into a spot of confusion regarding the mounting of the partitions between the Beginners Guide and the LVM guide – and that’s what lead me to the question about the path in that guy’s script (“/etc/mnt” vs “/mnt/etc”). Also, the LVM guide seems to indicate editing “/etc/mkinitcpio.conf” (note the path) at a point BEFORE I run “pacstrap -i /mnt base base-devel” and genfstab.
Below are the linear install steps that I attempted. In summary, I’m not sure about the mounting or when/where to edit mkinitcpio.conf.
Boot the install iso and set up the partitions.
[All GOOD]
Create physical volume, Vol group and logical vols
pvcreate /dev/sda2
vgcreate arch /dev/sda2
lvcreate -L 1G -n boot arch
lvcreate -C y -L 4G -n swap arch
lvcreate -L 100G -n root arch
lvcreate -L 100G -n home arch
[All GOOD]
Create file systems and mount logical volumes
mkfs.ext4 /dev/mapper/arch-root
mkfs.ext4 /dev/mapper/arch-boot
mkfs.ext4 /dev/mapper/arch-home
mkswap /dev/mapper/arch-swap
mount /dev/mapper/arch-root /mnt
[All GOOD]
Here's where my confusion starts:
Beginner's Guide (in "Mount the partitions" section) seems to indicate this way:
mkdir /mnt/boot
mkdir /mnt/home
mount /dev/mapper/arch-home /mnt/home
mount /dev/mapper/arch-boot /mnt/boot
LVM Guide (in "Create file systems and mount logical volumes") seems to indicate this way:
mount /dev/mapper/arch-home /home
mount /dev/mapper/arch-boot /boot
I'm not sure which of the above I need to go with. (Probably just a matter of preference?)
Then the LVM Guide seems to want me to "Edit [/etc/mkinitcpio.conf] and insert lvm2 between block and filesystems" but how should I access that file at "/etc"? I think I'd have to run "pacstrap -i /mnt base base-devel" first but the LVM guide seems to indicate doing this right after I mount the logical volumes - I probably misunderstand something here. (I can't find it anyway at this point using either mount method above.)
The rest I'll do right out of the beginners guide:
pacstrap -i /mnt base base-devel
swapon /dev/mapper/arch-swap <<<<< I suspect I need this here before running genfstab to get the entry in the table
genfstab -U -p /mnt >> /mnt/etc/fstab
nano /mnt/etc/fstab
Then I'll follow the rest of the beginners guide and edit /etc/mkinitcpio.conf during the "Create an initial ramdisk environment" step/
(I actually got to the point in the beginners guide where I should be editing the /etc/mkinitcpio.conf after pacstrap but I could not find it and suspect either I didn't mount correctly or messed up the chroot step.)
Last edited by hbc2 (2014-07-28 03:48:52)

Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine. I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
Waiting for 10 seconds for device /dev/md2 ...
Root device '/dev/md2' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/md2'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
/bin/sh: can't access tty; job control turned off
[ramfs /]#
As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
I think I've included all the appropriate bits of config here that should be working. I assume I've missed something fundamental - any ideas?
menu.lst:
# (0) Arch Linux
title Arch Linux [/boot/vmlinuz26]
root (hd0,0)
kernel /vmlinuz26 root=/dev/md2 ro
initrd /kernel26.img
mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
fstab:
/dev/md1 /boot ext3 defaults 0 1
/dev/md2 / ext3 defaults 0 1
mdadm.conf
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
47a9fe:d45dbc0c
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
043406:dbdabe38
Thanks!

Hi magec, that's quite helfpul - I've certainly got further.
Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -o bind /dev /mnt/dev
mount -t proc none /mnt/proc
chroot /mnt /bin/bash
But based on your suggestion it's working better
mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
mount /dev/md2 /mnt
mount /dev/md1 /mnt/boot
mount -t proc none /mnt/proc
mount -t sysfs none /mnt/sys
mount -n -t ramfs none /mnt/dev
cp -Rp /dev/* /mnt/dev
chroot /mnt /bin/bash
The boot is now getting further, but now I'm getting:
md: md2 stopped.
md: bind<sdb2>
md: bind<sda2>
raid1: raid set md2 active with 2 out of 2 mirrors
md2: detected capacity change from 0 to 32218349568
mdadm: /dev/md2 has been started with 2 drives.
md2: Waiting 10 seconds for device /dev/md2 ...
unknown partition table
mount: mounting /dev/md2 on /new_root failed: No such device
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
/bin/sh: can't access tty; job contol turned off
[ramfs /]#
The bit that really confuses me is this:
[ramfs /]# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda2[0] sdb2[1]
31463232 blocks [2/2] [UU]
md1 : active raid1 sda1[0] sdb1[1]
208704 blocks [2/2] [UU]
unused devices: <none>
[ramfs /]# mount /dev/md2 /new_root
mount: mounting /dev/md2 on /new_root failed: No such file or directory
[ramfs /]# ls /dev/md2
/dev/md2
[ramfs /]#
So the array is up, the device node is there but it can't be mounted? Very strange.
Last edited by chas (2010-05-02 11:24:09)

[SOLVED] How to restore kernel image after wrong /etc/mkinitcpio.conf

I wanted to learn a bit more about the kernel and boot, and I'm afraid I cannot start up my ArchLinux anymore.
I updated the /etc/mkinitcpio.conf to make the boot faster (with this reference: http://kmandla.wordpress.com/2007/01/30 … initcpio/) and executed #mkinitcpio -p kernel26
I thought that if there was any problem, I could start up with the "fallback image". Certainly, there was a problem (probably I didn´t loaded all the modules required) and when I tried the fallback image, I experimented the same problem:
Root device '/dev/disk/by-uuid/...' doesn´t exist
ramfs$
In fact, both images are the same (or at least they have the same size)
I tried the ArchLinux liveCD to recover my system. There's no recovery service, so I started up the CD-ROM, mounted my ArchLinux partitions, generated the images and copied into the /boot of my Archlinux partitions. But the same problem is still there.
What could I do to fix it?
Thank you in advance
Last edited by jjjaime (2009-05-10 15:45:45)

Thank you. I follow your instructions and it worked (perhaps it would be simpler with a "#pacman -Sy kernel26"). I didn't know the command chroot and it's really interesting.
red_erik wrote:
I have a similar problem, (read more in this thread), and I solve it by booting off the Live CD, and doing the following:
(replace sda1 with your / partition)
cd /
mount -t ext3 /dev/sda1 /mnt
mount -t proc proc /mnt/proc
mount -t sysfs sys /mnt/sys
mount -o bind /dev /mnt/dev
chroot /mnt /bin/bash
mkinitcpio -p kernel26
after that, I exit chroot, unmount all of my partitions and reboot...:
cd /
umount -a
exit
cd /
umount -a
reboot
hope this helps...

Can I delete 'scsi' in mkinitcpio.conf !!

I have no scsi device in my system , but in lsmod
I found :
scsi_mod 96460 5 usb_storage,sg,sr_mod,sd_mod,libata
and in dmesg:
I found
SCSI subsystem initialized
scsi0 : ata_piix
scsi1 : ata_piix
scsi 0:0:0:0: Direct-Access ATA ST380817AS 3.42 PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM AOPEN CD-RW CRW2440 2.02 PQ: 0 ANSI: 5
Since my system spent so much time in boot process, so I want to remove scsi in mkinitcpio.conf to make it faster,
may I?
(sorry for my poor english.)

scsi Adds SCSI modules to the image. Use this if your root device is on a SCSI disk. Also use the autodetect hook if you want to minimize your image size. Loads SCSI modules. You will need the udev or modload hook unless you specify the needed modules manually (see MODULES section below).
I don't think I have the SCSI hook in any of my setups (I have a server with P-ATA disks, a laptop with a P-ATA SSD, and a desktop with S-ATA disks) and neither of them has an SCSI hook.
The terminology is a bit confusing indeed, since the SCSI transport layer is used afaik for both P-ATA and S-ATA devices with the libata layer. Nevertheless, since the explanation on the wiki page explicitly says the SCSI hook is for SCSI HDs (which, even with the libata layer, the P-ATA and S-ATA HDs are not, you have separate PATA and SATA hooks for them), I'd say you can just dump it.
You can always try to take it out, rebuild the image of the default kernel, and try to boot it. If it breaks, you just try again - with the fallback kernel (that's what it's there for). Just make sure you don't rebuild that one accidentally.
Last edited by B (2008-11-04 13:23:32)

[SOLVED]fsck hook with new mkinitcpio.conf

Last night when I upgraded mkinitcpio it provided a new mkinitcpio.conf file as a pacnew. When comparing this new file to my previous config file the only difference I found was that the new one included the fsck hook. From what I've read it says that this hook is strongly recommended but only gives a reason for it if you have a separate /usr partition, which I do not. I have separate /boot, /swap, /, and /home partitions. Should I include this hook? Does it hurt? Doesn't matter?
Last edited by Lexworth (2012-03-15 14:52:47)

karol wrote:
You should have checked the wiki https://wiki.archlinux.org/index.php/Mkinitcpio#HOOKS too:
Adds the fsck binary and filesystem specific helpers. If added after the autodetect hook, only the helper specific to your root filesystem will be added. Usage of this hook is strongly recommended, and it is required with a separate /usr partition.
I did check the wiki. I mentioned what I had gathered from my reading in my original post, perhaps you should have read it. I then went on to explain that this didn't give much indication for including the fsck hook without a separate /usr partition. So I came here (Newbie Corner) to ask if someone could help me with my understanding, which Gcool was so kind enough to do.

Mkinitcpio.conf: 'systemd' hook disables 'resume' hook

Hello y'all,
I just discovered that the 'systemd' hook in mkinitcpio.conf disables resuming from hibernation on my system. After I switched back to 'udev', it works all fine again.
Can any of you confirm this, and if so, should we mention it on the wiki page? https://wiki.archlinux.org/index.php/Mk … mmon_hooks

Hello y'all,
I just discovered that the 'systemd' hook in mkinitcpio.conf disables resuming from hibernation on my system. After I switched back to 'udev', it works all fine again.
Can any of you confirm this, and if so, should we mention it on the wiki page? https://wiki.archlinux.org/index.php/Mk … mmon_hooks

Xorg.conf question

I am kind of embarassed to ask this question, but I have to. Where do I find xorg.conf? Do I even have such a file? It is not in /etc/X11.
When I installed Xorg, I also installed hal and then added it to module list in rc.conf. Does hal just detect my xorg settings everytime I run X, thus eliminating the need for xorg.conf?

The only solution was to boot from a live distro and edit the xorg.conf from there. I think the problem was the missing hal daemon - im not sure.
There's a much easier way - boot into single user mode (either add "single" or "init=3" to the kernel line in grub) and edit your xorg.conf using nano or any other text editor.
Now, hal is *required* as long as you don't have Option "AutoAddDevices" "False" in your xorg.conf. If you try to start X without having hal running, you will not be able to use your mouse/keyboard (again, if this happens, boot into single user mode and edit your xorg.conf). If you disable hotplugging (AutoAddDevices false), hal is optional (correct me if i'm wrong), but many features of KDE/Gnome depend on hal and won't work without it.
Personally, I'd recommend going with hotplugging and hal. First, try starting X without an xorg.conf. If everything looks good, you're done (on my notebooks I don't have xorg.conf). You might need xorg.conf to set stuff like your screen resolution - generate it (if you have an nvidia gfx card, use nvidia-xconfig), but make sure there are no lines concerning your mouse/keyboard in xorg.conf.
And, like paulez posted, you will need xf86-input-evdev.

Which hard-drive modules should I load for the mkinitcpio.conf file?

Hey all, I've always been confused by all the weird module names in the image files, anyway, here goes, since I have a laptop, I won't be upgrading my harddrive to a new interface. but.. that's not the problem, the problem is I don't know which modules I need to load for my hard-drive, here are some outputs from lspci, hdparm etc. Any help is appreciated!
lspci
00:14.1 IDE interface: ATI Technologies Inc Standard Dual Channel PCI IDE Controller (prog-if 8a [Master SecP PriP])
Subsystem: Hewlett-Packard Company Unknown device 30ae
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 17
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at 8410 [size=16]
Capabilities: <access denied>
hdparm
[bolu@presario ~]$ sudo hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: ST980829A
Serial Number: 5PK1LAHQ
Firmware Revision: 3.05
Standards:
Used: ATA/ATAPI-6 T13 1410D revision 2
Supported: 6 5 4
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156301488
device size with M = 1024*1024: 76319 MBytes
device size with M = 1000*1000: 80026 MBytes (80 GB)
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Advanced power management level: unknown setting (0x8080)
Recommended acoustic management value: 254, current value: 0
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
* Advanced Power Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* IDLE_IMMEDIATE with UNLOAD
* SMART Command Transport (SCT) feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 0 determined by CSEL
Checksum: correct

Do you have any problem with your current mkinitcpio setup, or why do you ask this?
If it works with the defaults, it's probably a good idea not to mess with it.
Okay, that's that and now for the adventerous part...
Here's a minimal setup that works for me:
MODULES="pata_hpt37x sd_mod jfs"
HOOKS="base udev"
You'd probably need to use pata_atiixp instead of pata_hpt37y, and whatever filesystem you use for / instead of jfs. In case you use encryption, lvm etc., take care to include the necessary hooks.

Silly makepkg.conf question

Does makepkg.conf dictate "make" behavior as well as "makepkg" behavior ?
For instance if I use MAKEFLAGS="-j3" will I be able to benefit from it using regular "make" ?

Cerebral wrote:
Well, if you want default CFLAGS and CXXFLAGS you can just set them before the alias:
export CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer"
export CXXFLAGS=${CFLAGS}
alias make='make -j3'
That would work as well.
Ah, brilliant, thank you. There's what I was looking for. I am assuming that this should work whether I put it in /etc/profile or ~/.bashrc. (I only have 1 user and root.)

/etc/pacman.conf question..

This may have been asked before, but I could not find it...
<yes, I did use the search on the forums... >
I was wondering if the NoUpgrade option in pacman.conf uses shell-like wildcard expansion...
Does the following work?
NoUpgrade = etc/host*
shell expansion should expand this to
/etc/host.conf
/etc/hosts
/etc/hosts.allow
/ec/hosts.deny
will pacman do the same?

No, but it would be nice to have something like that (or perhaps better with regexp)
BTW, regexp support for targets was already in pacman wishlist.
I've added noupgrade/ignorepkg options to it.
To be continued...

Few rc.conf questions

deleted
Last edited by Misbah (2012-02-14 05:48:14)

Misbah wrote:for Keymap, why do I use "us" instead of us.map.gz? Any difference?
No difference, loadkeys knows to loop for us.map or us.map.gz. You would end up with the same setup using either us or us.map.gz.
Misbah wrote:for Consolefont, I presume this just changes the font in vc, and has no affect on fonts anywhere within the desktop environment once X is started? How can I visibly browse these fonts, and what fonts are allowed to be installed? Ones retrieved from pacman only? Do I just drop them in the /usr/share/kbd/consolefonts folder?
Yes, CONSOLEFONT only affects the font for the consoles (imagine that!) It has no effect on X fonts. I'm not sure if there is any software to browse the fonts on your system, but there probably is. To see the fonts with standard tools you'd have to go to a console and then run setfont (see "man setfont" for more details.) Linux uses the psf format for its console fonts, so presumably you could download any PSF font, put it in /usr/share/kbd/consolefonts. (Actually it will accept some other legacy formats as well, I just don't know what they are.) Pacman does have some nice console fonts, like terminus, but any PSF font should work.
Misbah wrote:what does Consolemap set exactly?
I'm a bit hazy on this one myself, but it does the job of translating 8-bit (ASCII/ISO-8859, etc.) program output to 16-bit Unicode values so the output can be displayed on a UTF-8 console. Usually you won't need this as most good console fonts will have a Unicode font map built in. See the UNICODE FONT MAPS section of "man setfont" for more details.
Misbah wrote:USECOLOR...What portion of the vconsole does this affect?
Like the rc.conf states, it colorizes messages during startup. I assume this means that this determines if color is used once the initcpio is booted and init is launched.
Regards,
j

Rc.conf questions!

Hi,
Need help to configure the rc.conf file...
Current:
LOCALE="sv_SE.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Stockholm"
KEYMAP="sv-latin1"
Cant start conky couse it says: Cant set the specified locale!
And the keymap isnt working either...

http://wiki.archlinux.org/index.php/Locale
I think maybe you need to follow the steps in the wiki. I know that I often forget to run "locale-gen" as root. Hope that helps get you started.

[Solved] Quick question about mkinitcpio upgrade

I just ran pacman -Syu and got the following message:
(4/8) upgrading mkinitcpio [######################] 100%
==> If your /usr is on a separate partition, you must add the "usr" hook
to /etc/mkinitcpio.conf and regenerate your images before rebooting
I'm just wondering, what counts as a separate partition? My partitions contain:
/boot
/home
swap
My /usr is presumably on the / partition, which is "separate" from the boot partition where the kernel images are. Do I have to do anything?
Last edited by eggplantbren (2012-05-24 03:00:37)

eggplantbren wrote:
I just ran pacman -Syu and got the following message:
(4/8) upgrading mkinitcpio [######################] 100%
==> If your /usr is on a separate partition, you must add the "usr" hook
to /etc/mkinitcpio.conf and regenerate your images before rebooting
I'm just wondering, what counts as a separate partition? My partitions contain:
/boot
/home
swap
My /usr is presumably on the / partition, which is "separate" from the boot partition where the kernel images are. Do I have to do anything?
THANK YOU MAAN...
I'm so GLAD that you post this here, it's 2 days ago I updated my Archlinux, and after update and reset I didn't use to login to it.
I know that problem should be near MKINITCPIO but I didn't know where.
But today I read your post and after it I boot to archlinux by liveISO and update mkinitcpio again with MISSED parameter "usr".
Well done boy...
Thank you so much
Have a nice day.

Mkinitcpio question

I know I'm a little behind with this change over to mkinitcpio, but I thought it would be wise to ask before upgrading.
I have a software raid setup using md0 as root, and two other arrays as md1 and md2.
Anyway, I think this is all I need to do before upgrading to the new 26.18 kernel and mkinitcpio......
Add raid to mkinitcpio.conf...
HOOKS="base udev raid autodetect ide scsi sata filesystems"
hmm, I thought it might be wise to put (raid) before autodetect, or does it matter?
Changes to my my grub Menu.lst
root (hd0,0)
kernel /vmlinuz26 pci=conf1 root=/dev/md0 ro md=0,/dev/sda3,/dev/sdb3 md=1,/dev/sda1,/dev/sdb1 md=2,/dev/sda2,/dev/sdb2 vga=773
initrd /kernel26.img
and menu entry #2 same as above except...
initrd /kernel26-fallback.img
Before I actually do this upgrade, I wanted to ask if the above looks reasonable, or if it looks like I'm on the right track with these changes...?
also, I wanted to ask
Will there be a problem using the kernel option pci=conf1 with mkinitcpio and kernel 26.18 ?

Leigh wrote:hmm, I thought it might be wise to put (raid) before autodetect, or does it matter?
autodetect is sneaky. It actually does nothing at runtime, only when it builds the image. Basically, I read it as "everything after this is autodetected" - so your raid modules will be installed in full (I think) instead of specific to your system.
Leigh wrote:Will there be a problem using the kernel option pci=conf1 with mkinitcpio and kernel 26.18 ?
Not sure... I doubt it though. What does this option do?

S2disk mkinitcpio.conf question

Similar Messages

Maybe you are looking for