Categories

  • 12k Topics
    114k Posts
    L

    @lucamathuse Update

    I found some more information that changes a lot of stuff. Instead of it deploying correctly and somehow magically landing in the recovery screen it turns out Clonepart messes something up when capturing and deploying. It leaves out some partitions in the config files and when I try to deploy it it skips C:\ completely thus leaving it in a RAW state. I have collected some outputs:

    Image directory with all the files:

    0-rwxrwxr-x 1 fogproject fogproject 6 Apr 7 12:18 d1.fixed_size_partitions -rwxrwxr-x 1 fogproject fogproject 1.0M Apr 7 12:18 d1.mbr -rwxrwxr-x 1 fogproject fogproject 873 Apr 7 12:18 d1.minimum.partitions -rwxrwxr-x 1 fogproject fogproject 20 Apr 7 12:18 d1.original.fstypes -rwxrwxr-x 1 fogproject fogproject 0 Apr 7 12:18 d1.original.swapuuids -rwxrwxr-x 1 fogproject fogproject 873 Apr 7 12:18 d1.partitions -rwxrwxr-x 1 fogproject fogproject 873 Apr 7 12:18 d1.shrunken.partitions -rwxrwxr-x 1 fogproject fogproject 15M Apr 7 12:18 d1p1.img -rwxrwxr-x 1 fogproject fogproject 767 Apr 7 12:18 d1p2.img -rwxrwxr-x 1 fogproject fogproject 5.6G Apr 7 12:27 d1p3.img.000

    d1.partitions:

    label: gpt label-id: 99934977-65D0-41C6-B5E0-92E8085EC24F device: /dev/nvme0n1 unit: sectors first-lba: 34 last-lba: 500118158 sector-size: 512 /dev/nvme0n1p1 : start= 2048, size= 409600, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=740FC648-717D-439E-9AC9-224A270007E2, name="Basic data partition", attrs="GUID:63" /dev/nvme0n1p2 : start= 411648, size= 32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=45621D9E-3DD9-4D22-9D25-BCCDE3D0D714, name="Microsoft reserved partition", attrs="GUID:63" /dev/nvme0n1p3 : start= 444416, size= 498042880, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=F20FBC57-04B6-4522-9D20-33998BF119F9, name="Basic data partition" /dev/nvme0n1p4 : start= 498487296, size= 1628160, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=0D84E62A-99BF-4D91-A1D1-1B5D86FD2F45, attrs="RequiredPartition GUID:63"

    d1.original.fstypes

    /dev/nvme0n1p3 ntfs

    d1.fixed_size_partitions

    1:2:4

    Windows partition layout:

    Partition Type Size 1 EFI (System) 200MB 2 MSR (Reserviert) 16MB 3 Windows (Primär) 237GB 4 Recovery (Wiederherstellung) 795MB

    I have no clue why Clonepart or FOG is doing this.

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    H

    @hariskar

    I didn’t really catch the described use case…
    But anyway, if application stores something in the database, then the database need to be backed up, of course. Fully and incrementally also (separate logic).

    If you use application that stores data in the same machine where it is installed, better would be to configure it to store data on the remote database, e.g on specific database server or some other way.
    You can create network drive or other remote storage and point your database files there - if needed to be separate (for each PC).

    This way you have all the data in the same place, and you can make backups of this server or drive more easilly.

    Backuping entire PC with database in it - this can be done, but why?
    It feels strange.

    Example:
    Lets say, employees in your company are working with important documents.
    Do you really want to backup of entire PC (with os and applications and data), instead of storing those documents on secure and reliable remote storage?
    Better solution is to simply make network location (local or in cloud) and let the users to store documents there - so the documents would not be lost if some pc dies.
    If PC dies, then you simply replace the pc and deploy ready to use system image.

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

123

Online

12.6k

Users

17.5k

Topics

156.4k

Posts