Second OMLx 3 system on multi-boot computer won't boot - can't find root fs

Development Cooker (development)
1

Below is same text as in original comment in bug report.

As title says on a multi-boot Linux system any second or third (or more) OMLx 3 system will not boot. The given error is:

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

This happens very fast so I suspect something in OpenMandriva is telling grub2 to look for root fs in the wrong place. Just noticed this today so problem is very recent.

Problem exists on 2 computers. These are OMLx systems that have been in existence and working for many weeks. They all have multiple kernel versions and this error happens on every kernel version. Obviously Recovery Mode does same thing.

Checked root partition UUID and they appear to be correct.

I’ll provide any logs I can if requested. And if I know how to do so or someone explains how to.

To reproduce:

Set up a computer with OMLx 3.0 on 2 seperate partitions.

Result:

The first OMLx 3 system in grub2 list will boot. Any other OMLx 3 systems following in grub2 list will give this error.

2

Please provide boot parameters, logs, screens etc.
Without this i can’t help at all.

1 Like
3

Except for screens isn’t all of that in omv-bug-report.log.xz?

How do I get a screen-shot of a system that does not boot? The kernel panic error happens almost instantly. Recovery mode does not work, no virtual terminal, ect. I can chroot in to system to copy files or get any logs not in omv-bug-report.log.xz.

Edit: Maybe I wasn’t clear in 1st post:
https://issues.openmandriva.org/show_bug.cgi?id=2234

4

Poor quality cell phone photo of boot error message.

20170922_075232.jpg2918×1641 1.88 MB

5

Better photo (but still not great) from my desktop (ASUS H97M-E mobo) showing boot error:

Boot-Error.jpg4128×2322 2.31 MB

6

By all means any log or info not in omv-bug-report.log let me know and I’ll do my best to provide.

7

Guess this is best described as a workaround:

  1. chroot in to the system that isn’t booting

  2. # urpme microcode-intel

  3. # grub2-mkconfig -o /boot/grub2/grub.cfg

  4. Now exit that system and unmount everything.

  5. In the working system from which I’m booting also run

    `# urpme microcode-intel`

`# grub2-mkconfig -o /boot/grub2/grub.cfg`

And now problem is fixed except I don’t have the ‘microcode-intel’ package. So maybe, just maybe, it’s something in this package:

microcode-intel-20170707-1.src.rpm

OR it has something to do with how OMV impliements what is in that package?

1 Like