Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

20230331 release not work with ESXi 7.0U3 VM on Dell R730 #75

Open
Tokisaki opened this issue May 8, 2023 · 4 comments
Open

20230331 release not work with ESXi 7.0U3 VM on Dell R730 #75

Tokisaki opened this issue May 8, 2023 · 4 comments
Assignees

Comments

@Tokisaki
Copy link

Tokisaki commented May 8, 2023

after my test the 5.15.98 working good.but the 20230331 told me VFS:unable to mount root fs

@Sebastian-Roth Sebastian-Roth self-assigned this Aug 6, 2023
@Sebastian-Roth
Copy link
Member

@rluzuriaga @George1421 Can anyone confirm the latest inits are causing this issue?

@Tokisaki Sorry for the very long delay. Summer is a pretty busy time. Allow me a question. The version number 5.15.98 is a Linux kernel version but 20230331 is a FOS init version. Can you make checks with old and new kernels and inits to see which one is causing the problem?

@villalvilla
Copy link

Hi there! I can confirm that lastest's init.xz release is also giving the same problem.
I have tested with ESX 7.0.3 VMWare's x64 Virtual Machine and giving exactly the same issue.
Bad news continue: We are testing FOS in Alder Lake's 5150 mini pcs, that come with 12Gigas of RAM and NVME hard disk and also giving the same issue.
I am compiling in this moment (it is taking ages) init.xz and bzImage for x64 from master branch, so will let you know how it goes.

I have added verbose 7 in the FOG Client Boot Settings in the FOG Server frontend, so I was able to see the log that I attach to this comment as "FOS Kernel Panic.jpg"

FOS Kernel Panic

Thanks for your help

@villalvilla
Copy link

Update: kernel 5.15.98 isn't working (also). As the Virtual Machine's screen is bigger, I could compile this valuable information:
image

As you can see, it sais: RAMDISK: Couldn't find valid RAM disk image starting at 0 so the problem in both of the systems is that it is not recognizing the RAMDISK partitions... Might it be because of AHCI drivers? It doesn't make any sense, because the driver used for SDA is SD. If I run an ubuntu live image, it designates SD and AHCI drivers for hard disk.

Any help will be welcomed, because I am really stuck here...

@rluzuriaga
Copy link
Member

rluzuriaga commented Nov 27, 2023

@villalvilla can you try with the new kernel and init from this release and let me know if this works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants