Hi,
just have installed OMV on my gen8 microserver.
I configured two similar HD in RAID_Stripe and then wanted to create a filesytem.
I get a strange error:
Error #0:OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mkfs -V -t ext4 -b 4096 -m 0 -E lazy_itable_init=0,lazy_journal_init=0 -O 64bit -L 'MyRaidFinal' '/dev/md0' 2>&1' with exit code '1': mke2fs 1.44.5 (15-Dec-2018)/dev/md0 is apparently in use by the system; will not make a filesystem here! in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:642Stack trace:#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(536): OMVRpcServiceFileSystemMgmt->{closure}('/tmp/bgstatuswO...', '/tmp/bgoutputrE...')#1 /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc(658): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure), NULL, Object(Closure))#2 [internal function]: OMVRpcServiceFileSystemMgmt->create(Array, Array)#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('create', Array, Array)#5 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('FileSystemMgmt', 'create', Array, Array, 1)#6 {main}
I have no share folders, the HD have just been wiped.
Here is the result of a mdadm --detail /dev/md0
root@Gen8HP:~# mdadm --detail /dev/md0
mdadm: Unknown keyword INACTIVE-ARRAY
/dev/md0:
Version : 1.2
Creation Time : Sat Mar 16 16:51:59 2019
Raid Level : raid0
Array Size : 3906766848 (3725.78 GiB 4000.53 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sat Mar 16 16:51:59 2019
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : Gen8HP:MyRAID (local to host Gen8HP)
UUID : a5a0bee8:9efb348f:39c556cf:79ef5cb4
Events : 0
Number Major Minor RaidDevice State
0 8 0 0 active sync /dev/sda
1 8 16 1 active sync /dev/sdb
Alles anzeigen
And the result of a fdisk-l
Disk /dev/sda: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdb: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 931,5 GiB, 1000204886016 bytes, 1953525168 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: gpt
Disk identifier: 7C7BD159-7A19-482A-A1B9-EDB6CBC6A809
Device Start End Sectors Size Type
/dev/sdc1 2048 1953525134 1953523087 931,5G Linux filesystem
Disk /dev/sdd: 149,1 GiB, 160041885696 bytes, 312581808 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: 0x6de3946e
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 2048 296136703 296134656 141,2G 83 Linux
/dev/sdd2 296138750 312580095 16441346 7,9G 5 Extended
/dev/sdd5 296138752 312580095 16441344 7,9G 82 Linux swap / Solaris
Disk /dev/md0: 3,7 TiB, 4000529252352 bytes, 7813533696 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Alles anzeigen
Any idea ??
Thanks