Pi5 EXT4 mount problem

Hello.
I have a Pi4 with a 2TB seagate external HDD which I have been using it for a couple of years now with OMV 5 as media and torrent server and it has been working 24/7 with no issues.
This week I got my new Pi5 (I would like to add x265 hardware transcoding to plex) and installed OMV 6 using this guide but when I tried to mount my External HDD, I got an error, so I backed up my data, wiped the disk and created a new EXT4 file system in the OVM 6... Mounting error again.
Since then I have been trying to mount my HDD Drive with all possible combinations possible: Wiping it in OVM 5 and creating the filesystem, wiping in OVM 5, creating the file system in OVM 6, installing OVM 7 in the Pi5, fixing the data tables, plugging the HDD in the USB 2 and USB 3 ports, checked the HDD for bad sertors (0 bad sectors found), believe me, I have tried anything that I have found without success.
I would like to mention that the HDD works great on the Pi4 with OVM 5.
If someone have faced this issue before or knows how to solve it, I'll really appreciate the help.

Raspberry Pi 5 8GB
Seagate 2 TB disk USB 3.0

THis is the last error I got from OVM 7:

Succeeded: 2 (changed=1)

Failed: 1

------------

Total states run: 3

Total run time: 141.508 s

[ERROR ] Command 'mount' failed with return code: 32

[ERROR ] stderr: mount: /srv/dev-disk-by-uuid-887f2dd5-5250-4e40-ba4a-18ebbd22c803: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.

dmesg(1) may have more information after failed mount system call.

[ERROR ] retcode: 32

[ERROR ] mount: /srv/dev-disk-by-uuid-887f2dd5-5250-4e40-ba4a-18ebbd22c803: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.

dmesg(1) may have more information after failed mount system call. in /usr/share/php/openmediavault/system/process.inc:247

Stack trace:

#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()

#1 /usr/share/openmediavault/engined/rpc/config.inc(178): OMV\Engine\Module\ServiceAbstract->deploy()

#2 [internal function]: Engined\Rpc\Config->applyChanges()

#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()

#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod()

#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(622): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}()

#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(146): OMV\Rpc\ServiceAbstract->execBgProc()

#7 /usr/share/openmediavault/engined/rpc/config.inc(199): OMV\Rpc\ServiceAbstract->callMethodBg()

#8 [internal function]: Engined\Rpc\Config->applyChangesBg()

#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()

#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()

#11 /usr/sbin/omv-engined(535): OMV\Rpc\Rpc::call()

#12 {main}

Thanks

Quote from greg77

The error says:

wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.

What is the filesystem type on your disk?

Is it ext4 or something else which Linux supports natively?

Hello Greg.
The filesystem for the External HDD is EXT4.
Attached you can find an image of the very same HDD running without issues in my Pi4.
Thanks

Quote from Soma

armand2099

You mention OMV5 and 6 and 7.

Pi4 and 5 etc..

What you don't mention is the exact model of the external HDD other than it's a 2Tb Seagate.

Is it externally powered or it's just a portable drive?

About the Pi:

Which power supply are you using? The old 3A from the Pi4 or the new 5A that is for the Pi5?

Which image did you use on the Pi5? Pi5 only run with bookworm so, saying that you tried OMV6 or 5 doesn't make any sense.

To proper use Pi5, just start fresh with the bookworm OS 64bit Lite without any other drive attached.

After initial config of OMV7, then you attach the drive and move from there.

Display More

Hello Soma.
Thank you very much for your response.
You are totally right, the problem was the power supply that I was using.
Thank you and Greg for your help.