[Gelöst] Probleme bei opsi-local-image-restore

Antworten
bademeister
Beiträge: 141
Registriert: 28 Feb 2014, 10:21

[Gelöst] Probleme bei opsi-local-image-restore

Beitrag von bademeister »

Hallo zusammen,

wir sind gerade dabei die Möglichkeiten der local-image Erweiterung zu testen und stoßen beim restore auf Problem.
Folgendes Setup:
  • PC mit 2 Festplatten
  • 1 SSD fürs aktiv laufende System
  • 1 HDD für die Images
Ausgeführt wurden:
  • opsi-local-image-prepare: multi_disk_mode: prefer_ssd
  • opsi-local-image-win10-x64
  • opsi-local-image-backup: imagefile: test1
  • Dann mit opsi-local-image-win10-x64 neu installiert, nochmal ein backup gemacht mit anderem imagefile (test2)
Wenn wir nun das opsi-local-image-restore mit dem test1 image durchführen möchten, startet zwar der netboot, meldet aber dann: "Failed: Block size: 0 Byte"

Im bootimage-Log steht:
(11771) [2] [Apr 26 08:46:30] Traceback: (Logger.py|757)
(11772) [2] [Apr 26 08:46:30] File "/usr/local/bin/master.py", line 1461, in <module>
(11773) execfile(actionScript)
(11774) (Logger.py|757)
(11775) [2] [Apr 26 08:46:30] File "/tmp/setup.py", line 802, in <module>
(11776) restoreImage(diskDevice = disk.device, partition = int(systemPartitionNumber), imageType = "partclone", filesystem = filesystem, imageFile = u"%s" % (realimagefile), useGpt = useGpt, progressSubject=progressSubject)
(11777) (Logger.py|757)
(11778) [2] [Apr 26 08:46:30] File "/tmp/setup.py", line 220, in restoreImage
(11779) raise Exception(u"Failed: %s" % lastMsg)
(11780) (Logger.py|757)
(11781) [2] [Apr 26 08:46:30] ==>>> Failed: Block size: 0 Byte (master.py|1509)
Habe ich irgendwo was übersehen? Was geht hier schief?

Viele Grüße,
Felix
Zuletzt geändert von bademeister am 03 Mai 2018, 18:25, insgesamt 2-mal geändert.
bademeister
Beiträge: 141
Registriert: 28 Feb 2014, 10:21

Re: Probleme bei opsi-local-image-restore

Beitrag von bademeister »

Hier nochmal das gesamte Logfile (timeout counts wurden von mir entfernt ;) )

EDIT:
Dem Wunsch am Telefon, das gesamte Logfile zu posten kann ich leider nicht nachkommen:
Ihr Beitrag besteht aus 181557 Zeichen.
Es sind maximal 60000 Zeichen erlaubt.

Hab daher die ersten paar hundert Zeilen abgeschnitten.
(1418) [7] [Apr 26 09:27:50] Found filesystem: ntfs with blkid tool, using now this filesystemtype. (Posix.py|1558)
(1419) [7] [Apr 26 09:27:50] Partition found =>>> number: 3, start: 112658 MB (14362 cyl), end: 116753 MB (14883 cyl), size: 4094 MB (522 cyl), type: 12, fs: ntfs, boot: False (Posix.py|1593)
(1420) [7] [Apr 26 09:27:50] Waiting for device '/dev/sda3' to appear (Posix.py|1598)
(1421) [7] [Apr 26 09:27:50] Device '/dev/sda3' found (Posix.py|1606)
(1422) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1423) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1424) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1425) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1426) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1427) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1428) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1429) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1430) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk -L --no-reread -uS -l /dev/sda (Posix.py|768)
(1431) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1432) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1433) [7] [Apr 26 09:27:50] >>> Disk /dev/sda: 30401 cylinders, 255 heads, 63 sectors/track (Posix.py|845)
(1434) [7] [Apr 26 09:27:50] >>> Units: sectors of 512 bytes, counting from 0 (Posix.py|845)
(1435) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1436) [7] [Apr 26 09:27:50] >>> Device Boot Start End #sectors Id System (Posix.py|845)
(1437) [7] [Apr 26 09:27:50] >>> /dev/sda1 * 2048 209717247 209715200 7 HPFS/NTFS/exFAT (Posix.py|845)
(1438) [7] [Apr 26 09:27:50] >>> /dev/sda2 209731584 230737919 21006336 7 HPFS/NTFS/exFAT (Posix.py|845)
(1439) [7] [Apr 26 09:27:50] >>> /dev/sda3 230737920 239110143 8372224 12 Compaq diagnostics (Posix.py|845)
(1440) [7] [Apr 26 09:27:50] >>> /dev/sda4 0 - 0 0 Empty (Posix.py|845)
(1441) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1442) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1443) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1444) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1445) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1446) [6] [Apr 26 09:27:50] Total sectors of disk '/dev/sda': 488397168, 512 bytes per cylinder (Posix.py|1658)
(1447) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1448) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1449) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1450) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1451) [7] [Apr 26 09:27:50] Partition sector values =>>> number: 1, start: 2048 sec, end: 209717247 sec, size: 209715200 sec (Posix.py|1643)
(1452) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1453) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1454) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1455) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1456) [7] [Apr 26 09:27:50] Partition sector values =>>> number: 2, start: 209731584 sec, end: 230737919 sec, size: 21006336 sec (Posix.py|1643)
(1457) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1458) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1459) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1460) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1461) [7] [Apr 26 09:27:50] Partition sector values =>>> number: 3, start: 230737920 sec, end: 239110143 sec, size: 8372224 sec (Posix.py|1643)
(1462) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1463) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1464) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1465) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1466) [6] [Apr 26 09:27:50] Executing: cat /sys/block/sda/queue/rotational (Posix.py|768)
(1467) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1468) [7] [Apr 26 09:27:50] >>> 0 (Posix.py|845)
(1469) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1470) [7] [Apr 26 09:27:50] Found disk =>>> dev: '/dev/sdb', size: 931.00 GB (Posix.py|950)
(1471) [6] [Apr 26 09:27:50] Executing: /sbin/modprobe edd (Posix.py|768)
(1472) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1473) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1474) [6] [Apr 26 09:27:50] Using geo_override.so for all disks. (Posix.py|1302)
(1475) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1476) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1477) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1478) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1479) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk -L --no-reread -s -uB /dev/sdb (Posix.py|768)
(1480) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1481) [7] [Apr 26 09:27:50] >>> 976762584 (Posix.py|845)
(1482) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1483) [6] [Apr 26 09:27:50] Size of disk '/dev/sdb': 1000204886016 Byte / 953869 MB (Posix.py|1441)
(1484) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1485) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1486) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1487) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1488) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk -L --no-reread -l /dev/sdb (Posix.py|768)
(1489) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1490) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1491) [7] [Apr 26 09:27:50] >>> Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track (Posix.py|845)
(1492) [7] [Apr 26 09:27:50] >>> Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 (Posix.py|845)
(1493) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1494) [7] [Apr 26 09:27:50] >>> Device Boot Start End #cyls #blocks Id System (Posix.py|845)
(1495) [7] [Apr 26 09:27:50] >>> /dev/sdb1 0+ 121601- 121602- 976761560 83 Linux (Posix.py|845)
(1496) [7] [Apr 26 09:27:50] >>> /dev/sdb2 0 - 0 0 0 Empty (Posix.py|845)
(1497) [7] [Apr 26 09:27:50] >>> /dev/sdb3 0 - 0 0 0 Empty (Posix.py|845)
(1498) [7] [Apr 26 09:27:50] >>> /dev/sdb4 0 - 0 0 0 Empty (Posix.py|845)
(1499) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1500) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1501) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1502) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1503) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1504) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1505) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1506) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1507) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1508) [6] [Apr 26 09:27:50] Total cylinders of disk '/dev/sdb': 121601, 8225280 bytes per cylinder (Posix.py|1523)
(1509) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1510) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1511) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1512) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1513) [7] [Apr 26 09:27:50] Trying using Blkid (Posix.py|1551)
(1514) [6] [Apr 26 09:27:50] Executing: /sbin/blkid -o value -s TYPE /dev/sdb1 (Posix.py|768)
(1515) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1516) [7] [Apr 26 09:27:50] >>> ext4 (Posix.py|845)
(1517) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1518) [7] [Apr 26 09:27:50] Found filesystem: ext4 with blkid tool, using now this filesystemtype. (Posix.py|1558)
(1519) [7] [Apr 26 09:27:50] Partition found =>>> number: 1, start: 0 MB (0 cyl), end: 953875 MB (121601 cyl), size: 953875 MB (121602 cyl), type: 83, fs: ext4, boot: False (Posix.py|1593)
(1520) [7] [Apr 26 09:27:50] Waiting for device '/dev/sdb1' to appear (Posix.py|1598)
(1521) [7] [Apr 26 09:27:50] Device '/dev/sdb1' found (Posix.py|1606)
(1522) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1523) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1524) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1525) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1526) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1527) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1528) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1529) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1530) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1531) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1532) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1533) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1534) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1535) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1536) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1537) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1538) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk -L --no-reread -uS -l /dev/sdb (Posix.py|768)
(1539) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1540) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1541) [7] [Apr 26 09:27:50] >>> Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track (Posix.py|845)
(1542) [7] [Apr 26 09:27:50] >>> Units: sectors of 512 bytes, counting from 0 (Posix.py|845)
(1543) [7] [Apr 26 09:27:50] >>> (Posix.py|845)
(1544) [7] [Apr 26 09:27:50] >>> Device Boot Start End #sectors Id System (Posix.py|845)
(1545) [7] [Apr 26 09:27:50] >>> /dev/sdb1 2048 1953525167 1953523120 83 Linux (Posix.py|845)
(1546) [7] [Apr 26 09:27:50] >>> /dev/sdb2 0 - 0 0 Empty (Posix.py|845)
(1547) [7] [Apr 26 09:27:50] >>> /dev/sdb3 0 - 0 0 Empty (Posix.py|845)
(1548) [7] [Apr 26 09:27:50] >>> /dev/sdb4 0 - 0 0 Empty (Posix.py|845)
(1549) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1550) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1551) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1552) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1553) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1554) [6] [Apr 26 09:27:50] Total sectors of disk '/dev/sdb': 1953525168, 512 bytes per cylinder (Posix.py|1658)
(1555) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1556) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1557) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1558) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1559) [7] [Apr 26 09:27:50] Partition sector values =>>> number: 1, start: 2048 sec, end: 1953525167 sec, size: 1953523120 sec (Posix.py|1643)
(1560) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1561) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1562) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1563) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1564) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1565) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1566) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1567) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1568) [6] [Apr 26 09:27:50] Executing: /sbin/sfdisk --version (Posix.py|768)
(1569) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1570) [7] [Apr 26 09:27:50] >>> sfdisk from util-linux 2.25.1 (Posix.py|845)
(1571) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1572) [6] [Apr 26 09:27:50] Executing: cat /sys/block/sdb/queue/rotational (Posix.py|768)
(1573) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1574) [7] [Apr 26 09:27:50] >>> 1 (Posix.py|845)
(1575) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1576) [5] [Apr 26 09:27:50] We have more than one disk: 2 disks - looking for multi_disk_mode (opsisetuplib.py|635)
(1577) [5] [Apr 26 09:27:50] Check if disk /dev/sdb is ssd or classic (rotational) HD (opsisetuplib.py|85)
(1578) [5] [Apr 26 09:27:50] Disk /dev/sdb is rotational (Classic HD) (opsisetuplib.py|92)
(1579) [5] [Apr 26 09:27:50] dual_disk_mode is prefer_ssd - so we use disk 0 (opsisetuplib.py|651)
(1580) [5] [Apr 26 09:27:50] Using disk device /dev/sda (setup.py|337)
(1581) [5] [Apr 26 09:27:50] backup_partition_on_same_disk = False - so we use for backup disk 1 (opsisetuplib.py|664)
(1582) [5] [Apr 26 09:27:50] backup_partition_on_same_disk: False - backupdiskindex 1 (setup.py|339)
(1583) [5] [Apr 26 09:27:50] Will restore image: sal-default (setup.py|408)
(1584) [5] [Apr 26 09:27:50] Original image file name sal-default changed to internal image file name sal-default (setup.py|412)
(1585) [5] [Apr 26 09:27:50] /dev/sda1 exists as device - fine (opsisetuplib.py|198)
(1586) [5] [Apr 26 09:27:50] Partition /dev/sda1 has a correct block alignment (opsisetuplib.py|106)
(1587) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1588) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1589) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1590) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1591) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1592) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1593) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1594) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sda1 (Posix.py|768)
(1595) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1596) [7] [Apr 26 09:27:50] >>> system (Posix.py|845)
(1597) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1598) [5] [Apr 26 09:27:50] /dev/sda1 exists as device with label: system (opsisetuplib.py|335)
(1599) [5] [Apr 26 09:27:50] /dev/sda1 has label system (opsisetuplib.py|690)
(1600) [5] [Apr 26 09:27:50] /dev/sda1 exists as expected - fine (opsisetuplib.py|692)
(1601) [5] [Apr 26 09:27:50] /dev/sda2 exists as device - fine (opsisetuplib.py|198)
(1602) [5] [Apr 26 09:27:50] Partition /dev/sda2 has a correct block alignment (opsisetuplib.py|106)
(1603) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1604) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1605) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1606) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1607) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1608) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1609) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1610) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sda2 (Posix.py|768)
(1611) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1612) [7] [Apr 26 09:27:50] >>> data (Posix.py|845)
(1613) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1614) [5] [Apr 26 09:27:50] /dev/sda2 exists as device with label: data (opsisetuplib.py|335)
(1615) [5] [Apr 26 09:27:50] /dev/sda2 has label data (opsisetuplib.py|700)
(1616) [5] [Apr 26 09:27:50] /dev/sda2 exists as expected at 4 partions with label data - checking next partition (opsisetuplib.py|709)
(1617) [5] [Apr 26 09:27:50] /dev/sda3 exists as device - fine (opsisetuplib.py|198)
(1618) [5] [Apr 26 09:27:50] Partition /dev/sda3 has a correct block alignment (opsisetuplib.py|106)
(1619) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1620) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1621) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1622) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1623) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1624) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1625) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1626) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sda3 (Posix.py|768)
(1627) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1628) [7] [Apr 26 09:27:50] >>> WINPE (Posix.py|845)
(1629) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1630) [5] [Apr 26 09:27:50] /dev/sda3 exists as device with label: WINPE (opsisetuplib.py|335)
(1631) [5] [Apr 26 09:27:50] /dev/sda3 has label WINPE (opsisetuplib.py|717)
(1632) [5] [Apr 26 09:27:50] /dev/sda3 exists as expected - fine (opsisetuplib.py|719)
(1633) [5] [Apr 26 09:27:50] Change to backup disk with index: 1 - Device name/dev/sdb (opsisetuplib.py|729)
(1634) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device - fine (opsisetuplib.py|198)
(1635) [5] [Apr 26 09:27:50] Partition /dev/sdb1 has a correct block alignment (opsisetuplib.py|106)
(1636) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1637) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1638) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1639) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1640) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1641) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1642) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1643) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sdb1 (Posix.py|768)
(1644) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1645) [7] [Apr 26 09:27:50] >>> opsidata (Posix.py|845)
(1646) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1647) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device with label: opsidata (opsisetuplib.py|335)
(1648) [5] [Apr 26 09:27:50] /dev/sdb1 has label opsidata (opsisetuplib.py|743)
(1649) [5] [Apr 26 09:27:50] /dev/sdb1 exists as expected - fine (opsisetuplib.py|745)
(1650) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device - fine (opsisetuplib.py|198)
(1651) [5] [Apr 26 09:27:50] Partition /dev/sdb1 has a correct block alignment (opsisetuplib.py|106)
(1652) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1653) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1654) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1655) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1656) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1657) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1658) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1659) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sdb1 (Posix.py|768)
(1660) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1661) [7] [Apr 26 09:27:50] >>> opsidata (Posix.py|845)
(1662) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1663) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device with label: opsidata (opsisetuplib.py|335)
(1664) [5] [Apr 26 09:27:50] /dev/sdb1 has label opsidata (opsisetuplib.py|764)
(1665) [5] [Apr 26 09:27:50] /dev/sdb1 exists as expected - fine (opsisetuplib.py|766)
(1666) [5] [Apr 26 09:27:50] Partition numbers are now: system=1, data=2, swap=3, backup=1 (opsisetuplib.py|767)
(1667) [5] [Apr 26 09:27:50] /mntimg does not exists as directory - creating (opsisetuplib.py|343)
(1668) [6] [Apr 26 09:27:50] Executing: mkdir -p /mntimg (Posix.py|768)
(1669) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1670) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1671) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device - fine (opsisetuplib.py|198)
(1672) [5] [Apr 26 09:27:50] Partition /dev/sdb1 has a correct block alignment (opsisetuplib.py|106)
(1673) [6] [Apr 26 09:27:50] Executing: blkid (Posix.py|768)
(1674) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1675) [7] [Apr 26 09:27:50] >>> /dev/sda1: LABEL="system" UUID="84DC461EDC460ABE" TYPE="ntfs" PARTUUID="31ec9a53-01" (Posix.py|845)
(1676) [7] [Apr 26 09:27:50] >>> /dev/sda2: LABEL="data" UUID="6B8338E0044DB0B7" TYPE="ntfs" PARTUUID="31ec9a53-02" (Posix.py|845)
(1677) [7] [Apr 26 09:27:50] >>> /dev/sda3: LABEL="WINPE" UUID="456090BD1ACF939A" TYPE="ntfs" PARTUUID="31ec9a53-03" (Posix.py|845)
(1678) [7] [Apr 26 09:27:50] >>> /dev/sdb1: LABEL="opsidata" UUID="f5043aa2-b5dc-4424-bc5b-caf873efb4d3" TYPE="ext4" PARTUUID="876c80f2-01" (Posix.py|845)
(1679) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1680) [6] [Apr 26 09:27:50] Executing: blkid -o value -s LABEL /dev/sdb1 (Posix.py|768)
(1681) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1682) [7] [Apr 26 09:27:50] >>> opsidata (Posix.py|845)
(1683) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1684) [5] [Apr 26 09:27:50] /dev/sdb1 exists as device with label: opsidata (opsisetuplib.py|335)
(1685) [5] [Apr 26 09:27:50] /dev/sdb1 exists as expected - fine (setup.py|484)
(1686) [5] [Apr 26 09:27:50] mountpoint /mntimg exists (opsisetuplib.py|357)
(1687) [5] [Apr 26 09:27:50] mountpoint /mntimg >> /dev/null 2>&1 (opsisetuplib.py|362)
(1688) [5] [Apr 26 09:27:50] Nothing mounted on /mntimg - fine (opsisetuplib.py|377)
(1689) [5] [Apr 26 09:27:50] /dev/sdb1 is not mounted (opsisetuplib.py|401)
(1690) [6] [Apr 26 09:27:50] Executing: sync (Posix.py|768)
(1691) [6] [Apr 26 09:27:50] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1692) [7] [Apr 26 09:27:50] Exit code: 0 (Posix.py|852)
(1693) [5] [Apr 26 09:27:50] mount /dev/sdb1 /mntimg (opsisetuplib.py|421)
(1694) [5] [Apr 26 09:27:56] /dev/sdb1 mounted on /mntimg - fine.. (opsisetuplib.py|425)
(1695) [7] [Apr 26 09:27:56] Parsing ini file '/mntimg/sal-default/img.ini' (__init__.py|518)
(1696) [7] [Apr 26 09:27:56] Trying to lock file '/mntimg/sal-default/img.ini' (0/2000) (__init__.py|216)
(1697) [7] [Apr 26 09:27:56] File '/mntimg/sal-default/img.ini' locked after 0 millis (__init__.py|237)
(1698) [7] [Apr 26 09:27:56] Finished reading file after 0.008 seconds (__init__.py|595)
(1699) [5] [Apr 26 09:27:56] Reading image meta data: filesystem: ntfs (setup.py|523)
(1700) [5] [Apr 26 09:27:56] Reading image meta data: opsiproduct: opsi-local-image-win10-x64 (setup.py|525)
(1701) [5] [Apr 26 09:27:56] Reading image meta data: imagedate: Mon Apr 23 13:03:44 2018 (setup.py|527)
(1702) [5] [Apr 26 09:27:56] Reading image meta data: AveRate: 11980.8 (setup.py|529)
(1703) [5] [Apr 26 09:27:56] Reading image meta data: GPT: False (setup.py|531)
(1704) [5] [Apr 26 09:27:56] Reading image meta data: No uefiFirstBoot entries found (setup.py|540)
(1705) [5] [Apr 26 09:27:56] Existing system partition size = 102406 (setup.py|711)
(1706) [5] [Apr 26 09:27:56] Existing winPE partition size = 4094 (setup.py|717)
(1707) [5] [Apr 26 09:27:56] change id of partition /dev/sda 1 to 07 (setup.py|760)
(1708) [6] [Apr 26 09:27:56] Executing: sfdisk --change-id /dev/sda 1 07 (Posix.py|768)
(1709) [6] [Apr 26 09:27:56] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1710) [7] [Apr 26 09:27:56] >>> sfdisk: Done (Posix.py|845)
(1711) [7] [Apr 26 09:27:56] Exit code: 0 (Posix.py|852)
(1712) [5] [Apr 26 09:27:56] change id of partition /dev/sda 3 to 12 (setup.py|762)
(1713) [6] [Apr 26 09:27:56] Executing: sfdisk --change-id /dev/sda 3 12 (Posix.py|768)
(1714) [6] [Apr 26 09:27:56] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1715) [7] [Apr 26 09:27:56] >>> sfdisk: Done (Posix.py|845)
(1716) [7] [Apr 26 09:27:56] Exit code: 0 (Posix.py|852)
(1717) [5] [Apr 26 09:27:56] Activate (set boot flag) on partition /dev/sda1 (setup.py|769)
(1718) [6] [Apr 26 09:27:56] Executing: sfdisk -A /dev/sda 1 (Posix.py|768)
(1719) [6] [Apr 26 09:27:56] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1720) [7] [Apr 26 09:27:56] >>> sfdisk: Done (Posix.py|845)
(1721) [7] [Apr 26 09:27:56] Exit code: 0 (Posix.py|852)
(1722) [6] [Apr 26 09:27:56] Executing: sfdisk -l (Posix.py|768)
(1723) [6] [Apr 26 09:27:56] Using encoding 'ANSI_X3.4-1968' (Posix.py|801)
(1724) [7] [Apr 26 09:27:56] >>> (Posix.py|845)
(1725) [7] [Apr 26 09:27:56] >>> Disk /dev/sda: 30401 cylinders, 255 heads, 63 sectors/track (Posix.py|845)
(1726) [7] [Apr 26 09:27:56] >>> Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 (Posix.py|845)
(1727) [7] [Apr 26 09:27:56] >>> (Posix.py|845)
(1728) [7] [Apr 26 09:27:56] >>> Device Boot Start End #cyls #blocks Id System (Posix.py|845)
(1729) [7] [Apr 26 09:27:56] >>> /dev/sda1 * 0+ 13054- 13055- 104857600 7 HPFS/NTFS/exFAT (Posix.py|845)
(1730) [7] [Apr 26 09:27:56] >>> /dev/sda2 13055+ 14362- 1308- 10503168 7 HPFS/NTFS/exFAT (Posix.py|845)
(1731) [7] [Apr 26 09:27:56] >>> /dev/sda3 14362+ 14883- 522- 4186112 12 Compaq diagnostics (Posix.py|845)
(1732) [7] [Apr 26 09:27:56] >>> /dev/sda4 0 - 0 0 0 Empty (Posix.py|845)
(1733) [7] [Apr 26 09:27:56] >>> (Posix.py|845)
(1734) [7] [Apr 26 09:27:56] >>> Disk /dev/sdb: 121601 cylinders, 255 heads, 63 sectors/track (Posix.py|845)
(1735) [7] [Apr 26 09:27:56] >>> Units: cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 (Posix.py|845)
(1736) [7] [Apr 26 09:27:56] >>> (Posix.py|845)
(1737) [7] [Apr 26 09:27:56] >>> Device Boot Start End #cyls #blocks Id System (Posix.py|845)
(1738) [7] [Apr 26 09:27:56] >>> /dev/sdb1 0+ 121601- 121602- 976761560 83 Linux (Posix.py|845)
(1739) [7] [Apr 26 09:27:56] >>> /dev/sdb2 0 - 0 0 0 Empty (Posix.py|845)
(1740) [7] [Apr 26 09:27:56] >>> /dev/sdb3 0 - 0 0 0 Empty (Posix.py|845)
(1741) [7] [Apr 26 09:27:56] >>> /dev/sdb4 0 - 0 0 0 Empty (Posix.py|845)
(1742) [7] [Apr 26 09:27:56] Exit code: 0 (Posix.py|852)
(1743) [7] [Apr 26 09:27:56] MessageSubject 'backup_restore' created (Message.py|99)
(1744) [7] [Apr 26 09:27:56] ProgressSubject 'backup_restore' created (Message.py|227)
(1745) [7] [Apr 26 09:27:56] Created Progress box: <OPSI.UI.SnackProgressBox object at 0xb517d92c> (setup.py|797)
(1746) [5] [Apr 26 09:27:56] restoreImage(/dev/sda, 1, /mntimg/sal-default/sal-default.img, <ProgressSubject type: , id: backup_restore>, partclone, ntfs, False) (setup.py|61)
(1747) [5] [Apr 26 09:27:56] Image type is partclone (setup.py|128)
(1748) [6] [Apr 26 09:27:56] Restoring partclone image '/mntimg/sal-default/sal-default.img' to '/dev/sda1' (setup.py|133)
(1749) [5] [Apr 26 09:27:56] Restoring partclone image using command: partclone.restore -C --force --source /mntimg/sal-default/sal-default.img --output /dev/sda1 (setup.py|149)
(1750) [6] [Apr 26 09:27:56] Executing: partclone.restore -C --force --source /mntimg/sal-default/sal-default.img --output /dev/sda1 (Posix.py|768)
(1751) [7] [Apr 26 09:27:56] -->>> Partclone v0.2.86 http://partclone.org (setup.py|176)
(1752) [7] [Apr 26 09:27:56] -->>> Starting to restore image (/mntimg/sal-default/sal-default.img) to device (/dev/sda1) (setup.py|176)
(1753) [7] [Apr 26 09:27:56] -->>> restore: open /mntimg/sal-default/sal-default.img error (setup.py|176)
(1754) [6] [Apr 26 09:27:56] Save image: restore: open /mntimg/sal-default/sal-default.img error (setup.py|188)
(1755) [7] [Apr 26 09:27:56] -->>> Error exit (setup.py|176)
(1756) [7] [Apr 26 09:27:56] -->>> read image_hdr error (setup.py|176)
(1757) [7] [Apr 26 09:27:56] -->>> This is not partclone image. (setup.py|176)
(1758) [7] [Apr 26 09:27:56] -->>> Calculating bitmap... Please wait... done! (setup.py|176)
(1759) [7] [Apr 26 09:27:56] -->>> File system: (setup.py|176)
(1760) [6] [Apr 26 09:27:56] Save image: File system: (setup.py|188)
(1761) [7] [Apr 26 09:27:56] -->>> Device size: 0 Byte = 0 Blocks (setup.py|176)
(1762) [6] [Apr 26 09:27:56] Save image: Device size: 0 Byte = 0 Blocks (setup.py|188)
(1763) [7] [Apr 26 09:27:56] -->>> Space in use: 0 Byte = 0 Blocks (setup.py|176)
(1764) [6] [Apr 26 09:27:56] Save image: Space in use: 0 Byte = 0 Blocks (setup.py|188)
(1765) [7] [Apr 26 09:27:56] -->>> Free Space: 0 Byte = 0 Blocks (setup.py|176)
(1766) [7] [Apr 26 09:27:56] -->>> Block size: 0 Byte (setup.py|176)
(1767) [7] [Apr 26 09:27:56] -->>> timeout 1 (setup.py|223)
(1768) [7] [Apr 26 09:27:56] -->>> timeout 2 (setup.py|223)
(1769) [7] [Apr 26 09:27:56] -->>> timeout 3 (setup.py|223)
############################################################################# timeout 4-9997 entfernt
(11764) [7] [Apr 26 09:27:57] -->>> timeout 9998 (setup.py|223)
(11765) [7] [Apr 26 09:27:57] -->>> timeout 9999 (setup.py|223)
(11766) [7] [Apr 26 09:27:57] -->>> timeout 10000 (setup.py|223)
(11767) [2] [Apr 26 09:27:58] Traceback: (Logger.py|757)
(11768) [2] [Apr 26 09:27:58] File "/usr/local/bin/master.py", line 1461, in <module>
(11769) execfile(actionScript)
(11770) (Logger.py|757)
(11771) [2] [Apr 26 09:27:58] File "/tmp/setup.py", line 802, in <module>
(11772) restoreImage(diskDevice = disk.device, partition = int(systemPartitionNumber), imageType = "partclone", filesystem = filesystem, imageFile = u"%s" % (realimagefile), useGpt = useGpt, progressSubject=progressSubject)
(11773) (Logger.py|757)
(11774) [2] [Apr 26 09:27:58] File "/tmp/setup.py", line 220, in restoreImage
(11775) raise Exception(u"Failed: %s" % lastMsg)
(11776) (Logger.py|757)
(11777) [2] [Apr 26 09:27:58] ==>>> Failed: Block size: 0 Byte (master.py|1509)
(11778) [7] [Apr 26 09:27:58] Backend: <JSONRPCBackend(host=u'opsi.isw.uni-stuttgart.de', deflate=False)> (master.py|1512)
(11779) [7] [Apr 26 09:27:58] ProductId: opsi-local-image-restore (master.py|1513)
(11780) [7] [Apr 26 09:27:58] ClientId: tmp04.isw.uni-stuttgart.de (master.py|1514)
(11781) [7] [Apr 26 09:27:58] ProductOnClient: <ProductOnClient(clientId=u'tmp04.isw.uni-stuttgart.de', productId=u'opsi-local-image-restore', installationStatus=u'unknown', actionRequest=u'none')> (master.py|1515)
(11782) [7] [Apr 26 09:27:58] Executing jsonrpc method 'productOnClient_updateObjects' on host u'opsi.isw.uni-stuttgart.de' (JSONRPC.py|115)
(11783) [7] [Apr 26 09:27:58] Posting request... (JSONRPC.py|713)
(11784) [7] [Apr 26 09:27:58] Starting new HTTPS connection (0) to opsi.isw.uni-stuttgart.de:4447 (HTTP.py|648)
(11785) [7] [Apr 26 09:27:58] Connection established to: opsi.isw.uni-stuttgart.de (HTTP.py|650)
(11786) [7] [Apr 26 09:27:58] Closing connection: <httplib.HTTPSConnection instance at 0xb5132f4c> (HTTP.py|569)
(11787) [7] [Apr 26 09:27:58] Content-Type: gzip-application/json;charset=utf-8, Content-Encoding: deflate (JSONRPC.py|730)
(11788) [7] [Apr 26 09:27:58] Expecting deflated data from server (backwards compatible) (JSONRPC.py|738)
(11789) [5] [Apr 26 09:27:58] Writing log to service (master.py|1536)
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

Re: Probleme bei opsi-local-image-restore

Beitrag von d.oertel »

Hallo bademeister,

Ich habe das Problem gefunden und gefixed.
Mit dem neuen resore gehen auch die alten images wieder.
Das neue backup löscht ein altes image bevor das neue geschrieben wird.
https://download.uib.de/opsi4.0/experim ... 0.0-4.opsi

https://download.uib.de/opsi4.0/experim ... 0.0-3.opsi

Über eine Rückmeldung ob jetzt alle so funktioniert wie es soll würde ich mich freuen.

gruß
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
bademeister
Beiträge: 141
Registriert: 28 Feb 2014, 10:21

Re: Probleme bei opsi-local-image-restore

Beitrag von bademeister »

Hallo,

funktioniert bestens.
Allerdings hat es die imagefiles_list verspult.

Hierbei direkt eine Frage zum Verständnis. Wir möchten gerne mehrer images sichern und beliebig einspielen. Teils auch mit update_and_backup. Wenn mich nicht alle täuscht, wird dabei automatisch das netboot: oli-backup angestoßen. Mit welchem imagefile-Property? Mit dem im Produkt hinterlegtem? Also dem, welches ich als letztes angestoßen habe? Damit überschreibe ich ja images.

Das Problem mal an folgendem Szenario erklärt:
  1. oli-prepare -> läuft normal
  2. oli-win10-x64 -> läuft normal
  3. oli-backup -> ins Property habe ich "imagefile=image1" eingetragen
  4. oli-win10x64 -> installiert neues system drüber
  5. oli-backup -> ins Property habe ich jetzt "imagefile=image2" eingetragen
  6. oli-restore -> mit Property: "imagefile=image1 und update_and_backup=true"
Und wenn ich das bei uns gerade richtig beobachtet habe, läuft der restore sauber durch. Updated die notwendigen Pakete, stößt oli-backup-starter an, startet neu und läuft ins oli-backup.

Problem: In dem Paket steht von vorhin noch das Property auf: "imagefile=image2", folglich wird das restorte und geupdatet image1 nun als image2 gespeichert und mein bestehendes image2 wird überspielt und ist weg.

Stimmt das vom Verständnis her oder hängt das mit der verspulten imagefiles_list zusammen?

Viele Grüße,
Felix

EDIT:
Gleich noch was: Läuft der ganze Spaß auch mit UEFI-Boots? :twisted:

EDIT2:
Ich setze gleich noch einen drauf. Via UEFI, mit M2.SSD und HDD bekomme ich immer folgende Meldung im oli-prepare:
https://nextcloud.isw.uni-stuttgart.de/ ... pcRwqPTBDn
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

Re: Probleme bei opsi-local-image-restore

Beitrag von d.oertel »

Hallo bademeister,

Danke für den Hinweis mit dem UEFI-Problem.

Hier ist der Fix:
https://download.uib.de/opsi4.0/experim ... 0.0-3.opsi

Bitte Rückmeldung ob jetzt alles geht.

Zum Property imagefile von oli-backup:
Wenn es leer ist, wird als imagename das oli OS Produkt genommen welches auf installed steht.
Für automatisierte Abläufe muss evtl. per script über der opsi web service call setPrpductProperty das Property gezielt gesetzt werden. Das kann z.B. per opsi-produkt und opsiservicall gemacht werden.

gruß
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
bademeister
Beiträge: 141
Registriert: 28 Feb 2014, 10:21

Re: Probleme bei opsi-local-image-restore

Beitrag von bademeister »

Hallo d.oertel,

danke für den schnellen fix.
Der prepare läuft jetzt sauber durch und funktioniert.
Danach wird wie eingestellt bei uns das oli-win10-x64 gestartet.
Das Bootimage davon läuft sauber durch.
Nach dem Restart im Anschluss geht es allerdings mit der UEFI Kiste nicht weiter.
Im Bootmenu steht die Option: "opsitempwinpe" an erster Stelle, welche jedoch nicht gebootet wird und es mit einem UEFI IP4 Boot weiter geht.

Unser Inhalt von /var/lib/opsi/depot/opsi-local-image-win10-x64/ sieht wie folgt aus:

Code: Alles auswählen

drwxrws---   5 opsiconfd pcpatch  4096 Apr 23 14:05 .
drwxrws--- 117 opsiconfd pcpatch  4096 Apr 27 11:31 ..
-rwxrwx---   1 opsiconfd pcpatch  9488 Mär 13 17:23 create_driver_links.py
drwxrws---   3 opsiconfd pcpatch  4096 Apr 23 14:10 custom
lrwxrwxrwx   1 root      pcpatch    21 Apr 23 14:05 drivers -> ../win10-x64/drivers/
drwxrws---   3 opsiconfd pcpatch  4096 Apr 23 13:03 drivers.bak
-rwxrwx---   1 opsiconfd pcpatch  1196 Mär 13 17:23 extract_driver_pack.py
lrwxrwxrwx   1 root      pcpatch    25 Apr 23 14:03 installfiles -> ../win10-x64/installfiles
-rw-rw----   1 opsiconfd pcpatch  6907 Mär 13 17:23 nt6_repartition.opsiscript
drwxrws---   3 opsiconfd pcpatch  4096 Apr 23 13:03 opsi
-rw-rw----   1 opsiconfd pcpatch  1733 Apr 23 13:04 opsi-local-image-win10-x64.files
-rwxrwx---   1 opsiconfd pcpatch 31200 Mär 13 17:23 opsipreparelib.py
-rwxrwx---   1 opsiconfd pcpatch 40454 Mär 13 17:23 opsisetuplib.py
-rw-rw----   1 opsiconfd pcpatch 18727 Mär 13 17:23 setup.opsiscript
-rwxrwx---   1 opsiconfd pcpatch 76818 Mär 13 17:23 setup.py
-rwxrwx---   1 opsiconfd pcpatch 16909 Mär 13 17:23 show_drivers.py
-rw-rw----   1 opsiconfd pcpatch 29477 Mär 13 17:23 windows.png
lrwxrwxrwx   1 root      pcpatch    18 Apr 23 14:03 winpe -> ../win10-x64/winpe
lrwxrwxrwx   1 opsiconfd pcpatch     5 Apr 23 13:04 winpe_uefi -> winpe
Wir haben die Welt also nicht neu erfunden, sondern arbeiten mit den Inhalten unseres win10-x64 Pakets, welches einwandfrei läuft (Legacy + UEFI).

Viele Grüße,
Felix
Benutzeravatar
d.oertel
uib-Team
Beiträge: 3319
Registriert: 04 Jun 2008, 14:27

Re: Probleme bei opsi-local-image-restore

Beitrag von d.oertel »

Hi,

ich kann den Fehler hier nicht nachvollziehen.
(Auf einem HP Pavilion Desktop PC 570 mit NVME Disk)

Bitte:
1.) Prüfen ob das winpe wirklich ein 64 Bit PE ist. UEFI ist architecture sensitive d.h. wenn eich ein 64 Bit UEFI habe brauche ich auch ein 64 Bit PE und ein 64 Bit Windows. In den aktuellen netbootprodukten gibt es im Verzeichnis opsi eine test32bit.exe.
Das ist eine 32 Bit Applikation welche auf einem 32 Bit PE mit Exitcode 0 zurückkommt auf 64 Bit gibts einen Fehler.

2.) Bitte das bootimage.log an mich (d.oertel@uib.de) senden.

3.) BIOS Einstellungen kontrollieren. Jede UEFI BIOS its etwas anders von daher gibt es wenig allg. Regeln.
Einstellungen wie z.B. beim Boot mode 'both' sind meist des Teufels UEFI-only (mit CSM Support) ist meist besser.

4.) Wie wurde das PE erstellt und funktioniert das ganze auf einem UEFI mit klassischer Harddisk ?

gruß
d.oertel
opsi support - uib gmbh

For productive opsi installations we recommend support contracts.
http://www.uib.de
http://www.opsi.org
bademeister
Beiträge: 141
Registriert: 28 Feb 2014, 10:21

Re: Probleme bei opsi-local-image-restore

Beitrag von bademeister »

Hallo Herr Örtel,

bevor ich meine Antwort abgeschickt habe, habe ich noch einen Test gemacht und die Symlinks (siehe oben) entfernt und die Orignaldateien angelegt.
Siehe da.. Es läuft.

Mit einem weiteren Test habe ich nur für winpe und winpe_uefi keine Symlinks angelegt. Läuft auch.
Folglich sieht unser /var/lib/opsi/depot/opsi-local-image-win10-x64 Ordner wie folgt aus:
drwxrws--- 7 opsiconfd pcpatch 4096 Mai 3 15:15 .
drwxrws--- 111 opsiconfd pcpatch 4096 Apr 30 16:11 ..
-rwxrwx--- 1 opsiconfd pcpatch 9488 Mär 13 17:23 create_driver_links.py
drwxrws--- 3 opsiconfd pcpatch 4096 Mai 3 15:16 custom
lrwxrwxrwx 1 root pcpatch 21 Mai 3 15:14 drivers -> ../win10-x64/drivers/
drwxrws--- 3 opsiconfd pcpatch 4096 Apr 23 13:03 drivers.bak
-rwxrwx--- 1 opsiconfd pcpatch 1196 Mär 13 17:23 extract_driver_pack.py
lrwxrwxrwx 1 root pcpatch 26 Mai 3 15:15 installfiles -> ../win10-x64/installfiles/
-rw-rw---- 1 opsiconfd pcpatch 6907 Mär 13 17:23 nt6_repartition.opsiscript
drwxrws--- 3 opsiconfd pcpatch 4096 Apr 23 13:03 opsi
-rw-rw---- 1 opsiconfd pcpatch 1733 Apr 23 13:04 opsi-local-image-win10-x64.files
-rwxrwx--- 1 opsiconfd pcpatch 31200 Mär 13 17:23 opsipreparelib.py
-rwxrwx--- 1 opsiconfd pcpatch 40454 Mär 13 17:23 opsisetuplib.py
-rw-rw---- 1 opsiconfd pcpatch 18727 Mär 13 17:23 setup.opsiscript
-rwxrwx--- 1 opsiconfd pcpatch 76818 Mär 13 17:23 setup.py
-rwxrwx--- 1 opsiconfd pcpatch 16909 Mär 13 17:23 show_drivers.py
-rw-rw---- 1 opsiconfd pcpatch 29477 Mär 13 17:23 windows.png
drwxrws--- 4 opsiconfd pcpatch 4096 Nov 11 2015 winpe
drwxrws--- 41 opsiconfd pcpatch 4096 Dez 7 2015 winpe_uefi
Besten Dank für die Unterstützung.
Viele Grüße,
Felix

#######################################################
Geplante Antwort vor Entfernen der Symlinks - der Vollständigkeit halber trotzdem gepostet
#######################################################
Hallo Herr Oertel,
danke für die Rückmeldung.
Unten finden Sie meine Antworten:
d.oertel hat geschrieben: 1.) Prüfen ob das winpe wirklich ein 64 Bit PE ist. UEFI ist architecture sensitive d.h. wenn eich ein 64 Bit UEFI habe brauche ich auch ein 64 Bit PE und ein 64 Bit Windows. In den aktuellen netbootprodukten gibt es im Verzeichnis opsi eine test32bit.exe.
Das ist eine 32 Bit Applikation welche auf einem 32 Bit PE mit Exitcode 0 zurückkommt auf 64 Bit gibts einen Fehler.
Als bootmgr haben wir den von Ihnen in der UEFI Erweiterung mitgelieferten genommen. Unser bisheriges (damals für Win10) erstelltes WinPE hat auf den Maschinen bisher einwandfrei funktioniert.
d.oertel hat geschrieben: 2.) Bitte das bootimage.log an mich (d.oertel@uib.de) senden.
Geht gleich raus.
d.oertel hat geschrieben: 3.) BIOS Einstellungen kontrollieren. Jede UEFI BIOS its etwas anders von daher gibt es wenig allg. Regeln.
Einstellungen wie z.B. beim Boot mode 'both' sind meist des Teufels UEFI-only (mit CSM Support) ist meist besser.
Launch CSM [Enabled]
Boot option filter [UEFI only]
Launch PXE OpROM Policy [UEFI only]
ist bei allen Rechner seit dem wir Sie geliefert bekommen haben, eingestellt.
Die Rechner sind teil eines Pools, welcher bisher auch einwandfrei und ohne jegliche Probleme mit win10-x64 + UEFI aufgesetzt wurden.
d.oertel hat geschrieben: 4.) Wie wurde das PE erstellt und funktioniert das ganze auf einem UEFI mit klassischer Harddisk ?
Wie schon gesagt, haben wir das PE seit einiger Zeit im Einsatz mit dem win10-x64 netboot.
Bisher ohne Probleme bei Legacy und UEFI Maschinen. Nachweislich bei M2.SSDs und bei "nativen SSDs".
Bei klassischen HDDs mit UEFI muss ich passen. Da ist mir jetzt aktiv kein Fall bekannt. Hier müsste ich auch erstmal eine passenden Testclient suchen.

Wie gesagt, tritt der Fehler nicht auf, wenn wir auf der gleichen Maschine unser unangetastetes win10-x64 laufen lassen.
Das oli-win10-x64 haben wir lediglich mit symlinks auf das laufende win10-x64 verwiesen.

Viele Grüße,
Felix Kretschmer
Antworten