I thought at first that might be the case as well - but I did verify, and the drive is definitely detected before the script tries to read the password. No love there.
The version of the 'cryptroot' script that comes with edgy appears to be a bit different from the one in Etch - there is no 'modprobe -q dm_crypt' directive to load the dm_crypt module in that script, which is where you added the pause. I added the pause as well as the modprobe statement where I thought to be a logical place, and the drive is detected, but still no luck hoping for a chance to input the password. If the scripts are substantially different, there's probably not much you can do without having Edgy somewhere - I'm actually wondering if the 'cryptroot' script has been split into multiple scripts, but I haven't had a chance to look into it deeply. I'll hopefully get to poke at it today and get back to you if I find anything out. A copy of your final etch cryptroot script would be really useful if you could post it somewhere!
On a general note, I believe there are a couple of typos (or possibly this is just different with edgy) - instead of copying to /etc/initramfs, you need to copy scripts to /etc/initramfs-tools. As well, when you copy the cryptroot script, the source directory is /usr/share/initramfs-tools/scripts/local-top/ (scripts with an s). Other than that, everything else about the guide seems to be exactly right as far as I can recall (and as far as I've gotten it to work, though I feel like it's very close to working for me with edgy). I have to reiterate that it's very well done and much appreciated, this should be a supported install path IMO :)
Trying to make this work with Ubuntu Edgy...
I thought at first that might be the case as well - but I did verify, and the drive is definitely detected before the script tries to read the password. No love there.
The version of the 'cryptroot' script that comes with edgy appears to be a bit different from the one in Etch - there is no 'modprobe -q dm_crypt' directive to load the dm_crypt module in that script, which is where you added the pause. I added the pause as well as the modprobe statement where I thought to be a logical place, and the drive is detected, but still no luck hoping for a chance to input the password. If the scripts are substantially different, there's probably not much you can do without having Edgy somewhere - I'm actually wondering if the 'cryptroot' script has been split into multiple scripts, but I haven't had a chance to look into it deeply. I'll hopefully get to poke at it today and get back to you if I find anything out. A copy of your final etch cryptroot script would be really useful if you could post it somewhere!
On a general note, I believe there are a couple of typos (or possibly this is just different with edgy) - instead of copying to /etc/initramfs, you need to copy scripts to /etc/initramfs-tools. As well, when you copy the cryptroot script, the source directory is /usr/share/initramfs-tools/scripts/local-top/ (scripts with an s). Other than that, everything else about the guide seems to be exactly right as far as I can recall (and as far as I've gotten it to work, though I feel like it's very close to working for me with edgy). I have to reiterate that it's very well done and much appreciated, this should be a supported install path IMO :)