LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)
-   -   suspend to disk ruined system :| read an interesting story (https://www.linuxquestions.org/questions/linux-general-1/suspend-to-disk-ruined-system-%7C-read-an-interesting-story-413047/)

alaios 02-08-2006 11:40 AM

suspend to disk ruined system :| read an interesting story
 
Hi all .. I am using suse 10.0 with kde 3.5 (updated from kde 3.4).. i am using linux from suse 8.1.. I was using the hibernate(suspend to disk) funcionallity from 9.x Firstly i have to say that it isnt working correct all the time :( Suspend to disk never works having any fat or ntfs partitions mounted:( I have also noticed that every time that i use the suspend button when the system comes up the root partition (Reiserfs filesystem) informs me that some trans are replayed

Now let me come to the point..Yesterday i have pressed the suspend to disk..
Everything seemed to be fine.. At the boot time the system informed that some trans were replayed... but very soon i got the message the following problems can only be solved but running manually fsck with --rebuild-tree!!!
As u can understand the suspend functionality has ruined my disk...
Thx God fsck worked fine and my system after some rpm --rebuld database.. is now up again... I have lost some files... all the files that were open when i have pressed the suspend to disk button.. I have lost all my amule downloaded files.....

I want to know if u have ever faced similar problems.. and what is the fu....ng problem that has ruined my system.. suse has to face this serious problem. i think

alaios 02-16-2006 11:59 PM

Now i want to ask u if u face similar problems like that.. and what can i do so the restart to windows wont ruin my grub loader entry

alienDog 02-17-2006 01:33 AM

I've never had any problems with suspend to disk, it works perfectly on my machine. I use APM instead of ACPI (mostly because it works fine for me and I'm familiar with it). Having FAT filesystem mounted doesn't have any effect on suspend-to-disk on my system, it works all the same. If you use APM, you could try unmounting fat and ntfs filesystems from /etc/apm/apmd_proxy (or whatever that is in your system) on suspend, and then use the same file to remount them on resume. I don't have reiser filesystems, I'm using ext3 and it doesn't complain about anything on resume.

alaios 02-17-2006 03:54 PM

Thx
 
thxa lot plz give me some advice how can i check if my system use acpi or apm... How can i change it?

alienDog 02-18-2006 12:30 PM

Like I said, I'm not too familiar with ACPI, so I can't be of much help with that. To see if your computer is using APM, you could use

Code:

cat /proc/apm
that will give you APM status information if APM is in use. How you enable it depends on your distribution. You need at least apm kernel module. You can load it with:

Code:

/sbin/modprobe apm
There might be an initialization script in your distro that does it for you in Slackware it's in /etc/rc.d/rc.modules, you will need to open the file in text-editor and remove the # mark from that line. Your distribution might be different. You could try looking for /etc/rc.d/init.d/rc.apm or rc.apmd, or /etc/init.d/rc.apm or rc.apmd. In distributions using System V style init, you enable it using chkconfig. man chkconfig will probably help you with that.

In addition to kernel module, you will need apm-daemon.

Code:

/usr/sbin/apmd
If you system has rc.apm(d) somewhere, I think it will load the daemon automatically. Slackware will start apm daemon automatically if the apm kernel module is loaded, so you don't need to anything about that.

Furthermore, you will probably want to use apm-proxy file (to unmount those filesystems and such). The standard location for that is /etc/apm/apmd_proxy. In your distro it may be somewhere else or it might not exist at all (in which case I can show how it looks like, let me know if you need it).

You will also need to disble ACPI if you plan on using APM, the two should not be used simultaneously. Maybe it's /etc/rc.d/init.d/rc.acpi (or /etc/init.d/rc.acpi), or something like that, but I'm only guessing here. If it is, you can disable it using chkconfig. In Slackware you just:

Code:

chmod a-x /etc/rc.d/rc.acpi
(I think ;)).


All times are GMT -5. The time now is 01:13 PM.