Stuck on "loading initial ramdisk ..."
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Suddenly my computer does not open. It displays the trisquel packground picture and gets stuck.
When opening in safe mode, when it gets stuck, it says: "loading initial ramdisk ..."
How can I solve this?
I am a translator!
Did you try booting with another kernel from the grub menu?
Yex. I have tried the latest and the second latest kernels in ordinary and safe mode.
My machine runs coreboot (skulls), if hat is of any importance.
Skulls can be a pain to migrate off of, so I hope you never want to do so.
Problem is, if you want to migrate to libreboot for example, it won't allow you to do it all at once.
In my last experience, you have to split libreboot rom to install it.
Really annoying stuff.
I hope all goes well for you on skulls.
When booting from live USB disks tells me that the file system on 'partition 2' was damaged. Disks has now repaired it, and I try to reboot.
NO, That did not fix the problem :-(
Which version of trisquel? 12? 11.0.1? 13 alpha if it exists? etc?
12
I am a translator!
Did you do something that could result in boot issues?
What kind of disk(s) do you have? Did you check all file systems? Which one (boot, efi, root, home) was it that needed repair?
If your disk(s) is/are ok and the home file system is ok, backing up your data to another disk, reinstalling and restoring your data is a method that should work. If the problem was with boot or efi, it may be possible to repair using chroot, perhaps reinstalling the kernel, updating the initramfs and grub, but I did not have much success with such things so far.
I cannot think of something I did to provoke this behaviour.
The last "new" thing I did was to delete an older folder of element (the matrix client), uninstall element, update an reinstall element. For this I probably also updated an upgraded the system as such.
According to gnome disks, all partitions were fine, when I last checked. The disk itself is an ssd. I am not sure if it was boot, efi, root or home that needed repair, but I will check this.
I have no idea about how and what to "repair using chroot".
Can I reinstall the kernel from a live usb?
Do you know which is the latest kernel for T12?
The partition that had to be repaired was efi. It should be fixed now, but I still cannot start the OS.
I am a translator!
Once, I made something wrong on EFI so that I could not boot the system, I was able to fix it using https://wiki.debian.org/GrubEFIReinstall, the first method. There are extra details at https://wiki.debian.org/GrubEFIReinstallOnLUKS if root and home are in an encrypted partition. However, you will need to adapt to your device names, and recognize which device is which partition ("lsblk" and "lsblk --fs" should help you to find out).
EDIT: I just looked at https://github.com/merge/skulls, it seems your BIOS uses SeaBIOS, not UEFI. Then, the link I provided is probably not applicable.
I ended up following your advise to install from scratch via the net-installer, all in one partition.
Thanks a lot for your involvement.
That was wise suggestion on his part.
Sometimes you gotta reinstall.
Btw, backing up to a qcow2 is always possible if needed. Qemu-img for example.
Although that will copy the whole damn drive, so... probably put it on a storage that has lots of space.