New answers tagged

0

boot into liveusb or livedvd that you used to install parrot OS 4.7 open terminal and run : 1- sudo fdisk -l 3- sudo mount /dev/sda* /mnt (replace * with the number that shown with type= linux in "fdisk" results) 4- cd / 5- cd /boot 6- ls 7- cp /boot/initrd.img-*******-parrot1-amd64 /mnt/boot (replace ***** with numbers that shown with ...


0

solution that worked for me was to boot into the live cd/usb version and mount /boot. Then I copied THE LIVE CD version of /boot/initrd.img-xxxxx into /boot/ on the systems harddrive. Make a backup of the old one first. After this I rebooted and it booted into parrot. I think there is a better way to make the correct modules load but this worked for me ...


0

As commented by pizdelect, here is the solution: https://raw.githubusercontent.com/brgl/busybox/master/shell/cttyhack.c. For me, I simply use ::respawn:/bin/cttyhack /bin/sh.


0

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) You get this message because it could not find the init script. (Without init, it tries to proceed and then fails due to lack of rootfs). -append 'debug console=ttyS0 init=/bin/init' It should be /init, not /bin/init. Alternatively you can specify the initramfs init with the ...


1

I think perhaps your init script is too minimal for booting. Kernels work with /proc and /sys so it should include : mount -t proc none /proc mount -t sysfs none /sys


2

x86-64 CPUs, from both AMD and Intel, pre-date UEFI, so it was common for a while to see 64-bit systems with only old-style BIOSs. It is still possible to boot them, with new kernels, so it should be possible to boot your Packard Bell. I can’t guarantee that your failure is unrelated, but it could easily be related to something else. Attempting to kill init ...


0

Solved: The kernel argument: earlyshell didn't actually launch a shell??? But running the kernel with the argument: break=premount gave me the initramfs shell. This resource was very helpful: https://wiki.debian.org/InitramfsDebug


0

Keyfiles matching the shell-style (globbing) pattern KEYFILE_PATTERN defined in /etc/cryptsetup-initramfs/conf-hook will be included in the initramfs, but the other keyfiles will not, according to Debian's cryptsetup docs: For Debian 9: /usr/share/doc/cryptsetup/README.{initramfs,Debian}.gz For Debian 10: /usr/share/doc/cryptsetup{-initramfs/README....


Top 50 recent answers are included