there are too many (primary) partitions in the partition table

Hello,

I want to reinstall my HP Proliant Microserver N54L. It worked the last 7 years perfectly with omv 3.

The new thing is that I want to install omv5 from USB-Stick to an USB SSD arddrive "TREKSTOR I.GEAR USB SSD (Q0802B0)".

I downloaded the image as described here:

I prepared the usb-stick as as described here:

I took out all harddrives and pluged off all extern devices.

Then I plugged in the usb-stick (with the installation image) and the clean usb ssd "TREKSTOR I.GEAR USB SSD (Q0802B0)".

I cleaned it before by doing the following on my ubuntu 18.04.5 laptop:

sudo dd if=/dev/zero of=/dev/sdb bs=1M count=10

Now I switched on the microserver and the installation started.

When it comes to the section where i could choose my destination drive i have chosen the usb ssd "TREKSTOR I.GEAR USB SSD (Q0802B0)".

Then the following error message with a red background comes up:

[ [!!] Partition disks ]

Failed to partition the selected disk

This probably happened because there are too many (primary) partitions in the partition table.

<Go Back> <Continue>

Thanks in advance for any help.

regards

sh

Yes, my first try was to use gparted on the laptop but there was something wired ... gparted was not able to delete all partitions on the usb ssd.

So in my dispariation I searched and found this dd command.

Ok, now after all I used gparted to create a new partition table and created one ext4 partition. But the same error comes up after selecting the installation device.

OK I am back,

I got myself a new USB-Stick an USB SSD harddrive "TREKSTOR I.GEAR USB SSD (Q0802B0).

Got it out of the box and put it directly into the HP Proliant Microserver N54L and installed OMV 5.5.11 from cdrom and got the same problem. I even was not able to partition any thing. I got directly the following message when it came up to partitioning:

[ [!!] Partition disks ]

Failed to partition the selected disk

This probably happened because there are too many (primary) partitions in the partition table.

<Go Back> <Continue>

Then I tried to install OMV 3.0.86 which worked on this system several years without any problems (on an ordinary sata2 hd). The installation on the usb-ssd was like a walk through the park (no errors). But after the installation finished the computer starts from the usb-ssd and I landed in the grub rescue console. The file normal.mod was not found.

Then i tried to install xubuntu 20.04 LTS on to the usb-ssd and found my self again in the grub rescue console after the installation finished. The file normal.mod was not found.

Then I found this on the internet: https://ubuntuforums.org/showthread.php?t=1997316

I installed xubuntu again but made the partition by my self as follows:

One primaray partition; ext4; for /; and less then 25 GB ... i chose 24 GB.

After Installing the system booted up with no errors!

But after installing OpenmediaVault 4.1.22 I got the same error as I got with OMV 5.5.11:

[ [!!] Partition disks ]

Failed to partition the selected disk

This probably happened because there are too many (primary) partitions in the partition table.

<Go Back> <Continue>

In the OMV installation process I do not get the opportunity to do the partitioning by my self

Is there anybody out there who had the same problem or can help me with this nasty thing

Thanks in advance for any help.

KM0201:

Thank you very much for your answer/help!

Installing xUbuntu was just a test. The main goal was/is still to install pure openmediavault 5.

So I checked several times that there are only two partitions on the usb-ssd. But while the installation of omv I was never be able to delete or do any patitioningthing else. There is always the mentioned error. Even if I deleted all partitions with gparted this ... error came up.

crashtest:

Thank you that' s it!

The installation of Buster run flawlessly. I was able to do any partitioning I wanted/needed. Excellent link.

So it seems that this error is caused by the omv installer.

there is something crazy going on

I did the installation as mentioned here:

Quote from crashtest

Give this installation method a try - Alternate 64bit installation.

The first time I did so I was really delighted that i was able to finish the partitioning and after the installation of debian and the reboot I did

apt-get update

and

apt-get upgrade

But after a reboot I found out that my networkadapter is not working any more.

I had fixed it for my actual session by doing:

ip link set enp3s0 up

and

dhclient enp3s0

and after a reboot it was lost again.

So I decided to make a complete reinstall. And after the installation of debian i did not made a

apt-get upgrade

I installed wget as described and got the installscript. The command | sudo bash did not work so I just downloaded the install script and started it as root.

Following the lines on the screen it seem to me that the install scrip did although

apt-get update

and

apt-get upgrade

so after the installation of omv and a reboot my nic was not started.

So i started

omv-firstaid

to fix this permanently.

OK it worked after a reboot but now I have the following phenomena:

In an ssh session my one and only NIC is named "enp3s0" and in the web control panel there i have also only one NIC called "enp2s0" If I try to add a new NIC in the web control panel then i will see in the dropdown list only "enp3s0".

I checked a diffrent omv installation via vpn and there is only the same NIC-name in the ssh session as well as in the web control panel.

I am really confused before I will start now to set up all options in my new omv system I wanted to ask if there is something to worry about this behavior: two names (enp2s0 and enp3s0) for one NIC at the same time

As mentioned before I installed debian/omv on an usb/ssd from my usb cdrom. After the installaton of debian i plugged of the cdrom and restarted the system. This is the only change to the hardware i did after the debian installation. I think that this could not be the reason for this phenomena because the the NIC is on borad and its hardware address should not be changed by plugging of the usb cdrom, or should it?

Any help would be great ... thx

Quote from crashtest

Set aside the SSD, for now.

Buy a USB stick (a new one, 6 to 32 - USB 2 or 3), and use the new USB stick as the boot drive.

If / when you get this up and running, follow this -> Guide, starting at initial configuration. You're going to want to install the flashmemory plugin.

Thank you for your links and thank you for this painful answer ("Set aside the SSD, for now.") - I spent up to 100 bugs for this stick

Anyway ... with a new ordinary ssd the installation was as easy as usual.

Thx to all for your help.

cheers

om4711