I tried configuring fstab to use the UUID from blkid, but I had the same
problem. Could the problem be that the SCSI drives are not coming up until
cryptsetup has loaded?
Here is some info on my configuration:
t...@magnesium:/etc/initramfs-tools/conf.d$ cat resume
RESUME=/dev/mapper/magnesium-swap_1
t...@magnesium:/etc/initramfs-tools/conf.d$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mapper/magnesium-root / ext3 defaults,errors=remount-ro 0
1
/dev/sda1 /boot ext3 defaults 0 2
/dev/mapper/magnesium-swap_1 none swap sw 0 0
t...@magnesium:/etc$ cat /etc/crypttab
sda5_crypt /dev/sda5 none luks
t...@magnesium:/etc$ ls -l /dev/mapper/
crw-rw---- 1 root root 10, 63 2009-08-05 13:45 control
brw-rw---- 1 root disk 254, 1 2009-08-05 13:47 magnesium-root
brw-rw---- 1 root disk 254, 2 2009-08-05 13:47 magnesium-swap_1
brw-rw---- 1 root disk 254, 0 2009-08-05 13:47 sda5_crypt
t...@magnesium:/etc$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.26-2-686
On Wed, Aug 05, 2009 at 04:18:47PM +1000, Alex Samad wrote:
>
> do you have your root fs in fstab by LABEL or UUID if so I reported a
> bug report against cryptsetup.
>
> change to a dev like /dev/mapper/<device> and then run update-initramfs
> -u
>
> On Tue, Aug 04, 2009 at 06:50:56PM -0500, line...@halo.nu wrote:
> > Hi -
> >
> > I have a Debian Etch system which I recently upgraded to v5.0.2. The file
> > system was encrypted with LUKS at install time.
> >
> > The upgrade appeared to go well, however when I boot into the new system,
> > it gives the following error:
> >
> > Volume group "hostname" not found
> > cryptsetup: Source device /dev/sda5 not found
> > Begin: Waiting for root file system
> >
> > This may be unrelated, but it also says:
> > Driver 'sd' needs updating - Please use bus_type methods.
> >
> > After 5 minutes it says:
> >
> > Gave up wating for root device
> >
> > And drops to a busybox shell.
> >
> > The /dev/sda devices seem to come up ok, and sda is the same device name
> > that it had before.
> >
> > When I select the old 2.6.18 kernel in the GRUB menu, it works fine and I
> > can access my data. Every time I select the newer 2.6.26 kernel, I get
> > this error.
> >
> > How can I fix this issue?
> >
> > Thanks!
> >
> >
> >
>
> --
> "I can't tell you what it's like to be in Europe, for example, to be talking
> about the greatness of America. But the true greatness of America are the
> people."
>
> - George W. Bush
> 07/02/2001
> Washington, DC
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
