Anaconda crashing on start while trying to Install oVirt Node on bare metal
Hello there! I'm trying to install an oVirt node(the most stable recent one) on a machine(just in case you didn't figure from the title :P) and anaconda just crashes \o/ I've tried to start anaconda in text mode, but the error is the exact same. Here's a screenshot of the event(text mode, although it shouldn't matter): https://i.imgur.com/ihO1xWP.jpg The only "disk" attached to the machine has no partitions, it's absolutely clean. The machine in question is a PowerEdge M520, if that matters, and I'm trying to install on top of a pair of 32GB mirrored SD cards. I installed CentOS7 on a machine that's virtually the same(they're the exact same, but aren't the same machine) and didn't have any problem. I just have no idea. Never encountered such problem. So any help would be very appreciated. Thanks ^^
Can you wipe the beggining of both SD cards via 'dd' ?I have seen similar issues on CentOS's anaconda with extraordinary disk setups. Best Regards,Strahil Nikolov В сряда, 3 юли 2019 г., 20:34:58 ч. Гринуич+3, rubentrindade@live.com <rubentrindade@live.com> написа: Hello there! I'm trying to install an oVirt node(the most stable recent one) on a machine(just in case you didn't figure from the title :P) and anaconda just crashes \o/ I've tried to start anaconda in text mode, but the error is the exact same. Here's a screenshot of the event(text mode, although it shouldn't matter): https://i.imgur.com/ihO1xWP.jpg The only "disk" attached to the machine has no partitions, it's absolutely clean. The machine in question is a PowerEdge M520, if that matters, and I'm trying to install on top of a pair of 32GB mirrored SD cards. I installed CentOS7 on a machine that's virtually the same(they're the exact same, but aren't the same machine) and didn't have any problem. I just have no idea. Never encountered such problem. So any help would be very appreciated. Thanks ^^ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PHXYRBWVR677NB...
So, following your advise, what I did was "dd status=progress if=/dev/zero of=/dev/sda count=1" and that did indeed fix the anaconda starting up issue. By the way, when I said mirrored, it's raid 1, so if I do to one, I do on both at the same time. The raid is being done and managed on the bios. Maybe poor wording on my side. The thing is, as soon as I try to create partitions/LVMs it returns me an error. Here's the three different outputs: LVM Thin Provisioning https://i.imgur.com/tfbi0oo.jpg (curiously, it's the same output error as when it crashed) LVM https://i.imgur.com/nJXo3aK.jpg Standard Partition https://i.imgur.com/j6gNRpo.jpg After taking the screenshots above, I tried the same process using a CentOS7 minimal image on text mode to see the output, and there's no error output what so ever. Out of curiosity, I tried with a 4.3.3 ovirt node image and I had similar error as above(above I'm using 4.3.4) with a slight different wording, but still the same issue.
I ended up just installing CentOS. Wasn't my preferred way, but it gets things done.
participants (2)
-
rubentrindade＠live.com -
Strahil Nikolov