Find the answer to your Linux question:
Results 1 to 5 of 5
Fedora 10 isn't booting, give "unable to access resume device" I had fedora 10 install updates overnight and when I came back in the morning I turned on the monitor ...
  1. #1
    Just Joined!
    Join Date
    Nov 2008
    Posts
    27

    Fedora 10 isn't booting, shows "unable to access resume device"

    Fedora 10 isn't booting, give "unable to access resume device"
    I had fedora 10 install updates overnight and when I came back in the morning I turned on the monitor but there was not signal coming from the video card although the computer was on. I restarted. After Grub flashes on the screen it gives me this message
    Code:
    loadkeys: /lib/kbd/keymaps/i386/qwerty/us.map.map:4:
    cannot open include file qwerty-layout
    
    unable to access resume device (/dev/VolGroup00/LogVol01)
    mount: could not find filesystem '/dev/root'
    Thank you.

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    It seems your system either got suspended or hibernated. How did you restart it?
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Nov 2008
    Posts
    27
    I held the power button on the computer until it turned off. I couldn't shutdown normally because the monitor wasn't receiving a signal from the computer.

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
    Posts
    8,974
    When the system is suspended or hibernated, there is no signal to the monitor - that has been suspended... In such cases, you need to use the key-press combination required to unsuspend it, or just press the power button very quickly. It might take a minute to come back since if hibernating it has swapped all running processes and memory to disc. At this point, try shutting the system down and restarting from a cold boot. If that doesn't work, then you are going to need a recovery disc and fix the problems found. I had to do some cleanup and recovery recently on my CentOS system when we had a lengthy power failure and I didn't get everything shut down before the UPS timed out. I could only boot into single user mode, but I was able to fix the problems pretty easily.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  5. #5
    Just Joined!
    Join Date
    Nov 2008
    Posts
    27
    So should I boot it up right now, and once it gives me those message while booting i should press the power button quickly? and after that what happens? should I just restart after that?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...