root partition killed after waking up from hibernate

Rasi · 2012-04-30 13:35:27

Ok, i reproduced this 2 times today.

installed arch from scratch, set up pm-utils (by adding resume=/dev/sda2 - which is my swap partition)
Also added the resume hook to mkinitcpio.conf, because without nothing would happen at all.
Then put computer to hibernation.

After waking up the surprise: lots of "illegal pblock on /dev/sda3" (which is my root partition)
mount complains that there is no filesystem on /dev/sda3 and cfdisk confirms this.

As i said.. i reproduced this 2 times. Hibernation worked fine approximately 1 week ago.

**edit**

added a bug report:
https://bugs.archlinux.org/task/29673

Last edited by Rasi (2012-04-30 13:57:12)

kgas · 2012-04-30 16:32:29

I confirm this and trying to get the log files now. gparted says the partition is unknown and all the 12 GB is free now. comments added to the bug report with the log details.

Last edited by kgas (2012-04-30 17:05:01)

cryptkeeper · 2012-04-30 21:30:20

I was just about to open a new thread when I saw this one, and it seems to be the same issue, so I just jump in here instead of opening a new thread.

I've killed my system today, too, after waking up from hibernation (after running yaourt -Syu earlier today, without backing up before, of course...). Waking up looked fine at first, although gnome didn't react, but it never does for some seconds. Only it didn't react anymore at all, so I pressed the power button (nothing unusual up to then because I frequently have problems with hibernation, annoying but I can live with it), but now nothing works anymore at all! No filesystem is recognized by neither the GRUB shell nor SuperGrub2Disk nor SystemRescueDisc or whatever. I'm running Arch on a MacBook in dualboot, and OS X still works fine, but rEFIt now recognized the Arch partition (sda3) as FAT.

Is there a way to restore the filesystem? I've been a bit too lazy with backups lately (last one exactly one month ago...), so getting access to the file system would be convenient at least to rescue some files to the one month old full system backup. Nothing of real importance that could not be reproduced would be lost, at least, but it would still be annoying.

The "gone for good" in the bug report linked above doesn't give me too much hope though...

Last edited by cryptkeeper (2012-04-30 21:32:33)

graysky · 2012-04-30 21:37:07

Not to add insult to injury but why are you guys hibernating anyway? Laptops should be put to sleep, not hibernate.

cryptkeeper · 2012-04-30 21:41:40

Because it doesn't need any energy anymore when hibernated but still the whole session is restored, so I usually put the laptop to hibernation when I don't need it for some time (and/or don't have much battery left).

What's wrong with hibernating a laptop? (well, apart from the fact that it can quite obviously break your system... )

Last edited by cryptkeeper (2012-04-30 21:43:24)

graysky · 2012-04-30 22:06:49

...the fact that it can quite obviously break your system

cryptkeeper · 2012-05-01 07:47:26

Well I'll just restore my 1month old full backup... At least it wasn't a too busy month.

But I'll go on hibernating in the future, despite the danger, it's just too useful to give it up! I'll just have to backup more often.

Rasi · 2012-05-01 09:49:39

hibernating is not dangerous at all. Such a bug simply shouldnt happen. pm-utils shouldnt even touch your root partition. period.

Rasi · 2012-05-01 09:51:24

cryptkeeper wrote:

I was just about to open a new thread when I saw this one, and it seems to be the same issue, so I just jump in here instead of opening a new thread.
I've killed my system today, too
[...]

Could you add yourself to that bug report?

cryptkeeper · 2012-05-01 17:27:55

Rasi wrote:

cryptkeeper wrote:
I was just about to open a new thread when I saw this one, and it seems to be the same issue, so I just jump in here instead of opening a new thread.
I've killed my system today, too
[...]

Could you add yourself to that bug report?

Of course, but what do I have to do, just write something like "happened to me, too"?
(I've never done this before...)

Edit: Comment added to bug report, should be fine like this (I hope).

Last edited by cryptkeeper (2012-05-01 20:56:19)

Markus00000 · 2012-05-02 08:31:06

Did it happen to all of you the first time you resumed from hibernation after the upgrade? Or was anyone not affected until after subsequent resumes?

I am asking as I am running 3.3.4 and pm-hibernate once a day. Yet, my root is still fine after resuming at least twice.

cryptkeeper · 2012-05-02 11:21:12

Markus00000 wrote:

Did it happen to all of you the first time you resumed from hibernation after the upgrade? Or was anyone not affected until after subsequent resumes?
I am asking as I am running 3.3.4 and pm-hibernate once a day. Yet, my root is still fine after resuming at least twice.

I restarted the computer once successfully after the update, but yes, it crashed the first time I resumed from hibernation after the update.

anrxc · 2012-05-02 23:10:14

Laptops should be put to sleep, not hibernate

Well, they shouldn't be put in either state with this OS if you value your data, you can't trust them. Every few kernel releases something related to power management breaks. Corrupted memory, lost files, now missing partitions. I own three generations of Intel laptops and it's always the same story.

skunktrader · 2012-05-03 04:39:19

Same problem here i686 3.3.4-1 trashed the root partition (was marked as unknown) on resuming from hibernate. I was able to fix it by fsck'ing /dev/sda1 and rebooted normally with no apparent data loss. I have updated to 3.3.4-2 now but am too afraid to hibernate again...
Hibernate/thaw has been 100% reliable for more than a year on this machine.

Edit: Is everybody with this problem running i686 or are some of us running x86_64?

Last edited by skunktrader (2012-05-03 04:45:22)

kgas · 2012-05-04 16:44:33

skunktrader, this issue was with both 32 & 64 bit with the current update things are back to normal.

Arch Linux

#1 2012-04-30 13:35:27

root partition killed after waking up from hibernate

#2 2012-04-30 16:32:29

Re: root partition killed after waking up from hibernate

#3 2012-04-30 21:30:20

Re: root partition killed after waking up from hibernate

#4 2012-04-30 21:37:07

Re: root partition killed after waking up from hibernate

#5 2012-04-30 21:41:40

Re: root partition killed after waking up from hibernate

#6 2012-04-30 22:06:49

Re: root partition killed after waking up from hibernate

#7 2012-05-01 07:47:26

Re: root partition killed after waking up from hibernate

#8 2012-05-01 09:49:39

Re: root partition killed after waking up from hibernate

#9 2012-05-01 09:51:24

Re: root partition killed after waking up from hibernate

#10 2012-05-01 17:27:55

Re: root partition killed after waking up from hibernate

#11 2012-05-02 08:31:06

Re: root partition killed after waking up from hibernate

#12 2012-05-02 11:21:12

Re: root partition killed after waking up from hibernate

#13 2012-05-02 23:10:14

Re: root partition killed after waking up from hibernate

#14 2012-05-03 04:39:19

Re: root partition killed after waking up from hibernate

#15 2012-05-04 16:44:33

Re: root partition killed after waking up from hibernate

Board footer