raid error after aptitude upgrade
hi all,
i'm having a problem with my raid after i did an aptitude upgrade.
my setup is the following: debian sid, kernel 2.6.10-1-k7, 2 ide
drives building a raid1. these hold 3 partitions, the first is /boot
(/dev/md0, ext2). the second is a lvm2 volume group (/dev/md1,
called vgsys) including everything that's system related in several
logical volumes except /home. the third is a lvm2 group too
(/dev/md2, vguser), which holds /home and /data in separate
logical volumes. all logical volumes are of type reiserfs. i set up
raid and lvm with the debian installer. initially this was kernel 2.4.*
with lvm1, but all upgrades were done with aptitude.
now to the last upgrade. what i realized was, that among many other
packages, lvm2, mdadm and my kernel were to be upgraded.
hum, the kernel upgrade version was the same that i was already
using, so i thought i should just let aptitude finish its' job.
now, when i reboot, md0 and md2 won't be detected.
here is an excerpt from syslog:
Mar 28 19:26:36 flyricky syslogd 1.4.1#16: restart.
Mar 28 19:26:36 flyricky kernel: klogd 1.4.1#16, log source =
/proc/kmsg started.
Mar 28 19:26:36 flyricky kernel: Cannot find map file.
Mar 28 19:26:36 flyricky kernel: No module symbols loaded - kernel
modules not enabled.
Mar 28 19:26:36 flyricky kernel: valid argument.<4>devfs_mk_dev: could
not append to parent for /disc
Mar 28 19:26:36 flyricky kernel: devfs_mk_dir: invalid
argument.<4>devfs_mk_dev: could not append to parent for /disc
Mar 28 19:26:36 flyricky last message repeated 115 times
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: using ordered data mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: journal params: device
dm-0, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: checking transaction
log (dm-0)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-0: switching to journaled
data mode
Mar 28 19:26:36 flyricky kernel: hdd: ATAPI 48X DVD-ROM drive, 512kB
Cache, UDMA(33)
Mar 28 19:26:36 flyricky kernel: Uniform CD-ROM driver Revision: 3.20
Mar 28 19:26:36 flyricky kernel: Capability LSM initialized
Mar 28 19:26:36 flyricky kernel: md: md2 stopped.
Mar 28 19:26:36 flyricky kernel: md: md0 stopped.
Mar 28 19:26:36 flyricky kernel: EXT2-fs: unable to read superblock
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-6: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-6: using journaled data
mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-6: journal params: device
dm-6, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-6: checking transaction
log (dm-6)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-6: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-5: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-5: using journaled data
mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-5: journal params: device
dm-5, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-5: checking transaction
log (dm-5)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-5: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-2: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-2: using ordered data mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-2: journal params: device
dm-2, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-2: checking transaction
log (dm-2)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-2: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-4: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-4: using journaled data
mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-4: journal params: device
dm-4, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-4: checking transaction
log (dm-4)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-4: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-3: found reiserfs format
"3.6" with standard journal
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-3: using journaled data
mode
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-3: journal params: device
dm-3, size 8192, journal first block 18, max trans len 1024, max batch
900, max commit age 30, max trans age 30
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-3: checking transaction
log (dm-3)
Mar 28 19:26:36 flyricky kernel: ReiserFS: dm-3: Using r5 hash to sort
names
Mar 28 19:26:36 flyricky kernel: Adding 1572856k swap on
/dev/mapper/vgsys-swap. Priority:-1 extents:1
Mar 28 19:26:36 flyricky kernel: irda_init()
/proc/mdstat shows that md1 is active, but md0 and md2 don't get
listed there (it just says: unused devices: <none>). so my /boot
directory is empty when the system is up and running.
when the system is up (i continued the boot process
with control-d) i'm able to activate md0 manually and mount it on /boot.
md2 isn't running too, but the lvm2 volumes were mounted.
here is some mdadm info on the devices (with md0 mounted manually!):
# mdadm -Q /dev/md0
/dev/md0: 94.00MiB raid1 2 devices, 0 spares. Use mdadm --detail for
more detail.
/dev/md0: No md super block found, not an md component.
# mdadm -Q /dev/hda1
/dev/hda1: is not an md array
/dev/hda1: device 0 in 2 device active raid1 md0. Use mdadm --examine
for more detail.
# mdadm -Q /dev/hdc1
/dev/hdc1: is not an md array
/dev/hdc1: device 1 in 2 device active raid1 md0. Use mdadm --examine
for more detail.
# mdadm -Q /dev/md1
/dev/md1: 18.63GiB raid1 2 devices, 0 spares. Use mdadm --detail for
more detail.
/dev/md1: No md super block found, not an md component.
# mdadm -Q /dev/hda2
/dev/hda2: is not an md array
/dev/hda2: device 0 in 2 device active raid1 md1. Use mdadm --examine
for more detail.
# mdadm -Q /dev/hdc2
/dev/hdc2: is not an md array
/dev/hdc2: device 1 in 2 device active raid1 md1. Use mdadm --examine
for more detail.
# mdadm -Q /dev/md2
/dev/md2: is an md device which is not active
/dev/md2: is too small to be an md component.
# mdadm -Q /dev/hda3
/dev/hda3: is not an md array
/dev/hda3: device 0 in 2 device undetected raid1 md2. Use mdadm
--examine for more detail.
# mdadm -Q /dev/hdc3
/dev/hdc3: is not an md array
/dev/hdc3: device 1 in 2 device undetected raid1 md2. Use mdadm
--examine for more detail.
one also interesting line is shown by vgdisplay (this should be md2):
Found duplicate PV vcQfBIVn2WpEmvf4o5Bt1BMGbMPkYpgj: using /dev/hdc3
not /dev/hda3
this is the content of /etc/mdadm/mdadm.conf:
DEVICE partitions
ARRAY /dev/md2 level=raid1 num-devices=2
UUID=107466fc:2372209c:ac137ae9:ce2e24aa
devices=/dev/hda3,/dev/hdc3
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=1ea1855e:ef695c5a:1dd6abfd:6dc252a0
devices=/dev/hda2,/dev/hdc2
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=5891fe7d:9e2cd9f6:3f4afcf5:1aff0f94
devices=/dev/hda1,/dev/hdc1
this is the content of /etc/modules:
ide-cd
ide-detect
i'm not sure, but till now i thought this has something to do with a
new ramdisk created by this
senseless kernel upgrade. i'm still not that much of a linux user that
i don't have to read a lot.
well, searching mailing lists didn't answer this problem so far. i
found some slightly related
stuff, but the cases or answers didn't help.
someone can tell me what the problem is and what i should do ... and
perhaps a little bit of how?
"iamstuck" oliver
Reply to: