On 2010-09-17 14:17, Alexander Kurtz wrote:
IMHO your problem
can be divided into three parts. Let's discuss them separately:
Hello Alexander, thanks. Here goes:
1. Just for the record:
ii cryptsetup 2:1.1.3-3
ii lvm2 2.02.66-3
ii mdadm 3.1.4-1+8efb9d1
cryptsetup: WARNING: invalid line in /etc/crypttab -
- snip -
+ ls -l /dev/mapper
+ mount
+ cat /etc/fstab
+ cat /etc/crypttab
appended
* temporarily change line 185 of /usr/share/initramfs-tools/hooks/cryptroot
- snip -
* run update-initramfs -u with the modified hook and send me the
# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64
... and nothing else as output.
3. I don't know much about LVM. I tend to think that the
identical UUIDs might actually be correct - but I may be wrong here.
my guess as well, but see below (comparison md1 vs. md2)
> short overview over your block devices and how the work together
> Please include everything from the physical disks, physical and
> logical partitions, RAID, LVM, CRYPTO up to the FS level. Please
> also include the UUIDs in this.
sorry no real drawing but this may be clear enough, hopefully:
/dev/sda and /dev/sdb
Model=WDC WD2500BUDT-63DPZY0, FwRev=01.01A01, SerialNo=WD-WX71A4048816
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=488397168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=yes: unknown setting WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
RAID level is RAID1 with no spares
__________________________________________________________________
sd[ab]1 fd Linux raid autodetect a5636b29-510b-03b4-e4e0-47e18fd572e4
-> md0 64ec582b-89ef-4007-b745-eeb893ff1709
-> /boot ext3
__________________________________________________________________
sda2 83 Linux 7d68a33b-ac46-479c-bb55-bf64ba8743e1
-> complete unmirrored rescue system on one partition, ext3
sdb2 unused
__________________________________________________________________
sd[ab]3 5 Extended no UUID
->sd[ab]5 fd Linux raid autodetect 0c2a2312-4158-bc26-5db2-5327c0571f18
-> md1 crypto_LUKS 3a10eb55-2dd8-4846-97e5-74649abf234f
-> md1_crypt LVM2_member c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o
-> /dev/mapper/vg-md1dm0 LVM2 c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o
therein the following logical volumes (the last part of the name
denotes the mount point), all of them but swap are formatted ext4:
/dev/mapper/vg--md1dm0-slash 5a990fe7-3375-4f3c-9159-f1b002e01359
/dev/mapper/vg--md1dm0-swap 87925ea7-7d04-46a5-aab9-e345e0d75110
/dev/mapper/vg--md1dm0-tmp 9175fa39-35e2-4ac4-90b0-ec8ead38c12e
/dev/mapper/vg--md1dm0-usr 1497ba9e-9e17-492e-b80d-e437d889179e
/dev/mapper/vg--md1dm0-var 9a4682c0-2967-4e97-a5ee-b21aa7eec3a4
/dev/mapper/vg--md1dm0-vlog 3ea78632-f8c8-45e0-b715-44b0b4817920
/dev/mapper/vg--md1dm0-vtmp eab4632b-82fc-4f7f-bfbd-4e7f471643f9
/dev/mapper/vg--md1dm0-vcache 93e1c3c2-adf3-42c8-b3e7-706a670c57e9
/dev/mapper/vg--md1dm0-srv d4280e6c-eb59-4bbe-9407-727a11e481c5
/dev/mapper/vg--md1dm0-svmware b479f563-4312-41b1-99f2-ed382fa6bca2
->sd[ab]6 fd Linux raid autodetect 406130f5-3896-aac5-49a9-3ce2d277b5fc
-> md2 crypto_LUKS e78a6bea-cafb-41a7-89e9-03e999b38d6c
-> md2_crypt LVM2_member etVfXJ-7VYM-XcmT-ltfp-WDsW-TICB-UaX9E2
therein the following logical volumes:
/dev/mapper/vg--md2dm1-bk1 c480b9af-4c7b-4b41-ac67-6575b12ab92c
/dev/mapper/vg--md2dm1-bk2 021e8b70-6189-40dd-830d-83b43cc44fd7
__________________________________________________________________
sd[ab]4 0 Empty
__________________________________________________________________
sda7 82 Linux swap / Solaris 867019f4-b83a-4a69-a67a-66c12242c174
-> swap for rescue system
__________________________________________________________________
Note: The UUID of md1_crypt, vg-md1dm0, and md2_crypt are two chars
longer than all the other ones. Should be ok though as manual opening of
the devices works.
On md1_crypt there is a generic vg /dev/mapper/vg-md1dm0 with a
duplicate uuid and the mounted logical volumes. Is this an artifact from
manually starting the vg? For md2_crypt this is not the case - only the
mounted logical volumes are there.
The disks are new Western Digital 2.5" disks for 24/7 operation with 4kB
sectors, they are working well but the boundaries are a bit messy.
Partitioning was done within d-i.
# fdisk -l -c /dev/sda
Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000d5580
Device Boot Start End Blocks Id System
/dev/sda1 1 25 195584 fd Linux raid
autodetect
/dev/sda2 25 256 1859584 83 Linux
/dev/sda3 257 30298 241303553 5 Extended
Partition 3 does not start on physical sector boundary.
/dev/sda5 268 4523 34179072 fd Linux raid
autodetect
/dev/sda6 4523 30298 207030272 fd Linux raid
autodetect
/dev/sda7 257 268 93184 82 Linux swap / Solaris
Partition table entries are not in disk order
Finally the complete output of `blkid' would be great.
Please see below.
ADDENDUM: Alexander, while writing this mail your mail of 2010-09-17
19:54 CEST with the repair instructions reached me. They did not help in
my case. I did the following:
Booted into my rescue system on sda2, updated mdadm, rebooted into
rescue system, opened the crypto devices and mounted everything relevant
in /mnt/chroot. Chrooted there, created new initramfs and did an
update-grub. Had problems starting due to two grub installations in MBR
and sda2, fixed this with using the following lines in
/etc/grub.d/40_custom in the rescue system (need to fix this duplicity
some other time):
menuentry 'Debian GNU/Linux, default - Linux 2.6.32-5-amd64' --class
debian --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_msdos
insmod part_msdos
insmod ext2
set root='(md/0)'
search --no-floppy --fs-uuid --set
64ec582b-89ef-4007-b745-eeb893ff1709
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /vmlinuz-2.6.32-5-amd64
root=/dev/mapper/vg--md1dm0-slash ro quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-5-amd64
}
the initramfs came up but I got
ALERT! /dev/mapper/vg--md1dm0-slash does not exist
and ls -l /dev/dm* was empty,
ls -l /dev/mapper showed only /dev/mapper/control
The I proceeded manually as I did in the past week, got my duplicate
uuid warning again (md1_crypt and vg-md1dm0), and the system was up.
I have to add that I created the intiramdisk with line 185 of
/usr/share/initramfs-tools/hooks/cryptroot changed in the
way you had suggested. Never did I see any message that the changed line
185 could have sent.
Best regards,
Andreas v. Heydwolff
--
:~# ls -l /dev/mapper
insgesamt 0
crw------- 1 root root 10, 59 14. Sep 20:59 control
lrwxrwxrwx 1 root root 8 14. Sep 20:59 md1_crypt -> ../dm-11
lrwxrwxrwx 1 root root 8 14. Sep 20:59 md2_crypt -> ../dm-12
lrwxrwxrwx 1 root root 7 14. Sep 20:53 vg-md1dm0 -> ../dm-0
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-slash -> ../dm-1
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-srv -> ../dm-9
lrwxrwxrwx 1 root root 8 14. Sep 20:54 vg--md1dm0-svmware -> ../dm-10
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-swap -> ../dm-2
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-tmp -> ../dm-3
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-usr -> ../dm-4
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-var -> ../dm-5
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-vcache -> ../dm-8
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-vlog -> ../dm-6
lrwxrwxrwx 1 root root 7 14. Sep 20:54 vg--md1dm0-vtmp -> ../dm-7
lrwxrwxrwx 1 root root 8 14. Sep 20:59 vg--md2dm1-bk1 -> ../dm-13
lrwxrwxrwx 1 root root 8 14. Sep 20:59 vg--md2dm1-bk2 -> ../dm-14
~# mount
/dev/mapper/vg--md1dm0-slash on / type ext4 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/md0 on /boot type ext3 (rw)
/dev/mapper/vg--md2dm1-bk1 on /home/bk1 type ext4 (rw)
/dev/mapper/vg--md2dm1-bk2 on /home/bk2 type xfs (rw)
/dev/mapper/vg--md1dm0-srv on /srv type ext4 (rw)
/dev/mapper/vg--md1dm0-svmware on /srv/vmware type ext4 (rw)
/dev/mapper/vg--md1dm0-tmp on /tmp type ext4 (rw)
/dev/mapper/vg--md1dm0-usr on /usr type ext4 (rw)
/dev/mapper/vg--md1dm0-var on /var type ext4 (rw)
/dev/mapper/vg--md1dm0-vcache on /var/cache type ext4 (rw)
/dev/mapper/vg--md1dm0-vlog on /var/log type ext4 (rw)
/dev/mapper/vg--md1dm0-vtmp on /var/tmp type ext4 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/sda2 on /mnt/sda2 type ext3 (rw)
~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'vol_id --uuid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/vg--md1dm0-slash / ext4 errors=remount-ro 0
1
UUID=64ec582b-89ef-4007-b745-eeb893ff1709 /boot ext3 defaults 0 2
/dev/mapper/vg--md2dm1-bk1 /home/bk1 ext4 defaults 0 2
/dev/mapper/vg--md2dm1-bk2 /home/bk2 xfs defaults 0 2
/dev/mapper/vg--md1dm0-srv /srv ext4 defaults 0 2
/dev/mapper/vg--md1dm0-svmware /srv/vmware ext4 defaults 0
2
/dev/mapper/vg--md1dm0-tmp /tmp ext4 defaults 0 2
/dev/mapper/vg--md1dm0-usr /usr ext4 defaults 0 2
/dev/mapper/vg--md1dm0-var /var ext4 defaults 0 2
/dev/mapper/vg--md1dm0-vcache /var/cache ext4 defaults 0
2
/dev/mapper/vg--md1dm0-vlog /var/log ext4 defaults 0
2
/dev/mapper/vg--md1dm0-vtmp /var/tmp ext4 defaults 0
2
/dev/mapper/vg--md1dm0-swap none swap sw 0
0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
~# cat /etc/crypttab
#md1_crypt UUID=3a10eb55-2dd8-4846-97e5-74649abf234f none luks
#md2_crypt UUID=e78a6bea-cafb-41a7-89e9-03e999b38d6c none luks
#md1_crypt /dev/md/1 none luks
#md2_crypt /dev/md/2 none luks
#md1_crypt /dev/md1 none luks
#md2_crypt /dev/md2 none luks
md1_crypt /dev/disk/by-uuid/3a10eb55-2dd8-4846-97e5-74649abf234f none luks
md2_crypt /dev/disk/by-uuid/e78a6bea-cafb-41a7-89e9-03e999b38d6c none luks
~# blkid
/dev/sda1: UUID="a5636b29-510b-03b4-e4e0-47e18fd572e4" LABEL="kiefer:0"
TYPE="linux_raid_member"
/dev/sda5: UUID="0c2a2312-4158-bc26-5db2-5327c0571f18" LABEL="kiefer:1"
TYPE="linux_raid_member"
/dev/sda6: UUID="406130f5-3896-aac5-49a9-3ce2d277b5fc" LABEL="kiefer:2"
TYPE="linux_raid_member"
/dev/sdb1: UUID="a5636b29-510b-03b4-e4e0-47e18fd572e4" LABEL="kiefer:0"
TYPE="linux_raid_member"
/dev/sdb5: UUID="0c2a2312-4158-bc26-5db2-5327c0571f18" LABEL="kiefer:1"
TYPE="linux_raid_member"
/dev/sdb6: UUID="406130f5-3896-aac5-49a9-3ce2d277b5fc" LABEL="kiefer:2"
TYPE="linux_raid_member"
/dev/md1: UUID="3a10eb55-2dd8-4846-97e5-74649abf234f" TYPE="crypto_LUKS"
/dev/md2: UUID="e78a6bea-cafb-41a7-89e9-03e999b38d6c" TYPE="crypto_LUKS"
/dev/mapper/md1_crypt: UUID="c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o"
TYPE="LVM2_member"
/dev/mapper/md2_crypt: UUID="etVfXJ-7VYM-XcmT-ltfp-WDsW-TICB-UaX9E2"
TYPE="LVM2_member"
/dev/mapper/vg--md1dm0-slash: LABEL="slash"
UUID="5a990fe7-3375-4f3c-9159-f1b002e01359" TYPE="ext4"
/dev/mapper/vg--md1dm0-swap: UUID="87925ea7-7d04-46a5-aab9-e345e0d75110"
TYPE="swap"
/dev/mapper/vg--md1dm0-tmp: LABEL="tmp"
UUID="9175fa39-35e2-4ac4-90b0-ec8ead38c12e" TYPE="ext4"
/dev/mapper/vg--md1dm0-usr: LABEL="usr"
UUID="1497ba9e-9e17-492e-b80d-e437d889179e" TYPE="ext4"
/dev/mapper/vg--md1dm0-var: LABEL="var"
UUID="9a4682c0-2967-4e97-a5ee-b21aa7eec3a4" TYPE="ext4"
/dev/mapper/vg--md1dm0-vlog: LABEL="vlog"
UUID="3ea78632-f8c8-45e0-b715-44b0b4817920" TYPE="ext4"
/dev/mapper/vg--md1dm0-vtmp: LABEL="vtmp"
UUID="eab4632b-82fc-4f7f-bfbd-4e7f471643f9" TYPE="ext4"
/dev/mapper/vg--md1dm0-vcache: LABEL="vcache"
UUID="93e1c3c2-adf3-42c8-b3e7-706a670c57e9" TYPE="ext4"
/dev/mapper/vg--md1dm0-srv: LABEL="srv"
UUID="d4280e6c-eb59-4bbe-9407-727a11e481c5" TYPE="ext4"
/dev/mapper/vg--md1dm0-svmware: LABEL="svmware"
UUID="b479f563-4312-41b1-99f2-ed382fa6bca2" TYPE="ext4"
/dev/mapper/vg--md2dm1-bk1: LABEL="bk1"
UUID="c480b9af-4c7b-4b41-ac67-6575b12ab92c" TYPE="ext4"
/dev/mapper/vg--md2dm1-bk2: LABEL="bk2"
UUID="021e8b70-6189-40dd-830d-83b43cc44fd7" TYPE="xfs"
/dev/md0: UUID="64ec582b-89ef-4007-b745-eeb893ff1709" TYPE="ext3"
/dev/sda2: UUID="7d68a33b-ac46-479c-bb55-bf64ba8743e1" SEC_TYPE="ext2"
TYPE="ext3"
/dev/sda7: UUID="867019f4-b83a-4a69-a67a-66c12242c174" TYPE="swap"
/dev/mapper/vg-md1dm0: UUID="c1Evvw-vx3Z-fBwD-WRyh-hI0n-Y864-wtPZ3o"
TYPE="LVM2_member"
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
