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

OhMyVirtual · 20. Juni 2016

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:

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).

ryecoaaron · 20. Juni 2016

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

OhMyVirtual · 20. Juni 2016

Code

root@raspberrypi:~# cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.


# Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
  printf "My IP address is %s\n" "$_IP"
fi


test -f /etc/ssh/ssh_host_dsa_key || dpkg-reconfigure openssh-server


exit 0

Alles anzeigen

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).

Wolf2000 · 20. Juni 2016

Hi
raspi-config ?
https://www.raspberrypi.org/do…iguration/raspi-config.md

ryecoaaron · 21. Juni 2016

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.

OhMyVirtual · 21. Juni 2016

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

Code

root@raspberrypi:~# ./resize_mmcp3.sh


Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.


Command (m for help): Disk /dev/mmcblk0: 119.1 GiB, 127865454592 bytes, 249737216 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
Disklabel type: dos
Disk identifier: 0x000b5098


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


Command (m for help): Partition number (1-3, default 3):
Partition 3 has been deleted.


Command (m for help): Partition type
   p   primary (2 primary, 0 extended, 2 free)
   e   extended (container for logical partitions)
Select (default p): Partition number (3,4, default 3): First sector (2048-249737215, default 2048): Value out of range.
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):
Do you really want to quit? e2fsck 1.42.12 (29-Aug-2014)
Superblock last mount time (Wed Dec  7 12:17:03 2016,
        now = Tue Jun 21 03:14:29 2016) is in the future.
Fix? yes


Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mmcblk0p3: 13/16384 files (7.7% non-contiguous), 7472/65536 blocks
Resizing the filesystem will take a few minutes or longer.
resize2fs 1.42.12 (29-Aug-2014)
The filesystem is already 65536 (1k) blocks long.  Nothing to do!

Alles anzeigen

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.

ryecoaaron · 21. Juni 2016

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?

OhMyVirtual · 21. Juni 2016

Zitat von ryecoaaron

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.

ryecoaaron · 21. Juni 2016

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.

OhMyVirtual · 22. Juni 2016

Zitat von ryecoaaron

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.

ryecoaaron · 22. Juni 2016

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.

carriba · 29. September 2016

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:

Code

root@raspberrypi:~# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.2G  1.6G  1.5G  51% /
devtmpfs        483M     0  483M   0% /dev
tmpfs            98M  248K   98M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           195M     0  195M   0% /run/shm
/dev/mmcblk0p1   56M   21M   35M  38% /boot
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/log
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/php5
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/openmediavault/rrd
folder2ram      487M     0  487M   0% /var/lib/php5
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/spool
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/tmp
folder2ram      487M  376K  487M   1% /var/lib/openmediavault/rrd
folder2ram      487M     0  487M   0% /var/tmp
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/monit
folder2ram      487M  404K  487M   1% /var/log
folder2ram      487M  696K  486M   1% /var/spool
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/rrdcached
folder2ram      487M  4.0K  487M   1% /var/lib/monit
folder2ram      487M   14M  474M   3% /var/lib/rrdcached
root@raspberrypi:~# fdisk -l


Disk /dev/mmcblk0: 30.9 GB, 30908350464 bytes
4 heads, 16 sectors/track, 943248 cylinders, total 60367872 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 identifier: 0x000b5098


        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192      122879       57344    c  W95 FAT32 (LBA)
/dev/mmcblk0p2          122880     7028735     3452928   83  Linux
/dev/mmcblk0p3         7028736    60367871    26669568   83  Linux
root@raspberrypi:~# ./resize_mmcp3.sh
umount: /dev/mmcblk0p3: not mounted


Command (m for help):
Disk /dev/mmcblk0: 30.9 GB, 30908350464 bytes
4 heads, 16 sectors/track, 943248 cylinders, total 60367872 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 identifier: 0x000b5098


        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            8192      122879       57344    c  W95 FAT32 (LBA)
/dev/mmcblk0p2          122880     7028735     3452928   83  Linux
/dev/mmcblk0p3         7028736    60367871    26669568   83  Linux






Command (m for help): Partition number (1-4):
Command (m for help): Partition type:
   p   primary (2 primary, 0 extended, 2 free)
   e   extended
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
1): Using default value 60367871


Command (m for help): The partition table has been altered!


Calling ioctl() to re-read partition table.


WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
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)
Syncing disks.
e2fsck 1.42.5 (29-Jul-2012)
/dev/mmcblk0p3 is in use.
e2fsck: Cannot continue, aborting.




Resizing the filesystem will take a few minutes or longer.
resize2fs 1.42.5 (29-Jul-2012)
resize2fs: Device or resource busy while trying to open /dev/mmcblk0p3
Couldn't find valid filesystem superblock.
mount: /dev/mmcblk0p3 already mounted or /media/fa36508a-b3c4-4499-b30a-711dd5994225 busy
root@raspberrypi:~# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.2G  1.6G  1.5G  51% /
devtmpfs        483M     0  483M   0% /dev
tmpfs            98M  252K   98M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           195M     0  195M   0% /run/shm
/dev/mmcblk0p1   56M   21M   35M  38% /boot
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/log
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/php5
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/openmediavault/rrd
folder2ram      487M  4.0K  487M   1% /var/lib/php5
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/spool
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/tmp
folder2ram      487M  376K  487M   1% /var/lib/openmediavault/rrd
folder2ram      487M     0  487M   0% /var/tmp
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/monit
folder2ram      487M  528K  487M   1% /var/log
folder2ram      487M  700K  486M   1% /var/spool
/dev/root       3.2G  1.6G  1.5G  51% /var/folder2ram/var/lib/rrdcached
folder2ram      487M  4.0K  487M   1% /var/lib/monit
folder2ram      487M   14M  474M   3% /var/lib/rrdcached
/dev/mmcblk0p3   25G  2.8M   24G   1% /media/fa36508a-b3c4-4499-b30a-711dd5994225

Alles anzeigen

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

ryecoaaron · 29. September 2016

Zitat von carriba

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.

carriba · 29. September 2016

Yes, you're right and sorry for the confusion.

I manually deleted now the 3rd partition and extented the 1st partition following the steps described with the RPi Resize Flash Partitions documentation.

Will now do the same on the OMV 3.0.24 (beta) platform...

ryecoaaron · 29. September 2016

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.

carriba · 29. September 2016

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:

Code

root@raspberrypi:~# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.2G  1.7G  1.4G  56% /
devtmpfs        483M     0  483M   0% /dev
tmpfs           487M     0  487M   0% /dev/shm
tmpfs           487M  6.7M  480M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           487M     0  487M   0% /sys/fs/cgroup
/dev/mmcblk0p1   56M   21M   36M  37% /boot
folder2ram      487M  368K  487M   1% /var/log
folder2ram      487M     0  487M   0% /var/tmp
folder2ram      487M  376K  487M   1% /var/lib/openmediavault/rrd
folder2ram      487M  708K  486M   1% /var/spool
folder2ram      487M  8.0K  487M   1% /var/lib/monit
folder2ram      487M   12K  487M   1% /var/lib/php5
/dev/mmcblk0p3   58M  1.3M   53M   3% /media/fa36508a-b3c4-4499-b30a-711dd5994225
tmpfs            98M     0   98M   0% /run/user/0

Alles anzeigen

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:

Code

root@raspberrypi:~# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.2G  1.7G  1.4G  56% /
devtmpfs        483M     0  483M   0% /dev
tmpfs           487M     0  487M   0% /dev/shm
tmpfs           487M  6.7M  480M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           487M     0  487M   0% /sys/fs/cgroup
/dev/mmcblk0p1   56M   21M   36M  37% /boot
folder2ram      487M  368K  487M   1% /var/log
folder2ram      487M     0  487M   0% /var/tmp
folder2ram      487M  376K  487M   1% /var/lib/openmediavault/rrd
folder2ram      487M  708K  486M   1% /var/spool
folder2ram      487M  8.0K  487M   1% /var/lib/monit
folder2ram      487M   12K  487M   1% /var/lib/php5
/dev/mmcblk0p3   58M  1.3M   53M   3% /media/fa36508a-b3c4-4499-b30a-711dd5994225
tmpfs            98M     0   98M   0% /run/user/0
root@raspberrypi:~# umount /dev/mmcblk0p3
root@raspberrypi:~# df -kh
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       3.2G  1.7G  1.4G  56% /
devtmpfs        483M     0  483M   0% /dev
tmpfs           487M     0  487M   0% /dev/shm
tmpfs           487M  6.7M  480M   2% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           487M     0  487M   0% /sys/fs/cgroup
/dev/mmcblk0p1   56M   21M   36M  37% /boot
folder2ram      487M  376K  487M   1% /var/log
folder2ram      487M     0  487M   0% /var/tmp
folder2ram      487M  376K  487M   1% /var/lib/openmediavault/rrd
folder2ram      487M  708K  486M   1% /var/spool
folder2ram      487M  8.0K  487M   1% /var/lib/monit
folder2ram      487M   12K  487M   1% /var/lib/php5
tmpfs            98M     0   98M   0% /run/user/0
root@raspberrypi:~# fdisk /dev/mmcblk0
Welcome to fdisk (util-linux 2.25.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/mmcblk0: 28.8 GiB, 30908350464 bytes, 60367872 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
Disklabel type: dos
Disk identifier: 0x000b5098
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
Command (m for help): d
Partition number (1-3, default 3): 3
Partition 3 has been deleted.
Command (m for help): n
Partition type
   p   primary (2 primary, 0 extended, 2 free)
   e   extended (container for logical partitions)
Select (default p): p
Partition number (3,4, default 3): 3
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.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
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).

Alles anzeigen

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:

Code

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

Alles anzeigen

Unless I'm mistaken, to me it seems a bug with the "fdisk" command...

ryecoaaron · 29. September 2016

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.

carriba · 3. Oktober 2016

Unless it wasn't evident from the output quoted in my previous post, instead of taking the default values printed during the "fdisk create partition" prompt, it seems to me to be fine if parsing out the real values from the "fdisk" command output, and then input them within the script.

Other people have similar challenges as described in the "Resized SD" article...

ryecoaaron · 3. Oktober 2016

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.

carriba · 3. Oktober 2016

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).

Jetzt mitmachen!