Skip to main content
increased the address of initrd, because the previous one does not work with some kernels see https://archlinuxarm.org/forum/viewtopic.php?f=31&t=8304 and added hint to modprobe configs
Source Link

In case there is no config.gz in /proc, first run this:

sudo modprobe configs
initramfs initrd 0x00f000000x01f00000
...root=/dev/mmcblk0p1 initrd=0x00f00000initrd=0x01f00000 rootfstype=ext4...
initramfs initrd 0x00f00000
...root=/dev/mmcblk0p1 initrd=0x00f00000 rootfstype=ext4...

In case there is no config.gz in /proc, first run this:

sudo modprobe configs
initramfs initrd 0x01f00000
...root=/dev/mmcblk0p1 initrd=0x01f00000 rootfstype=ext4...
LVM is Logical Volume Management, not Linux Volume Management
Source Link

This explains how you can boot the Raspberry Pi into a system with the root partition on an LVM volume. LVM is LinuxLogical Volume Management.

This explains how you can boot the Raspberry Pi into a system with the root partition on an LVM volume. LVM is Linux Volume Management.

This explains how you can boot the Raspberry Pi into a system with the root partition on an LVM volume. LVM is Logical Volume Management.

edited body
Source Link
starfry
  • 356
  • 1
  • 3
  • 12
# pvcreate /dev/sda1
# vgcreate storage /dev/sda5sda1
# lvcreate -L 5G storage -n root
# pvcreate /dev/sda1
# vgcreate storage /dev/sda5
# lvcreate -L 5G storage -n root
# pvcreate /dev/sda1
# vgcreate storage /dev/sda1
# lvcreate -L 5G storage -n root
Source Link
starfry
  • 356
  • 1
  • 3
  • 12
Loading