OMV 3 did not pick up on actual size of SDcard in RaspberryPi

    • OMV 3.x
    • OMV 3 did not pick up on actual size of SDcard in RaspberryPi

      Installed OMV 3 beta image on microSDcard (128GB, SanDisk, UHS-I), booted it with RaspBerryPi 3B, did apt-get update, upgrade, dist-upgrade and then ended up with an up to date system; Erasmus 3.0.24

      In OMV web admin under Storage > Physical disks
      it actually says the disk is 119.08GB so that should be OK.
      However, under File systems this is what it shows:
      [Blocked Image: http://afluisterland.nl/img/omv_.png]

      and I can't resize or do anything (gui doesn't respond to actions, only mounting works). Rather disappointing, but hey, it's a beta. I'm inclined to do a RPi debian install image, and then maybe try OMV on top of it, because this didn't happen with a debian install on the Pi (had it on this Pi before).

      The post was edited 1 time, last by OhMyVirtual ().

    • Chill out. I wrote a script to resize the third partition but obviously something didn't work. The normal OMV installer uses the entire OS drive for OS purposes and you would have a lot more work to do to use it for data.... Plus OMV 3.x is still beta as you mentioned. Is a beta release allowed to have issues?

      What is the output of cat /etc/rc.local
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Source Code

      1. root@raspberrypi:~# cat /etc/rc.local
      2. #!/bin/sh -e
      3. #
      4. # rc.local
      5. #
      6. # This script is executed at the end of each multiuser runlevel.
      7. # Make sure that the script will "exit 0" on success or any other
      8. # value on error.
      9. #
      10. # In order to enable or disable this script just change the execution
      11. # bits.
      12. #
      13. # By default this script does nothing.
      14. # Print the IP address
      15. _IP=$(hostname -I) || true
      16. if [ "$_IP" ]; then
      17. printf "My IP address is %s\n" "$_IP"
      18. fi
      19. test -f /etc/ssh/ssh_host_dsa_key || dpkg-reconfigure openssh-server
      20. exit 0
      Display All



      So, I'm guessing there needs to be something else in there? Yes, I know it's a beta, and I first installed v2 Stable, but it is running such old wheezy stuff I can't have the OS do what I want, separate from OMV I mean. Plus I got an error when I tried to update the btsync repo (I really want OMV's multi-instance syncthing on this Pi).

      The post was edited 5 times, last by OhMyVirtual ().

    • raspi-config isn't installed on the image.

      The script ran because the entry in rc.local to execute it was gone. The resize script remove that entry from rc.local.

      Just execute the script - resize_mmcp3.sh - that is still in the /root/ directory. Let me know what kind of output you get. It might need to be tweaked for OMV 3. I didn't test it because it kills my SD cards due to the number of times it would run.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Had already tried fdisk and raspi-config (I always first run apt-get install bash whereis bind-tools mc raspi-config ll to get me some crucial shell stuff),
      in raspi-config Expanding filesystem didn't work, saying

      "mmcblk0p2 is not the last partition. Don't know how to expand"

      and here's the output of the resize script

      Source Code

      1. root@raspberrypi:~# ./resize_mmcp3.sh
      2. Welcome to fdisk (util-linux 2.25.2).
      3. Changes will remain in memory only, until you decide to write them.
      4. Be careful before using the write command.
      5. Command (m for help): Disk /dev/mmcblk0: 119.1 GiB, 127865454592 bytes, 249737216 sectors
      6. Units: sectors of 1 * 512 = 512 bytes
      7. Sector size (logical/physical): 512 bytes / 512 bytes
      8. I/O size (minimum/optimal): 512 bytes / 512 bytes
      9. Disklabel type: dos
      10. Disk identifier: 0x000b5098
      11. Device Boot Start End Sectors Size Id Type
      12. /dev/mmcblk0p1 8192 122879 114688 56M c W95 FAT32 (LBA)
      13. /dev/mmcblk0p2 122880 7028735 6905856 3.3G 83 Linux
      14. /dev/mmcblk0p3 7028736 7159807 131072 64M 83 Linux
      15. Command (m for help): Partition number (1-3, default 3):
      16. Partition 3 has been deleted.
      17. Command (m for help): Partition type
      18. p primary (2 primary, 0 extended, 2 free)
      19. e extended (container for logical partitions)
      20. Select (default p): Partition number (3,4, default 3): First sector (2048-249737215, default 2048): Value out of range.
      21. First sector (2048-249737215, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (2048-8191, default 8191): Last sector, +sectors or +size{K,M,G,T,P} (2048-8191, default 8191):
      22. Do you really want to quit? e2fsck 1.42.12 (29-Aug-2014)
      23. Superblock last mount time (Wed Dec 7 12:17:03 2016,
      24. now = Tue Jun 21 03:14:29 2016) is in the future.
      25. Fix? yes
      26. Pass 1: Checking inodes, blocks, and sizes
      27. Pass 2: Checking directory structure
      28. Pass 3: Checking directory connectivity
      29. Pass 4: Checking reference counts
      30. Pass 5: Checking group summary information
      31. /dev/mmcblk0p3: 13/16384 files (7.7% non-contiguous), 7472/65536 blocks
      32. Resizing the filesystem will take a few minutes or longer.
      33. resize2fs 1.42.12 (29-Aug-2014)
      34. The filesystem is already 65536 (1k) blocks long. Nothing to do!
      Display All


      I'm betting it has to do with the stupid UHS-I on the microSDcard. Never had any luck with UHS-I cards for raspberry pi systems.
    • Pretty sure bash and whereis are already installed on the image and I really wouldn't install raspi-config...

      And you are probably right, that card is most likely causing the issue. I don't have any cards anywhere near that size to test but it looks like it isn't supported well. Why not boot gparted-live on the system you wrote the sd card with and resize it?
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Why not boot gparted-live on the system you wrote the sd card with and resize it?

      Thought about that. I actually formatted it using SDformatter on Windows 7, then made it FAT32 using this tool and then used the recommended Win32imagewriting tool to write the OMV img to the sdcard.
      (By the way, strangely I do recall that the OMV 2 did show the full size in its filesystem..)
      Running a gparted live is a bit of a gamble on the laptop with the sdcard slot, not sure if it even sees the sdcard then, but I guess it's my only way out here.

      I went from the incorrect compatibility list for raspberry pi 3 B, which stated that 128 GB UHS 1 microSDXC cards are fine. I doubt that they are, it's the third one that has issues for me.
    • Why did you use sdformatter and make it FAT32? All you need to do is use win32diskimager. It writes everything including boot record, partitions, etc.

      If gparted-live isn't new enough, then use systemrescuecd 4.7.3 and select the alternate kernel in the boot menu. It should work on just about any hardware. Once it boots, type startx and then gparted is a icon on the bottom left. I recommend using linux live usb creator to write systemrescuecd to a usb stick. Don't worry when it says it can't match the exact version of systemrescuecd.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Why did you use sdformatter and make it FAT32? All you need to do is use win32diskimager. It writes everything including boot record, partitions, etc.
      Yes, I would expect that too, and did that the first try. It left a weird unknown partition at the start of the sdcard, could not remove it, or re-write it using Win32diskimager. The errors lead me to a manual on RPi forums telling me to pre-format to FAT32 to get rid of that useless storage waste at the start of the SDXC card. Which is probably also why it's now not working as expected. These are strange cards, obviously, and need special treatment.

      I've used gparted live-disks/sticks about weekly for the past 10 years at work, but thanks anyway. :)
    • Strange... Other than wireless adapters and winmodems, I have yet to find something systemrescuecd doesn't work with since it based on bleeding-edge gentoo. But oh well.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I'm running into the same reported issues when using OMV 2.2.5 (Stone Burner) on a Raspberry PI 2. After firing the script manually, I'm getting the following output:

      Source Code

      1. root@raspberrypi:~# df -kh
      2. Filesystem Size Used Avail Use% Mounted on
      3. /dev/root 3.2G 1.6G 1.5G 51% /
      4. devtmpfs 483M 0 483M 0% /dev
      5. tmpfs 98M 248K 98M 1% /run
      6. tmpfs 5.0M 0 5.0M 0% /run/lock
      7. tmpfs 195M 0 195M 0% /run/shm
      8. /dev/mmcblk0p1 56M 21M 35M 38% /boot
      9. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/log
      10. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/php5
      11. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/openmediavault/rrd
      12. folder2ram 487M 0 487M 0% /var/lib/php5
      13. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/spool
      14. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/tmp
      15. folder2ram 487M 376K 487M 1% /var/lib/openmediavault/rrd
      16. folder2ram 487M 0 487M 0% /var/tmp
      17. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/monit
      18. folder2ram 487M 404K 487M 1% /var/log
      19. folder2ram 487M 696K 486M 1% /var/spool
      20. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/rrdcached
      21. folder2ram 487M 4.0K 487M 1% /var/lib/monit
      22. folder2ram 487M 14M 474M 3% /var/lib/rrdcached
      23. root@raspberrypi:~# fdisk -l
      24. Disk /dev/mmcblk0: 30.9 GB, 30908350464 bytes
      25. 4 heads, 16 sectors/track, 943248 cylinders, total 60367872 sectors
      26. Units = sectors of 1 * 512 = 512 bytes
      27. Sector size (logical/physical): 512 bytes / 512 bytes
      28. I/O size (minimum/optimal): 512 bytes / 512 bytes
      29. Disk identifier: 0x000b5098
      30. Device Boot Start End Blocks Id System
      31. /dev/mmcblk0p1 8192 122879 57344 c W95 FAT32 (LBA)
      32. /dev/mmcblk0p2 122880 7028735 3452928 83 Linux
      33. /dev/mmcblk0p3 7028736 60367871 26669568 83 Linux
      34. root@raspberrypi:~# ./resize_mmcp3.sh
      35. umount: /dev/mmcblk0p3: not mounted
      36. Command (m for help):
      37. Disk /dev/mmcblk0: 30.9 GB, 30908350464 bytes
      38. 4 heads, 16 sectors/track, 943248 cylinders, total 60367872 sectors
      39. Units = sectors of 1 * 512 = 512 bytes
      40. Sector size (logical/physical): 512 bytes / 512 bytes
      41. I/O size (minimum/optimal): 512 bytes / 512 bytes
      42. Disk identifier: 0x000b5098
      43. Device Boot Start End Blocks Id System
      44. /dev/mmcblk0p1 8192 122879 57344 c W95 FAT32 (LBA)
      45. /dev/mmcblk0p2 122880 7028735 3452928 83 Linux
      46. /dev/mmcblk0p3 7028736 60367871 26669568 83 Linux
      47. Command (m for help): Partition number (1-4):
      48. Command (m for help): Partition type:
      49. p primary (2 primary, 0 extended, 2 free)
      50. e extended
      51. Select (default p): Partition number (1-4, default 3): First sector (2048-60367871, default 2048): Last sector, +sectors or +size{K,M,G} (7028736-60367871, default 6036787
      52. 1): Using default value 60367871
      53. Command (m for help): The partition table has been altered!
      54. Calling ioctl() to re-read partition table.
      55. WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
      56. The kernel still uses the old table. The new table will be used at
      57. the next reboot or after you run partprobe(8) or kpartx(8)
      58. Syncing disks.
      59. e2fsck 1.42.5 (29-Jul-2012)
      60. /dev/mmcblk0p3 is in use.
      61. e2fsck: Cannot continue, aborting.
      62. Resizing the filesystem will take a few minutes or longer.
      63. resize2fs 1.42.5 (29-Jul-2012)
      64. resize2fs: Device or resource busy while trying to open /dev/mmcblk0p3
      65. Couldn't find valid filesystem superblock.
      66. mount: /dev/mmcblk0p3 already mounted or /media/fa36508a-b3c4-4499-b30a-711dd5994225 busy
      67. root@raspberrypi:~# df -kh
      68. Filesystem Size Used Avail Use% Mounted on
      69. /dev/root 3.2G 1.6G 1.5G 51% /
      70. devtmpfs 483M 0 483M 0% /dev
      71. tmpfs 98M 252K 98M 1% /run
      72. tmpfs 5.0M 0 5.0M 0% /run/lock
      73. tmpfs 195M 0 195M 0% /run/shm
      74. /dev/mmcblk0p1 56M 21M 35M 38% /boot
      75. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/log
      76. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/php5
      77. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/openmediavault/rrd
      78. folder2ram 487M 4.0K 487M 1% /var/lib/php5
      79. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/spool
      80. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/tmp
      81. folder2ram 487M 376K 487M 1% /var/lib/openmediavault/rrd
      82. folder2ram 487M 0 487M 0% /var/tmp
      83. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/monit
      84. folder2ram 487M 528K 487M 1% /var/log
      85. folder2ram 487M 700K 486M 1% /var/spool
      86. /dev/root 3.2G 1.6G 1.5G 51% /var/folder2ram/var/lib/rrdcached
      87. folder2ram 487M 4.0K 487M 1% /var/lib/monit
      88. folder2ram 487M 14M 474M 3% /var/lib/rrdcached
      89. /dev/mmcblk0p3 25G 2.8M 24G 1% /media/fa36508a-b3c4-4499-b30a-711dd5994225
      Display All

      Anyting what I can do here to manually to rectify the problem of removing the /dev/mmcblk0p3 and extend the FS /dev/mmcblk0p1 ??
    • carriba wrote:

      Anyting what I can do here to manually to rectify the problem of removing the /dev/mmcblk0p3 and extend the FS /dev/mmcblk0p1 ??
      The script doesn't remove the third partition and extend the OS partition. It extends the third partition to use the rest of the SD card since I create an image that will work on SD cards 4GB and bigger.

      The script should only be run after first installing. If you make changes, you don't want to use the script.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Odd that you would increase the size of the first partition... You can't use that for data storage from the web interface. It will also shorten the life of the card if you use it for other things.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • OK, I went ahead and flashed the OMV 3.0.24 (Erasmus) image on a 32GB SD card.

      After the 1st run, it seems that a 3rd partition is being created with the "resize_mmcp3.sh" script, however it seems that it doesn't use the entire remainig disk space of the SD card, despite an additional reboot of the box.

      Here is the output of my system queries on the shell prompt:

      Source Code

      1. root@raspberrypi:~# df -kh
      2. Filesystem Size Used Avail Use% Mounted on
      3. /dev/root 3.2G 1.7G 1.4G 56% /
      4. devtmpfs 483M 0 483M 0% /dev
      5. tmpfs 487M 0 487M 0% /dev/shm
      6. tmpfs 487M 6.7M 480M 2% /run
      7. tmpfs 5.0M 0 5.0M 0% /run/lock
      8. tmpfs 487M 0 487M 0% /sys/fs/cgroup
      9. /dev/mmcblk0p1 56M 21M 36M 37% /boot
      10. folder2ram 487M 368K 487M 1% /var/log
      11. folder2ram 487M 0 487M 0% /var/tmp
      12. folder2ram 487M 376K 487M 1% /var/lib/openmediavault/rrd
      13. folder2ram 487M 708K 486M 1% /var/spool
      14. folder2ram 487M 8.0K 487M 1% /var/lib/monit
      15. folder2ram 487M 12K 487M 1% /var/lib/php5
      16. /dev/mmcblk0p3 58M 1.3M 53M 3% /media/fa36508a-b3c4-4499-b30a-711dd5994225
      17. tmpfs 98M 0 98M 0% /run/user/0
      Display All
      It only shows 58M instead of 25G pertaining to the partition size :(

      So I went ahead and fired the following commands to delete the 3rd partition and recreate it again not using:

      Source Code

      1. root@raspberrypi:~# df -kh
      2. Filesystem Size Used Avail Use% Mounted on
      3. /dev/root 3.2G 1.7G 1.4G 56% /
      4. devtmpfs 483M 0 483M 0% /dev
      5. tmpfs 487M 0 487M 0% /dev/shm
      6. tmpfs 487M 6.7M 480M 2% /run
      7. tmpfs 5.0M 0 5.0M 0% /run/lock
      8. tmpfs 487M 0 487M 0% /sys/fs/cgroup
      9. /dev/mmcblk0p1 56M 21M 36M 37% /boot
      10. folder2ram 487M 368K 487M 1% /var/log
      11. folder2ram 487M 0 487M 0% /var/tmp
      12. folder2ram 487M 376K 487M 1% /var/lib/openmediavault/rrd
      13. folder2ram 487M 708K 486M 1% /var/spool
      14. folder2ram 487M 8.0K 487M 1% /var/lib/monit
      15. folder2ram 487M 12K 487M 1% /var/lib/php5
      16. /dev/mmcblk0p3 58M 1.3M 53M 3% /media/fa36508a-b3c4-4499-b30a-711dd5994225
      17. tmpfs 98M 0 98M 0% /run/user/0
      18. root@raspberrypi:~# umount /dev/mmcblk0p3
      19. root@raspberrypi:~# df -kh
      20. Filesystem Size Used Avail Use% Mounted on
      21. /dev/root 3.2G 1.7G 1.4G 56% /
      22. devtmpfs 483M 0 483M 0% /dev
      23. tmpfs 487M 0 487M 0% /dev/shm
      24. tmpfs 487M 6.7M 480M 2% /run
      25. tmpfs 5.0M 0 5.0M 0% /run/lock
      26. tmpfs 487M 0 487M 0% /sys/fs/cgroup
      27. /dev/mmcblk0p1 56M 21M 36M 37% /boot
      28. folder2ram 487M 376K 487M 1% /var/log
      29. folder2ram 487M 0 487M 0% /var/tmp
      30. folder2ram 487M 376K 487M 1% /var/lib/openmediavault/rrd
      31. folder2ram 487M 708K 486M 1% /var/spool
      32. folder2ram 487M 8.0K 487M 1% /var/lib/monit
      33. folder2ram 487M 12K 487M 1% /var/lib/php5
      34. tmpfs 98M 0 98M 0% /run/user/0
      35. root@raspberrypi:~# fdisk /dev/mmcblk0
      36. Welcome to fdisk (util-linux 2.25.2).
      37. Changes will remain in memory only, until you decide to write them.
      38. Be careful before using the write command.
      39. Command (m for help): p
      40. Disk /dev/mmcblk0: 28.8 GiB, 30908350464 bytes, 60367872 sectors
      41. Units: sectors of 1 * 512 = 512 bytes
      42. Sector size (logical/physical): 512 bytes / 512 bytes
      43. I/O size (minimum/optimal): 512 bytes / 512 bytes
      44. Disklabel type: dos
      45. Disk identifier: 0x000b5098
      46. Device Boot Start End Sectors Size Id Type
      47. /dev/mmcblk0p1 8192 122879 114688 56M c W95 FAT32 (LBA)
      48. /dev/mmcblk0p2 122880 7028735 6905856 3.3G 83 Linux
      49. /dev/mmcblk0p3 7028736 7159807 131072 64M 83 Linux
      50. Command (m for help): d
      51. Partition number (1-3, default 3): 3
      52. Partition 3 has been deleted.
      53. Command (m for help): n
      54. Partition type
      55. p primary (2 primary, 0 extended, 2 free)
      56. e extended (container for logical partitions)
      57. Select (default p): p
      58. Partition number (3,4, default 3): 3
      59. First sector (2048-60367871, default 2048): 7028736
      60. Last sector, +sectors or +size{K,M,G,T,P} (7028736-60367871, default 60367871):
      61. Created a new partition 3 of type 'Linux' and of size 25.4 GiB.
      62. Command (m for help): w
      63. The partition table has been altered.
      64. Calling ioctl() to re-read partition table.
      65. Re-reading the partition table failed.: Device or resource busy
      66. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
      Display All

      Now, If you pay attention when recreating the 3rd partition, it seems that "fdisk is using some default (and incorrect!) values that do not make senss, and I have to key in the correct values for the starting sector.

      Once, I have rebooted the box, I run the command "resize2fs /dev/mmcblk0p3" and the mounted 3rd partition shows its correct size:

      Source Code

      1. root@raspberrypi:~# df -kh
      2. Filesystem Size Used Avail Use% Mounted on
      3. /dev/root 3.2G 1.7G 1.4G 56% /
      4. devtmpfs 483M 0 483M 0% /dev
      5. tmpfs 487M 0 487M 0% /dev/shm
      6. tmpfs 487M 6.7M 480M 2% /run
      7. tmpfs 5.0M 0 5.0M 0% /run/lock
      8. tmpfs 487M 0 487M 0% /sys/fs/cgroup
      9. /dev/mmcblk0p3 25G 2.8M 24G 1% /media/fa36508a-b3c4-4499-b30a-711dd5994225
      10. /dev/mmcblk0p1 56M 21M 36M 37% /boot
      11. folder2ram 487M 652K 486M 1% /var/log
      12. folder2ram 487M 0 487M 0% /var/tmp
      13. folder2ram 487M 380K 487M 1% /var/lib/openmediavault/rrd
      14. folder2ram 487M 696K 486M 1% /var/spool
      15. folder2ram 487M 8.0K 487M 1% /var/lib/monit
      16. folder2ram 487M 8.0K 487M 1% /var/lib/php5
      17. tmpfs 98M 0 98M 0% /run/user/0
      Display All

      Unless I'm mistaken, to me it seems a bug with the "fdisk" command...
    • fdisk is updated in OMV 3.x. So, I probably need to update my script. I disable it when testing images because it is a lot of wear & tear on my SD cards.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • I guess I don't know what you are trying to say. Have you looked at the script? The only time it takes a default is when it is selecting the ending sector which should be fine.
      omv 4.1.19 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • OK, let me do a walkthrough again from the "fdisk" output in my original posting by stripping the irrelevant info and walk step by step what I've been able to observe:

      When firing "fidsk" on the shell prompt, and am printing the disk info, I'm getting:

      Disk /dev/mmcblk0: 28.8 GiB, 30908350464 bytes, 60367872 sectors
      ...
      Device Boot Start End Sectors Size Id Type
      /dev/mmcblk0p1 8192 122879 114688 56M c W95 FAT32 (LBA)
      /dev/mmcblk0p2 122880 7028735 6905856 3.3G 83 Linux
      /dev/mmcblk0p3 7028736 7159807 131072 64M 83 Linux

      I deteted the 3rd partition in my list (last line above), and recreate it:

      First sector (2048-60367871, default 2048): 7028736
      Last sector, +sectors or +size{K,M,G,T,P} (7028736-60367871, default 60367871):
      Created a new partition 3 of type 'Linux' and of size 25.4 GiB.

      And here the situation when recreating the 3rd partition:
      • Instead of accepting the default value 2048 for the 1st sector, I have to type 7028736.
      • For the last sector, I keep the default proposed value.
      I'll check your script to which extent it takes into account the correct value for the 1st sector. However, confirming as input the default value for the 1st sector will destroy the contents of the SD card, and the device will not be able to boot up (that's what happened to me).