"could not stat the resume device file"

We have a local mirror of the Ubuntu repos here at work and they are pretty fast. I couldn't figure out how to get update-manager to use them, so I upgraded my desktop machine to Hardy Heron by changing everything in /etc/apt/sources.list from gutsy to hardy and typed sudo aptitude update && sudo aptitude full-upgrade and let it run. It asked a couple questions about modified config files and such which I answered, and then it was done. I rebooted and it put up the pretty "UBUNTU" with the new pulsating KITT-esque progress bar...and it never went beyond that. I finally hit alt-f1 and saw that it was waiting for my input with the prompt:

resume: could not stat resume device file /dev/sda10. Please type in the name to try again or press ENTER to boot the system

I hit enter and it seemed to boot just fine. This is a pretty annoying thing to have to do every time you boot, so I searched until I found the solution for me: reinstall initramfs-tools, like so: 

sudo aptitude reinstall initramfs-tools

Like Lauri Kainulainen wrote in that launchpad bug report, I've never used hibernate on this machine, so this is pretty puzzling. However, I'm continually impressed that I can find help for these obscure problems so quickly. It pays to use a popular distribution and to not be the first to try out new things with it.

Comments

Anonymous said…
This error happened to me too. So I followed the instruction:

sudo aptitude reinstall initramfs-tools

and now don't get this error on booting. I encountered this error after adding a new controller (Promise 133TX and two IDE drives as a RAID) to Ubuntu 8.04 running on an Abit BP6 dual celeron.
May 31, 2008 at 11:34 PM
Paul said…
But why does the error say /dev/sda10 and not /dev/disk/by-uuid/
January 5, 2009 at 4:22 PM
Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more