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 |
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
|
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.
|
Thx
thxa lot plz give me some advice how can i check if my system use acpi or apm... How can i change it?
|
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 Code:
/sbin/modprobe apm In addition to kernel module, you will need apm-daemon. Code:
/usr/sbin/apmd 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 |
All times are GMT -5. The time now is 01:13 PM. |