Differences

This shows you the differences between two versions of the page.

--- linux:filesystems:boot [2012/04/25 17:08]
tkilla
+++ linux:filesystems:boot [2022/11/06 21:39] (current)
tkilla
@@ Line 1: / Line 1: @@
-====== boot ======
+====== Bootloader ======
 **linux boot process tricks**
-=== howto clone harddisc and boot new system ===
+==== howto clone harddisc and boot new system ====
 **To transfer all system files,** it's best to get a live USB-stick or CD and boot into it \\
@@ Line 13: / Line 13: @@
   rsync -a -v -z -h --perms -E -o -g  --times --compress --update --delete \
-        --exclude="/proc/*" --exclude="/sys/*" --exclude="/mnt/*" --exclude="/media/*"
+        --exclude="/proc/*" --exclude="/sys/*" --exclude="/mnt/*" --exclude="/media/*" / /mnt/newsys/
+-> may cause strange bugs, like permissions in /var/run/, maybe /dev probs
 . simple **copy** with "**cp**" (untested):
@@ Line 25: / Line 26: @@
-. **gparted** - no ext4, only from livesystems
+. **parted** - no ext4, only from livesystems
 etc...
@@ Line 55: / Line 56: @@
 **generate a new (/mnt/newsys) /boot/grub/grub.cfg**:
   update-grub
+In case of error "no such disc" run
+  grub-mkdevicemap
 **Install to the MBR (no partition number) of the new disc, finally:**
   grub-install /dev/sdX
+reboot & good luck!
+----
 \\
-reboot & good luck!
+** initramfs **
+the step after the bootloader needs all (fs, rais,..) modules to mount root, check: /etc/initramfs-tools/modules
+update existing initramfs:
+  update-initramfs -u -k all
+** RAID **
+if you changed your raid setup, you need to update initramfs:
+  dpkg-reconfigure mdadm
+make sure these modules are in /etc/initramfs-tools/modules
+  raid0
+  raid1
+  md
 \\
-References:
+References: http://unix.stackexchange.com/questions/5297/debian-grub2-moving-root-partition-to-new-drive
+\\
+==== howto boot from grub2 rescue console ====
+If you drop to the grub rescue after cloning a system disc or something, it's possible to boot an existing system.
+Enter this, to start a system on sda3 for example:  sda = hd0 + partition 3 = (hd0,3)
+  set prefix=(hd0,3)/boot/grub
+  insmod (hd0,3)/boot/grub/linux.mod
+if this works, the console gets upgraded to standard grub console.
+if it doesn't work, try another partition. grub counts partitions from 1 (not 0), btw.
+This boots arch linux:
+  set root=(hd0,3)
+  linux /boot/vmlinuz26 root=/dev/sda5
+  initrd /boot/kernel26.img
+  boot
+This is required to boot debian - unfortunately the filenames contain versionnumbers :(
+  set root=(hd0,3)
+  linux /boot/vmlinuz-3.1.0-1-amd64 root=/dev/sda3
+  initrd /boot/initrd.img-3.1.0-1-amd64
+  boot
+This should boot your system. Just re-install grub:
+  update-grub
+  grub-install /dev/sdX
+===== Bugs =====
+Inside a chroot, grub complains
+  # update-grub
+  Generating grub configuration file ...
+  WARNING: Device /dev/ram0 not initialized in udev database even after waiting 10000000 microseconds.
+  ...
+Fix:
+Outside chroot /debian/:
+  mkdir /debian/run/udev
+  mount --bind /run/udev /debian/run/udev
+  mount --bind /run/udev /mnt/run/udev
+===== Crypto Bugs =====
+Grub complains root device couldn't be found
+Fix:
+- set
+  GRUB_ENABLE_CRYPTODISK=y
+  apt install cryptsetup-initramfs lvm2
+- if it is a brtfs, set in /etc/initramfs/modules
+  btrfs
+Commands to execute in chroot to reinstall grub:
+  update-initramfs -c -k all
+  grub-install /dev/sdX
+  update-grub
+If update-grub echos: "cannot find device for / in fstab" and you have a btrfs rootsys:
+  mount -o "subvol=@" /dev/mapper/vgubuntu-root
-http://unix.stackexchange.com/questions/5297/debian-grub2-moving-root-partition-to-new-drive
+is required to mount the @ subvol!

fr33.info

User Tools

Site Tools

Differences

Page Tools