Posts by valentin

    So wiping sdc or sdb? In other words, there is no way to sync those two drives back to how they were? Im not sure i understand the point of raid 1 then ?( . If sdb is dependent on something on sdc, wouldnt that defeat the purpose of raid, in that i cannot restore it after a potential drive failure? Oh well, the data wasnt all that important any way, guess i will wipe and start from fresh. Thanks for the help!

    Ahh rookie mistake :/


    However, now im getting this:

    Code
    root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sdb /dev/sdc
    mdadm: looking for devices for /dev/md0
    mdadm: No super block found on /dev/sdc (Expected magic a92b4efc, got 00000000)
    mdadm: no RAID superblock on /dev/sdc
    mdadm: /dev/sdc has no superblock - assembly aborted

    Cool! Didnt know that. When i try that i get:

    Code
    root@openmediavault:~# mdadm --stop /dev/md0
    mdadm: stopped /dev/md0
    root@openmediavault:~# mdadm --assemble --force --verbose /dev/md0 /dev/sdb /dev/sdc/
    mdadm: looking for devices for /dev/md0
    mdadm: cannot open device /dev/sdc/: Not a directory
    mdadm: /dev/sdc/ has no superblock - assembly aborted


    sdc - "not a directory". Do i need to create a filesystem first on sdc or something? Also it seems the superblock is missing. I know that there is a --zero-superblock flag, however no entirely sure how to use it. Thanks for the help so far!

    After having removed and mounted a disk (sdc) on a different computer, my raid 1 array now does not appear in the web GUI under raid management when returned to my server.



    cat /proc/mdstat

    Code
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
    md0 : inactive sdb[0](S)
    2930135512 blocks super 1.2
    unused devices: <none>


    blkid

    Code
    /dev/sda1: UUID="b40a2842-935f-424f-be3c-8eff091e7a4b" TYPE="ext4" PARTUUID="326a2e34-01"
    /dev/sda5: UUID="31ed5f71-3b23-4db7-8d75-a7aefa980882" TYPE="swap" PARTUUID="326a2e34-05"
    /dev/sdb: UUID="9481f885-48b8-5b55-b930-b86b3e152e6c" UUID_SUB="1350e551-f6bc-41e3-f2c4-39f54de07cf5" LABEL="openmediavault:Raid1" TYPE="l inux_raid_member"
    /dev/sdd1: LABEL="1TBDrive" UUID="0163461d-12a9-47eb-91ea-f7e3f245aaeb" TYPE="ext4" PARTUUID="8e15da09-0f0e-4dda-8fe9-323cb7a9272a"


    fdisk -l | grep "Disk "


    Code
    Disk /dev/sda: 29.5 GiB, 31675383808 bytes, 61865984 sectors
    Disk identifier: 0x326a2e34
    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Disk /dev/sdd: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Disk identifier: A2B116B8-5357-45A5-9483-9C88D1D51CFD
    Disk /dev/sdc: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors


    cat /etc/mdadm/mdadm.conf



    mdadm --detail --scan --verbose


    Code
    INACTIVE-ARRAY /dev/md0 num-devices=1 metadata=1.2 name=openmediavault:Raid1 UUID=9481f885:48b85b55:b930b86b:3e152e6c
    devices=/dev/sdb


    As far as i can tell the device sdb still is listed as a raid member. However, in trying to rebuild the array (by adding sdc) gives the following error:

    Code
    root@openmediavault:~# mdadm --assemble /dev/md0 /dev/sdb /dev/sdc/
    mdadm: /dev/sdb is busy - skipping
    mdadm: cannot open device /dev/sdc/: Not a directory
    mdadm: /dev/sdc/ has no superblock - assembly aborted


    Keep in mind that im new to OMV and mdadm, just in case the above command is not how you are supposed to do it :P . Tried following tips found here, however to no avail. Any help is appreciated!