All of lore.kernel.org
 help / color / mirror / Atom feed
From: "L.M.J" <linuxmasterjedi@free.fr>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM issues after replacing linux mdadm RAID5 drive
Date: Thu, 17 Apr 2014 12:23:15 +0200	[thread overview]
Message-ID: <20140417122315.4c3687ea@netstation> (raw)

Hi,

  For the third time, I had to change a failed drive from my home linux RAID5
  box. Previous time went right and this time, I don't know what I did wrong,
  but I broke my RAID5. Well, at least, he won't start.
  /dev/sdb was the failed drive
  /dev/sdc and /dev/sdd are OK.
  
  I tried to reassamble the RAID with this command after I replace sdb and
  create a new partition :
  ~# mdadm -Cv /dev/md0 --assume-clean --level=5
  --raid-devices=3 /dev/sdc1 /dev/sdd1 /dev/sdb1

  Well, I gues I did a mistake here, I should have done this instead :
  ~# mdadm -Cv /dev/md0 --assume-clean --level=5
  --raid-devices=3 /dev/sdc1 /dev/sdd1 missing

  Maybe this wipe out my data...

  Let's go futher, then, pvdisplay, pvscan, vgdisplay returns empty
  information :-(

  Google helped me, and I did this :
  ~# dd if=/dev/md0 bs=512 count=255 skip=1 of=/tmp/md0.txt
   
	[..]
	physical_volumes {
		pv0 {
			id = "5DZit9-6o5V-a1vu-1D1q-fnc0-syEj-kVwAnW"
			device = "/dev/md0"
			status = ["ALLOCATABLE"]
			flags = []
			dev_size = 7814047360
			pe_start = 384
			pe_count = 953863
		}
	}
	logical_volumes {

		lvdata {
			id = "JiwAjc-qkvI-58Ru-RO8n-r63Z-ll3E-SJazO7"
			status = ["READ", "WRITE", "VISIBLE"]
			flags = []
			segment_count = 1
	[..]



  Since I saw lvm information, I guess I haven't lost all information yet...

  I tried an unhoped command :
  ~# pvcreate --uuid "5DZit9-6o5V-a1vu-1D1q-fnc0-syEj-kVwAnW" --restorefile /etc/lvm/archive/lvm-raid_00302.vg /dev/md0

  Then,
  ~# vgcfgrestore lvm-raid

  ~# lvs -a -o +devices
  LV     VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert  Devices 
  lvdata lvm-raid -wi-a- 450,00g                                       /dev/md0(148480)
  lvmp   lvm-raid -wi-a-  80,00g                                       /dev/md0(263680)

  Then :
  ~# lvchange -ay /dev/lvm-raid/lv*

  I was quite happy until now.
  Problem appears now when I try to mount those 2 LV (lvdata & lvmp) as ext4 partition :
  ~# mount /home/foo/RAID_mp/

  ~# mount | grep -i mp
     /dev/mapper/lvm--raid-lvmp on /home/foo/RAID_mp type ext4 (rw)

  ~# df -h /home/foo/RAID_mp
     Filesystem                  Size  Used Avail Use% Mounted on
     /dev/mapper/lvm--raid-lvmp   79G   61G   19G  77% /home/foo/RAID_mp


  Here is the big problem 
  ~# ls -la /home/foo/RAID_mp
     total 0

  Worst on the other LVM :
  ~# mount /home/foo/RAID_data 
     mount: wrong fs type, bad option, bad superblock on /dev/mapper/lvm--raid-lvdata,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so


  I bet I recover the LVM structure but the data are wiped out, don't you think ?

  ~# fsck -n -v /dev/mapper/lvm--raid-lvdata
     fsck from util-linux-ng 2.17.2
     e2fsck 1.41.11 (14-Mar-2010)
     fsck.ext4: Group descriptors look bad... trying backup blocks...
     fsck.ext4: Bad magic number in super-block when using the backup blocks
     fsck.ext4: going back to original superblock
     fsck.ext4: Device or resource busy while trying to open /dev/mapper/lvm--raid-lvdata
     Filesystem mounted or opened exclusively by another program?


   
  Any help is welcome if you have any idea how to rescue me pleassse !

 

  
 
-- 
 LMJ
 "May the source be with you my young padawan"

             reply	other threads:[~2014-04-17 10:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 10:23 L.M.J [this message]
2014-04-17 19:33 ` [linux-lvm] LVM issues after replacing linux mdadm RAID5 drive Stuart Gathman
2014-04-18 21:14   ` L.M.J
2014-04-26 18:47     ` L.M.J
2014-04-30 20:57       ` L. M. J
2014-05-02  4:02       ` Stuart Gathman
2014-05-04  7:57         ` L.M.J

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=20140417122315.4c3687ea@netstation \
    --to=linuxmasterjedi@free.fr \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.