Problem with installing fedora33

Hi!
I have Asus zenbook 2014
I have two systems Windows 8 and Fedora 23.
After reset to factory setting windows removed my old fedora.
And than i can not install fedora 33.
I boot from Fefora Live Workstation 33.
That i click to “Install to Hard Drive” and anaconda did not start.
Where i can find errors of anaconda??
When i try to install Centos 8, i can see error “Pane is dead”.

How can i start anaconda at terminal for see errors?
Thanks

1 Like

I search that “modprobe.blacklist=cnic,bnx2i” can help, but unfortunately did not help me, because fedora33 do not boot from vmlinuz

https://docs.fedoraproject.org/en-US/fedora/rawhide/install-guide/install/Installing_Using_Anaconda/#sect-consoles-logs-during-installation

1 Like

I tried to install in TextMode, but when i try change start menu:
linuxefi … rd.live.image quite inst.text
Than click Ctrl+X and Fedora live boot in GraphicalMode

I tried to install Fedora 23
Anaconda is working, but in Fedora 30 - Anaconda is not working

As I understand you, you are saying that the Live CD boots fine but anaconda itself crashes. This is highly unusual. Did you find anything in the logs linked above?

Are you sure the computer does not have a hardware problem?

1 Like

Some system show anaconda problem in live system, later show graphic problem…! take care~

Unfortunately Fedora removed memory test from live dvd, may be problem with memory of notebook.
Here is screen shot for Fedora 30:
Because i removed fedora 33 from my flash drive.

I found similar error at google from Fedora 26, for example.
Errors are not fixed and the solution is unknown.

The same error, when i tryied install Fedora 27.
I found Fedora 23 only, which have not error

It doesn’t work with UEFI, unfortunately. You can get a comparable non-open-source (stand-alone bootable) tool from https://www.memtest86.com/

Can you please file a bug in bugzilla against the “anaconda” component? Please include a copy-paste of the traceback you’ve shown there, not just a screenshot.

Without knowing exactly what’s going on it looks like the problem is that it’s scanning your devices for system partitions and coming across a string in a format it wasn’t expecting.

And (again, without really knowing what I’m talking about), here’s a related change which landed in F27 1412022 – During RHEL 7 installation, anaconda should ignore partition with OEMDRV label, which probably explains why that older version works.

Can you run this with sudo lsblk -f so it prints the labels?

Okay, not seeing anything weird there — I was kind of hoping for something easy like garbage in a label.

What’s sda3? That’s the only thing that strikes me as slightly interesting since it’s got nothing…

sda1 100M EFI system
sda2 900M Windows recovery environment
sda3 128M Microsoft reserved
sda4 85.6G Microsoft basic data
sda5 20G Windows recovery environment
sda6 500M Here was /boot
sda7 8G Linux swap
sda8 Here was /
empty 79G – Here was /home, i removed it
I do not know what is sda5, very big size for recovery.

I think that fedora 33 can use 79G only

Yeah, I think there’s probably a real bug here. Can you file one at Log in to Red Hat Bugzilla please?

I speak english very poor(bad), and i can not write good text at Bugzilla.
Here is nohup of /usr/bin/livinst

/usr/bin/livinst

Traceback (most recent call last):
File “/usr/bin/anaconda-cleanup”, line 80, in
devicetree.populate(cleanup_only=True)
File “/usr/lib/python3.9/site-packages/blivet/threads.py”, line 53, in run_with_lock
return m(*args, **kwargs)
File “/usr/lib/python3.9/site-packages/blivet/populator/populator.py”, line 416, in populate
self._populate()
File “/usr/lib/python3.9/site-packages/blivet/threads.py”, line 53, in run_with_lock
return m(*args, **kwargs)
File “/usr/lib/python3.9/site-packages/blivet/populator/populator.py”, line 442, in _populate
new_devices = udev.get_devices()
File “/usr/lib/python3.9/site-packages/blivet/udev.py”, line 81, in get_devices
dev = device_to_dict(device)
File “/usr/lib/python3.9/site-packages/blivet/udev.py”, line 53, in device_to_dict
result = dict(device.properties)
File “/usr/lib/python3.9/site-packages/pyudev/device/_device.py”, line 1068, in getitem
return ensure_unicode_string(value)
File “/usr/lib/python3.9/site-packages/pyudev/_util.py”, line 64, in ensure_unicode_string
value = value.decode(sys.getfilesystemencoding())
UnicodeDecodeError: ‘utf-8’ codec can’t decode byte 0xd1 in position 4: invalid continuation byte
Starting installer, one moment…
terminal size detection failed, using default width
anaconda 33.25.4-1.fc33 for Fedora 33 started.

  • installation log files are stored in /tmp during the installation
  • shell is available on TTY2 and in second TMUX pane (ctrl+b, then press 2)
  • when reporting a bug add logs from /tmp as separate text/plain attachments
    Traceback (most recent call last):
    File “/sbin/anaconda”, line 635, in
    ignore_oemdrv_disks()
    File “/usr/lib64/python3.9/site-packages/pyanaconda/ui/lib/storage.py”, line 384, in ignore_oemdrv_disks
    matched = device_matches(“LABEL=OEMDRV”, disks_only=True)
    File “/usr/lib64/python3.9/site-packages/pyanaconda/core/storage.py”, line 180, in device_matches
    single_spec_matches = udev.resolve_glob(full_spec)
    File “/usr/lib/python3.9/site-packages/blivet/udev.py”, line 163, in resolve_glob
    for dev in get_devices():
    File “/usr/lib/python3.9/site-packages/blivet/udev.py”, line 81, in get_devices
    dev = device_to_dict(device)
    File “/usr/lib/python3.9/site-packages/blivet/udev.py”, line 53, in device_to_dict
    result = dict(device.properties)
    File “/usr/lib/python3.9/site-packages/pyudev/device/_device.py”, line 1068, in getitem
    return ensure_unicode_string(value)
    File “/usr/lib/python3.9/site-packages/pyudev/_util.py”, line 64, in ensure_unicode_string
    value = value.decode(sys.getfilesystemencoding())
    UnicodeDecodeError: ‘utf-8’ codec can’t decode byte 0xd1 in position 4: invalid continuation byte