Package: grub-pc Severity: normal
Same here on a clean install of an amd64 system with md0 as /boot and md1 encrypted with lvm on a 4 year old system that ran Lenny without problems. Only difference is that I have replaced the two disks with 4kB sector Western Digital ones as the old ones wore away. Partitioning was a pain. I wanted to delete and rename two vgs which I could do in the graphical installer. But then the renamed vgs did not show up when I tried to create lvs. Then I went to a console and managed to do the rest of the partitioning with lvcreate. For formatting and labeling and the mount points I went back to the graphical installer. Later I learned that md0 for /boot had problems (see below) but I am sure I did assign /boot as a mount point and ext3 as filesystem. Perhaps the interruption with manual lv creation made the installer forget? Installing grub-pc failed and the manual install was difficult. This was because /dev/md0 was initially not mounted as /target/boot/ and received no blkid. /target/boot/ did exist and got filled as expected. I fixed all this and was then able to install grub, however it complained about not finding partition info upon execution of "update-grub" but "grub-install /dev/sda" and sdb went well, also with --rechecking. Then I tried to boot, GRUB came up, the mds were started, and /sys/devices/virtual/block/md0 (numbers in the high 5000s here) scrolled by for all 3 arrays. The passphrase was entered and the machine just remained stuck with the single server case hdd activity light on all the time, both with a regular boot and a rescue mode boot, so I never got past the passphrase promt. My 2ct. --AvH -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
