Ok I guess the system is just hosed. If no one has any more suggestions in the
next couple days I will reinstall.
I will never trust Debian upgrades again, at least not when encrypted
filesystems are in use.
On Mon, Aug 10, 2009 at 06:49:51PM -0500, line...@ruiner.halo.nu wrote:
> > hmm
> hmmm not sure, you could try
> turning of quiet mode remove the quiet from the kernel option on boot
> and maybe try turning on debug (add debug to the kernal options)
There is no quiet mode in my kernel line. Adding the debug option didn't seem
to add any additional relevant information;
>
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
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 /d
Hi -
I have a cryptsetup encrypted filesystem on Etch. I set it up at install time.
When I updated to 5.0.2, it no longer boots.
The kernel says "Waiting for root file system", then "cryptsetup: source device
/dev/sda5 not found"
The system still boots when I select the old kernel in GRUB.
Hi -
I have a cryptsetup encrypted filesystem on Etch. I set it up at install time.
When I updated to 5.0.2, it no longer boots.
The kernel says "Waiting for root file system", then "cryptsetup: source device
/dev/sda5 not found"
The system still boots when I select the old kernel in GRUB.
Hi
I have a relaively recent debian install with LUKS encrypted filesystem,
default options.
An error has been detected on the HD and it will not boot anymore, FSCK wants
the root password to do system maintenence.
I do not know the root password and I would like to fsck the drive.
How can
sed.
One more thing. I have all the required packages from dselect installed.
If I run dselect again, should I leave the present status for those
packages to "install" as opposed to "remove"? Just how much space do all
the "recommended" packages take up?
Any help
Hello again.
First off, I'd like to thank Mr. Pitts and Mr. Maze, who very kindly
answered my previous mail.
Now, (and a little more to the point :) here 0is my present dilemma:
I have been a long time DOS user, and I'm quite accustomed to having a
prompt with the path you're in, like this:
27; for more details
The same thing happened if I tried making scripts containing mv -iv and cp
-iv. What is the problem here, and just as importantly, what is a posssible
solution? If Debian supports aliases, would this help me? Any help on
either of these two subjects would be grately appr
, and just as importantly, what is a posssible
solution? If Debian supports aliases, would this help me? Any help on
either of these two subjects would be grately appreciated.
Sincerely,
Tom Lineman
P.S. I know this is probab
11 matches
Mail list logo
