LVM and Raid... Volume keeps dropping...

Genesys · 04-24-2013, 08:33 PM

I'm not really sure how to start this question other than.... why does my LV group keep dropping?

A little background on the situation...

I have a NAS running Debian (Lenny). It has two 1TB drives configured for Raid 0. It had been running perfectly for weeks, but now for some reason, my main storage LV (i.e. the one with all of my data) keeps dropping.

So... a little data:

Quote:

NAS:~# vgdisplay -v vg0
Using volume group(s) on command line
Finding volume group "vg0"
--- Volume group ---
VG Name vg0
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.81 TB
PE Size 4.00 MB
Total PE 475564
Alloc PE / Size 475564 / 1.81 TB
Free PE / Size 0 / 0
VG UUID BGlHD2-tm1d-VItN-8NA8-pBch-D2zd-83oR0b

--- Logical volume ---
LV Name /dev/vg0/lv0
VG Name vg0
LV UUID J9t0QV-bGov-Fvsr-Fvtv-S2B0-RiGx-wl8lBY
LV Write Access read/write
LV Status available
# open 1
LV Size 1.81 TB
Current LE 475564
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Physical volumes ---
PV Name /dev/md3
PV UUID f48Xwm-3ecz-2cmQ-1Fym-1kw1-DEiE-jfnyhH
PV Status allocatable
Total PE / Free PE 475564 / 0

So, I'm hoping that someone will be able to help me track down the error[s]...

Edit: more data...

Quote:

NAS:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md3 : active raid0 sda4[0] sdb4[1]
1947912064 blocks super 1.2 64k chunks

md1 : active raid1 sdb2[1] sda2[0]
1044800 blocks [2/2] [UU]

md2 : active raid1 sdb3[1] sda3[0]
521408 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
1043840 blocks [2/2] [UU]

unused devices: <none>

smallpond · 04-24-2013, 10:01 PM

Check /var/log/messages for md or disk errors.

Genesys · 04-25-2013, 03:46 PM

I was going through /var/log/messages and looking for something that would stand out... but I didn't see anything. I'll probably keep looking tonight after I get home...

Although, I was wondering... In addition to looking for disk errors... would there be any messages regarding system reboots?

Genesys · 04-27-2013, 08:59 AM

So, I looked in /var/log/messages and I don't see anything that stands out...

Quote:

NAS:/var/log# cat messages | grep md3
Apr 25 02:50:37 NAS kernel: md: md3 stopped.
Apr 25 02:50:37 NAS kernel: md3: setting max_sectors to 128, segment boundary to 32767

Just for S&Gs, here's a copy of my fstab... I'm definitely not an exert on such things... but it looks ok to me:

Quote:

NAS:/# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/md0 / ext3 errors=remount-ro 0 1
/dev/md1 none swap sw 0 0
/dev/md2 /mnt/md2 ext3 defaults 0 2

#/dev/mapper/vg0-lv0 /mnt/vg0-lv0 ext3 defaults 0 2

/dev/vg0/lv0 /media/Data ext3 defaults 0 0

Genesys · 04-27-2013, 11:43 AM

Just checked my mdadm.conf, and to my surprise, it seemed like it was incomplete...

Original;

Quote:

NAS:/etc/mdadm# cat mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR blah

# definitions of existing MD arrays

# This file was auto-generated on Sat, 18 Dec 2010 10:26:52 +0100
# by mkconf $Id$

Modified:

Quote:

NAS:/etc/mdadm# cat mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR blah

# definitions of existing MD arrays

# This file was auto-generated on Sat, 18 Dec 2010 10:26:52 +0100
# by mkconf $Id$
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=b07083e0:2d78a9c5:d33c2718:aa7ffeb2
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=c0f83d5e:284d2995:0eaac66e:5b712a01
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=55edfb9f:fdde3c2c:842050b0:081237cd
ARRAY /dev/md/3 level=raid0 metadata=1.2 num-devices=2 UUID=f10c6406:a53b8d28:3141e2db:f3386637 name=3