Linux partition not recognized (damaged?) after hibernating

Bug #219687 reported by MariuszS
This bug report is a duplicate of:  Bug #203537: Hardy -- Suspend RUINS FILESYSTEM. Edit Remove
2
Affects Status Importance Assigned to Milestone
hibernate (Ubuntu)
New
Undecided
Unassigned

Bug Description

After hibernating and turning on ubuntu 8.04 RC I have grub error 17. I have Windows Vista SP1 installed and now both systems are inaccessible.

After booting from live cd I saw problem with linux root partition, I cant mount this partition (sudo mount /dev/sda5 /mnt/linux -t ext3)
[ 381.104304] VFS: Can't find ext3 filesystem on dev sda5.

cfdisk still printed this partition like "Linux"

Before hibernating I have installed latest patches by system update.

What is wrong?

Hardware: Toshiba Satellite A215-S7422 (more info on UbuntuLaptopTesting, this happen when I try to describe this laptop on this page ;) )

MariuszS (mariuszs)
description: updated
Revision history for this message
MariuszS (mariuszs) wrote :

Additional information (important):

System was hibernated without problem, but when turned on I have black screen. I wait some times, clicked buttons etc but this not work. I make hard turn off, and after this I receive Grub 17.

I have restored linux partition with fsck.ext3 /dev/sda5 (many errors).

Revision history for this message
MariuszS (mariuszs) wrote :

I think, if this bug report is not useful for hibernate maintainer, theb should be closed.

Maybe information about repairing linux partition when grub error 17 happens is useful.

Revision history for this message
MariuszS (mariuszs) wrote :

I try second hibernate, and now I have blank screen after wake up. I make hard turn off when was no disk activity (hdd led was off). I have grub error 17 and system dead.

When linux partition was repaired I have this error:
root@ubuntu:~# fsck.ext3 -p /dev/sda5
fsck.ext3: Bad magic number in super-block while trying to open /dev/sda5
/dev/sda5:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

but manual e2fsck.ext3 work nice (with many questions :()

fsck.ext3: Superblock invalid, trying backup blocks...
Superblock has an invalid ext3 journal (inode 8).

/dev/sda5 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Journal inode is not in use, but contains data.

Revision history for this message
MariuszS (mariuszs) wrote :

Is good to say, that after this second hibernate/repair home folder was destroyed and many files (from /etc for example) are missed. I think ubuntu is unusable...

Revision history for this message
MariuszS (mariuszs) wrote :

I have antoher big mistake, I press Fn+F3 and this is Standby mode (sleep mode), so this is not related to hibernate mode! Sorry for this.

Revision history for this message
hazelnutz18 (stevemhazel) wrote :

I have the same problem - I put my machine on suspend - when I went to wake it up it failed to do so. I did a hard reboot and during boot I got the following error

"GRUB loading, please wait....
Error 17"

I have 2 HD'a - 1 IDE and 1 SATA. UBUNTU was on the SATA HD while WinXP was on the IDE.

I've tried everything I can think of to boot either OS - using the BIOS to change boot sequence - SGD to fix GRUB - the Ubuntu Live CD to edit menu.lst.

Finally I used Gpartitioner to see if the drives were still recognized. I found out that the partition that Ubuntu was on is still present but there is no information available for it (no size used vs. size available etc.) The partitioner didn't even know how the partition was formatted (though I know it wax ext3). So far I have been unable to fix this error or recover my files on that partition.

Desktop AMD AthalonX2-64 - MSI K9A2 motherboard - ATI Radeon 2600HD GPU

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.