On 5/12/10 11:38 AM, Phillip Susi wrote:
[...]
> Huh? You have? I'm planning on fixing this in time for 10.04.1, but
> I've not had time to look at it yet. Based on the comments about the p
> being in the device name, I have a pretty good idea of where the problem
> is, so hopefully this weekend I'll have it fixed.
FYI after I muddled through the install a couple weekends ago by linking
or renaming stuff under /dev/mapper I ended up with a bootable system.
But the problem that persisted was grub-update (or whatever runs during
system updates) continued to try to write to /dev/sda which is one
element of my RAID5 group. I used the information from a post that
noted there was no /boot/device.map and created one on my system.
That resolved the last issue I was having. So apparently that file is
required for ongoing updates.
I also get screen fulls of messages about "you have a memory leak" but
you probably can't do anything about that.
On 5/12/10 11:38 AM, Phillip Susi wrote:
[...]
> Huh? You have? I'm planning on fixing this in time for 10.04.1, but
> I've not had time to look at it yet. Based on the comments about the p
> being in the device name, I have a pretty good idea of where the problem
> is, so hopefully this weekend I'll have it fixed.
FYI after I muddled through the install a couple weekends ago by linking
or renaming stuff under /dev/mapper I ended up with a bootable system.
But the problem that persisted was grub-update (or whatever runs during
system updates) continued to try to write to /dev/sda which is one
element of my RAID5 group. I used the information from a post that
noted there was no /boot/device.map and created one on my system.
That resolved the last issue I was having. So apparently that file is
required for ongoing updates.
I also get screen fulls of messages about "you have a memory leak" but
you probably can't do anything about that.