Bug 26363 - upgrade fails on a UP1000
upgrade fails on a UP1000
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.0
alpha Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-06 16:45 EST by Need Real Name
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-02-07 16:51:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-02-06 16:45:04 EST
raceback (innermost last):
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line
20, in run
    rc = self.todo.doInstall ()
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1480, in
doInstall
    if self.method.systemMounted (self.fstab, self.instPath,
self.hdList.selected()):
  File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py", line 63, in
systemMounted
    isys.lochangefd("/tmp/loop", self.loopbackFile)
  File "/usr/lib/anaconda/isys.py", line 55, in lochangefd
    _isys.lochangefd(loop, targ)
SystemError: (22, 'Invalid argument')

Local variables in innermost frame:
file: /mnt/sysimage/home/rhinstall-stage2.img
loop: 15
targ: 16
device: /tmp/loop
ToDo object:
(itodo
ToDo
p1
(dp2
S'method'
p3
(iimage
CdromInstallMethod
p4
(dp5
S'currentDisc'
p6
I1
sS'tree'
p7
S'/mnt/source'
sS'device'
p8
S'hdc'
sS'progressWindow'
p9

<failed>

System: UP1000  (booting with API apb.exe)
Comment 1 Matt Wilson 2001-02-07 15:07:24 EST
you are using the stock kernel to boot, yes?
Comment 2 Need Real Name 2001-02-07 16:49:25 EST
Right!. If I copy the kernell from cdrom/kernells instead of the diskette image.
I can do the upgrade.
Thanks.

Comment 3 Matt Wilson 2001-02-07 16:51:16 EST
no worries, not a bug then. :)

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