Re: Etch with encrypted lvm, remapping of sata hd names, problem
"Thomas Anderson" <andersonthomas@gmail.com> wrote in message
[🔎] ac916430704190449o5e8fab8aj66316dc4e40bd4b8@mail.gmail.com">news:[🔎] ac916430704190449o5e8fab8aj66316dc4e40bd4b8@mail.gmail.com...
>I tried to replace this:
>
> title Debian GNU/Linux, kernel 2.6.18-4-k7
> root (hd0,0)
> kernel /vmlinuz-2.6.18-4-k7 root=/dev/mapper/tommy--d4-root ro
> initrd /initrd.img-2.6.18-4-k7
> savedefault
>
> with this:
>
> title Debian GNU/Linux, kernel 2.6.18-4-k7
> root (hd0,0)
> kernel /vmlinuz-2.6.18-4-k7
> root=/dev/disk/by-uuid/some-letters-in-hexa-decimal ro
> initrd /initrd.img-2.6.18-4-k7
> savedefault
>
> That didn't work. So I tried:
>
> title Debian GNU/Linux, kernel 2.6.18-4-k7
> root (hd0,0)
> kernel /vmlinuz-2.6.18-4-k7 root=/dev/hdb1 ro
> initrd /initrd.img-2.6.18-4-k7
> savedefault
>
> That didn't work. So I tried:
>
> title Debian GNU/Linux, kernel 2.6.18-4-k7
> root (hd0,0)
> kernel /vmlinuz-2.6.18-4-k7 root=/dev/hdb5 ro
> initrd /initrd.img-2.6.18-4-k7
> savedefault
>
> That didn't work either.
>
> In all the above cases I got this line:
>
> "Setting up cryptographic volume sda5_crypt (based on /dev/sda5)"
> before the "Enter LUKS passphrase" line. So even if I changed grubs
> menu.lst according to above, the computer still tries to decrypt my
> root filesystem from sda instead of from sdb. I guess the initrd file
> that comes with Etch needs editing, correct? But what to edit and how?
> I've never changed any initrd file before.
>
> On 4/16/07, Jay Flory <jflory@aeiconsultants.com> wrote:
>>
>> "Thomas Anderson" <andersonthomas@gmail.com> wrote in message
>> [🔎] 46222DB0.9050904@gmail.com">news:[🔎] 46222DB0.9050904@gmail.com...
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA1
>> >
>> > Hi,
>> >
>> > I disconnected all my drives during a fresh install of Debian Etch with
>> > encrypted LVM on a new sata hd. Everything work fine if I don't add my
>> > old sata hd.
>> >
>> > If I add the old sata hd, Etch refuses to accept my passphrase during
>> > boot to mount my / partition. When I booted Knoppix to diagnose the
>> > system, I noticed that the names of the hd's changed.
>> > Etch was during install sda1 and now it is sdb1. I tried to add "map
>> > (hd0) (hd1)" and "map (hd1) (hd0)" in grub, but it still wont work.
>> > Any ideas/help?
>> >
>> > The old sata hd has winxp.
>> > If I connect the old sata hd on sata cable 1, winxp boots.
>> > If I connect the old sata hd on sata cable 2, Etch boots.
>> > My bios doesn't let me choose a particular sata drive to boot from. It
>> > only lets me choose "SCSI", "CDROM" or the pata drives.
>> >
>> > So my bios thinks Etch is the first sata hd in my system and chooses
>> > the
>> > Etch hd to boot from.
>> > But after my bios let's control over to Etch, Etch thinks of itself as
>> > being sdb1. Strange, huh?
>> >
>> > - --
>> > Regards,
>> >
>> > Thomas Anderson
>> > "Quidquid latine dictum sit, altum sonatur"
>> >
>> > OpenPGP fingerprint: ED7E 1E98 225A 3FCC 458C B3D7 D625 20E6 F316 BD21
>> > OpenPGP public key: http://todu.dyndns.org/pubkey.txt
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.1 (GNU/Linux)
>> > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>> >
>> > iD8DBQFGIi2w1iUg5vMWvSERAnKPAJ9NWCSi7ff/2cExHScblPp7ubw0FACeOZqz
>> > 3sequuouXhRCpGkUVYEvuGY=
>> > =LW6e
>> > -----END PGP SIGNATURE-----
>> >
>> >
>>
>> Thomas,
>>
>> I too have had the same problems while attempting to install Etch on sata
>> drives. The system can change the drive names when you remove/add a
>> drive.
>> To solve this problem you have three options.
>>
>> 1. You can change the menu.lst file int /boot/grub
>>
>> To do this you will of course need to boot up and get into your file
>> filesystem. Edit the menu.lst file and look for:
>>
>> kernel /boot/vmlinuz-2.6.18-3-amd64 root=/dev/sda1 ro
>>
>> or equivalent in your file. Change the /dev/sda1 to /dev/sdb1
>>
>> 2. Take advantage of the udevs more permanent names in the
>> /dev/disk/by-uuid directory and use the names found there instead of
>> /dev/sdb1.
>>
>> You still need to edit the menu.lst file. However, by taking advantage of
>> udev you can remove any possibility for problems should you change your
>> system by adding/removing a drive. Run the command:
>>
>> ls -l /dev/disk/by-uuid
>>
>> to get a list of which name you will need to use in the kernel line.
>> Look
>> for the entry that links to sdb1.
>>
>> 3. Again taking advantage of udev you may rename your devices.
>>
>> This is more complex and I don't have enough experience doing it. I do
>> understand however, that it is possible. Perhaps someone else in the
>> list
>> can offer advice on how to do this.
>>
>> Finally, it is possible to interrupt the grub bootloader and specify
>> which
>> drive to boot from at a grub command line. I did this when originally
>> installing etch on my system. Unfortunately I don't remember the exact
>> commands so you'll have to google it to find out.
>>
>> Thanks
>> Jay
>>
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact
>> listmaster@lists.debian.org
>>
>>
>
>
> --
> Regards,
>
> Thomas Anderson
> "Quidquid latine dictum sit, altum sonatur"
>
>
Thomas,
In your origianly post you specified that your drive was being listed as
sdb1 not hdb1. If you tried to change the kernel line to root=/dev/hdb1 it
would not have found hdb1.
The last part of your post seems to have to do with your file system being
encrypted. I don't know how to handle that as I have never encrypted the
base file system before. Sorry, can't help you there.
Thanks
Jay
Reply to: