Tag Info

New answers tagged

1

So, the reason was that I had compiled the kernel like so: make oldconfig make -j6 sudo make install I was wondering why my previous (official ubuntu repo) initrd was 28m in size while the new one was 8m. I had not installed the modules! Doing sudo make INSTALL_MOD_STRIP=1 modules_install sudo make install fixed it. Now the HD crypto is initialized ...


0

If I understood correctly, you have already fixed the volume, even though you have a lost+found directory which may or may not have critical files. What is going on now that's blocking the VM from booting? It still can't find the boot device? Your fdisk -l output seems a bit off to me. Have you considered the possibility that only the partition table was ...


1

So I figured out what the problem was: Red Hat's mkbldevs in the init script of the initrd.img was failing to make the block devices. Without any block devices LVM was not able to mount drives. I installed BusyBox and made a custom initrd and while in the shell I noticed that mkblkdevs called by the /bin/nash script didn't make /dev/sd*. I suppose you ...


2

Of course the primary goal is not to have the need to use swap in the first place... The main thing is to create the swap LVM volume when the system is still quite fresh, the same as when you create a swap file, as swap space performs best when it is contiguous. You don't want to actual disk blocks that make up the logical volume to be fragmented all over ...


0

I'd start with taking a look at the setup of your system, specifically the contents of the file, /etc/fstab. In there it will show you what partitions are being mounted and how they're being mounted. It's likely the case that with the addition of this new device that it's throwing the device handles off slightly, causing your system not to be able to access ...


0

You should always have a simple partitioning scheme that leaves space for the boot loader, good old DOS MBR works the best for this purpose plus guards the disk from being treated as unformatted when attached to windows machine. Even the fancy new GPT format uses MBR as the basis. The GRUB2 bootloader is capable of booting from stuff like RAID and LVM and ...


0

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616689 is relevant here. It's to do with timeouts such that lvm root does not appear in time.



Top 50 recent answers are included