Stuck in initramfs - mounting /sys in /root/sys failed : no such file

alexandremassoutier · 2024-02-17 22:22

Hi all,

I need some help since I am stuck in a region where "things" are far beyond my competences...

I installed Q4OS thanks to .exe package on a computer. Very fine. The only thing is that I get at every start up "could not open EFI/DebianBoot/____ where ____ is a blank area... But selecting Aquarius goes OK.

Some two weeks ago, at a time of an update, I got a log telling me a "linux-image update" failed... I did not pay very much attention and I don't really know if my problem is related to this.

Next time I booted I could not start Aquarius. I got initramfs and :
mounting /sys on /root/sys failed: no such file or directory
mounting /proc on /rootproc failed : no such file or directory
/init: line 331: cannot open /root/dev/console

I followed (probably erroneously) an Internet page saying "backuo your root.disk and make fresh install and relocate your root.disk".
=> the same.

I read several info here and there ; tried to mount myself but i always get a "invalid argument" at the end of each trial... Tried to undertstand grub files....

Well I don't really understand in which direction I should go and I don't know how I can retrieve my environment and data. I really like Q4OS ; it's thin, stable, user-friendly, intuitive...

Just in case it could help a reader :

fdisk -l
/dev/nvme0n1 = main hard drive with Windows + Linux64 folder at c://
/dev/nvme0n1p1 = ?? (type EFI GPT)
/dev/nvme1n1 = a data hard drive (not involved in the problem I think)
/dev/nvme1n1p1 = ? (type EFI GPT)
/dev/nvme1n1 = a data hard drive (not invol

blkid
/dev/nvme0n1p3 : LABEL "recovery" type ntfs basic partition data XXX as uuid YYY as patrition-uuid
/dev/nvme0n1p1 : LABEL_fatboot "SYSTEM" type vfat PARTLABEL "EFI system patrition" basic partition data XXX as uuid YYY as patrition-uuid
/dev/nvme0n1p4 : LABEL "Windows" type ntfs basic partition data XXX as uuid YYY as patrition-uuid
/dev/nvme1n1p2 : LABEL Data (my 2nd hard drive) type ntfs basic partition data XXX as uuid YYY as patrition-uuid
/dev/nvme0n1p2 : PARTLABEL "Microsopft Reserved Patrition" just has a PARTUUID like XXXX
/dev/nvme1n1p1 : PARTLABEL "Microsopft Reserved Patrition" just has a PARTUUID like XXXX

I don't really know where is my Aquarius OS...

I tried to use boot-repar but the live usb I created was rejected for some securiy reason and did not work in the end...
I have a live usb of Q4OS but I don't reaaly know what I could do with that (I can see the content of the hard drives but then...?)

Can some one help please ?

Thank you.

Alexandre

alexandremassoutier · 2024-02-18 11:15

I managed to get in with a Ubunto live USB.

Boot info report wriiten below.

Has someone a clue of what I should do?

Thanks.

Alexandre

boot-repair-4ppa2075 [20240218_1006]

============================== Boot Info Summary ===============================

=> Windows is installed in the MBR of /dev/nvme0n1.
=> No boot loader is installed in the MBR of /dev/nvme1n1.

nvme0n1p1: _____________________________________________________________________

File system:
Boot sector type: -
Boot sector info:

nvme0n1p2: _____________________________________________________________________

File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

nvme1n1p1: _____________________________________________________________________

File system: vfat
Boot sector type: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /efi/Boot/bootx64.efi /efi/DebianBoot/fbx64.efi
/efi/DebianBoot/grubia32.efi
/efi/DebianBoot/grubx64.efi /efi/DebianBoot/mmx64.efi
/efi/DebianBoot/shimx64.efi /efi/DebianBoot/grub.cfg
/efi/Microsoft/Boot/bootmgfw.efi
/efi/Microsoft/Boot/bootmgr.efi

nvme1n1p2: _____________________________________________________________________

File system:
Boot sector type: -
Boot sector info:

nvme1n1p3: _____________________________________________________________________

File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

nvme1n1p4: _____________________________________________________________________

File system: ntfs
Boot sector type: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 10 or 11
Boot files: /Windows/System32/winload.exe

sda: ___________________________________________________________________________

File system: iso9660
Boot sector type: Grub2 (v1.99-2.00)
Boot sector info: Grub2 (v1.99-2.00) is installed in the boot sector of
sda and looks at sector 0 of the same hard drive for
core.img, but core.img can not be found at this
location.
Mounting failed: mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.

================================ 1 OS detected =================================

OS#1: Windows 10 or 11 on nvme1n1p4

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: GA107M [GeForce RTX 3050 Mobile] Intel Corporation EFI VGA from NVIDIA Corporation Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 22.04.3 LTS, jammy, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: 1.07.04TPCS3(7.4) from INSYDE Corp.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0003,0002,2003,0004,2001,2002
Boot0000* EFI PXE 0 for IPv4 (D4-93-90-27-0E-5A) PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/MAC(d49390270e5a,0)/IPv4(0.0.0.00.0.0.0,0,0)RC
Boot0001* EFI PXE 0 for IPv6 (D4-93-90-27-0E-5A) PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/MAC(d49390270e5a,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0002* Windows Boot Manager HD(1,GPT,a82660d5-a5a6-4b99-b62c-0aa13e36d794,0x800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...e................
Boot0003* Q4OS Aquarius HD(1,GPT,a82660d5-a5a6-4b99-b62c-0aa13e36d794,0x800,0x82000)/File(\EFI\DebianBoot\shimx64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.e.f.5.1.b.b.e.c.-.4.3.d.1.-.1.1.e.e.-.8.e.4.0.-.c.3.4.e.9.5.7.e.d.5.6.2.}...e................
Boot0004* Linpus lite HD(2,GPT,f45e2fa1-c5a6-4d79-876d-c8245af921e0,0x95f864,0x2754)/File(\EFI\Boot\grubx64.efi)RC
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC

11ca963cd3c39273b7d38c06c5e9bb74 nvme1n1p1/Boot/bootx64.efi
ca0aa9ad51118a4a0b9026db28271163 nvme1n1p1/DebianBoot/fbx64.efi
e3e0d084f7a61ace01e1644294967eb7 nvme1n1p1/DebianBoot/grubia32.efi
2114c39d52c64a3b35753b13a231f098 nvme1n1p1/DebianBoot/grubx64.efi
1efa63a183a729b309c16267cbba5b67 nvme1n1p1/DebianBoot/mmx64.efi
fe2090106517ccf680e12e538b4274db nvme1n1p1/DebianBoot/shimx64.efi
11ca963cd3c39273b7d38c06c5e9bb74 nvme1n1p1/Microsoft/Boot/bootmgfw.efi
94379b2c1204c8c38423fb9cca2a9774 nvme1n1p1/Microsoft/Boot/bootmgr.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1 : is-GPT, no-BIOSboot, has-noESP, not-usb, not-mmc, no-os, no-wind, 34 sectors * 512 bytes
nvme1n1 : is-GPT, no-BIOSboot, has---ESP, not-usb, not-mmc, has-os, has-win, 2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p2 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB
nvme1n1p1 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme1n1p3 : no-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, not-far
nvme1n1p4 : is-os, 64, nopakmgr, no-docgrub, nogrub, nogrubinstall, no-grubenv, noupdategrub, end-after-100GB

Partitions info (2/3): _________________________________________________________

nvme0n1p2 : isnotESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme1n1p1 : is---ESP, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot
nvme1n1p3 : isnotESP, part-has-no-fstab, no-nt, no-winload, recovery-or-hidden, no-bmgr, notwinboot
nvme1n1p4 : isnotESP, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot

Partitions info (3/3): _________________________________________________________

nvme0n1p2 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme0n1
nvme1n1p1 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme1n1
nvme1n1p3 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme1n1
nvme1n1p4 : not--sepboot, no---boot, part-has-no-fstab, not-sep-usr, no---usr, part-has-no-fstab, no--grub.d, nvme1n1

fdisk -l (filtered): ___________________________________________________________

Disk nvme1n1: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk identifier: 8430FAB5-BE7B-43B4-856A-2FA411670FE6
Start End Sectors Size Type
nvme1n1p1 2048 534527 532480 260M EFI System
nvme1n1p2 534528 796671 262144 128M Microsoft reserved
nvme1n1p3 796672 1820671 1024000 500M Windows recovery environment
nvme1n1p4 1820672 1953523711 1951703040 930.6G Microsoft basic data
Disk nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk identifier: ADC42FBC-FBC5-4E46-961A-DD19833E4905
Start End Sectors Size Type
nvme0n1p1 34 32767 32734 16M Microsoft reserved
nvme0n1p2 32768 1000214527 1000181760 476.9G Microsoft basic data
Disk sda: 14.46 GiB, 15525216256 bytes, 30322688 sectors
Disk identifier: F45E2FA1-C5A6-4D79-876F-C8245AF921E0
Start End Sectors Size Type
sda1 64 9828451 9828388 4.7G Microsoft basic data
sda2 9828452 9838519 10068 4.9M EFI System
sda3 9838520 9839119 600 300K Microsoft basic data
sda4 9842688 30322624 20479937 9.8G Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:15.5GB:scsi:512:512:gpt: USB DISK 2.0:;
1:32.8kB:5032MB:5032MB::ISO9660:hidden, msftdata;
2:5032MB:5037MB:5155kB::Appended2:boot, esp;
3:5037MB:5038MB:307kB::Gap1:hidden, msftdata;
4:5039MB:15.5GB:10.5GB:ext4::;
nvme0n1:512GB:nvme:512:512:gpt:SOLIDIGM SSDPFKKW512H7:;
1:17.4kB:16.8MB:16.8MB::Microsoft reserved partition:msftres;
2:16.8MB:512GB:512GB:ntfs:Basic data partition:msftdata;
nvme1n1:1000GB:nvme:512:512:gpt:Samsung SSD 990 PRO 1TB:;
1:1049kB:274MB:273MB:fat32:EFI system partition:boot, esp;
2:274MB:408MB:134MB::Microsoft reserved partition:msftres;
3:408MB:932MB:524MB:ntfs:Basic data partition:hidden, diag;
4:932MB:1000GB:999GB:ntfs:Basic data partition:msftdata;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda iso9660 2023-08-08-01-19-05-00 Ubuntu 22.04.3 LTS amd64
├─sda1 iso9660 2023-08-08-01-19-05-00 f45e2fa1-c5a6-4d79-876e-c8245af921e0 Ubuntu 22.04.3 LTS amd64 ISO9660
├─sda2 vfat F7DB-4D56 f45e2fa1-c5a6-4d79-876d-c8245af921e0 ESP Appended2
├─sda3 f45e2fa1-c5a6-4d79-876c-c8245af921e0 Gap1
└─sda4 ext4 2dfb8c7d-68d3-42d6-ad9d-07cb48e69dbb b1a3d9b8-be32-1946-80d6-e15929a21a9d writable
nvme1n1
├─nvme1n1p1 vfat CCD7-DED7 a82660d5-a5a6-4b99-b62c-0aa13e36d794 SYSTEM EFI system partition
├─nvme1n1p2 785ba37e-c058-44ab-9b40-7267c7cfe3d1 Microsoft reserved partition
├─nvme1n1p3 ntfs 8868D82A68D81930 be3e9006-336f-4f7e-9617-6fe5a461c270 Recovery Basic data partition
└─nvme1n1p4 ntfs 0A58E4DD58E4C911 fb0f73a1-13da-4f98-8a74-7f53147dce3a Windows Basic data partition
nvme0n1
├─nvme0n1p1 bb1dca57-96a2-448d-919f-2a0e53ae5667 Microsoft reserved partition
└─nvme0n1p2 ntfs A0C62BECC62BC200 bd467a9f-baac-440d-8bd9-fef5babbf9a6 Data Basic data partition

Mount points (filtered): _______________________________________________________

Avail Use% Mounted on
/dev/nvme0n1p2 268.2G 44% /mnt/boot-sav/nvme0n1p2
/dev/nvme1n1p1 202.6M 21% /mnt/boot-sav/nvme1n1p1
/dev/nvme1n1p3 490M 2% /mnt/boot-sav/nvme1n1p3
/dev/nvme1n1p4 245.5G 74% /mnt/boot-sav/nvme1n1p4
/dev/sda1 0 100% /cdrom

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p2 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme1n1p3 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/nvme1n1p4 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096
/dev/sda1 iso9660 ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

================= nvme1n1p1/efi/DebianBoot/grub.cfg (filtered) =================

Q4OS Aquarius Desktop
Windows Boot Manager (on nvme0n1p1) osprober-efi-CCD7-DED7
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

======================== Unknown MBRs/Boot Sectors/etc =========================

/dev/nvme1n1p1: unknown GPT attributes
8000000000000000

/dev/nvme1n1p2: unknown GPT attributes
8000000000000000

/dev/nvme1n1p3: unknown GPT attributes
8000000000000001

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the MBR.
Additional repair would be performed: win-legacy-basic-fix

q4osteam · 2024-02-18 11:54

You can boot from Q4OS live media and mount the root.disk filesystem as described https://www.q4os.org/forum/viewtopic.php?id=4789

alexandremassoutier · 2024-02-18 13:20

Thank you for your help !!

I managed to mount the disk. But what can I do next if my purpose is to restore my dual boot system ?

I don't find here /etc/fstab (thought it could be a matter of uuid disk as I read some posts about that)

I have there an initrd.img + init.img.old (both locked)
I have also vmlinuz and vmlinuz.old (both locked too)

Are there at the right place? According to q4os start up as edited on boot (-e) search --set=root -f -n /EFI/DebianBoot/vmlinuz0
Could the problem be the "0" at the end which in my root.disk isn't ?

Or shall I go for a backup of this root.disk and make a true dualboot install ? Of course I would like to retrieve my environnement.

Thanks for the help again.

(posted from Q4OS LIVE USB)

q4osteam · 2024-02-18 16:47

We would recommend you to retrieve your personal and other important data from the root.disk, boot into Windows, remove Q4OS Aquarius from the Windows settings panel > Add or remove programs and make a fresh Q4OS for Windows installation. Upon a fresh install we also recommend you to save desktop profile for possible later usage as described https://www.q4os.org/dqa016.html

It would be also helpful, if you would post back the result for both cases, success or failure.

alexandremassoutier wrote:

...According to q4os start up as edited on boot (-e) search --set=root -f -n /EFI/DebianBoot/vmlinuz0
Could the problem be the "0" at the end which in my root.disk isn't ?

No, the file /EFI/DebianBoot/vmlinuz0 is correct.

Last edited by q4osteam (2024-02-18 16:49)

alexandremassoutier · 2024-02-18 20:37

OK. Thank you for your response.
I will take care of this next WE and I will keep you aware.
Very interesting the "Profile" if I can in one click get back my envrionment.

alexandremassoutier · 2024-02-19 19:01

Hello !

> Now that I can access file system (thanks to post #3)
> And given that my my objective is to repair the boot (if possible of course)

What are my chances to reach my objective looking around :
> on /etc/initramfs-tools/initramfs.conf ?
> on linux-images (since I had this strange error on updating the linux-image)

Thanks.

q4osteam · 2024-02-19 19:37

Q4OS normally updates kernel with no issues, however there was some failure on updating Debian kernel with Nvidia drivers enabled. So it may be connected, see https://www.q4os.org/forum/viewtopic.php?id=4782
You could try to redirect symlinks /vmlinuz and /initrd.img to an older counterparts and reboot.

alexandremassoutier · 2024-02-22 17:54

--- SOLVED ---

I share below what I did to solve my problem.

1) Thanks to POST #3 I was able to access my filesystem
2) I read https://wiki.debian.org/BootProcess (thanks to all the people who write those documentations)
3) I then went into my filesystem and I noticed a symbolic link was broken
4) Given my filesystem is in /tmp/mntpoint I had at root level :
initrd.img -> boot/initrd.img-6.1.0.-18-amd64
I HADN'T THIS IMAGE IN MY /BOOT FOLDER
5) Then I executed
sudo -i
ln -sfn boot/initrd.img-6.1.0-17-amd64 initrd.img
SINCE vmlinuz was pointing at 06.1.0.-18 version, for matter of consistency I also modified another symbolic link
ln -sfn boot/vmlinuz-6.1.0-17-amd64 vmlinuz (instead of 0-18...)

I rebooted on q4os and OK.

It seems I haven't lost any data.

THANKS FOR THE HELP Q4OS Team

Hope this post may help.

q4osteam · 2024-02-22 18:06

Thanks for sharing the solution

Q4OS Forum

#1 2024-02-17 22:22

Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#2 2024-02-18 11:15

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#3 2024-02-18 11:54

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#4 2024-02-18 13:20

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#5 2024-02-18 16:47

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#6 2024-02-18 20:37

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#7 2024-02-19 19:01

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#8 2024-02-19 19:37

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#9 2024-02-22 17:54

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

#10 2024-02-22 18:06

Re: Stuck in initramfs - mounting /sys in /root/sys failed : no such file

Board footer