Hello;
I have a post which I believe to be unique. Searched on several forums but most initramfs end up resulting from improper 2nd OS shutdown or on a new linux install.

I have two filesystems on separate physical drives. Used the win[cough]s drive and properly shut it down (I always do b/c it's not as robust). When I restarted with Parrot Linux OS, the error read:

007.39371 x86/cpu VMX (outside txt) disabled by BIOS
busybox v1.30.1
Debian 1.1.30.1-4
built in shell (ash)

I tried turning off, going back into the win[cough]s drive and did chkdsk, then a proper shutdown and restart into linux. That didn't work.
I then saw this on youtube and did
blkid
fsck -y /dev/sdb4
what I got back was this:
fsck from util-linux 2.35.2

I saw another version here - https://www.linuxquestions.org/quest...em-4175663569/
don't know what the --vg--root does but wanted to know the reason before taking action that might compromise the OS.

I hope that this post doesn't mimic other posts or display insufficient troubleshooting. I've never encountered this type of difficulty.

Thank you in advance for any advice or search terms to research.
Aaron

I am not sure if I understand you, because I don't see an error message.

You mean that your boot sequence stops in the initramfs, correct? If so, that's hardly unique. It can happen due to an entry in the file system table that can't be mounted.

Now you say that you ran chkdisk - on the Linux disk drive? If so, I wonder what that did to the data.

The vg-root that you saw in another Linuxquestions thread means that LVM is used on that installation. Whether it is used on yours, I don't know.

To sort this out, let's start with this:

• tell us on which disk you ran the Windows chkdsk.
• What disk is /dev/sdb4?
• fsck -y should have given you a bit more information than just the version of fsck. Can you share what it says?
• are you sure there are no other messages before you get the initramfs prompt? Look for other messages and share them here.
• tell us what disks you have. Run lsblk, or blkid, and if that fails, ls /sys/block.
• give us the content of /etc/fstab (this will only be useful if the root filesystem is already mounted, but it's worth a try).

The only text showing that looked to be an error msg was this:

007.39371 x86/cpu VMX (outside txt) disabled by BIOS
busybox v1.30.1
Debian 1.1.30.1-4
built in shell (ash)

Otherwise there was just a black screen with the 'initramfs' prompt.
-------
You mean that your boot sequence stops in the initramfs, correct? If so, that's hardly unique. It can happen due to an entry in the file system table that can't be mounted.
There have been other discussions of this issue, but nothing that showed the same input/output which I saw. If this should have been posted in another area, I apologize.
-------
Now you say that you ran chkdisk - on the Linux disk drive? If so, I wonder what that did to the data.
I did chkdisk on a windows drive (physically separated). It shows up as /dev/mmcblk0p1 while I am troubleshooting with a thumbdrive.
-------
To sort this out, let's start with this:

tell us on which disk you ran the Windows chkdsk. -> /dev/mmcblk0p1
What disk is /dev/sdb4? -> this was the label for what I believe the linux drive was while I did a blkid within the non-booting drive (see below)
fsck -y should have given you a bit more information than just the version of fsck. Can you share what it says? -> it only said 'fsck from util-linux 2.35.2'
are you sure there are no other messages before you get the initramfs prompt? Look for other messages and share them here. -> it was a black screen with the preceding text at the top
tell us what disks you have. Run lsblk, or blkid, and if that fails, ls /sys/block.
give us the content of /etc/fstab (this will only be useful if the root filesystem is already mounted, but it's worth a try).

If it helps, this is the total response to blkid
mint@mint:~$ blkid
/dev/mmcblk0p1: UUID="7C33-81C3" TYPE="vfat" PARTUUID="5370dad2-b0b9-44e5-b263-b56f50f7655d" -> (I believe this is the drive with windows on it)
/dev/mmcblk0p2: UUID="3e4f29a5-d0a9-4600-8ec8-17b656734f26" TYPE="ext4" PARTUUID="991d7737-fb72-43d8-8c6e-d23efad1c88d"
/dev/sda1: UUID="882D-54D6" TYPE="vfat" PARTLABEL="Data-drive" PARTUUID="86e7b594-e538-d147-50ef-6fc95f1d11a1" -> (I believe this is the linux drive that is not booting properly)

Here is the return from lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 1.8G 1 loop /rofs
sda 8:0 0 931.5G 0 disk
└─sda1 8:1 0 931.5G 0 part -> data drive with no OS
sdb 8:16 1 7.6G 0 disk /cdrom
├─sdb1 8:17 1 1.9G 0 part
└─sdb2 8:18 1 2.3M 0 part
sdc 8:32 0 238.5G 0 disk
├─sdc1 8:33 0 500M 0 part
├─sdc2 8:34 0 164.7G 0 part /media/mint/98B278AAB2788E8E
├─sdc3 8:35 0 857M 0 part
└─sdc4 8:36 0 72.5G 0 part
sr0 11:0 1 1024M 0 rom
mmcblk0 179:0 0 60.4G 1 disk
├─mmcblk0p1 179:1 0 512M 1 part
├─mmcblk0p2 179:2 0 56G 1 part
└─mmcblk0p3 179:3 0 3.9G 1 part

mint@mint:~$ ls /sys/block
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 mmcblk0 sda sdb sdc sr0

I ran fsck once again using the thumbdrive instead of from the non-booting linux drive and this was the text returned:
fsck from util-linux 2.31.1
fsck.fat 4.1 (2017-01-24)
/dev/sda1: 147541 files, 17621360/30516376 clusters

If there is any other info that I can provide, I'm happy to do so. Thank you in advance for the time.
A

here is a picture of the screen

Attached Thumbnails