Fedora :: Error "unable To Access Resume Device (LABEL=SWAP-sda8)
Mar 7, 2010
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)
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'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
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.
Dual PII 400, 512Mb with a Promise SuperTrak 100 IDE Array Controller. At present I have only one drive on the controller, configured for 1 JBOD array. I install FC9 with no problem. New partition is created and formatted, Grub is installed, and then... Grub is found and booted, but then I get:
Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found Unable to access resume device (/dev/VolGroup00/LogVol01) mount: could not find filesystem '/dev/root' I can boot in rescue mode, chroot to the installed system. I changed the kernel boot parm "root=/dev/VolGroup00/LogVol00"
I have installed both Windows Xp and Fedora 12. Last time when i was working on Fedora it didn't shut down properly. Now following error occurs and finally the system sleeps.
ata1.00 : exception Emask 0x0 Sact 0x0 SErr 0x0 action 0x0 ata1.00 : BMDMA stat 0x25 ata1.00 : cmd c8/00:00:50:5a:34/00:00:00:00:00/e4 tag 0 dma 131072 1n res 51/40:7f:d1:5a:34//00:00:00:00:00/e4 Emask 0x9 (media error) ata1.00 : status : { DRDY ERR } ata1.00 : err : { UNC } end_request: I/O error, dev sda, sector 70539985 JBD : Failed to read block at offset 5884 EXT4-fs(sda): error loading journal mount: wrong fs type, bad option, bad superblock on /dev/sda8, codepage or helper program, or other error In some case useful info is found in syslog-ty dmesg | tail or so
why I'd be receiving this error. I have created a partition and filesystem and put the label in fstab. Everytime I reboot the server it is unable to mount the filesystem. However I am able to mount it manually.
I have HP ML350 G6 Server with RAID10 enabled on bios While trying to install Centos 5.5 64 bit OS I am getting the error mentioned below. "An Error Occured trying to initialize swap on device cciss/codop3. This problem is serious and the install cannot continue."
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
I went to print something and I get this message: Summary: SELinux is preventing access to files with the default label, default_t.
Detailed Description: SELinux permission checks on files labeled default_t are being denied. These files/directories have the default label on them. This can indicate a labeling problem, especially if the files being referred to are not top level directories. Any files/directories under standard system directories, /usr, /var. /dev, /tmp, ..., should not be labeled with the default label. The default label is for files/directories which do not have a label on a parent directory. So if you create a new directory in / you might legitimately get this label.
fc10 86_64Every time I login and do not run any programs, the swap space used goes from 300 MB to 6GB. Memory stays at about 320 MB (out of 4 GB). I takes several minutes to fill the swap space, and when it gets full, it then goes back to 300 MB. Then the system runs ok.The system monitor shows no processes (other than itself) running, but cpu usage is about 20% on 1 of the 2 cpus
For the past several days the Package Updater has popped up wanting me to install an update to iceweasel. Each time I try to do the iceweasel-31.8.0esr-1-deb8u1 (64-bit) I get the following error message:
E: Internal Error, ordering was unable to handle the media swap
I just compiled my first own kernel (I'm using Arch Linux), following the tutorial on the german site. Now I tried to boot it, I ended up failing with this message: Code: Waiting 10 seconds for device /dev/sda1 ... Root device '/dev/sda1' doesn't exist, Attempting to create it. ERROR: Unable to determine major/minor number of root device '/dev/sda1' Here is the important part of my menu.lst:
[Code]....
I simply copy&pasted the Arch-entry, i.e. I also had the disk by uuid there. The failure message was the same, just the root device name was the different name Also, at first I did not have the initrd line in my menu.lst (as written in my tutorial that I may not need it). In this case I had this error message:
I have a lenovo x200 laptop running Fedora 14, fully up to date with the Fedora repository. Seemingly out of nowhere, some websites will no longer load. First it happened to www.facebook.com, next (after a day or so) wikipedia.org, now the Fedora forum. Other Internet access seems fine, but when I try to go to these pages I just get "unable to find host" errors. Its totally bizarre. It first happened in an airport so I thought it was just a strange network there, but now it happens at home. I can't get on these sites in firefox or elinks browsers (in a terminal) BUT I can ping both sites no problem. Also, the other computers in this house have no problem visiting these sites.
I 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 ?
Using Debian Lenny. I'm trying to label my usb flash drives. I checked on the Internet and found a page, but I can't get it to work: [URL]. I umounted the usb drive. I checked it with Debian:~# blkid /dev/sda1: UUID="B1CC-3C4F" TYPE="vfat"
But when I try to make a label I get this message: Debian:~# mlabel -i /dev/sda1 ::VFAT_DOC Can't open /dev/sda1: No such file or directory Cannot initialize '::' mlabel: Cannot initialize drive
If I try mlabel -i /dev/sda1 ::VFAT_DOC when the drive is mounted I get this output: Debian:~# mlabel -i /dev/sda1 ::VFAT_DOC Total number of sectors (7855032) not a multiple of sectors per track (62)! Add mtools_skip_check=1 to your .mtoolsrc file to skip this test but no label is attached to the drive.
I added this to /etc/mtools.conf: drive p: file=/dev/sdb1 and ran this command: mlabel p:VFAT_DOC and still can't get it to work Can't open /dev/sda1: No such file or directory Cannot initialize 'P:' mlabel: Cannot initialize drive
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.)
I just installed OS 11.4 this morning. Was previously on CentOS. I chose to have it import the partition & raid setup during install. Now when it boots it hangs with
"Could not find /dev/disk/by-label //" "Want me to fall back to /dev/disk/by_id/ata-ST(lots of drive stuff) -part2 (Y/n)" If I just hit ENTER at that point the boot will go on and it runs fine, but it stalls every time with that same error on boot. I did quite a bit of searching with Google and here (the search here considers every word in the error message to be too short or too common).
Everytime I to turn on my wireless device, and try to connect to a wireless network, i see the phrase " device not ready" greyed out, and not able to access a wireless network. i do not know what to do
So I've tried some hours ago to install the new kernel 2.6.38 and when I did the reboot, it prompted this error: "Error 11: Unrecognize device strong
Press any key to continue..." I know this is such a general question but how to install the new kernel with Fedora 14? I think I did compiled and configured it ok and did something that wasn't recognized by grub or perhaps when I ran the command to make the new initrd.
Attempting to use PLACES>Home (or Documents,Bin,Desktop,etc.)brings up the error message "There is no Windows program configured to open this type of file." If I open Open Office I can find all files in home, documents, etc. and open them.The computer is otherwise functioning normally but using the usual methods all the files that should show look empty. How did this happen? I was attempting to use WINE to load Avery Wizard (a Win utility) through AWsetup.exe. To do this I changed permissions for that file but I have subsequently removed the file and its subfiles using the terminal.
I updated quite a lot - kernel, selinux policies, initscripts, glibc and a lot more - and after reboot one filesystem does not mount. It says:Command failed: Can not access device... and asks for password. This is: RAID -> LVM (mirrored) -> LUKS -> ext3. Similar filesystem (raid->lvm(not mirrored)->luks->ext3) mounts fine. Mounting the problematic system by hand works fine. During boot, the lvm blockdev is named by UUID in crypttab, and the name used in fstab.
Of course I removed it from fstab to boot now. I tried downgrading initscripts so far, will try others. What I also noticed is that the emergency shell (bash) complains about something, I'd need to write it down next time I reboot; also "lvs" fails when / is ro, but maybe that's normal, dunno.Googling for the error message brought something about cryptsetup, but I didn't upgrade it (there is no upgrade available), and all I gather from it is that the error message might really mean something else, like device is already mapped.
It is probably something related to lvm mirrors, maybe also to luks, though the only related package in the list is the kernel, maybe the module-init-tools. SELinux seems not to be the cause, booting with permissive has the same problem. What I wrote above, leads me to thinking that luks is trying to set up lvm mirrors in parallel as they have the same uuid, but a) later during boot the mapping name is not there b) I have no idea what reads crypttab
Does a mailserver have to have direct access to WAN or can it be a LAN device with just one NIC ?
We have two WAN access points.
One is an adsl router joined to the switch and all seems fine for internet browsing.
The other is a wireless system with a linksys router joining by way of PPPoE and this appears to connect fine.
This PPPoE is direct to our ISP and where we need to downlod our mail to our pending mailserver.
When the linksys router is also joined to the switch all devices can use either the adsl or linksys to roam the net. 192.168.1.1 linksys & 192.168.1.10 is adsl.
When I join the linksys direct to the mailserver I will then need two NIC's. One for the Linksys and one for the LAN.
This is where the fun has started.
So.... Can I just have one NIC (connected to the switch) on the mailserver?
I'm fairly new to Ubuntu/Linux. Here's the problem I'm encountering after I tried to install Ubuntu Desktop 10.10. I was installing from a CD, as I tried to install alongside Windows XP, (The setup detected 2 hard drives, the first one was 40 GB, with all my windows stuff on it, the other was a 160 GB one), I got the message "error informing kernel about changes made to .....", which would not disappear no matter what I clicked. So, choosing the seemingly only option, I force powered down the computer. As I powered it back on.
Windows did not boot, instead I just got a black screen of nothing but a flashing _. I tried booting from the LiveCD again, which worked well enough, EXCEPT, the 40 GB hardrive full of my Windows stuff and files was not detected, and the 160 GB drive was detected only in the drives tool, but not accessible. I have no clue as to how to: 1. retrieve important files from my 40 GB drive. 2. Restore Windows XP professional.
[ 3635.194162] usb 3-1: new full speed USB device using uhci_hcd and address 2 [ 3635.338159] usb 3-1: New USB device found, idVendor=066f, idProduct=4200 [ 3635.338165] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
