[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "Could not stat resume device file"



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I originally wrote:

> Ken Heard skrev:
>> When I boot up any box with encryption activated for a partition in
>> it, the following message is received at the beginning of the boot
>> process, or soon thereafter:
>>
>>       Begin:       Running /scripts//local-premount ...
>>       resume:  libgcrypt  Version 1.2.3
>>       resume:  Could not stat the resume device file
>>       resume:  Please type in the file name and try again
>>                          or press Enter to boot the system
>>
>>     Questions: What does "stat" mean? 
>
First, thanks to Johan.Grönqvist for the info about the "stat" command,
which was new to me.

Second, as to to the inability for the lenny startup process to stat
resume device file /dev/mapper/sda8_crypt, Johan had the following to say:

> I had a similar (I think) error when my swap partition changed "device
> file" from /dev/sda5 to /dev/sda3 (or similar) after repartitioning, and
> I had to tell the program giving the error to use the new device file
> instead of the old one (that no longer existed, I think).
> 
> My guess is your /dev/sdaX (or /dev/hdaX) files have changed  meaning,
> and the swap partition to use for resumption has a new device file name.
> 
> If that is the problem, then running "dpkg-reconfigure uswususp" might
> be a solution. (Suggested at
> http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/b5dca520d6b1dd5b)

This device file in fact does exist.  I am able as route to stat it
successfully; consequently I cannot understand why the start-up process
cannot stat it.

As for the package uswususp, it is not installed in my in my Lenovo R61
Thinkpad.  Further, it is not a package which Lenny knows about.

While after on each boot receiving the message quoted at the beginning
of this post hitting the enter key is not particularly onerous, I am
still wondering why I receive this message.  Should I file a bug report
- -- assuming I can figure out how to do so?

Regards,

Ken Heard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjVBWIACgkQlNlJzOkJmTdntwCdFcmhFPMpJ/bnE4qBXR2b6cuG
Q/UAn3drpKDMx2I84gbBCrvW9Qweck5Y
=GqPJ
-----END PGP SIGNATURE-----


Reply to: