I O Error Reading Swsusp Image

As far as the files I restored and how they might relate to swsusp, I have no idea. Also, bootin single user mode or even with init=/bin/bash (and then "mount -oremount,rw /") and purge any package related to swsusp ("apt-cachesearch swsusp" gives me only the package uswsusp). But then I did an update and upgrade, and now I am > > getting the same swsusp error I had before and can't boot! > > check in the bootloader prompt the kernel command line. Are you sure that the files you restored arenot responsable for the apparence of swsusp in the boot process?Yes, I'm sure mondorestore doesn't change the partitions (not usingthe nuke option, just restoring files, and I've done that part beforesuccessfully).Post by NN_il_ConfusionarioPost by w***@gmail.comthat point.

We want + * them synced (in case something goes wrong) but we DO not want to mark + * filesystem clean: it is not. (And it does not matter, if we resume + * correctly, we'll mark system clean, anyway.) + */ +int swsusp_write(void) +{ + int error; + + if ((error = swsusp_swap_check())) { + printk(KERN_ERR "swsusp: cannot find swap device, try swapon -a.\n"); + return error; + } + lock_swapdevices(); + error = write_suspend_image(); + /* This will unlock ignored swap devices since writing is finished */ + lock_swapdevices(); + return error; +} + +/** + * Using bio to read from swap. + * This code requires a bit more work than just using buffer heads + * but, it is the recommended way for 2.5/2.6. + * The following are to signal the beginning and end of I/O. The partition table is definately messed up. for devfs] - * and they'll be considered the same device. As far as the files I restored and how they might relate toswsusp, I have no idea.

w***@gmail.com 2008-05-04 17:16:42 UTC PermalinkRaw Message Post by NN_il_ConfusionarioPost by w***@gmail.comI did a fresh etch install, then restored somemondo backup files using mondorestore.I do not use mondo; so I ask: are you sure that mondorestore does notchange the partition table? If all seems to fail,boot with a live cd (or the debian installation cd in rescue mode),mount your disk, chroot where the disc is mounted, purge uswsusp, editthe boot loader configuration (possibly menu.lst in /boot/grub/, but itdepends upon your boot loader), reinstall the kernel (to recreate theinitrd) and the boot loaderThere is absolutely NO need to reinstall once again (unless you haveseverely messed up your partition table and filesysetems, or things likethat).--Chi usa software non libero avvelena anche te. Tutty 2008-05-04 01:41:10 UTC PermalinkRaw Message Post by w***@gmail.comHelp! If there issomething related to resuming a suspended session, delete it.