• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Failed to read back partitions

Scheduled Pinned Locked Moved Unsolved
FOG Problems
2
3
442
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    Jedi
    last edited by Apr 24, 2019, 11:15 PM

    I have an OS installed on a hardware RAID controller with two 2TB SSD’s.

    I have taken an image. It had to be “Multiple Partition Image - Single Disk (Not Resizeable)”. The “Single Disk - Resizable” option would not work for some reason.

    Now I am wanting to deploy the image to a different drive on the same computer (a 2TB HDD).

    I unplugged the sata cables for all the drives except the one I am wanting to deploy the image to.

    When I attempted to deploy the image I got the following error:

    Failed to read back partitions (runPartprobe)
    Args Passed: /dev/sdd
    

    20190425_104527_resized.jpg

    Any help with this would be much appreciated.

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator
      last edited by george1421 Apr 24, 2019, 5:36 PM Apr 24, 2019, 11:34 PM

      Let me see if I understand this correctly. We are talking about the target computer right?

      That target computer has a hardware raid controller in it, but its presenting the drive as sdd?

      I unplugged the sata cables for all the drives except the one I am wanting to deploy the image to.

      Would that make /dev/sdd become /dev/sda?

      What I want you to do is reinstall all of the drives into that target computer. Goto FOG Configuration->FOG Settings, then hit the expand all button. Somewhere in that list find “kernel args”. Place the following parameter in that field mdraid=true. Save the settings.
      Then setup a new capture/deploy task (don’t care) but before you schedule the task, tick the debug check box then schedule the task.

      PXE boot the target computer, after a few enter key presses you will be dropped to a FOS linux command prompt. At the FOS command prompt key in lsblk and fdisk -l and post the results here. This will show us the exact geometry of the disks.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      1 Reply Last reply Reply Quote 0
      • J
        Jedi
        last edited by Jedi Apr 24, 2019, 7:50 PM Apr 25, 2019, 1:46 AM

        Hi George,

        Thank you for your reply. My system is Ubuntu 19.04 so I just took the output from terminal, hope that’s ok?

        The image was taken from /dev/sdd and I am wanting to deploy it to /dev/sdb

        In case its relevant I specified “/dev/sdd” as Host Primary Disk to prevent FOG taking Windows as the image.

        See here:

        https://forums.fogproject.org/topic/13042/how-to-edit-drive-cloning-options

        root@Ubuntu19:/home/mike# lsblk
        NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
        loop0 7:0 0 35.3M 1 loop /snap/gtk-common-themes/1198
        loop1 7:1 0 3.7M 1 loop /snap/gnome-system-monitor/77
        loop2 7:2 0 143.5M 1 loop /snap/gnome-3-28-1804/23
        loop3 7:3 0 53.7M 1 loop /snap/core18/941
        loop4 7:4 0 14.8M 1 loop /snap/gnome-characters/206
        loop5 7:5 0 1008K 1 loop /snap/gnome-logs/57
        loop6 7:6 0 3.7M 1 loop /snap/gnome-system-monitor/70
        loop7 7:7 0 151M 1 loop /snap/gnome-3-28-1804/36
        loop8 7:8 0 4M 1 loop /snap/gnome-calculator/406
        loop9 7:9 0 91.1M 1 loop /snap/core/6531
        loop10 7:10 0 53.7M 1 loop /snap/core18/782
        loop11 7:11 0 89.3M 1 loop /snap/core/6673
        loop12 7:12 0 14.8M 1 loop /snap/gnome-characters/254
        loop13 7:13 0 1008K 1 loop /snap/gnome-logs/61
        loop14 7:14 0 4M 1 loop /snap/gnome-calculator/352
        sda 8:0 0 596.2G 0 disk
        └─sda1 8:1 0 596.2G 0 part
        sdb 8:16 0 1.8T 0 disk
        sdc 8:32 0 931.5G 0 disk
        └─sdc1 8:33 0 931.5G 0 part
        sdd 8:48 0 1.8T 0 disk
        ├─sdd1 8:49 0 512M 0 part
        └─sdd2 8:50 0 1.8T 0 part
        ├─ubuntu–vg-root 253:0 0 1.8T 0 lvm /
        └─ubuntu–vg-swap_1 253:1 0 976M 0 lvm [SWAP]
        sr0 11:0 1 1024M 0 rom
        nvme0n1 259:0 0 232.9G 0 disk
        ├─nvme0n1p1 259:1 0 232.3G 0 part
        ├─nvme0n1p2 259:2 0 100M 0 part /boot/efi
        └─nvme0n1p3 259:3 0 502M 0 part
        root@Ubuntu19:/home/mike# fdisk -l
        Disk /dev/loop0: 35.3 MiB, 37027840 bytes, 72320 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop1: 3.7 MiB, 3821568 bytes, 7464 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop2: 143.5 MiB, 150470656 bytes, 293888 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop3: 53.7 MiB, 56315904 bytes, 109992 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop4: 14.8 MiB, 15458304 bytes, 30192 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop5: 1008 KiB, 1032192 bytes, 2016 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop6: 3.7 MiB, 3846144 bytes, 7512 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop7: 151 MiB, 158343168 bytes, 309264 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/nvme0n1: 232.9 GiB, 250059350016 bytes, 488397168 sectors
        Disk model: Samsung SSD 970 EVO 250GB
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disklabel type: gpt
        Disk identifier: 09583A20-4CD6-11E9-B903-C97FD46B0FAF

        Device Start End Sectors Size Type
        /dev/nvme0n1p1 2048 487161329 487159282 232.3G Microsoft basic data
        /dev/nvme0n1p2 487161856 487366655 204800 100M EFI System
        /dev/nvme0n1p3 487366656 488394751 1028096 502M Windows recovery environment

        Disk /dev/sda: 596.2 GiB, 640135028736 bytes, 1250263728 sectors
        Disk model: WDC WD6400AAKS-0
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disklabel type: dos
        Disk identifier: 0x0000a7b9

        Device Boot Start End Sectors Size Id Type
        /dev/sda1 2048 1250263039 1250260992 596.2G 83 Linux

        Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
        Disk model: WDC WD20EFRX-68E
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes

        Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
        Disk model: WDC WD10EZEX-00M
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 4096 bytes
        I/O size (minimum/optimal): 4096 bytes / 4096 bytes
        Disklabel type: gpt
        Disk identifier: 1A9126E1-F57F-4FD8-B67C-35B6AB0A5AF0

        Device Start End Sectors Size Type
        /dev/sdc1 2048 1953523711 1953521664 931.5G Linux filesystem

        Disk /dev/sdd: 1.8 TiB, 2000315023360 bytes, 3906865280 sectors
        Disk model: MARVELL Raid VD
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        Disklabel type: gpt
        Disk identifier: 70FAF413-B8D4-4AD7-BEB0-ACEC78095D8B

        Device Start End Sectors Size Type
        /dev/sdd1 2048 1050623 1048576 512M EFI System
        /dev/sdd2 1050624 3906865151 3905814528 1.8T Linux LVM

        Disk /dev/mapper/ubuntu–vg-root: 1.8 TiB, 1998749433856 bytes, 3903807488 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/mapper/ubuntu–vg-swap_1: 976 MiB, 1023410176 bytes, 1998848 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop8: 4 MiB, 4218880 bytes, 8240 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop9: 91.1 MiB, 95522816 bytes, 186568 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop10: 53.7 MiB, 56315904 bytes, 109992 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop11: 89.3 MiB, 93581312 bytes, 182776 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop12: 14.8 MiB, 15462400 bytes, 30200 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop13: 1008 KiB, 1032192 bytes, 2016 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes

        Disk /dev/loop14: 4 MiB, 4214784 bytes, 8232 sectors
        Units: sectors of 1 * 512 = 512 bytes
        Sector size (logical/physical): 512 bytes / 512 bytes
        I/O size (minimum/optimal): 512 bytes / 512 bytes
        root@Ubuntu19:/home/mike#

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        1 / 1
        • First post
          2/3
          Last post

        272

        Online

        12.0k

        Users

        17.3k

        Topics

        155.2k

        Posts
        Copyright © 2012-2024 FOG Project