From: NeilBrown <neilb@suse.com>
To: Joseba Ibarra <wajalotnet@gmail.com>,
list linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Can't mount /dev/md0 Raid5
Date: Thu, 28 Sep 2017 08:38:59 +1000 [thread overview]
Message-ID: <87tvzn6a2k.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <59C4D44A.7080302@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1315 bytes --]
On Fri, Sep 22 2017, Joseba Ibarra wrote:
> Hi.I have a RAID5 using 4 drives in a HO Proliant G8 Microserver
>
> I got a Proxmox installed and the disks for RAID are associated with a
> specific VM with Debian 9. It worked like a charm.
>
> But, some days ago i broke a proccess giving some permissions (sudo
> chmod....) to some folders into of the mounted /dev/md0. Then after
> restart the VM the RAID din't mount again. The raid contents very
> important data for me, so i'm not very sure what to do in order don't
> lose the data. So, i´m getting bit panic.
>
> I need some guide to rebuild the system without losing the content.
Thanks for providing lots of useful data.
>
> root@grafico:/# cat /proc/mdstat
> Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0]
> [raid1] [raid10]
> md0 : active (auto-read-only) raid5 sdb1[0] sde1[3] sdc1[1] sdd1[2]
> 2929889280 blocks super 1.2 level 5, 512k chunk, algorithm 2
> [4/4] [UUUU]
> bitmap: 0/8 pages [0KB], 65536KB chunk
It appears that md0 has been successfully assembled. What does it
contain? What do you expect it to contain? ext4? xfs? btrfs? LVM volume
??
What does "pvscan" show?
What does "fsck -n /dev/md0" show?
What happens when you "mount /dev/md0 /mnt" ?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-09-27 22:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 9:13 Can't mount /dev/md0 Raid5 Joseba Ibarra
2017-09-27 22:38 ` NeilBrown [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-11 10:25 Joseba Ibarra
2017-10-11 10:42 ` Rudy Zijlstra
2017-10-11 11:14 ` Joseba Ibarra
2017-10-11 11:29 ` Adam Goryachev
2017-10-11 11:56 ` Joseba Ibarra
2017-10-11 13:23 ` Adam Goryachev
2017-10-11 13:35 ` Joseba Ibarra
2017-10-11 19:13 ` Adam Goryachev
2017-10-11 19:46 ` Joseba Ibarra
2017-10-11 14:01 ` Mikael Abrahamsson
2017-10-11 17:27 ` Joseba Ibarra
2017-10-11 20:46 ` NeilBrown
[not found] ` <59DE891F.1@gmail.com>
[not found] ` <878tghwf6j.fsf@notabene.neil.brown.name>
[not found] ` <59DE9313.50509@gmail.com>
2017-10-11 21:55 ` Joseba Ibarra
2017-10-11 19:49 ` John Stoffel
2017-10-11 20:57 ` Joseba Ibarra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvzn6a2k.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=wajalotnet@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).