You are not logged in.
Could i have on a separate partition an arch rescue system ? I dont want to have another archlinux , just want rescue system using its tools and other tools if i could
Last edited by user7z (2024-05-15 23:06:24)
Offline
To my mind that's what an initrd is for -- if your root partition can't be mounted for whatever reason, you'll be dropped to an emergency shell to investigate further.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
How about https://wiki.archlinux.org/title/Multib … ly_release? Only works with GRUB though.
Para todos todo, para nosotros nada
Offline
To my mind that's what an initrd is for -- if your root partition can't be mounted for whatever reason, you'll be dropped to an emergency shell to investigate further.
Yeah but its limited in such cases like storage failures you ve been puted into emergency shell but without access to the system binaries so alots of commands are unknown for the shell
Offline
How about https://wiki.archlinux.org/title/Multib … ly_release? Only works with GRUB though.
I use the new UKI provided by mkinitcpio so i dont use any bootloader , but i think that i might do a work around on this wiki its interesting , thank you bro
Offline
It looks like archboot (an alternative arch installation environment by an arch developer) provides its complete environment as a UKI:
https://archboot.com
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I am using SystemRescueCD (arch linux based with xfce gui) stored on EFI partition, systemd-boot as bootloader.
Also Arch installation CD can be stored on EFi
Shortened file structure:
/boot
├── EFI
│ ├── ArchISO
│ │ ├── initramfs-linux.img
│ │ ├── vmlinuz-linux
│ │ └── x86_64
│ │ └── airootfs.sfs
│ ├── RescueCD
│ │ ├── sysresccd.img
│ │ ├── vmlinuz
│ │ └── x86_64
│ │ └── airootfs.sfs
│ └── systemd
├── loader
├── entries
├── archiso.conf
└── sysres.conf
sysres.conf
title SystemRescue (11.0)
sort-key b1
linux /EFI/RescueCD/vmlinuz
initrd /amd-ucode.img
initrd /EFI/RescueCD/sysresccd.img
options archisobasedir=EFI/RescueCD archisolabel=EFISYS iomem=relaxed copytoram
archiso.conf
title Arch Linux
version iso 05/24
sort-key b3
linux EFI/ArchISO/vmlinuz-linux
initrd amd-ucode.img
initrd EFI/ArchISO/initramfs-linux.img
options archisobasedir=EFI/ArchISO archisolabel=EFISYS copytoram
Remark: EFISYS is label of the EFI partition
Offline
I use a three level approach with a local ArchISO HTTP mirror.
1. A copy of an older UKI image (via bootloader from the EFI partition) which can tell me if a bug/error was present before the latest kernel update.
2. A heavily modified "ipxe.efi" (via bootloader from the EFI partition) which boots into an up-to-date copy of the Arch ISO (with secure boot) in case I need to do checks in a different and reliable boot environment.
3. That same "ixpe.efi" served by DHCP/TFTP (via mainboard PXE with secure boot) in case something went awfully wrong.
Offline
I use mkosi to build a single EFI executable with an embedded Arch root filesystem which I just copy to the EFI system partition and boot directly, see https://github.com/swsnr/rescue-image
Offline
My USER is doomed to eventually FUBAR their Archlinux installation and, other than initrd, management has no hope whatsoever.
MANAGEMENT keeps USER's guilty mind occupied by rsyncing to a separate, isolated SSD.
CRON job. https://wiki.archlinux.org/title/Rsync#Automated_backup
25+ years of general Linux experience says USER's Archlinux install is still DOOMED, but whatever.
UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn
Offline
It looks like archboot (an alternative arch installation environment by an arch developer) provides its complete environment as a UKI:
https://archboot.com
i try install it but the link there resend me to the archwiki
Offline
I am using SystemRescueCD (arch linux based with xfce gui) stored on EFI partition, systemd-boot as bootloader.
Also Arch installation CD can be stored on EFiShortened file structure:
/boot ├── EFI │ ├── ArchISO │ │ ├── initramfs-linux.img │ │ ├── vmlinuz-linux │ │ └── x86_64 │ │ └── airootfs.sfs │ ├── RescueCD │ │ ├── sysresccd.img │ │ ├── vmlinuz │ │ └── x86_64 │ │ └── airootfs.sfs │ └── systemd ├── loader ├── entries ├── archiso.conf └── sysres.conf
sysres.conf
title SystemRescue (11.0) sort-key b1 linux /EFI/RescueCD/vmlinuz initrd /amd-ucode.img initrd /EFI/RescueCD/sysresccd.img options archisobasedir=EFI/RescueCD archisolabel=EFISYS iomem=relaxed copytoram
archiso.conf
title Arch Linux version iso 05/24 sort-key b3 linux EFI/ArchISO/vmlinuz-linux initrd amd-ucode.img initrd EFI/ArchISO/initramfs-linux.img options archisobasedir=EFI/ArchISO archisolabel=EFISYS copytoram
Remark: EFISYS is label of the EFI partition
he frined how to do it exactly is there alot of overhead
Offline
I just keep a bootable iso on a flash drive. If you have a drive failure or issue with the drive cable, another bootable system on the same drive wont do any good.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I use Ventoy. I have a usb key with a few ISO images on it, even a zfs-enable Arch iso as i run root-on-zfs on my laptop. Works beautifully with little to no effort.
Linux user since 1996. Currently running Arch on an I7 11th gen laptop with root on zfs with zrepl.
Offline