Elisabetta Falivene wrote:
> It wasn't me to configure the machine in the first place so is a bit
> tricky. I can give more information if you can point me out what you could
> need. thank you a lot
well it is interesting to know if you have raid or so, if your boot and root
are on LVM, or probably only root is on lvm.
Perhaps it will be sufficient to pass root parameter to the kernel
the process to fix initrd is not that complicated
1. boot from rescue media usb like ubuntu
2. become root (sudo bash)
3. vgscan
4. vgchange -ay <volume group>
5. mount root and boot somewhere ex. /mnt/root and /mnt/root/boot (if boot
is separate partition)
6. prepare to chroot
mount --bind /dev /mnt/root/dev
mount --bind /dev/pts /mnt/root/dev/pts
mount --bind /proc /mnt/root/proc
mount --bind /sys /mnt/root/sys
7. chroot /mnt/root
now you can fix initrd
example
update-initramfs -u -k `uname -r`
8. update-grub (not really needed, but to be on the safe side)
9. reboot
In addition
7.1 if you need to examine initrd
cd /tmp/
mkdir test
cd test/
zcat /boot/initrd.img-<version> | cpio -id
do whatever you need to do
find . ! -name *~ | cpio -H newc --create | gzip -9
> /boot/initrd.img-<version>
perhaps test this process in VM to get familiar with it before doing this on
production system
IMO it will be solved if you recreate initrd from the chroot environment, if
not see what you have in the initrd ... but perhaps someone else will do
this
regards
