Hi,
Just to thanks the community for the hard and excellent work.
I’ve just upgraded my OMV7 to 8 without any problem including Plex in Docker.
Using the omv-upgrade-release command only.
Bravo ! ![]()
Hi,
Just to thanks the community for the hard and excellent work.
I’ve just upgraded my OMV7 to 8 without any problem including Plex in Docker.
Using the omv-upgrade-release command only.
Bravo ! ![]()
Hi ryecoaaron ,
Thanks for your help. My apologies for the delay but I had some problems with my internet...
It seems I have a problem as I can't login as root.
I will try to make a fresh install.
Hello,
I’m trying to update my omv and i have an error code 500.
Specific installation as It’s a VM on a Freebox Ultra.
No problem during the last year.
Any idea ?
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; apt-get update 2>&1' with exit code '100': Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
Get:6 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Get:8 file:/var/cache/openmediavault/archives Release
Ign:8 file:/var/cache/openmediavault/archives Release
Hit:9 http://security.debian.org/debian-security bookworm-security InRelease
Hit:10 http://httpredir.debian.org/debian bookworm-backports InRelease
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Hit:13 http://packages.openmediavault.org/public sandworm InRelease
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:14 https://openmediavault.github.io/packages sandworm InRelease [12.8 kB]
Hit:3 https://deb.debian.org/debian bookworm InRelease
Hit:4 https://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.debian.org/debian bookworm-backports InRelease
Hit:7 https://deb.debian.org/debian-security bookworm-security InRelease
Get:15 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease [4111 B]
Err:15 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A NO_PUBKEY 63D8A7D17FDC2980
Reading package lists...
W: GPG error: https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A NO_PUBKEY 63D8A7D17FDC2980
E: The repository 'https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease' is not signed.
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; apt-get update 2>&1' with exit code '100': Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
Get:6 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Get:8 file:/var/cache/openmediavault/archives Release
Ign:8 file:/var/cache/openmediavault/archives Release
Hit:9 http://security.debian.org/debian-security bookworm-security InRelease
Hit:10 http://httpredir.debian.org/debian bookworm-backports InRelease
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Hit:13 http://packages.openmediavault.org/public sandworm InRelease
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Ign:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:11 file:/var/cache/openmediavault/archives Packages
Get:12 file:/var/cache/openmediavault/archives Translation-en
Ign:12 file:/var/cache/openmediavault/archives Translation-en
Get:14 https://openmediavault.github.io/packages sandworm InRelease [12.8 kB]
Hit:3 https://deb.debian.org/debian bookworm InRelease
Hit:4 https://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.debian.org/debian bookworm-backports InRelease
Hit:7 https://deb.debian.org/debian-security bookworm-security InRelease
Get:15 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease [4111 B]
Err:15 https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A NO_PUBKEY 63D8A7D17FDC2980
Reading package lists...
W: GPG error: https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A NO_PUBKEY 63D8A7D17FDC2980
E: The repository 'https://openmediavault-plugin-developers.github.io/packages/debian sandworm InRelease' is not signed. in /usr/share/openmediavault/engined/rpc/apt.inc:272
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(628): Engined\Rpc\Apt->Engined\Rpc\{closure}()
#1 /usr/share/openmediavault/engined/rpc/apt.inc(265): OMV\Rpc\ServiceAbstract->execBgProc()
#2 [internal function]: Engined\Rpc\Apt->update()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(546): OMV\Rpc\Rpc::call()
#6 {main}
Display More
Hi guys,
Just for update :
root@serveurmaison:~# omv-salt deploy run initramfs mdadm
debian:
----------
ID: remove_cron_daily_mdadm
Function: file.absent
Name: /etc/cron.daily/mdadm
Result: True
Comment: File /etc/cron.daily/mdadm is not present
Started: 17:48:12.479927
Duration: 1.972 ms
Changes:
----------
ID: divert_cron_daily_mdadm
Function: omv_dpkg.divert_add
Name: /etc/cron.daily/mdadm
Result: True
Comment: Leaving 'local diversion of /etc/cron.daily/mdadm to /tmp/_etc_cron.daily_mdadm'
Started: 17:48:12.483175
Duration: 11.351 ms
Changes:
----------
ID: configure_default_mdadm
Function: file.managed
Name: /etc/default/mdadm
Result: True
Comment: File /etc/default/mdadm is in the correct state
Started: 17:48:12.494776
Duration: 157.727 ms
Changes:
----------
ID: configure_mdadm_conf
Function: file.managed
Name: /etc/mdadm/mdadm.conf
Result: True
Comment: File /etc/mdadm/mdadm.conf updated
Started: 17:48:12.652624
Duration: 155.152 ms
Changes:
----------
diff:
---
+++
@@ -20,4 +20,3 @@
HOMEHOST <system>
# definitions of existing MD arrays
-ARRAY /dev/md/OMV metadata=1.2 spares=1 name=openmediavault:OMV UUID=b1bd0cdb:83d9766c:8fd3c89b:dd62753a
----------
ID: mdadm_save_config
Function: cmd.run
Name: mdadm --detail --scan >> /etc/mdadm/mdadm.conf
Result: True
Comment: Command "mdadm --detail --scan >> /etc/mdadm/mdadm.conf" run
Started: 17:48:12.810557
Duration: 24.62 ms
Changes:
----------
pid:
931825
retcode:
0
stderr:
stdout:
----------
ID: update_initramfs_nop
Function: test.nop
Result: True
Comment: Success!
Started: 17:48:12.836695
Duration: 0.984 ms
Changes:
----------
ID: update_initramfs
Function: cmd.run
Name: update-initramfs -u
Result: True
Comment: Command "update-initramfs -u" run
Started: 17:48:12.837784
Duration: 38097.991 ms
Changes:
----------
pid:
931827
retcode:
0
stderr:
stdout:
update-initramfs: Generating /boot/initrd.img-6.12.32+bpo-amd64
Summary for debian
------------
Succeeded: 7 (changed=3)
Failed: 0
------------
Total states run: 7
Total run time: 38.450 s
root@serveurmaison:~#
Display More
Thanks for your patience and help ![]()
Hi geaves,
Display Moremdadm --detail
root@serveurmaison:~# mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Fri May 19 23:36:36 2017
Raid Level : raid5
Array Size : 5860150272 (5.46 TiB 6.00 TB)
Used Dev Size : 1953383424 (1862.89 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jul 11 15:02:09 2025
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : openmediavault:OMV
UUID : b1bd0cdb:83d9766c:8fd3c89b:dd62753a
Events : 278506
Number Major Minor RaidDevice State
0 8 32 0 active sync /dev/sdc
1 8 48 1 active sync /dev/sdd
2 8 16 2 active sync /dev/sdb
4 8 0 3 active sync /dev/sda
Display Morecat /etc/mdadm/mdadm.conf
root@serveurmaison:~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md/OMV metadata=1.2 spares=1 name=openmediavault:OMV UUID=b1bd0cdb:83d9766c:8fd3c89b:dd62753a
Pass, that's out of my ball park
I don't shutdown my Microserver and it's very rare I connect a monitor to check the console
Idem. It was more for my knowledge
Hi geaves,
Should I put again the "old" disk in place and then remove it ? Cause I've made exactly what you said (maybe with the second reboot missing, can't remember).
Display Moremdadm --detail /dev/sda
root@serveurmaison:~# mdadm --detail /dev/sda
mdadm: /dev/sda does not appear to be an md device
root@serveurmaison:~# mdadm --detail /dev/sdb
mdadm: /dev/sdb does not appear to be an md device
root@serveurmaison:~# mdadm --detail /dev/sdc
mdadm: /dev/sdc does not appear to be an md device
root@serveurmaison:~# mdadm --detail /dev/sdd
mdadm: /dev/sdd does not appear to be an md device
Thank again for you help ![]()
EDIT :
Using this page : https://phoenixnap.com/kb/fsck-command-linux I've corrected a lot of errors. Seems to be ok now.
BUT (always a BUT), now I found initialramdisk very long to load (about 1 to 2 mn). I've not noticed this before but not sure it's new...
Hi, it's me (again),
My RAID has finished the recovering, but is always not mounting.
root@serveurmaison:~# mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Fri May 19 23:36:36 2017
Raid Level : raid5
Array Size : 5860150272 (5.46 TiB 6.00 TB)
Used Dev Size : 1953383424 (1862.89 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Mon Jul 7 18:13:07 2025
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : openmediavault:OMV
UUID : b1bd0cdb:83d9766c:8fd3c89b:dd62753a
Events : 278498
Number Major Minor RaidDevice State
0 8 48 0 active sync /dev/sdd
1 8 32 1 active sync /dev/sdc
2 8 0 2 active sync /dev/sda
4 8 16 3 active sync /dev/sdb
Display More
root@serveurmaison:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10]
md127 : active raid5 sda[2] sdd[0] sdb[4] sdc[1]
5860150272 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/15 pages [0KB], 65536KB chunk
unused devices: <none>
root@serveurmaison:~# blkid
/dev/sdd: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="e67f0313-548c-4414-d8c8-fe79867ea78a" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
/dev/md127: LABEL="Raid5" UUID="b6dd9418-30ce-499c-90ca-7fc678a3fe24" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="a3cd44ed-b24b-ca41-25bf-6ef359d37588" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
/dev/sde5: UUID="0747ae2c-7242-41d2-b70f-d20bacbe9126" TYPE="swap" PARTUUID="0a762683-05"
/dev/sde1: UUID="20dd934e-4034-45ce-aacf-c6ea0d908b28" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0a762683-01"
/dev/sdc: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="85ed296c-7ef9-37bd-16ed-d61c11f676b8" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
/dev/sda: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="f123a240-b61a-ae20-ffeb-6140b93c49b7" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
root@serveurmaison:~# fdisk -l | grep "Disk "
Disk /dev/sda: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TOSHIBA DT01ABA2
Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN003-3CW1
Disk /dev/sdd: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN004-2E41
Disk /dev/sdc: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN004-2E41
Disk /dev/sde: 111,79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Force LE200 SSD
Disk identifier: 0x0a762683
Disk /dev/md127: 5,46 TiB, 6000793878528 bytes, 11720300544 sectors
Display More
root@serveurmaison:~# cat /etc/mdadm/mdadm.conf
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
# Note, if no DEVICE line is present, then "DEVICE partitions" is assumed.
# To avoid the auto-assembly of RAID devices a pattern that CAN'T match is
# used if no RAID devices are configured.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# definitions of existing MD arrays
ARRAY /dev/md/OMV metadata=1.2 spares=1 name=openmediavault:OMV UUID=b1bd0cdb:83d9766c:8fd3c89b:dd62753a
Display More
root@serveurmaison:~# mdadm --detail --scan --verbose
ARRAY /dev/md/OMV level=raid5 num-devices=4 metadata=1.2 name=openmediavault:OMV UUID=b1bd0cdb:83d9766c:8fd3c89b:dd62753a
devices=/dev/sda,/dev/sdb,/dev/sdc,/dev/sdd
In addition, losing to the console, I have this message :
My understanding is that I should not have swapped just as it the disks but :
1/ remove form the raid the disk,
2/ Rebooting
3/ Then add the new disk ?
Is it too late to correct this ?
Hi geaves,
I will continue with SW raid as I trust OMV as a very good solution with a very good community. 😀
I've just received new disk and replaced the one which seems in the baddest condition (sda). I'm now in recovering mode. ![]()
I will order a second disk next month and replace the other one with SMART warnings.
I'm using OMV since... a long time, and each time I had problems I had a solution via the community.
I'm using it in a VM on a Freebox Ultra (triple play box from Internet provider Free) and it's working well (but no RAID) and in the configuration with an HP Microserver Gen8.
Thanks for the help ! ![]()
Obviously I have a question : is it better to enable a Raid with HW from the server or as actually SW raid via OMV ?
Hi,
I confirm that sda is normally in the raid but not anymore.
Since last reboot, the Raid is not mounting (see screen shot).
root@serveurmaison:~# mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Fri May 19 23:36:36 2017
Raid Level : raid5
Array Size : 5860150272 (5.46 TiB 6.00 TB)
Used Dev Size : 1953383424 (1862.89 GiB 2000.26 GB)
Raid Devices : 4
Total Devices : 3
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jul 4 15:22:01 2025
State : clean, degraded
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Consistency Policy : bitmap
Name : openmediavault:OMV
UUID : b1bd0cdb:83d9766c:8fd3c89b:dd62753a
Events : 266449
Number Major Minor RaidDevice State
0 8 32 0 active sync /dev/sdc
1 8 16 1 active sync /dev/sdb
2 8 48 2 active sync /dev/sdd
- 0 0 3 removed
Display More
Hello,
Sorry for the delay.
Thanks for your help.
root@serveurmaison:~# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10]
md127 : active raid5 sdc[2] sdb[1] sdd[0]
5860150272 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/3] [UUU_]
bitmap: 15/15 pages [60KB], 65536KB chunk
unused devices: <none>
root@serveurmaison:~# blkid
/dev/sdd: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="e67f0313-548c-4414-d8c8-fe79867ea78a" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
/dev/md127: LABEL="Raid5" UUID="b6dd9418-30ce-499c-90ca-7fc678a3fe24" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="85ed296c-7ef9-37bd-16ed-d61c11f676b8" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
/dev/sde5: UUID="0747ae2c-7242-41d2-b70f-d20bacbe9126" TYPE="swap" PARTUUID="0a762683-05"
/dev/sde1: UUID="20dd934e-4034-45ce-aacf-c6ea0d908b28" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0a762683-01"
/dev/sdc: UUID="b1bd0cdb-83d9-766c-8fd3-c89bdd62753a" UUID_SUB="f123a240-b61a-ae20-ffeb-6140b93c49b7" LABEL="openmediavault:OMV" TYPE="linux_raid_member"
root@serveurmaison:~# fdisk -l | grep "Disk "
Disk /dev/sda: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN004-2E41
Disk /dev/sdc: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: TOSHIBA DT01ABA2
Disk /dev/sdb: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN004-2E41
Disk /dev/sdd: 1,82 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000VN004-2E41
Disk /dev/sde: 111,79 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Force LE200 SSD
Disk identifier: 0x0a762683
Disk /dev/md127: 5,46 TiB, 6000793878528 bytes, 11720300544 sectors
Display More
root@serveurmaison:~# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# !NB! Run update-initramfs -u after updating this file.
# !NB! This will ensure that initramfs has an uptodate copy.
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
# This configuration was auto-generated on Mon, 23 Dec 2024 13:38:58 +0000 by mkconf
Display More
root@serveurmaison:~# mdadm --detail --scan --verbose
ARRAY /dev/md/OMV level=raid5 num-devices=4 metadata=1.2 name=openmediavault:OMV UUID=b1bd0cdb:83d9766c:8fd3c89b:dd62753a
devices=/dev/sdb,/dev/sdc,/dev/sdd
4 HDD 2TB for the Raid. Seems after running a SMART that 2 HDD a in a degraded state. See att
1 SSD 128 Gb (not sure of the capacity) for OMV
I had the problem after updating and rebooting.
Hello,
After reboot, one of the HDD on my NAS is not mounting anymore (RAID5).
Trying to add the disk to the RAID via RAID -> Recover and I have the following error ;
"Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; mdadm --manage '/dev/md127' --add /dev/sda 2>&1' with exit code '1': mdadm: add new device failed for /dev/sda as 4: Invalid argument
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; mdadm --manage '/dev/md127' --add /dev/sda 2>&1' with exit code '1': mdadm: add new device failed for /dev/sda as 4: Invalid argument in /usr/share/php/openmediavault/system/process.inc:247
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/mdmgmt.inc(420): OMV\System\Process->execute()
#1 [internal function]: Engined\Rpc\MdMgmt->add()
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array()
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#4 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#5 {main}"
Does anybody knows what should be the problem ?
HP MicroServer gen 8.
On ILO starting, no error message (as I know).
Hello,
Excuse my English, I'm French ![]()
I'm under OMV 5.5.4-1 (Usul) and tried the Donate button.
It opens a new blank tab.
New installation on Proxmox 6.
Same problem on a second server HP Microserver gen8 with only OMV on it.