On Feb 4, 2009, at 2:32 PM, martin f krafft wrote:
also sprach Will Glynn <w...@lerfjhax.com> [2009.02.04.2114 +0100]:
This appears to be at least as functional than the previous
version. I
can boot, anyway.
I haven't been able to test reshaping with actual disks -- although I
get two more from UPS either Friday or Monday, and will try another
reshape then. In the interim, I'm trying a reshape with loopback
devices; I'll let you know how that pans out.
Thanks!
Two more disks came. I added them to /dev/md0, my RAID 1 /boot, which
worked without incident. I then added them to /dev/md2, my RAID 6 LVM
volume, and initiated a reshape. Rebooting, I get:
[ 0.359819] dca service started, version 1.4
[ 0.408632] pci 0000:08:00.0: BAR 6: can't allocate mem resource
[0xd0000000-0xcfffffff]
[ 1.036337] ioatdma 0000:00:08.0: Intel(R) I/OAT DMA Engine found,
4 channels, device version 0x12, driver version 3.30
Loading, please wait...
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 00.90 unknown, ignored.
mdadm: no devices found for /dev/md0
mdadm: no devices found for /dev/md2
/dev/md0: File exists
mdadm: /dev/md/0 has been started with 8 drives.
Volume group "vg00" not found
Volume group "vg00" not found
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/mapper/vg00-root does not exist. Dropping to a shell!
BusyBox v1.10.2 (Debian 1:1.10.2-2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
I *can* assemble by hand:
(initramfs) mdadm --assemble /dev/md2 /dev/sd?2
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 00.90 unknown, ignored.
mdadm: /dev/md2 has been started with 8 drives.
(initramfs) lvm pvscan
PV /dev/md2 VG vg00 lvm2 [3.64 TB / 318.52 GB free]
Total: 1 [1.64 TB] / in use: 1 [1.64 TB] / in no VG: 0 [0 ]
(initramfs) lvm vgchange -a y vg00
11 logical volume(s) in volume group "vg00" now active
(initramfs) ^D
INIT: version 2.86 booting
...
/etc/mdadm/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 root
# definitions of existing MD arrays
# This file was auto-generated on Sat, 17 Jan 2009 13:00:11 -0600
# by mkconf $Id$
ARRAY /dev/md0 level=raid1 num-devices=6 metadata=00.90
UUID=cb13aea8:910535dd:b77cec8a:40dd9fa0
ARRAY /dev/md2 level=raid6 num-devices=6 metadata=00.90
UUID=0eceb6c2:f6d68bd9:e43a03b1:21cdca08
Current array list:
# mdadm --detail --scan
mdadm: metadata format 00.90 unknown, ignored.
mdadm: metadata format 00.90 unknown, ignored.
ARRAY /dev/md0 level=raid1 num-devices=8 metadata=00.90
UUID=cb13aea8:910535dd:b77cec8a:40dd9fa0
ARRAY /dev/md2 level=raid6 num-devices=8 metadata=00.91
UUID=0eceb6c2:f6d68bd9:e43a03b1:21cdca08
I'm set for INITRDSTART='all', AUTOSTART=true.
Not sure what to do about this; maybe I configured something wrong?
Can't think of what, though. At a minimum, this is still an
improvement over last release, because it's recoverable from the
console with the contents of the initrd.
--Will
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
