I am trying to install AlmaLinux 8.8 via use IPMI. I tried several times but installer every time stuck at same step. At first I thought the problem was in the alma iso file so I downloaded the updated version 8.8 from the almalinux official page and tried again. this did not work. I installed the proxmox iso file to see if the problem applies to almalinux 8.8 and it installed successfully. i think the problem applies to almalinux 8.8. when i check the logs i don't see any problem. what do you think is the problem? logs;

I have done something stupid and messed up my Debian Squeeze installation. Now, the problem is I have enough data and sowftware installations which I don't want to repeat; is it possible to reinstall the OS and still somehow save and maintain data on my box? I have still not tinkered with the installation, I am just frustrated with issues and lack of time.

I'm intending to replace a NAS's Custom Linux with Arch Linux (details at the bottom), of course wishing to preserve all user data and (due to the SSH-only headless access) attempting to be fool-proof since a mistake may require firmware reinstallation (or even brick the device). So instead of running the installation (downloading the appropriate [Arch Linux ARM release](http://archlinuxarm.org/developers/downloads) and probably using the [chroot into LiveCD approach](https://wiki.archlinux.org/index.php/Install_from_Existing_Linux#Method_2:_Chroot_into_LiveCD-image)) without appropriate preparations, what must I keep in mind? (Please feel free to answer without restriction to Arch Linux) More precisely: > * Do I somehow have to bother with figuring out how a specific device's boot process works (e.g. which parts of the bootloader reside on the flash memory and which ones are on the harddisk) or can I rely on the distribution's installer to handle this correctly? * How can I determine whether some (possibly proprietary) drivers are used and how can I migrate them into the new setup? * Is the RAID configuration safe from accidental deletion? * Is there a way to fake the booting process so I can check for correct installation while the original system remains accessible by simply rebooting? E.g. using [chroot](http://linux.die.net/man/1/chroot) and [kexec](http://linux.die.net/man/8/kexec) somehow? * What else should I be aware of? --- The specific case is that I want to replace the custom Linux from a [Buffalo LinkStation Pro Duo](http://www.buffalotech.com/products/network-storage/home-and-small-office/linkstation-pro-duo-1) (armv5tel architecture, the [nas-central description](http://buffalo.nas-central.org/wiki/Category:LS-WVL) is a bit more helpful here and also provides instructions on how to [gain SSH root access](http://buffalo.nas-central.org/wiki/Open_Stock_Firmware_LS-VL)) with [Arch Linux ARM](http://archlinuxarm.org/) . But a more general answer may be more helpful for others as well.

I have recently tried to reinstall Ubuntu to my Lenovo X1 Carbon but I'm getting the following issues (all my data is backed up): - I tried installing ubuntu from live disk. I selected "reinstall" and followed the default settings to the end where I got the following error:

unable to install GRUB in /dev/sda
Executing grub-install /dev/sda failed.
This is a fatal error.

- Since I had problems with my previous version I thought these may have transferred in the reinstall so I then tried Erase Ubuntu 14 and replace with Ubuntu 20. This gave me to same error. I tried following the suggestions on this post: namely: - Manually deleting the previous partition and creating a new one. This gave the same error. - Installing grub via the boot terminal and via the terminal inside Try Ubuntu. Using sudo grub-install /dev/sdb and sudo grub-install /dev/sda In both instances I got

$ grub-install /dev/sda
grub-install: error: cannot find EFI directory.

So following advice from here I mounted the efi system. Now when I use sudo grub-install /dev/sdb I get the error:

sudo grub-install /dev/sda
Install for x86_64-efi platform
grub-install: error: failed to get canonical path of `cow'.

- Returning to forum searches for this error I tried following the advice here . When I try: grub-install --recheck --root-directory=/mnt /dev/sda I get:

sudo grub-install --recheck --root-directory=/mnt /dev/sda
Install for x86_64-efi platform
grub-install: error: cannot find EFI directory.

- So I go back to the error search and find a similar post here: This time I try grub-install --efi-directory=/dev/sda7 and I get:

grub-install --efi-directory=/dev/sda7
Installing x86_64-efi platform
grub-install: error: failed to get canonical path of udev.

- Advice from here so I then use grub-install --efi-directory=/boot which gives

sudo grub-install /dev/sda
Install for x86_64-efi platform
grub-install: error: failed to get canonical path of `cow'.

Which is the same error I got before so it seems like I've gone round in circles. I've tried running boot-repair both from within TryUbuntu and via a live disk. These executed successfully but then when I restarted and tried to access Ubuntu I got the same errors as before. I know that each of these has their own forums but I feel like I'm going round in circles between them all. Can anyone piece together each of the errors to help me? Some background- The reason I'm reinstalling is that a few years ago my laptop crashed in the middle of an update (I hadn't realised the battery cable had been switch off.). My friend kindly spent an afternoon manually fixing parts to get it to work again. Since then there have been a few things I've not been able to get working properly (printer drivers and calendar syncing for example). Since these weren't a problem for my research I continued without them until the end of my PhD. I recently had some errors trying to use Firedrake. Since I've now finished my PhD it seemed like a safe time to back up all my data and reinstall Ubuntu. Hoping that the reinstall would rectify the problems from the previous crash.

After having a number of issues with applications crashing and worries about my hard drives being corrupt (I kept getting kernel panic signals at startup unless I started in recovery mode), I decided to just wipe everything and reinstall from a usb. After completing this step, I seemed to have a functional OS and proceeded to set up the rest of my applications and environments (conda, singularity, steam ect.). After completing this step, everything seems to run as expected for about an hour, at which point applications begin to crash. After noticing this, I used the USB to entry "try Linux" setup so I could check and repair all disks/partitions. Doing this, showed there were no issues with any of my partitions. After this did not work, I tried to see if the issue was due to the lack of swap space, as this seems to be a common problem after installation. So following a guide which creates a swap file, and increases the swap space to something larger, I still ran into the issue. At this point I am not sure what the issue could be or how to resolve it. I am wondering if during installation I did not partition my hard drive correctly since I opted to install the new os on the second hard drive instead of the first (where my original installation was). I do also know that the crashes are from an oom error following journalctl -u system-oomd, however even when I disable systemd-oomd the crashes still occur. I should also clarify that my machine has two hard drives, one of which is partitioned into a FAT (unmounted), Ext4 (unmounted), Swap (active), +freespace, while the second (which I used to create my installation is partitioned into FAT (mounted) and Ext4 (mounted at root). It seems like I am not correctly creating a swap (I was following https://askubuntu.com/questions/178712/how-to-increase-swap-space/1177939#1177939) , but I am not sure how to resolve. Any and all help would be much appreciated!

I'll change my system from 32 bits to 64 bits, and will be the same I had before, Debian Squeeze, but I do not want to lose the programs I installed before, because I do not remember the name of them all. So I wanted a command to do this for me, save the name of all the programs I installed on a file, but not the standard programs that came with the system, and when I'm using the other system I would mention the name of the file and your directory for everything to be installed automatically. One more question: is it possible to do this with programs that were installed manually with dpkg-i package.deb? If so, how can I do that?

There was power failure during system upgrade (pacman -Suy). So I have a lot of broken packages. They seems to be fixed on reinstall with force overwriting (e.g pacman -S systemd-sysvcompat--overwrite "*"). So my question is how to apply reinstallation to all broken packages?

I messed up Xorg & I am unable to resolve errors and I now want to reinstall xorg how do I do this? I tried doing # dnf groupinstall "X Window System" But it didn't work.

I am currently using Ubuntu 22.04. I want to reinstall ubuntu (cause I think the current one is corrupted) The only problem is, it boots into the current OS even though I connected the bootable pendrive/thumb-drive/usb-stick and configured it on the BIOS. I thought it was a problem with the usb but any other distro work fine (I tried fedora and arch). Here's some more info: Current OS: Ubuntu 22.04 x86_64
Pendrive: SanDisk 64Gigabyte
ISO file in the pendrive: Ubuntu 22.04 LTS x86_64
ISO Source: [Ubuntu's official site](https://ubuntu.com/#download) - CLICKING WILL START THE DOWNLOAD!
Tool I used to burn it onto the usb: BalenaEtcher and Startup disk creator

I uninstall samba this way: My os is debian11. sudo rm -f /etc/samba/smb.conf sudo apt purge samba sudo apt install samba Now check the default samba's configuration file. sudo ls /etc/samba/smb.conf ls: cannot access '/etc/samba/smb.conf': No such file or directory

Is there any easy way to re-install / re-build a "clean" Linux installation on top of existing partitions, etc? In other words, I'm happy with the partitions, the file system, the existing drive mounts, and KVM / VMs. I would like to do a clean reset back to the unmodified files, except for the existing file system, drives, and VMs. Thoughts?

How do I tell zypper to reinstall all currently installed packages?

Does rolling release differ from non-rolling release in that there is only incremental change to the system and packages, theoretically no need for reinstallation? If reinstallation can still practically happen in rolling release, when does that happen? Similarly, does rolling release require less reboots when updating/upgrading the kernel and packages than non-rolling release? When does rolling release require reboot after updating/upgrading? (what is difference between updating and upgrading?) If I am correct, NixOS follows rolling release pattern.

I am using Ubuntu 20.04. I have read that if my /home partition is separate from the root then in case of reinstalling Ubuntu, I still can keep my personal files. This is like having a separate drive in Windows other than C:\ to keep my files on. In case of a re-installation, I only format the OS drive/partition. Suppose I have a separate /usr partition, can I keep using the software installed in /usr after I reinstall Ubuntu on the root partition? This won't work in Windows, for example. The software installed in another drive won't be usable if I reinstall Windows on drive C:\. I am wondering if the same is true with Ubuntu.

I'm having some issues with my system and I would like to reinstall packages to see if that resolves it, but I'm not sure how I'd go about doing this. How do I reinstall all installed packages in Alpine Linux?

I currently have my laptop set up with dual boot windows and linux mint. I'm planning to remove windows completely, so I need to know which partitions I can delete safely to clean up my harddrive, since I have 8 partitions 1p3 is my windows partition 1p6 is for shared data between windows and linux 1p5 is linux mint I don't know about the rest. If it helps: I have a Lenovo Thinkpad L380Yoga, the Windows partition is encrypted with bitlocker. If any more info is needed, I'll gladly provide it. Thank you! For clarity: I want to do a fresh install and need to know if I can safely wipe all partitions. Data is backed up and everything

This is my current partition table: Which option should I use to reinstall Linux? Does the erase disc option also erase the partitions? Would I need to create a new partition table? Or would choosing the something else option allow me to keep my current table and just erase the current data in those partitions? I had a good partitioning tutorial from here, but sadly can't seem to find it. I should also mention that I don't need to keep anything. Any help would be awesome. Thanks!

These errors (see pic. 1 and 2) appear every time I boot in Debian. I tried to update from stretch to buster, but it didn't have any effect. I have dual boot with Windows 10, so that potentially might cause part of the problem. It boots fine, however some things are broken (was able to run a program with clear stack smashing problem).

Are there any Gnu/Linux installers that will look at an old /home partition, to set up the users based on the directories in the root of this partition? So if I install a new Gnu/Linux, and keep my old /home, the /home partition will be full of files owned by various users and groups. I also need to set up a load of users, these users need to match the ones from the old system, so that the file in /home have the correct ownership. The root of the /home partition have a directory for each user, that is owned by that user, and their primary group. Therefore it should be possible to scan this directory, and create a user/primary-group for each directory that is found. - Are there any tools that already do this? - Are they used in any Gnu/Linux installed? - Does Debian do this? (I am about to install a new Debian.)

We have a new linux server CentOS 6.5 with Plesk. Default PHP is 5.3.3, I have installed PHP5.4 & 5.5 on the server. I have to install PHP by using this [guide](http://alexbouma.me/multiple-php-versions-for-plesk-11-5/) PHP installed successfully but some functions do not work, such as mysqli. Default PHP 5.3.3 configure command is: --with-mysql=shared,/usr --with-mysqli=shared,/usr/lib64/mysql/mysql_config but my installed PHP 5.4 configure command is: --with-mysql=/usr --with-mysqli I think something is missing. I want to know how to restore mysqli features?