Created attachment 3358 [details] A screenshot of the reported issue Trying to upgrade a Cauldron installation using a network installation I get the message Si è verificato un errore Oops, no root partition and the installation process cannot continue. I'm experiencing this issue into a VirtualBox virtual machine with Cauldron already installed. Its disk has three partitions: /boot (ext3), /root(ext4) and swap. The messages I get on tty3: * starting step `doPartitionDisks` * calling umount(/mnt/sys/kernel/debug/usb) * running: umount /mnt/sys/kernel/debug/usb * running: umount /mnt/sys/kernel/debug/usb * calling umount(/mnt/sys) * running: umount /mnt/sys * running: umount /mnt/sys * calling umount(/mnt/proc) * running: umount /mnt/proc * running: umount /mnt/proc * umounting all filesystems * step "doPartitionDisks" took: 0:00:00 * error: Oops, no root partition at /usr/lib/libDrakX/fs/any.pm line 69. Part of the messages I get on tty4: EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null) Let me know if I can provide much useful details and how.
Created attachment 3359 [details] A screenshot of the current partition scheme I reach this step into the installation process if I choose Install rather than Upgrade
you wanted to upgrate cauldron with cauldron ? maybe you could add the report.bug.gz as an attachment switch to console 2 (by pressing 'Ctrl-Alt-F2') during installation, put a floppy in floppy drive or plug a USB key/stick and type: 'bug' then press Enter. It will put report.bug on the floppy/key.
Hello Manuel, yes, I was trying that procedure to "recover" an installation corrupted due to the initrd corrupted issue (utils-linux, iirc). Upgrading this way worked with another vm but there was another partition scheme. Talking about your suggested procedure, I'm on a virtualized Mageia without usb/floppy support :-/ Any chance I can save locally report.bug and then try to transfer it using the network? Is this procedure documented somewhere? Thank you
CC: (none) => thierry.vignaud
I'm going to close this br because it's old and I'm not able to reproduce it anymore. Regards
Status: NEW => RESOLVEDResolution: (none) => OLD