LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 08-22-2012, 09:19 AM   #1
minty33
Member
 
Registered: Aug 2012
Location: earth
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Posts: 136

Rep: Reputation: 1
Question swap not working?


i am having an issue where my laptop (toshiba sattelite) was hanging using mint13 since i switched from mint11 mostly when alot of ram was being used (i.e vbox, firefox w/ lots tabs ect...). i was getting an error at boot of "can't find drive uuid=**some longID**** do you want to wait or manually recover" it only is there for a second so i was figuring it was just slow mounting one of my partitions but always saw them all after it booted so didn't make any connection to swap until i tried to use swapon or swapoff to see if this was the source of my woes. sure enough swapon -a gave me an erron "unable to find uuid=******same as booterrorID******" i tried to mount umount ect that device but kept saying it wasn't in mtab. finally i used gparted to reformat that partition as swap again and reeboot still same thing. any ideas or how i can investigate further -- i'm not sure of the intracacies of the swapon/off command so if there is a way to verify its not working or how to fix this pls help.
i suspect it is doing the same thing when i boot from a live disk because it seems to run slower than even a live disk used to. before i noticed the swap issue i thought one of my ram chips was going bad or something. it is an old laptop but had good specs for its age core 2 duo, 3 G of ram, processors only 1.83ghz but never really had issues till very recently.

Last edited by minty33; 08-22-2012 at 01:39 PM.
 
Old 08-22-2012, 09:22 AM   #2
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,133
Blog Entries: 2

Rep: Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836
Please post the output of the commands
Code:
cat /etc/fstab
blkid
 
Old 08-22-2012, 09:26 AM   #3
minty33
Member
 
Registered: Aug 2012
Location: earth
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Posts: 136

Original Poster
Rep: Reputation: 1
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sda2 during installation
UUID=ed60df52-7116-45d8-9ac3-4a254b859b46 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=9894cb86-bb3f-4e5e-adc4-b439dbd429f5 none swap sw

--------

/dev/sda2: UUID="ed60df52-7116-45d8-9ac3-4a254b859b46" TYPE="ext4"
/dev/sda3: UUID="bf36e68a-505f-4243-b839-54d6d37ff470" TYPE="ext4"
/dev/sda4: UUID="a4838b9a-ad3b-4441-8e47-04a79806e459" TYPE="ext4"
/dev/sda5: UUID="9512949f-8eaf-478d-8268-00fc82a08d87" TYPE="swap"
/dev/sdc1: LABEL="1.0 TB Hard Disk" UUID="df01ddff-b2a9-496b-99e1-536ac44f4613"

****note****
the id for is not any of these - here is the actual error - swapon: cannot find the device for UUID=9894cb86-bb3f-4e5e-adc4-b439dbd429f5
 
Old 08-22-2012, 09:35 AM   #4
m1chel
LQ Newbie
 
Registered: Jan 2012
Location: Holland
Distribution: Gentoo
Posts: 4

Rep: Reputation: 0
The UUID of your swap partition has changed, probably due to the upgrade. Copy the UUID for /dev/sd5 that blkid reports and insert it replacing the UUID of the swap drive in /etc/fstab (last line). Save /etc/fstab. Then turn on swap.
 
Old 08-22-2012, 01:09 PM   #5
minty33
Member
 
Registered: Aug 2012
Location: earth
Distribution: Mint Xfce, Korora Gnome3, Ubuntu Server NoGui,
Posts: 136

Original Poster
Rep: Reputation: 1
thanx

i believe that worked swapon -a gave me no output but no error either. that means it worked i assume i'll reboot see if i get that message.

my mint has been sooo buggy i don't know why i didn't upgrade i fresh installed maya. i should start another thread but you seem to always answer tobi so i'll just post this here if thats ok.

while i was editing fstab before i used nano i tried to gksu caja to do it in the gui for some reason and got the following error.
keep in mind this persisted through a reboot and also never did this before because i always ued gksu caja to get write permissions on my external hd w/ no issue. i see no d-bus daemon running why and how do i restart it. unrelated i was getting dbus issues connecting wireless w/ wicd on a diff OS the other day. is my hardware failing or is this all coincidence.

------------

(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GConf Error: No D-BUS daemon running


(gksu:3764): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

(caja:3765): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)

(caja:3765): Eel-WARNING **: MateConf error:
Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
MateConf warning: failure listing pairs in `/apps/caja/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/desktop/mate/lockdown': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)MateConf warning: failure listing pairs in `/apps/caja/desktop-metadata': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for MateCORBA, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/mateconf/ for information. (Details - 1: Failed to get connection to session: The connection is closed)
(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(caja:3765): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(caja:3765): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.
 
Old 08-22-2012, 01:53 PM   #6
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,133
Blog Entries: 2

Rep: Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836Reputation: 4836
Sorry, not a Gnome/Mint user, can't help with that.
You will always get the best answers to your questions if you keep unrelated questions in different threads.
So I would recommend to open a new thread in the Desktop or the Linux Mint sections for your new question.
It is also recommended to put commands and output from commands between [code][/code] tags. This will make your post much more readable.

By the way, most Unix/Linux commands act to the principle "No message is a good message!", so if you have a program that just returns to the command-line it usually has worked. If you want a more verbose command-line, most programs have a -v option that gives you some useful output.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Swap not working nova49 Slackware 5 02-06-2011 09:14 AM
Swap not working? impee Linux - Software 2 03-28-2007 05:52 AM
how do i know if my swap is working? binary_0011 Linux - Newbie 3 12-29-2006 06:02 AM
swap not working djabbot Linux - Hardware 2 01-19-2005 07:23 AM
Is my swap working? Tyir Slackware 10 12-08-2003 11:21 PM


All times are GMT -5. The time now is 08:14 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration