Cannot mound raid after reinstall

    Code
    /dev/sdb: UUID="47a5cb5d-c1aa-d89d-c08c-1e2e811e54c2" UUID_SUB="5d1476e4-9514-30db-54d4-8150df394bcb" LABEL="Serveur.lan:0" TYPE="linux_raid_member"
/dev/sda1: UUID="04ca02fe-0dff-494f-989d-dd6be1a2c45f" TYPE="ext4" PARTUUID="649c6604-01"
/dev/sda5: UUID="4b0360fe-eff6-4e78-aa11-846f8b97f368" TYPE="swap" PARTUUID="649c6604-05"
/dev/sdc: UUID="47a5cb5d-c1aa-d89d-c08c-1e2e811e54c2" UUID_SUB="2df20143-b81b-055d-9638-818daef7e303" LABEL="Serveur.lan:0" TYPE="linux_raid_member"
/dev/sdd: UUID="47a5cb5d-c1aa-d89d-c08c-1e2e811e54c2" UUID_SUB="38d4da11-9c19-870f-6af8-1a8f0e793013" LABEL="Serveur.lan:0" TYPE="linux_raid_member"
    • Offizieller Beitrag

    Even with the assume-clean flag, doing a mdadm --create on an existing array is very dangerous. I have seen it lose the filesystem in well over half that attempts. That is why i stopped recommending that people even try.

    omv 7.1.0-2 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.5 | scripts 7.0.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag
    Zitat von answer35

    So i guess I am good to format my RAID after all right

    The only reason I suggested doing a create, assume clean was that the existing array had no file system or could not locate one, that was obvious from the output of blkid in your first post. Other posts on the forum state that if blkid does not show the file system then OMV cannot detect them.


    If you just create a file system then there will be additional configuration, the better option is to start again, remove the raid, wipe the drives and recreate, I'm sorry but I think the damage was done when the outset. Whatever happened the file system must have become corrupted during the removal and re adding of the one drive.


    Personally I've stopped using it, I've moved to mergerfs and snapraid at least I can recover an accidentally deleted file and I can fix data errors, which I have been grateful for more than once. Another option I have is a large drive which runs rsync jobs to backup existing folders (I do that way, some backup a complete drive) this just adds additional piece of mind, photos and any other important data get synced to cloud storage.


    I'm sorry you're in this position but it might be worth reevaluating what you're doing, my server is small, but it houses 6 drives and just sits there, an errors come through via email, other than I check it once a week and do an OS backup once a month.

    Thank you for your time, anyway that's what I was thinking to do after all, I was asking in case there were a way to fix that because I am not so used to linux and everything so there is a lot I don't know. If there is nothing to do then it will only be the way I thought by do it fresh new again. At least maybe I will organize it better :p

    Thanks again :)

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden