Beiträge von dopey_it

root@Cubotto:~# mdadm --stop /dev/md0
mdadm: Cannot get exclusive access to /dev/md0:Perhaps a running process, mounted filesystem or active volume group?

Thanks ryecoaaron - but i recive an error when i try to stop the raid

Hi i need help becouse my raid is degraded.
the raid was created by disks /dev/sdb and /dev/sdc/

Please help me becouse i can't restore with the funcion in omv. (3.0.99)

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mdadm --manage '/dev/md0' --add /dev/sdb 2>&1' with exit code '1': mdadm: add new device failed for /dev/sdb as 2: Invalid argument

Errore #0:
exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; mdadm --manage '/dev/md0' --add /dev/sdb 2>&1' with exit code '1': mdadm: add new device failed for /dev/sdb as 2: Invalid argument' in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/raidmgmt.inc(362): OMV\System\Process->execute()
#1 [internal function]: OMVRpcServiceRaidMgmt->add(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('add', Array, Array)
#4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('RaidMgmt', 'add', Array, Array, 1)
#5 {main}

This is the information.

root@Cubotto:~# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdc[1]
      1953383488 blocks super 1.2 [2/1] [_U]
      bitmap: 10/15 pages [40KB], 65536KB chunk
unused devices: <none>

root@Cubotto:~# blkid
/dev/sda1: UUID="b19de7a4-45cf-4bff-ae2a-032c0696f900" TYPE="ext4" PARTUUID="228bd653-01"
/dev/sda5: UUID="23e7a2ab-6e0d-476f-8382-6565bad9790f" TYPE="swap" PARTUUID="228bd653-05"
/dev/md0: LABEL="Dati" UUID="47b7050e-2199-4d82-8de9-4bafd91047d4" TYPE="ext4"
/dev/sdc: UUID="a388506b-8091-a6e4-93d0-4ad5f9e5cdae" UUID_SUB="ae433e0c-5c96-e4d4-e963-8d98c51c8f76" LABEL="Cubotto:Dati" TYPE="linux_raid_member"

root@Cubotto:~# fdisk -l | grep "Disk "
Disk /dev/sdb: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk /dev/sda: 55,9 GiB, 60022480896 bytes, 117231408 sectors
Disk identifier: 0x228bd653
Disk /dev/sdc: 1,8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk /dev/md0: 1,8 TiB, 2000264691712 bytes, 3906766976 sectors

root@Cubotto:~# cat /etc/mdadm/mdadm.conf
# 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/md0 metadata=1.2 name=Cubotto:Dati UUID=a388506b:8091a6e4:93d04ad5:f9e5cdae
# instruct the monitoring daemon where to send mail alerts

root@Cubotto:~# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=Cubotto:Dati UUID=a388506b:8091a6e4:93d04ad5:f9e5cdae
   devices=/dev/sdc