linux-kernel - Re: RAID array is gone, please help

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170323210908.GQ14186@csclub.uwaterloo.ca>
Date:   Thu, 23 Mar 2017 17:09:08 -0400
From:   lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:     Stephen Mueller <stephen@...ller.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: RAID array is gone, please help

On Thu, Mar 23, 2017 at 10:02:23PM +0100, Stephen Mueller wrote:
> Looks like it worked! Thanks!

Well at least you could backup the data, just in case.

> I used:
> 
> sudo mdadm --create /dev/md0 --assume-clean --verbose --level-10
> --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf

I wonder about the assume-clean, but I would think any data you wrote
will have been duplicated at the time you wrote it, and only unused
space might not have been synced yet.

Maybe running a forced resync would be worthwhile.

> And I got my instructions for creating the array here, and they
> also don't use partitions...
> 
> https://www.digitalocean.com/community/tutorials/how-to-create-raid-arrays-with-mdadm-on-ubuntu-16-04

Well it works, as long as you don't leave anything around to confuse it,
in this case a GPT partition table that somehow came back to bite you.

I wonder if mdadm could perhaps warn about the existing partition table
when being asked to create a new device.

Does it survive reboots now?

-- 
Len Sorensen