When I boot CentOS 5.5, I receive the message:Unable to access resume device ( UUID = some UUID etc. )How do I find out what actual device to which this UUID refers ? It does not appear to be a block device since it does not show when I try 'blkid'.To what does "resume device" refer ?
View 6 Replies
I'm running CentOS 5.5 with a hardware Areca controller (Raid 10). I initially installed a machine and rsynced the file system to a third machine; I'm then pulling in the file system to new machines and updating grub with a script to make it bootable.
I've done this before with other machines (no raid sets) but with these machines I'm running into errors code...
I face a problem with my server after i rebooted it i got a message on start up tell me that " Unable to access resume device (label=swap-sdb3) " and the system doesn't startup
the error message exactly is
Unable to access resume device (lable=swap-sdb3)
Creating root device.
Mounting root filesystem.
[ 3.305354] EXT-fs (md1) : error : unable to read superplock
mount: error mounting /dev/root on sysroot as ext3 : invalid argument
[Code]....
I virtualized a PC with VMware vCenter Converter. But when I boot my virtual PC, I have an error.I found this link but I can't mount /dev, /sys and /proc. I have this error message : mount: /dev is not a block device.
View 2 Replies View RelatedAfter asking on both this forum and the Fedora forum, I felt it was safe enough to install a copy of Fedora on my working-well openSUSE drive. I have a 1 TB drive, partitioned as follows:
I did an install of Fedora 13, was VERY careful to set up the installer to put it's files in the partitions I wanted, although I did let it mark the partition as active, feeling it may have to boot during the installation process.
I had grub installed in the root of the partition rather than the MBR for both systems.
When Fedora finished installing, I rebooted the system only to find that it wouldn't. I got the dreaded "No Boot Device" message.
So, I started the 5 hour process of booting with the parted magic disk, booting with a Gentoo live disk (only one around), monkeying with the install parts of the openSUSE and Fedora disks, swapping drives to Windows to download openSUSE Live CDs (yes, both) and searching the forums and various other web sites for some poor bloke who did the same stupid whatever it was I did, and finally, as I was using fdisk on the Gnome Live CD, I noticed the warning message stating that fdisk would not work on a drive that was partitioned with the GPD format.
Notice that I have 5 partitions? That is not a typo on my part, I used the GPD format when I set it up so I could do what I did without using "imitation" partitions.
When I used parted (the command line editor on the Gnome Live CD) to change the active partition, everything started working again! Well, at least I can boot the openSUSE system, the most important thing.
It is my suspicion that the Fedora install uses fdisk to do it's work, and fdisk just mucks up a GPD formatted disk. Not the information, just the part of the drive that holds the partition table. Perhaps just the flags section. I don't know enough to say with any certainty.
I didn't change the drives parameters during the installation of Fedora, so I don't know of it even offers the GPD partitioning option. If not, I can understand how this sort of thing could happen.
Still....So now all I have to do is make the grub menu, the one installed with openSUSE, boot the Fedora installation on the next partition. Seems simple enough.
Installed CentOS 5.4 x86-64, installation is fine. First bootup after install always fails (after a few messages are displayed) with my monitor showing an "out of range" message.I know exactly what to fix (sync values in xorg.conf) and what values to enter there, but what I can't figure out is, how to get to a stupid prompt! Or a smart one for that matter.Also, I do get a message (before the "out of range" message) from CentOS, telling me to "press I for interactive startup" - but all that does is print as many "I" on the screen as I press. And did they really mean "I" and not "i" for this?
I hear great things about CentOS and if you can help with this silly question - How to get to a prompt - as easy as it probably is for you all, it would help me a lot.
Currently I only only resume from suspension by pressing the power button. I learned that by editing /proc/acpi/wakeup one can enable resuming from other devices. But how to figure out which is for which device? Here is my /proc/acpi/wakeup file:
Code:
DeviceS-state Status Sysfs node
PCE2 S4*disabled pci:0000:00:02.0
[code]....
How do you actually remove and install kernel when the system is not booting.
View 4 Replies View RelatedI was trying to get this feature: wake up my htpc from s3 with my remote control and the solution is to modify /proc/acpi/wakeup and a descriptor in /sys. Here are the details: I'm using a Microsoft IR receiver for MCE remote that appears as dev 2 of bus 2 in lsusb
root@htpc:~# lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 045e:0714 Microsoft Corp.
Bus 001 Device 005: ID 045e:0715 Microsoft Corp.
Bus 001 Device 004: ID 045e:0707 Microsoft Corp. Wireless Laser Mouse 8000
Bus 001 Device 003: ID 045e:070c Microsoft Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub....
That's USB0 I have to enabled, why not usb 1 or 2 (bus 2 in lsusb)? Moreover why are all the disabled/enabled preceded with a star and S4 and not S3 mentioned? Nevertheless that wasn't enough to get it work. I looked in gconf-editor in apps/gnome-power-manager/general but I have no can-suspend or something similar... (I'm running on 10.10, with 10.04 I could suspend only once, afterwards the computer didn't go to suspend, just black screen then login screen). So I looked in /sys/ and found that 'cat /sys/bus/usb/devices/2-1/power/wakeup' (notice the 2.1 as bus 2 device 2 (0,1,...) gave 'disabled' so a echo enabled > /sys/bus/usb/devices/2-1/power/wakeup and now I can wake-up with the remote when I want.
What I don't understand:
Why USB0 in /proc/acpi/wakeup ?
Why have to change in /proc and /sys ?
Is it possible to automate this to get it work even if I change the usb port the receiver is plugged in ?
Reboot and select proper boot device or insert boot media in selected boot device and press a key. I got this error after: Reducing my Windows 7 partition by about 100gb. Creating a new partition (100gb) and copying my Ubuntu partition (10gb) to the new partition. After it was copied, and pasted, the original partition was deleted. I now had two partitions a new 100gb Ubuntu partition and a 600gb (or so) Windows 7 partition.
All of this was done using a bootable USB with Ubuntu 10.10 and GParted partition editor. Now when I boot I get the "Reboot and select proper boot device or insert boot media in selected boot device and press a key." error.
I am having trouble with a rather peculiar timeout during resume from suspension and I was wondering if any of you have encountered the error or might have some leads as to what causes the problem.I am using Gentoo Linux with TuxOnIce patched kernel. While both hibernation and suspension works as advertised, there is a rather irritating timeout while trying to resume from suspension. Each and every time it takes about 60s for notebook to resume back to X session again, no matter what the conditions are (i.e. USB deviced plugged in, etc.)
View 3 Replies View Relatedi want to change boot install message "wel-come to CentOS" .How can i change it.
View 1 Replies View Relatedi have 5.4 installed on a super-micro server motherboard (has two gigabit ether ports). when i boot while its initializing everything it gets to the "starting eth0" and just stays there?
right before it boots up and says press any key for options i press a key and choose "centos (2.6.18-164.el5)" and it boots up fine but when i choose "centos (2,6,18-164.el5xen)" the problem occurs. and that is the default boot option.
I'm trying to move an existing FC10 install (created by someone else) from a 160GB WD1600AAJS SATA disk to a 160GB WD1600AAJB PATA disk (cursed trend of horizontally mounting SATA connectors at the end of the motherboard means the latest rev mobo doesn't fit in our enclosure!). I've used DD to copy the disk image from one to the other, but when attempting to boot, I get the following error:
Code:
Unable to access resume device (UUID=946f216f-0c24-4b02-a996-f42059970de7)
mount: error mounting /dev/root on /sysroot as ext3: no such file or directory
That particular UUID maps to sda2, which is the swap partition. Interestingly, both the SATA and PATA disk come up as /dev/sda on the motherboard. I kind of grok that the UUIDs are substitutes for directly naming the disks, and that they're referred to in fstab, initrd-2.6.27.12-170.2.5.fc10.i686.img, and in /dev/disk/by-* I'm guessing the problem is that the GUIDs (at least the one for swap) are no longer the same. How are they assigned to the partitions during boot?
I tried doing
Code:
swapoff -a
mkswap /dev/sda2
swapon -a
and put that new GUID in fstab and into initrd-* (using some steps I found elsewhere on how to gunzip/rezip it).At that point, I get a kernel panic on boot
Code:
Kernel panic - not syncing: CFS: Unable to mount root fs on unknown-block(0,0)
So I'm guessing that the other UUUDs have changed as well and I need to update them. How would I figure out what they are? I suppose I could change the references to /dev/sda*, but I didn't build this original image and I'm thinking whoever did had a good reason to go with UUIDs.
I have FC6 system with kernel 2.6.22.14-72.fc6 When I rebooted my system, I got error message "unable to access resume device (LABEL=SWAP-sda8) then it went to fsck automatically to all the partition and then stop (failed)
Checking filesystems
/1:clean, 10543/2560864 files, 204494/2560359 blocks
fsck.ext3: unable to resolve 'LABEL=/backup'
/boot: clean, 155076/19546112 files, 13456168/39072080 blocks
[Code]...
I'm having a consistent problem with instances on Amazon EC2, which a lot of searching including here has resulted in no solution.During boot I see the following message on the console (or "System Log" in the Amazon console):Code:Mounting local filesystems: mount: /dev/sdg already mounted or /apps busy(I'll append a extract from the full log below).Once I log into the instance, I can access the filesystem so it's mounted somehow but I can't figure out what's going on:
Code:
# df -k /apps
Filesystem 1K-blocks Used Available Use% Mounted on
[code]....
The server comes up after rebooting and after setting the hostname it starts setting up logical volume management. It says that 2 logical volume(s) in volume group "VolGroupOO" now active But then it starts to check the file system and errors with fsck.ext3: Device or resource busy while trying to open /dev/sdb1 [failed]
***An error occured during the file system check
***Droppping you to a shell, the system will reboot when you leave the shell
Give root password for maintenace
After I log in with the root I get the message mesg: error tty device is not owned by group 'tty' Can the forum tell me how to troubleshoot this issue so I can boot back up again? I have 2 harddrives in this server and only 1 drive was detected when I first installed CentOS. The error first appeared when I mounted the 2nd drive at the mount point /UserGeneratedData. drive was formatted with ext3 before mounting and did not have any data on it I don't want any software RAID if thats what seems to be going on with "VolGroup00"
I've just ordered my first vps with centos 5. I've got a minecraft server running through the provider's in house ssh client. After I close and reconnect to the session the server continues to run (which is great) but I can't give it any commands because I have no idea how to resume the session with a given program that's already running.
View 3 Replies View RelatedI've been trying to find an answer to the following problem : whenever my PC is put in Suspend/Hibernate mode, it fails to recover when pushing the power button. This happens both with automatic suspend or manual suspend. I've been reading this problem, and mine is quite similar, but no solution is given.
uname -rmi
2.6.18-194.11.4.el5 x86_64 x86_64
PS: this computer is not connected to Internet, no update possible.
I already know "what" my problem is, however I am having difficulty fixing it. I recently upgraded our companies server to a HP ML150; decided to upgrade to FC10 hoping it would go smooth and it is not. It does not detect the SATA drives after the installation.
I get.
"Volume Group "VOLGroup00" not found
Unable to access resume device (/dev/VolGroup00/LogVol01
mount: error mounting /dev/root on /sysroot as ext3: No such file or directory
I know the problem is that my SATA is not enabled in the kernel or grub, but I don't know how to fix this. My internet searches are coming up a little short and LIVE discs are not working so I am having trouble figuring this out.
My laptop beeps three times during the resume from hibernation. How can I disable this beeping. I use CentOS 5.3. Interestingly, this issue did not occur when I used CentOS 5.2 on the same laptop last year.
View 6 Replies View RelatedI have a netbook with Windows 7 and already have my HDD partitioned. I downloaded UNR 9.10 and saved it to a 1GB USB drive. I set my boot priority to have it boot off of USB prior to the HDD and I save/reboot. Upon boot up I get a message to remove devices and reboot. I tried several different BIOS configurations and cannot get it to recognize the boot file. Does anyone have any ideas on how I can get this corrected? I would like to have a linux dual boot system especially since I'm taking a linux admin course.
View 4 Replies View RelatedI have been using my desktop as a dual boot machine for several months now. The primary hard drive with windows on it died, and since we have been using ubunto 9.10 exclusively, I just removed the dead drive, changed the jumpers on the secondary drive to primary and did a clean install on the drive which presumably formats the disk before installing. When I try to boot from the hard drive i get the following message:
ERROR: no such device 2eb48bcb-7bb4-4080-b04d-fc32dec8c252
For the sake of security, I want the screen to be locked after the system is resumed from suspend or hibernation. Now the only way I can do this is to check the options "Lock screen when screen saver is active." in the screensaver preference. But this method is annoying since I have to type the password to quit the screensaver. Is there other way to do this? Thanks.
By the way, I use CentOS 5.2 x86_64.
Leonard
2009-3-21
i dont know why my system dosnt resume from suspend sstate.i it goes in suspend state.it doesnt resume .i have to poweroff then restart it again.and when i get logged in it gives me Following Error: Resume problem: Your system did not appear to resume correctly from Suspend/Hibernate. This may be a driver problem or a hardware problem. Check the GNOME Power Manager Manual for common problems.
do you think it is because of batterry.i have a problem in my By Battery .IN DOS operating system.when i check my battery icon . A red Cross constantly blink on lower right side of the battery and it says (your Battery consider Replacing).i have notice one thing .And My battery timing hias become Decreased. Do you think this Resume problm is cause of battery problm.Or there is some problm in my Os software.
solve this error "3c501 device eth0 does not seem to be present, delaying initialization".
View 3 Replies View RelatedWhen inserting/removing a usb device to a board based on linux system, an output is given:
Code:
# mmc1: card 0001 removed
mmc1: new SD card at address 0001
[code]...
My computer have ATI X600 graphics card installed, and I installed CentOS5.3.
Every time I suspend my computer and then resume it, it seem the graphics card can't resume and the monitor says 'no signal', but the system still responses, I can use keyboard.
Is there any configuration I can't do to make it resume normally? I've searched a lot in Google but can't find out any one else run into the same problem.
Information about the card:
Quote:
I speeded up boot time significantly. This was accomplished by using chkconfig off to stop unneeded services from starting at boot time and by reinstalling without LVMs
There are now just two remaining things that are slowing down boot time:
1- At boot time, I see the message "Setting up LVM" and after a while "LVM not found" Is there a way to keep Centos from trying to set up LVM? (I am not using LVM, that is why it is not found)
2- I am using a Lenovo Thinkpad and there is a delay at boot time as Centos setting up the built in mouse: "TPPS/2 IBM TRACKPOINT as class /input/input6"
I do not need the trackpoint (I use an USB mouse), Is there a way to disable the built in trackpoint (mouse) so that Centos doesn't spend unnecessary time install it at boot time?
I have installed live cd on usb pendrive. Everything works great. How can I find out which device driver it is using? Where are the device driver files stored? How do you specify the device driver when mounting a device?
View 3 Replies View Related
