Bug 5125 - Upgrade fails.
Upgrade fails.
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Brock Organ
Depends On:
  Show dependency treegraph
Reported: 1999-09-14 08:47 EDT by Kjartan Maraas
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-06-28 15:05:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kjartan Maraas 1999-09-14 08:47:12 EDT
When I try to upgrade from 6.0.50 to the latest iso from
gribble, it just hangs after saying: "Searching for Red Hat
Linux installations"

The same happened when I tried to upgrade from 6.0 to the
first beta.

First console shows:

error opening security policy file

Glib-WARNING **: getpwuid_r(): failed due to: No such user
Traceback (innermost last):
  File "/usr/lib/python1.5/site-packages/gtk.py", line 120,
in __call__
    ret = apply(seld.func, a)
  File "/usr/lib/python1.5/site-packages/gui.py", line 183,
in nextClicked
    self.setScreen (self.currentScreen, self.nextClicked)
  File "/usr/lib/python1.5/site-packages/gui.py", line 216,
in setScreen
    new_screen = screen.getScreen ()
line 30, in getScreen
  File "/usr/lib/python1.5/site-packages/todo.py", line 924,
in upgradeFindRoot
    self.intf.messageWindow(_("Error"), _("Error mounting
%s: %s") %(device, msg))
NameError: device

and on console 4 i get:

<4>VFS: Can't find an ext2 filesystem on dev ide0(3,1)
Comment 1 Kjartan Maraas 1999-11-18 14:59:59 EST
I'm not 100% sure, but I guess this is the known NTFS bug in the
installer, so this could probably be closed

Kjartan Maraas
Comment 2 Brock Organ 2000-06-13 13:56:48 EDT
does this still occur using 6.2?
Comment 3 Brock Organ 2000-06-28 15:04:59 EDT
this should be fixed in 6.2 ... please reopen if still a problem ... thanks for
your report!

Note You need to log in before you can comment on or make changes to this bug.