Arch Linux

RazZziel

Member

From: Spain

Registered: 2007-07-13

Posts: 36

Arch won't boot after trying ususepnd

I wanted to try suspension to disk so I installed uswsusp and hibernate-script, added the ususpend hook in mkinitcpio.conf just before filesystems, mkinitcpio -p kernel26 and after some configuration issued the command "hibernate" as root.

Thigs seemed to work, but after the screen turned off, it instantly turned on again and I was back in my desktop (I suppose the modules were loading again because my wifi card was reconnecting).

I rebooted, and then the mkinitcpio hook seemed to start working and restored my desktop, just where I was when I tried the "hibernate" command. Tried to reboot again, but the KDE reboot buttons didn't did anything. Seconds later, all the desktop hanged, and I had to force a cold reboot.

After that, every time I try to boot, both with the "Archlinux" and the "Archlinux Fallback" entries in Grub, I get a really nasty kernel panic.

I tried to load a LiveCD, delete ususpend from the hooks array and rebuild the initcpio image, but nothing seems to hange.

My system is updated to the present day, including stable kernel26.

I think I really fucked it up this time. Any idea?

RazZziel

Member

From: Spain

Registered: 2007-07-13

Posts: 36

Re: Arch won't boot after trying ususepnd

Tried to boot again, and a different message:

cu3edweb

Member

From: USA

Registered: 2007-10-07

Posts: 291

Re: Arch won't boot after trying ususepnd

The hook I believe should be 'uresume'

not 'ususpend'

RazZziel

Member

From: Spain

Registered: 2007-07-13

Posts: 36

Re: Arch won't boot after trying ususepnd

Uh, meh, exactly, I tried uresume, not ususpend

Not my best day.

RazZziel

Member

From: Spain

Registered: 2007-07-13

Posts: 36

Re: Arch won't boot after trying ususepnd

Heh, posting from Archlinux LiveCD.

I was trying to check what happened in a chroot, and I realized that every now and then I couldn't access directories I normally can access even from chroot, like some subdirectories of /var. When I tried to read some files the console threw "Permission denied" and "IO Error" errors. However, the majority of the filesystem seems to be accesible.

I'm performing a reiserfsck on my root partition, and the things seems to be quite screwd up. I'm getting "block ******: The level of the node (******) is not correct, (1) expected the problem in the internal node occurred  (******), whole subtree skipped". Does this have fix :\?

What do you think could have caused theese issues? Failed hibernation? Just the cold reboots?

RazZziel

Member

From: Spain

Registered: 2007-07-13

Posts: 36

Re: Arch won't boot after trying ususepnd

Heh, funny, after a reiserfsck --rebuild-tree, my system is back, but with an empty /var/lib/pacman :\ I had to reinstall everything by hand to try to "re-sync" the pacman database.