Intel Raid - Erste Installation geht, zweit Installation geht nicht
Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hallo,
wir haben hier einen Rechner mit einem Intel Rapid Raid installiert. Die erste Installation hat funktioniert.
Als wir ein zweites mal installieren wollten, versucht das Netboot-image immer das Device /dev/sda zu nutzen, anstatt ein /dev/mdXXX.
Als Fehlermeldung kommt:
can´t det device qualifier: Resource temporarily unavailable
RunTimeError(Unable to get geometry for disk #/dev/sda'")
Gibt es da eine Lösung?
Danke
MS
wir haben hier einen Rechner mit einem Intel Rapid Raid installiert. Die erste Installation hat funktioniert.
Als wir ein zweites mal installieren wollten, versucht das Netboot-image immer das Device /dev/sda zu nutzen, anstatt ein /dev/mdXXX.
Als Fehlermeldung kommt:
can´t det device qualifier: Resource temporarily unavailable
RunTimeError(Unable to get geometry for disk #/dev/sda'")
Gibt es da eine Lösung?
Danke
MS
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hi
wo wird denn das Intel Rapid Raid konfiguriert? Im BIOS oder im Windows?
Welche Version der Netboot Pakete hast du?
In solch einem Fall ist ein komplettes Log deutlich besser zum Nachverfolgen des Fehlers, als nur die Zeile mit der Fehlermeldung
Welche Ausgabe liefert denn der Befehl?
Gruß
Mathias
wo wird denn das Intel Rapid Raid konfiguriert? Im BIOS oder im Windows?
Welche Version der Netboot Pakete hast du?
In solch einem Fall ist ein komplettes Log deutlich besser zum Nachverfolgen des Fehlers, als nur die Zeile mit der Fehlermeldung
Welche Ausgabe liefert denn der Befehl
Code: Alles auswählen
blkid
Gruß
Mathias
Kein Support per DM!
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hallo,
hat etwas gedauert, aber mit HomeOffice ist das nicht immer ganz einfach!
Das RAID wird über das BIOS konfiguriert!
Das Netboot Produkt win10_x86 liegt in 4.1.0.2-14 vor.
blid liefert folgendes:
Und hier noch das Log:
Besten Dank
MS
hat etwas gedauert, aber mit HomeOffice ist das nicht immer ganz einfach!
Das RAID wird über das BIOS konfiguriert!
Das Netboot Produkt win10_x86 liegt in 4.1.0.2-14 vor.
blid liefert folgendes:
Code: Alles auswählen
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/md126p1: SEC_TYPE="msdos" UUID="CECE-0658" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/md126p2: PARTLABEL="MS reserved" PARTUUID="00000000-0000-0000-0000-000000000000"
/dev/md126p3: LABEL="WINDOWS" UUID="7A0BB8B17A539AC9" TYPE="ntfs" PTTYPE="dos" PARTLABEL="WINDOWS" PARTUUID="6aeafc2b-66d1-4415-be07-6af82edfc25d"
/dev/md126p4: LABEL_FATBOOT="WINPE" LABEL="WINPE" UUID="D0DE-0318" TYPE="vfat" PARTLABEL="WINPE" PARTUUID="9f4b325e-5e75-4310-973b-c1333e34d5c1"
Code: Alles auswählen
[7] [2021-06-21 13:46:58.916] [ ] Command sfdisk found at: /sbin/sfdisk (Posix.py:805)
[7] [2021-06-21 13:46:58.916] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-21 13:46:58.916] [ ] Executing: /sbin/sfdisk --no-reread -s (Posix.py:910)
[6] [2021-06-21 13:46:58.919] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:58.926] [ ] >>> /dev/sda: 250059096 (Posix.py:992)
[7] [2021-06-21 13:46:58.926] [ ] >>> /dev/sdb: 250059096 (Posix.py:992)
[7] [2021-06-21 13:46:58.926] [ ] >>> /dev/md126: 250056704 (Posix.py:992)
[7] [2021-06-21 13:46:58.926] [ ] >>> total: 750174896 blocks (Posix.py:992)
[7] [2021-06-21 13:46:58.926] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:58.926] [ ] Exit code: 0 (Posix.py:999)
[7] [2021-06-21 13:46:58.926] [ ] Found disk =>>> dev: '/dev/sda', size: 250.06 GB (Posix.py:1069)
[7] [2021-06-21 13:46:58.932] [ ] Command modprobe found at: /sbin/modprobe (Posix.py:805)
[7] [2021-06-21 13:46:58.932] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-21 13:46:58.932] [ ] Executing: /sbin/modprobe edd (Posix.py:910)
[6] [2021-06-21 13:46:58.935] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:58.990] [ ] >>> modprobe: ERROR: could not insert 'edd': No such device (Posix.py:992)
[7] [2021-06-21 13:46:58.990] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:58.990] [ ] Exit code: 1 (Posix.py:999)
[3] [2021-06-21 13:46:58.990] [ ] Command '/sbin/modprobe edd' failed (1):
modprobe: ERROR: could not insert 'edd': No such device
(Posix.py:1312)
[7] [2021-06-21 13:46:58.990] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-21 13:46:58.990] [ ] Executing: /sbin/sfdisk --no-reread -s /dev/sda (Posix.py:910)
[6] [2021-06-21 13:46:58.993] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:59.002] [ ] >>> 250059096 (Posix.py:992)
[7] [2021-06-21 13:46:59.002] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:59.002] [ ] Exit code: 0 (Posix.py:999)
[6] [2021-06-21 13:46:59.002] [ ] Size of disk '/dev/sda': 256060514304 Byte / 256060.514304 MB (Posix.py:1453)
[7] [2021-06-21 13:46:59.002] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-21 13:46:59.002] [ ] Executing: /sbin/sfdisk --no-reread -l /dev/sda (Posix.py:910)
[6] [2021-06-21 13:46:59.005] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:59.018] [ ] >>> GPT PMBR size mismatch (500113407 != 500118191) will be corrected by write. (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> The backup GPT table is not on the end of the device. This problem will be corrected by write. (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Disk model: SAMSUNG MZ7LH256 (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Units: sectors of 1 * 512 = 512 bytes (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Sector size (logical/physical): 512 bytes / 512 bytes (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> I/O size (minimum/optimal): 512 bytes / 512 bytes (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Disklabel type: gpt (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Disk identifier: 2DFD2B7B-2BA0-4E84-8B2E-DCEC3D35B0BC (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> Device Start End Sectors Size Type (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> /dev/sda1 2048 204800 202753 99M EFI System (Posix.py:992)
[7] [2021-06-21 13:46:59.018] [ ] >>> /dev/sda2 206848 468991 262144 128M Microsoft reserved (Posix.py:992)
[7] [2021-06-21 13:46:59.019] [ ] >>> /dev/sda3 468992 478054399 477585408 227.7G Microsoft basic data (Posix.py:992)
[7] [2021-06-21 13:46:59.019] [ ] >>> /dev/sda4 478054400 498534399 20480000 9.8G Microsoft basic data (Posix.py:992)
[7] [2021-06-21 13:46:59.019] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:59.019] [ ] Exit code: 0 (Posix.py:999)
[7] [2021-06-21 13:46:59.019] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-21 13:46:59.019] [ ] Executing: /sbin/sfdisk -g /dev/sda (Posix.py:910)
[6] [2021-06-21 13:46:59.022] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:59.030] [ ] >>> /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] >>> GPT PMBR size mismatch (500113407 != 500118191) will be corrected by write. (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] >>> The backup GPT table is not on the end of the device. This problem will be corrected by write. (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] >>> (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] Exit code: 0 (Posix.py:999)
[5] [2021-06-21 13:46:59.030] [ ] geometryLine : /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track (Posix.py:1496)
[5] [2021-06-21 13:46:59.031] [ ] geometryLine : GPT PMBR size mismatch (500113407 != 500118191) will be corrected by write. (Posix.py:1496)
[2] [2021-06-21 13:47:00.034] [ ] Unable to get geometry for disk '/dev/sda' (Logger.py:344)
Traceback (most recent call last):
File "run-master", line 1647, in <module>
File "/tmp/setup.py", line 570, in <module>
disks = getHarddisks()
File "OPSI/System/Posix.py", line 1070, in getHarddisks
File "OPSI/System/Posix.py", line 1292, in __init__
File "OPSI/System/Posix.py", line 1468, in readPartitionTable
File "OPSI/System/Posix.py", line 1499, in _parsePartitionTable
RuntimeError: Unable to get geometry for disk '/dev/sda'
[7] [2021-06-21 13:47:00.035] [ ] Backend: <JSONRPCBackend(host=xxx.xxx.xxx.xxx, compression=True)> (run-master:1702)
[7] [2021-06-21 13:47:00.035] [ ] ProductId: win10-x64 (run-master:1703)
[7] [2021-06-21 13:47:00.035] [ ] ClientId: test.pc.lan (run-master:1704)
[7] [2021-06-21 13:47:00.035] [ ] ProductOnClient: <ProductOnClient(clientId='anite081.vlan-anite.office', productId='win10-x64', installationStatus='unknown', actionRequest='none')> (run-master:1705)
[6] [2021-06-21 13:47:00.035] [ ] Updating productOnClient: {'targetConfiguration': None, 'installationStatus': 'unknown', 'actionRequest': 'none', 'lastAction': None, 'actionProgress': '', 'actionResult': 'failed', 'productVersion': None, 'packageVersion': None, 'modificationTime': None, 'actionSequence': None, 'productId': 'win10-x64', 'productType': 'NetbootProduct', 'clientId': 'anite081.vlan-anite.office', 'type': 'ProductOnClient'} (run-master:1717)
[7] [2021-06-21 13:47:00.036] [ ] Executing jsonrpc method productOnClient_updateObjects on host xxx.xxx.xxx.xxx (JSONRPC.py:112)
[7] [2021-06-21 13:47:00.036] [ ] Posting request... (JSONRPC.py:726)
[7] [2021-06-21 13:47:00.036] [ ] Starting new HTTPS connection (1) to xxx.xxx.xxx.xxx:4447 (HTTP.py:521)
[7] [2021-06-21 13:47:00.036] [ ] Connection established to: xxx.xxx.xxx.xxx (HTTP.py:523)
[7] [2021-06-21 13:47:00.100] [ ] Closing connection: <http.client.HTTPSConnection object at 0x7f26fd4af520> (HTTP.py:427)
[5] [2021-06-21 13:47:00.101] [ ] EXITING (run-master:1723)
[5] [2021-06-21 13:47:00.101] [ ] Writing log to service (run-master:1729)
MS
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Guten Morgen,
das Problem ist folgendes
Eigentlich wird nur die Zeile mit den Cylindern Heads und Sectoren erwartet, die weiten Zeilen führen zu dem Problem, da das Parsing der Zeilen dann nicht sauber läft.
Mach mal
und schreibe das einfach mittels "w" schreiben.
Dann auch noch mit sdb und md126 um auszuschliessen das es da auch irgendwelche Ungereimtheiten gibt.
Danach nochmals laufen lassen.
Gruß
Mathias
das Problem ist folgendes
Code: Alles auswählen
[6] [2021-06-21 13:46:59.019] [ ] Executing: /sbin/sfdisk -g /dev/sda (Posix.py:910)
[6] [2021-06-21 13:46:59.022] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-21 13:46:59.030] [ ] >>> /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] >>> GPT PMBR size mismatch (500113407 != 500118191) will be corrected by write. (Posix.py:992)
[7] [2021-06-21 13:46:59.030] [ ] >>> The backup GPT table is not on the end of the device. This problem will be corrected by write. (Posix.py:992)
Mach mal
Code: Alles auswählen
sfdisk /dev/sda
Dann auch noch mit sdb und md126 um auszuschliessen das es da auch irgendwelche Ungereimtheiten gibt.
Danach nochmals laufen lassen.
Gruß
Mathias
Kein Support per DM!
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hallo,
danke für die Anwort, also wenn ich dich jetzt richtig verstanden habe:
Ich habe mich auf dem BootImage eingeloggt und
sfdisk /dev/sda
danach mit "write" speichern
und das Image nochmal laufen lassen!
Das habe ich jetzt entsprechend gemacht. Da ich aktuell nicht vor Ort bin, konnte ich den Rechner nicht neustarten (PXE auswählen), daher habe ich "master.sh" gestartet.
Gleicher Fehler!
Manfred
danke für die Anwort, also wenn ich dich jetzt richtig verstanden habe:
Ich habe mich auf dem BootImage eingeloggt und
sfdisk /dev/sda
danach mit "write" speichern
und das Image nochmal laufen lassen!
Das habe ich jetzt entsprechend gemacht. Da ich aktuell nicht vor Ort bin, konnte ich den Rechner nicht neustarten (PXE auswählen), daher habe ich "master.sh" gestartet.
Gleicher Fehler!
Manfred
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hi
bitte mach das auch für /dev/sdb und /dev/md126
Falls es weiterhin fehlschlägt, ist erneut ein Log nötig
Gruß
Mathias
bitte mach das auch für /dev/sdb und /dev/md126
Falls es weiterhin fehlschlägt, ist erneut ein Log nötig
Gruß
Mathias
Kein Support per DM!
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hallo,
ja das hattte ich schon gleich mit gemacht, hier das Log:
Manfred
ja das hattte ich schon gleich mit gemacht, hier das Log:
Code: Alles auswählen
[5] [2021-06-24 11:58:21.094] [ ] Swapoff all to avoid disk in use ..... (setup.py:566)
[7] [2021-06-24 11:58:21.094] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.094] [ ] Executing: swapoff -a -v (Posix.py:910)
[6] [2021-06-24 11:58:21.097] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.106] [ ] Exit code: 0 (Posix.py:999)
[5] [2021-06-24 11:58:21.106] [ ] Clear all existing LVM volume groups.... (<string>:163)
[7] [2021-06-24 11:58:21.203] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.203] [ ] Executing: vgs --noheadings 2> /dev/null (Posix.py:910)
[6] [2021-06-24 11:58:21.206] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.294] [ ] Exit code: 0 (Posix.py:999)
[5] [2021-06-24 11:58:21.294] [ ] Remove all dead Links in /dev.... (<string>:185)
[5] [2021-06-24 11:58:21.302] [ ] Remove all empty directories in /dev.... (<string>:187)
[5] [2021-06-24 11:58:21.307] [ ] Look for still existing LVM volume groups.... (<string>:190)
[7] [2021-06-24 11:58:21.307] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.307] [ ] Executing: vgs --noheadings 2> /dev/null (Posix.py:910)
[6] [2021-06-24 11:58:21.310] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.398] [ ] Exit code: 0 (Posix.py:999)
[7] [2021-06-24 11:58:21.403] [ ] Command sfdisk found at: /sbin/sfdisk (Posix.py:805)
[7] [2021-06-24 11:58:21.404] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.404] [ ] Executing: /sbin/sfdisk --no-reread -s (Posix.py:910)
[6] [2021-06-24 11:58:21.407] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.414] [ ] >>> /dev/sda: 250059096 (Posix.py:992)
[7] [2021-06-24 11:58:21.414] [ ] >>> /dev/sdb: 250059096 (Posix.py:992)
[7] [2021-06-24 11:58:21.414] [ ] >>> /dev/md126: 250056704 (Posix.py:992)
[7] [2021-06-24 11:58:21.414] [ ] >>> total: 750174896 blocks (Posix.py:992)
[7] [2021-06-24 11:58:21.414] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.414] [ ] Exit code: 0 (Posix.py:999)
[7] [2021-06-24 11:58:21.414] [ ] Found disk =>>> dev: '/dev/sda', size: 250.06 GB (Posix.py:1069)
[7] [2021-06-24 11:58:21.420] [ ] Command modprobe found at: /sbin/modprobe (Posix.py:805)
[7] [2021-06-24 11:58:21.420] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.420] [ ] Executing: /sbin/modprobe edd (Posix.py:910)
[6] [2021-06-24 11:58:21.423] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.486] [ ] >>> modprobe: ERROR: could not insert 'edd': No such device (Posix.py:992)
[7] [2021-06-24 11:58:21.486] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.486] [ ] Exit code: 1 (Posix.py:999)
[3] [2021-06-24 11:58:21.486] [ ] Command '/sbin/modprobe edd' failed (1):
modprobe: ERROR: could not insert 'edd': No such device
(Posix.py:1312)
[7] [2021-06-24 11:58:21.486] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.486] [ ] Executing: /sbin/sfdisk --no-reread -s /dev/sda (Posix.py:910)
[6] [2021-06-24 11:58:21.489] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.498] [ ] >>> 250059096 (Posix.py:992)
[7] [2021-06-24 11:58:21.498] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.498] [ ] Exit code: 0 (Posix.py:999)
[6] [2021-06-24 11:58:21.498] [ ] Size of disk '/dev/sda': 256060514304 Byte / 256060.514304 MB (Posix.py:1453)
[7] [2021-06-24 11:58:21.498] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.498] [ ] Executing: /sbin/sfdisk --no-reread -l /dev/sda (Posix.py:910)
[6] [2021-06-24 11:58:21.501] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.510] [ ] >>> Disk /dev/sda: 238.49 GiB, 256060514304 bytes, 500118192 sectors (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Disk model: SAMSUNG MZ7LH256 (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Units: sectors of 1 * 512 = 512 bytes (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Sector size (logical/physical): 512 bytes / 512 bytes (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> I/O size (minimum/optimal): 512 bytes / 512 bytes (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Disklabel type: gpt (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Disk identifier: 2DFD2B7B-2BA0-4E84-8B2E-DCEC3D35B0BC (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> Device Start End Sectors Size Type (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> /dev/sda1 2048 204800 202753 99M EFI System (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> /dev/sda2 206848 468991 262144 128M Microsoft reserved (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> /dev/sda3 468992 478054399 477585408 227.7G Microsoft basic data (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> /dev/sda4 478054400 498534399 20480000 9.8G Microsoft basic data (Posix.py:992)
[7] [2021-06-24 11:58:21.510] [ ] >>> The backup GPT table is corrupt, but the primary appears OK, so that will be used. (Posix.py:992)
[7] [2021-06-24 11:58:21.511] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.511] [ ] Exit code: 0 (Posix.py:999)
[7] [2021-06-24 11:58:21.511] [ ] Removing LD_LIBRARY_PATH from env for subprocess (Posix.py:824)
[6] [2021-06-24 11:58:21.511] [ ] Executing: /sbin/sfdisk -g /dev/sda (Posix.py:910)
[6] [2021-06-24 11:58:21.514] [ ] Using encoding 'UTF-8' (Posix.py:946)
[7] [2021-06-24 11:58:21.522] [ ] >>> /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track (Posix.py:992)
[7] [2021-06-24 11:58:21.522] [ ] >>> The backup GPT table is corrupt, but the primary appears OK, so that will be used. (Posix.py:992)
[7] [2021-06-24 11:58:21.522] [ ] >>> (Posix.py:992)
[7] [2021-06-24 11:58:21.522] [ ] Exit code: 0 (Posix.py:999)
[5] [2021-06-24 11:58:21.522] [ ] geometryLine : /dev/sda: 31130 cylinders, 255 heads, 63 sectors/track (Posix.py:1496)
[5] [2021-06-24 11:58:21.523] [ ] geometryLine : The backup GPT table is corrupt, but the primary appears OK, so that will be used. (Posix.py:1496)
[2] [2021-06-24 11:58:22.526] [ ] Unable to get geometry for disk '/dev/sda' (Logger.py:344)
Traceback (most recent call last):
File "run-master", line 1647, in <module>
File "/tmp/setup.py", line 570, in <module>
disks = getHarddisks()
File "OPSI/System/Posix.py", line 1070, in getHarddisks
File "OPSI/System/Posix.py", line 1292, in __init__
File "OPSI/System/Posix.py", line 1468, in readPartitionTable
File "OPSI/System/Posix.py", line 1499, in _parsePartitionTable
RuntimeError: Unable to get geometry for disk '/dev/sda'
[7] [2021-06-24 11:58:22.527] [ ] Backend: <JSONRPCBackend(host=xxx.xxx.xxx.xxx, compression=True)> (run-master:1702)
[7] [2021-06-24 11:58:22.527] [ ] ProductId: win10-x64 (run-master:1703)
[7] [2021-06-24 11:58:22.527] [ ] ClientId: anite081.vlan-anite.office (run-master:1704)
[7] [2021-06-24 11:58:22.527] [ ] ProductOnClient: <ProductOnClient(clientId='test.lan.test', productId='win10-x64', installationStatus='unknown', actionRequest='none')> (run-master:1705)
[6] [2021-06-24 11:58:22.527] [ ] Updating productOnClient: {'targetConfiguration': None, 'installationStatus': 'unknown', 'actionRequest': 'none', 'lastAction': None, 'actionProgress': '', 'actionResult': 'failed', 'productVersion': None, 'packageVersion': None, 'modificationTime': None, 'actionSequence': None, 'productId': 'win10-x64', 'productType': 'NetbootProduct', 'clientId': 'anite081.vlan-anite.office', 'type': 'ProductOnClient'} (run-master:1717)
[7] [2021-06-24 11:58:22.528] [ ] Executing jsonrpc method productOnClient_updateObjects on host xxx.xxx.xxx.xxx (JSONRPC.py:112)
[7] [2021-06-24 11:58:22.528] [ ] Posting request... (JSONRPC.py:726)
[7] [2021-06-24 11:58:22.528] [ ] Starting new HTTPS connection (1) to xxx.xxx.xxx.xxx:4447 (HTTP.py:521)
[7] [2021-06-24 11:58:22.528] [ ] Connection established to: xxx.xxx.xxx.xxx (HTTP.py:523)
[7] [2021-06-24 11:58:22.582] [ ] Closing connection: <http.client.HTTPSConnection object at 0x7f968742be20> (HTTP.py:427)
[5] [2021-06-24 11:58:22.583] [ ] EXITING (run-master:1723)
[5] [2021-06-24 11:58:22.583] [ ] Writing log to service (run-master:1729)
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Die Fehlermeldung als solche ist jetzt die gleiche, die Ausgabe von sfdisk ist aber eine andere
Versuche mal die Schritte mit sgdisk, die hier beschrieben werden:
https://itectec.com/ubuntu/ubuntu-fixin ... gpt-table/
Gruß
Mathias
Versuche mal die Schritte mit sgdisk, die hier beschrieben werden:
https://itectec.com/ubuntu/ubuntu-fixin ... gpt-table/
Gruß
Mathias
Kein Support per DM!
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
_________________________
opsi support - http://www.uib.de/
For productive opsi installations we recommend support contracts.
Re: Intel Raid - Erste Installation geht, zweit Installation geht nicht
Hallo,
und wieder hat es eine ganze weile gedauert
Ich hab das ganze nochmal nach der ob genannten Anleitung gemacht.
Leider immer noch das gleiche Problem!
Danke
MS
und wieder hat es eine ganze weile gedauert
Ich hab das ganze nochmal nach der ob genannten Anleitung gemacht.
Leider immer noch das gleiche Problem!
Danke
MS