Mailinglist Archive: opensuse (4656 mails)
| < Previous | Next > |
Re: [opensuse] running mkinitrd on a dead system
- From: Kenneth Schneider <suse-list3@xxxxxxxxxxxxx>
- Date: Wed, 31 Jan 2007 07:41:57 -0500
- Message-id: <1170247317.1686.1.camel@xxxxxxxxxxxxxxxxx>
On Wed, 2007-01-31 at 01:00 -0800, John Brown wrote:
> Hello SUSE users,
>
> I encrypted my laptop's hard disc using instructions from
> http://en.opensuse.org/
> Encrypted_Root_File_System_with_SUSE_HOWTO. (To be short, I now have
> LUKS-
> encrypted filesystems, and also a custom initrd image, which asks me for
> password
> before every boot. I created the initrd image using a pached mkinitrd
> script.)
>
> In my infinite stupidity, I decided that I need another kernel. I
> downloaded kenel's rpm
> version, and it promptly overwrited my custom initrd image. Now, when I
> boot my laptop,
> I am greeted with a message that my encrypted (cryptsetup-LUKS)
> filesystem is
> unknown, and can't be mounted.
>
> I tried to boot from CD using Knoppix, and execute mkinitrd from it, but
> it failed as it can't
> find /etc/sysconfig/kernel (It's obvious that Knoppix does not have this
> folder). I can
> mount my encrypted filesystems from Knoppix, so the question now is
> which command
> line parameters should I give mkinitrd so that it correctly creates
> initrd - finds my kernel
> and copies it to my boot (unencrypted) partition
>
Before running mkinitrd use chroot to the mount point of the encrypted
filesystem. That will have the command operate on that filesystem.
--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
> Hello SUSE users,
>
> I encrypted my laptop's hard disc using instructions from
> http://en.opensuse.org/
> Encrypted_Root_File_System_with_SUSE_HOWTO. (To be short, I now have
> LUKS-
> encrypted filesystems, and also a custom initrd image, which asks me for
> password
> before every boot. I created the initrd image using a pached mkinitrd
> script.)
>
> In my infinite stupidity, I decided that I need another kernel. I
> downloaded kenel's rpm
> version, and it promptly overwrited my custom initrd image. Now, when I
> boot my laptop,
> I am greeted with a message that my encrypted (cryptsetup-LUKS)
> filesystem is
> unknown, and can't be mounted.
>
> I tried to boot from CD using Knoppix, and execute mkinitrd from it, but
> it failed as it can't
> find /etc/sysconfig/kernel (It's obvious that Knoppix does not have this
> folder). I can
> mount my encrypted filesystems from Knoppix, so the question now is
> which command
> line parameters should I give mkinitrd so that it correctly creates
> initrd - finds my kernel
> and copies it to my boot (unencrypted) partition
>
Before running mkinitrd use chroot to the mount point of the encrypted
filesystem. That will have the command operate on that filesystem.
--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |