Seite 1 von 1

Fehler bei WinXP-Installation

Verfasst: 03 Aug 2011, 10:03
von ake
Hallo,

auf einem OPSI4-Server kommt bei der Installation von WindowsXP auf neuen Rechner immer der Fehler:

Code: Alles auswählen

local variable 'type' referenced before assignment
Die Installation scheint in diesem Moment bei der Treiberintegration zu stehen. Hatte jemand schonmal dieses Problem?

Re: Fehler bei WinXP-Installation

Verfasst: 03 Aug 2011, 10:32
von d.oertel
Hi,
auf einem OPSI4-Server kommt bei der Installation von WindowsXP auf neuen Rechner immer der Fehler:
kannst Du das vielleicht noch ein wenig konkretisieren ?
In welcher Logdatei ?
Etwas mehr Kontext der Logdatei ...


gruss
d.oertel

Re: Fehler bei WinXP-Installation

Verfasst: 03 Aug 2011, 13:11
von ake
Das ist keine Logdatei, sondern die Ausgabe am angeschlossenen Bildschirm bei der OS-Installation. Dem Text hinter der Fehlermeldung nach, werden in dem Moment gerade die Treiber integriert.

Re: Fehler bei WinXP-Installation

Verfasst: 03 Aug 2011, 14:08
von d.oertel
Hi,

also kommt die Meldung nicht auf dem opsi-server sondern auf dem Client und zwar während das bootimage läuft ?

Wenn dem so ist:

bootimage aktuell ?

Log des bootimages posten.

gruss
d.oertel

Re: Fehler bei WinXP-Installation

Verfasst: 04 Aug 2011, 14:32
von ake
Hallo,

ja deine Aussagen sind richtig, hier der betreffende Logauszug:

Code: Alles auswählen

[6] [Aug 03 10:05:15] Trying to integrate textmode driver for storage controller: {'device': u'scsi0', 'vendorId': u'8086', 'hwPath': u'/0/100/1f.2', 'description': u'6 Series Chipset Family 4 port SATA IDE Controller', 'deviceId': u'1C00'} (setup.py|139)
[5] [Aug 03 10:05:15] Integrating textmode drivers (WindowsDrivers.py|290)
[6] [Aug 03 10:05:15] Searching for txtsetup.oem in '/mnt/hd/drv' (WindowsDrivers.py|295)
[7] [Aug 03 10:05:15] Including file 'txtsetup.oem' (__init__.py|672)
[7] [Aug 03 10:05:15] Including file 'txtsetup.oem' (__init__.py|672)
[7] [Aug 03 10:05:16] Including file 'TXTSETUP.OEM' (__init__.py|672)
[7] [Aug 03 10:05:16] Including file 'txtsetup.oem' (__init__.py|672)
[7] [Aug 03 10:05:16] Including file 'TXTSETUP.OEM' (__init__.py|672)
[6] [Aug 03 10:05:16] File '/mnt/hd/drv/5/lenovoM81/LAN/c2etn22us17/APPS/iSCSI/Win32/txtsetup.oem' found (WindowsDrivers.py|302)
[7] [Aug 03 10:05:16] Parsing txtsetup.oem file /mnt/hd/drv/5/lenovoM81/LAN/c2etn22us17/APPS/iSCSI/Win32/txtsetup.oem (__init__.py|996)
[7] [Aug 03 10:05:16] Trying to lock file '/mnt/hd/drv/5/lenovoM81/LAN/c2etn22us17/APPS/iSCSI/Win32/txtsetup.oem' (0/2000) (__init__.py|190)
[7] [Aug 03 10:05:16] File '/mnt/hd/drv/5/lenovoM81/LAN/c2etn22us17/APPS/iSCSI/Win32/txtsetup.oem' locked after 0 millis (__init__.py|212)
[6] [Aug 03 10:05:16] Searching for component names and options (__init__.py|1022)
[6] [Aug 03 10:05:16] Component names found: [u'scsi'] (__init__.py|1045)
[6] [Aug 03 10:05:16] Component options found: [{'componentName': u'scsi', 'optionName': None, 'description': u'Intel(R) iSCSI Setup Driver', 'componentId': u'IntelSCSI'}] (__init__.py|1046)
[6] [Aug 03 10:05:16] Searching for default component ids (__init__.py|1049)
[6] [Aug 03 10:05:16] Found default component ids: [{'componentName': u'scsi', 'componentId': u'IntelSCSI'}] (__init__.py|1058)
[6] [Aug 03 10:05:16] Searching for devices (__init__.py|1061)
[6] [Aug 03 10:05:16] Found hardwareIds section 'HardwareIds.scsi.IntelSCSI', component name 'scsi', component id 'IntelSCSI' (__init__.py|1068)
[3] [Aug 03 10:05:16] Parse error: =>Root\InteliSCSI<= (__init__.py|1088)
[2] [Aug 03 10:05:17] Traceback: (Logger.py|721)
[2] [Aug 03 10:05:17]      line 1381 in '<module>' in file '/usr/local/bin/master.py' (Logger.py|721)
[2] [Aug 03 10:05:17]      line 141 in '<module>' in file '/tmp/setup.py' (Logger.py|721)
[2] [Aug 03 10:05:17]      line 308 in 'integrateWindowsTextmodeDrivers' in file '/usr/lib/pymodules/python2.6/OPSI/Util/WindowsDrivers.py' (Logger.py|721)
[2] [Aug 03 10:05:17]      line 913 in 'isDeviceKnown' in file '/usr/lib/pymodules/python2.6/OPSI/Util/File/__init__.py' (Logger.py|721)
[2] [Aug 03 10:05:17]      line 1089 in 'parse' in file '/usr/lib/pymodules/python2.6/OPSI/Util/File/__init__.py' (Logger.py|721)
[2] [Aug 03 10:05:17]      ==>>> local variable 'type' referenced before assignment (master.py|1429)
[7] [Aug 03 10:05:17] Backend: <OPSI.Backend.JSONRPC.JSONRPCBackend instance at 0x8a8538c> (master.py|1432)
[7] [Aug 03 10:05:17] ProductId: winxppro (master.py|1433)
[7] [Aug 03 10:05:17] ClientId: zeus.imiq.local (master.py|1434)
[7] [Aug 03 10:05:17] ProductOnClient: <ProductOnClient clientId 'zeus.imiq.local', productId 'winxppro', installationStatus 'unknown', actionRequest 'none'> (master.py|1435)
[6] [Aug 03 10:05:17] Updating productOnClient: {'actionProgress': u'', 'actionResult': u'failed', 'clientId': u'zeus.imiq.local', 'modificationTime': None, 'actionRequest': u'none', 'targetConfiguration': None, 'productVersion': None, 'productType': u'NetbootProduct', 'type': u'ProductOnClient', 'lastAction': None, 'packageVersion': None, 'actionSequence': None, 'installationStatus': u'unknown', 'productId': u'winxppro'} (master.py|1446)
[7] [Aug 03 10:05:17] Executing jsonrpc method 'productOnClient_updateObjects' on host 192.168.4.45 (JSONRPC.py|104)
[7] [Aug 03 10:05:17] Starting new HTTPS connection (0) to 192.168.4.45:4447 (HTTP.py|493)
[7] [Aug 03 10:05:17] Connection established to: 192.168.4.45 (HTTP.py|496)
[7] [Aug 03 10:05:18] Closing connection: <httplib.HTTPSConnection instance at 0x8e9dbac> (HTTP.py|425)
[7] [Aug 03 10:05:18] Content-Type: gzip-application/json;charset=utf-8, Content-Encoding: gzip (JSONRPC.py|635)
[7] [Aug 03 10:05:18] Expecting compressed data from server (JSONRPC.py|639)

Re: Fehler bei WinXP-Installation

Verfasst: 05 Aug 2011, 11:55
von d.oertel
Hi,

bitte mal die

lenovoM81/LAN/c2etn22us17/APPS/iSCSI/Win32/txtsetup.oem

posten

danke

d.oertel

Re: Fehler bei WinXP-Installation

Verfasst: 08 Aug 2011, 09:26
von ake
Hier die txtsetup.txt

Code: Alles auswählen

;
; format for txtsetup.oem.
;
; Follow this format for PNP adapters like PCI and ISAPNP
;
; Follow the txtsetup.oem in aha154x for non-PNP adapters
;
; Txtsetup.oem is a generic way to install Storage adapters to get them through
; textmode setup.  Do as little as possible and allow GUI mode setup to do the 
; remaining work using the supplied inf.
;
; General format:
;
; [section]
; key = value1,value2,...
;
;
; The hash ('#') or semicolon (';') introduces a comment.
; Strings with embedded spaces, commas, or hashes should be double-quoted
;


; This section lists all disks in the disk set.
;
; <description> is a descriptive name for a disk, used when
;   prompting for the disk
; <tagfile> is a file whose presence allows setup to recognize
;   that the disk is inserted.
; <directory> is where the files are located on the disk.
;
[Disks]
d1 = "Intel iSCSI DISK",\


; This section lists the default selection for each 'required'
; hardware component.  If a line is not present for a component,
; the default defaults to the first item in the [<component_name>]
; section (see below).
;
; <component_name> is one of computer, display, keyboard, mouse, scsi
; <id> is a unique <within the component> string to be associated
;   with an option.
[Defaults]
scsi = IntelSCSI

; This section lists the options available for a particular component.
;
; <id> is the unique string for the option
; <description> is a text string, presented to the user in a menu
; <key_name> gives the name of the key to be created for the component in
;   HKEY_LOCAL_MACHINE\ControlSet001\Services
[scsi]
IntelSCSI = "Intel(R) iSCSI Setup Driver"

; This section lists the files that should be copied if the user
; selects a particular component option.
;
; <file_type> is one of driver, port, class, dll, hal, inf, or detect.
;   See below.
; <source_disk> identifies where the file is to be copied from, and must
;   match en entry in the [Disks] section.
; <filename> is the name of the file. This will be appended to the
;   directory specified for the disk in the [Disks] section to form the
;   full path of the file on the disk.
; <driverkey> this is the name that will show under the services\driver key
; this should be the same name as the driver that is being installed.

[Files.scsi.IntelSCSI]
driver  = d1, iSSetup.sys, iSSetup
inf     = d1, iSSetup.inf
catalog = d1, iSSetup.cat

; This section specifies values to be set in the registry for
; particular component options.  Required values in the services\xxx
; key are created automatically -- use this section to specify additional
; keys to be created in services\xxx and values in services\xxx and
; services\xxx\yyy.
;
; This section must be filled out for storage controllers that 
; are PNP adapters like PCI and ISA PNP adapters.  Failure to do this 
; can cause the driver failure to load. Must also add the section
; [HardwareIds.scsi.ID] to identify the supported ID's.
;
; <key_name> is relative to the services node for this device.
;   If it is empty, then it refers to the services node.
;   If specified, the key is created first.
; <value_name> specifies the value to be set within the key
; <value_type> is a string like REG_DWORD.  See below.
; <value> specifies the actual value; its format depends on <value_type>
;
;[Config.IntelSCSI]
;value = parameters\PnpInterface,0,REG_DWORD,1
;value = parameters\PnpInterface,1,REG_DWORD,1

; This section sets up the ID's that are to be supported by
; the driver.
;
; 'id =' prepend needed to identify that this is an id.
; <pnp_id> specifies the pnp ID to match too.
; <driver_name> this is the driver name specified in [Files.scsi.Id]
; without the .sys attached to the end.
;
[HardwareIds.scsi.IntelSCSI]
id = "Root\InteliSCSI", "iSSetup"

Re: Fehler bei WinXP-Installation

Verfasst: 08 Aug 2011, 14:00
von j.schneider
Hallo,

bitte einmal das testing-Bootimage (20110808-1) ausprobieren:
http://download.opensuse.org/repositori ... 0-testing/

Gruß,
Jan Schneider

Re: Fehler bei WinXP-Installation

Verfasst: 08 Aug 2011, 17:44
von ake
Jetzt wurde die Datei zumindest erkannt, dann kam direkt ein Bluescreen:

Code: Alles auswählen

*** STOP: 0x0000007B (0xF78D2524,0xC0000034,0x00000000,0x00000000)
Im Bios SATA AHCI deaktiviert und neu gestartet und siehe da: Es geht.