forum.opsi.org

opsi support forum
https://forum.opsi.org/

Opsi 4 - IBM Hardware x3650 m3

https://forum.opsi.org/viewtopic.php?t=2355

Seite 1 von 1

Opsi 4 - IBM Hardware x3650 m3

Verfasst: 02 Mär 2011, 13:35
von Popken
Hallo ich habe folgendes Problem mit der Windows2003 R2 32/64 Bit installation auf IBM Hardware.
Opsi 4.0.1.5
Bootimage: opsi-linux-bootimage_20110117-1_all.deb

Im Boot-Log sieht soweit alles gut aus.

Code: Alles auswählen

[6] [Mär 02 13:01:35] Trying to integrate textmode driver for storage controller: {'device': u'scsi0', 'vendorId': u'1000', 'hwPath': u'/0/100/1c/0', 'description': u'LSI MegaSAS 9260', 'deviceId': u'0079'} (setup.py|139)
[5] [Mär 02 13:01:35] Integrating textmode drivers (WindowsDrivers.py|290)
[6] [Mär 02 13:01:35] Searching for txtsetup.oem in '/mnt/hd/drv' (WindowsDrivers.py|295)
[7] [Mär 02 13:01:35] Including file 'txtsetup.oem' (__init__.py|708)
[6] [Mär 02 13:01:35] File '/mnt/hd/drv/2/txtsetup.oem' found (WindowsDrivers.py|302)
[7] [Mär 02 13:01:35] Parsing txtsetup.oem file /mnt/hd/drv/2/txtsetup.oem (__init__.py|921)
[7] [Mär 02 13:01:35] Trying to lock file '/mnt/hd/drv/2/txtsetup.oem' (0/2000) (__init__.py|165)
[7] [Mär 02 13:01:35] File '/mnt/hd/drv/2/txtsetup.oem' locked after 0 millis (__init__.py|187)
[6] [Mär 02 13:01:35] Searching for component names and options (__init__.py|947)
[6] [Mär 02 13:01:35] Component names found: [u'scsi'] (__init__.py|970)
[6] [Mär 02 13:01:35] Component options found: [{'componentName': u'scsi', 'optionName': u'megasas', 'description': u'LSI MegaRAID SAS RAID Controller Driver (Windows 2000)', 'componentId': u'MEGASAS'}, {'componentName': u'scsi', 'optionName': u'msas2k3', 'description': u'LSI MegaRAID SAS RAID Controller Driver (Server 2003 32-bit)', 'componentId': u'MSAS2K3'}] (__init__.py|971)
[6] [Mär 02 13:01:35] Searching for default component ids (__init__.py|974)
[6] [Mär 02 13:01:35] Found default component ids: [{'componentName': u'scsi', 'componentId': u'MEGASAS'}] (__init__.py|983)
[6] [Mär 02 13:01:35] Searching for devices (__init__.py|986)
[6] [Mär 02 13:01:35] Found hardwareIds section 'HardwareIds.scsi.MEGASAS', component name 'scsi', component id 'MEGASAS' (__init__.py|993)
[7] [Mär 02 13:01:35]    Found PCI device: 1000:0411, service name: megasas (__init__.py|1023)
...
[6] [Mär 02 13:01:35] Found hardwareIds section 'HardwareIds.scsi.MSAS2K3', component name 'scsi', component id 'MSAS2K3' (__init__.py|993)
...
[6] [Mär 02 13:01:35] Found services: [u'megasas', u'msas2k3'] (__init__.py|1032)
........
[6] [Mär 02 13:01:35] Searching for disks (__init__.py|1036)
[6] [Mär 02 13:01:35] Found driver disks: [{'diskName': u'd1', 'description': u'LSI MegaRAID SAS RAID Controller Driver (Windows 2000)', 'driverDir': u'', 'tagfile': u'megasas.sys'}, {'diskName': u'd2', 'description': u'LSI MegaRAID SAS RAID Controller Driver (Server 2003 32-bit)', 'driverDir': u'', 'tagfile': u'msas2k3.sys'}] (__init__.py|1056)
[6] [Mär 02 13:01:35] Searching for files (__init__.py|1059)
[6] [Mär 02 13:01:35] Found files section 'Files.scsi.MSAS2K3', component name 'scsi', component id 'MSAS2K3' (__init__.py|1066)
[6] [Mär 02 13:01:35] Found files section 'Files.scsi.MEGASAS', component name 'scsi', component id 'MEGASAS' (__init__.py|1066)
[7] [Mär 02 13:01:35] Found files: [{'diskName': u'd2', 'componentName': u'scsi', 'fileType': u'driver', 'filename': u'msas2k3.sys', 'optionName': u'msas2k3', 'componentId': u'MSAS2K3'}, {'diskName': u'd2', 'componentName': u'scsi', 'fileType': u'inf', 'filename': u'oemsetup.inf', 'optionName': u'msas2k3', 'componentId': u'MSAS2K3'}, {'diskName': u'd2', 'componentName': u'scsi', 'fileType': u'inf', 'filename': u'nodev.inf', 'optionName': None, 'componentId': u'MSAS2K3'}, {'diskName': u'd2', 'componentName': u'scsi', 'fileType': u'catalog', 'filename': u'megasas.cat', 'optionName': None, 'componentId': u'MSAS2K3'}, {'diskName': u'd1', 'componentName': u'scsi', 'fileType': u'driver', 'filename': u'megasas.sys', 'optionName': u'megasas', 'componentId': u'MEGASAS'}, {'diskName': u'd1', 'componentName': u'scsi', 'fileType': u'inf', 'filename': u'oemsetup.inf', 'optionName': u'megasas', 'componentId': u'MEGASAS'}, {'diskName': u'd1', 'componentName': u'scsi', 'fileType': u'inf', 'filename': u'nodev.inf', 'optionName': None, 'componentId': u'MEGASAS'}, {'diskName': u'd1', 'componentName': u'scsi', 'fileType': u'catalog', 'filename': u'megasas.cat', 'optionName': None, 'componentId': u'MEGASAS'}] (__init__.py|1077)
[6] [Mär 02 13:01:35] Searching for configs (__init__.py|1081)
[6] [Mär 02 13:01:35] Found configs section 'Config.megasas', component id 'megasas' (__init__.py|1087)
[6] [Mär 02 13:01:35] Found configs section 'Config.msas2k3', component id 'msas2k3' (__init__.py|1087)
[7] [Mär 02 13:01:35] Found configs: [{'valueType': u'REG_DWORD', 'keyName': u'""', 'componentId': u'megasas', 'value': u'20', 'valueName': u'Tag'}, {'valueType': u'REG_DWORD', 'keyName': u'parameters\\PnpInterface', 'componentId': u'msas2k3', 'value': u'1', 'valueName': u'5'}, {'valueType': u'REG_DWORD', 'keyName': u'""', 'componentId': u'msas2k3', 'value': u'20', 'valueName': u'Tag'}] (__init__.py|1096)
[7] [Mär 02 13:01:35] Textmode driver '/mnt/hd/drv/2' supports device {'vendorId': u'1000', 'deviceId': u'0079'} (WindowsDrivers.py|309)
[5] [Mär 02 13:01:35] Integrating textmode driver '/mnt/hd/drv/2' (WindowsDrivers.py|319)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/megasas.sys' to '/mnt/hd/$/textmode/megasas.sys' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/megasas.sys' to '/mnt/hd/$win_nt$.~bt/$oem$/megasas.sys' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/oemsetup.inf' to '/mnt/hd/$/textmode/oemsetup.inf' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/oemsetup.inf' to '/mnt/hd/$win_nt$.~bt/$oem$/oemsetup.inf' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/nodev.inf' to '/mnt/hd/$/textmode/nodev.inf' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/nodev.inf' to '/mnt/hd/$win_nt$.~bt/$oem$/nodev.inf' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/megasas.cat' to '/mnt/hd/$/textmode/megasas.cat' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/megasas.cat' to '/mnt/hd/$win_nt$.~bt/$oem$/megasas.cat' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/txtsetup.oem' to '/mnt/hd/$/textmode' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[7] [Mär 02 13:01:35] MessageSubject 'copy_progress' created (Message.py|112)
[7] [Mär 02 13:01:35] ProgressSubject 'copy_progress' created (Message.py|238)
[6] [Mär 02 13:01:35] Copying from '/mnt/hd/drv/2/txtsetup.oem' to '/mnt/hd/$win_nt$.~bt/$oem$' (__init__.py|257)
[6] [Mär 02 13:01:35] Copy done (__init__.py|267)
[5] [Mär 02 13:01:35] Registering textmode drivers in sif file '/mnt/hd/$win_nt$.~bt/winnt.sif' (WindowsDrivers.py|343)
[6] [Mär 02 13:01:35] Patching sections for driver 'LSI MegaRAID SAS RAID Controller Driver (Windows 2000)' (WindowsDrivers.py|365)
[7] [Mär 02 13:01:35] Patching [MassStorageDrivers] in file '/mnt/hd/$win_nt$.~bt/winnt.sif': (WindowsDrivers.py|376)
[7] [Mär 02 13:01:35] [u'\r\n', u'[MassStorageDrivers]\r\n', u'"LSI MegaRAID SAS RAID Controller Driver (Windows 2000)" = "OEM"\r\n'] (WindowsDrivers.py|377)
[7] [Mär 02 13:01:35] Patching [OEMBootFiles] in file '/mnt/hd/$win_nt$.~bt/winnt.sif': (WindowsDrivers.py|379)
[7] [Mär 02 13:01:35] [u'\r\n', u'[OEMBootFiles]\r\n', u'megasas.sys\r\n', u'oemsetup.inf\r\n', u'nodev.inf\r\n', u'megasas.cat\r\n', u'txtsetup.oem\r\n'] (WindowsDrivers.py|380)
[6] [Mär 02 13:01:35] Generating oemPnpDriversPath (WindowsDrivers.py|458)
[6] [Mär 02 13:01:35] Returning oemPnpDriversPath 'drv\1;drv\2;drv\3' (WindowsDrivers.py|478)
[6] [Mär 02 13:01:35] Executing: /usr/local/bin/patcha '/mnt/hd/$win_nt$.~bt/winnt.sif' (Posix.py|610)
[6] [Mär 02 13:01:35] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mär 02 13:01:35] Exit code: 0 (Posix.py|695)
[6] [Mär 02 13:01:35] Executing: /usr/local/bin/patcha -f /var/tmp/opsi/patcha.in '/mnt/hd/$win_nt$.~bt/winnt.sif' (Posix.py|610)
[6] [Mär 02 13:01:35] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mär 02 13:01:35] Exit code: 0 (Posix.py|695)
[6] [Mär 02 13:01:35] Executing: /usr/local/bin/patcha '/mnt/hd/opsi/opsi-client-agent/files/opsi/cfg/config.ini' (Posix.py|610)
[6] [Mär 02 13:01:35] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mär 02 13:01:35] Exit code: 0 (Posix.py|695)
[6] [Mär 02 13:01:35] Executing: /usr/local/bin/patcha -f /var/tmp/opsi/patcha.in '/mnt/hd/opsi/opsi-client-agent/files/opsi/cfg/config.ini' (Posix.py|610)
[6] [Mär 02 13:01:35] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mär 02 13:01:35] Exit code: 0 (Posix.py|695)
[7] [Mär 02 13:01:35] Command 'umount' found at: '/bin/umount' (Posix.py|590)
[6] [Mär 02 13:01:35] Executing: /bin/umount /dev/sda1 (Posix.py|610)
[6] [Mär 02 13:01:35] Using encoding 'UTF-8' (Posix.py|641)
[7] [Mär 02 13:01:36] Exit code: 0 (Posix.py|695)
[7] [Mär 02 13:01:36] Command 'sleep' found at: '/bin/sleep' (Posix.py|590)
[7] [Mär 02 13:01:36] Command 'shutdown' found at: '/sbin/shutdown' (Posix.py|590)
[6] [Mär 02 13:01:36] Executing: /bin/sleep 60; /sbin/shutdown -r now (Posix.py|610)
[7] [Mär 02 13:01:36] Command 'bash' found at: '/bin/bash' (Posix.py|590)
[5] [Mär 02 13:01:36] Script execution successful (master.py|1401)
Auf einer VMWARE funktioniert die Installation

Hat schon jemand mit der Hardware schon Erfahrungen gesammelt?

Re: Opsi 4 - IBM Hardware x3650 m3

Verfasst: 02 Mär 2011, 13:41
von ueluekmen
Hi,

ist das wirklich der richtige Treiber?
LSI MegaRAID SAS RAID Controller Driver (Windows 2000)

Sieht komisch aus.

Re: Opsi 4 - IBM Hardware x3650 m3

Verfasst: 02 Mär 2011, 13:46
von Popken
Ja ist der Originaltreiber von der Hardware-CD. Von Hand über F6 funktioniert dieser auch.

In der txtsetup.oem des Treibers sind zwei Einträge.

Code: Alles auswählen

[Disks]
d1 = "LSI MegaRAID SAS RAID Controller Driver (Windows 2000)", \megasas.sys, \
d2 = "LSI MegaRAID SAS RAID Controller Driver (Server 2003 32-bit)", \msas2k3.sys, \
]

Re: Opsi 4 - IBM Hardware x3650 m3

Verfasst: 02 Mär 2011, 14:23
von ueluekmen
Hi,

ich würde als nächstes gucken, was in der Zeile 4 der Datei überhaupt steht.

Irgendwas scheint da schief zu laufen. Die volle Bootimage-Log würde auch weiterhelfen.

Ansonsten schreit das aber förmlich nach einem Support-Vertrag.

Re: Opsi 4 - IBM Hardware x3650 m3

Verfasst: 02 Mär 2011, 15:25
von Popken
Habe die Logs mal angehägt. Bootlog ist gezippt, da über 2 MB
Das ist die txtsetup.sif vom Server.... Zeile 4 wäre dann wohl die signature....
Alle Zeiten sind UTC+02:00
Seite 1 von 1

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de